terminal

Abstract

To provide a terminal, a base station, a wireless communication system, and a wireless communication method that appropriately select a valid RO (Random Access Opportunity) for a non-SBFD (subband non-overlapping full duplex) symbol when a legacy RACH (Random Access Channel) setting and a RACH setting for SBFD (subband non-overlapping full duplex) are assumed.SOLUTION: In a wireless communication system, a terminal 200 includes a communication unit that communicates with a cell to which a duplex duplexing scheme is applied, which is capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band, and a control unit that determines whether or not to select an RO on the basis of a second RACH setting that assumes the duplex duplexing scheme in a first symbol that does not assume the duplex duplexing scheme.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support subband non-overlapping full duplex (SBFD). [Background technology]

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

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

[0004] Furthermore, support for random access (RA) in SBFD is being considered for Release 19 (Non-Patent Document 1). Specifically, it is being considered to extend the configuration (RACH configuration) related to the random access channel (RACH) to the SBFD symbol.

[0005] A terminal (hereinafter also referred to as a user equipment (UE)) determines a random access opportunity (RO) for transmitting a preamble to start a random access (RA) based on a RACH configuration from a base station (hereinafter also referred to as a gNodeB (gNB)), and further determines a valid RO (and an invalid RO) from the determined ROs. Furthermore, the valid RO is mapped to an index of a synchronization signal block (SSB index) based on SSB-to-RO mapping. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 Summary of the Invention [Problem to be solved by the invention]

[0007] Incidentally, in addition to the RACH configuration that does not assume SBFD (hereinafter, legacy RACH configuration), it is expected that a RACH configuration that assumes SBFD (hereinafter, RACH configuration for SBFD) will be introduced.

[0008] Under such circumstances, the inventors have conducted extensive research and found that it is necessary to clarify whether or not the RACH setting for SBFD is valid for non-SBFD symbols.

[0009] Therefore, an object of the present disclosure is to provide a terminal, a base station, a wireless communication system, and a wireless communication method that can appropriately select a valid RO for a non-SBFD symbol when a legacy RACH setting and a RACH setting for SBFD are assumed. [Means for solving the problem]

[0010] The disclosed aspect is a terminal including: a communication unit that communicates with a cell to which a duplexing method is applied that can perform simultaneous communication of uplink signals and downlink signals within a time division duplex band; and a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplexing method based on a second random access channel setting that assumes the duplexing method.

[0011] The disclosed aspect is a base station including: a communication unit that communicates with a terminal via a duplex cell that can perform simultaneous communication of uplink signals and downlink signals within a time division duplex band; and a control unit that assumes that the terminal decides whether to select the random access opportunity based on a second random access channel setting that assumes the duplex mode in a first symbol that does not assume the duplex mode.

[0012] An aspect of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a communication unit that communicates with a cell to which a duplexing method is applied that can perform simultaneous communication of uplink signals and downlink signals within a time division duplex band, and a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplexing method based on a second random access channel setting that assumes the duplexing method.

[0013] The disclosed aspect is a wireless communication method comprising: a step of communicating with a cell to which a duplexing method capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band is applied; and a step of determining whether to select the random access opportunity in a first symbol that does not assume the duplexing method based on a second random access channel setting that assumes the duplexing method. [Brief explanation of the drawings]

[0014] [Figure 1]FIG. 1 is a diagram showing the overall configuration of a wireless communication system. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in wireless communication systems. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, a slot, and a symbol used in a radio communication system. [Figure 4] FIG. 4 is a functional block diagram of the terminal. [Figure 5] FIG. 5 is a functional block diagram of the base station. [Figure 6] FIG. 6 is a diagram illustrating an example of SBFD slots / symbols. [Figure 7] FIG. 7 is a diagram illustrating an example of application of the extended rule for determining a valid RO. [Figure 8] FIG. 8 is a diagram illustrating an example of application of the extended rule for determining a valid RO. [Figure 9] FIG. 9 is a diagram illustrating an example of application of the extended rule for determining a valid RO. [Figure 10] FIG. 10 is a diagram illustrating an example of application of the extended rule for determining a valid RO. [Figure 11] FIG. 11 is a diagram illustrating an example of application of the extended rule for determining a valid RO. [Figure 12] FIG. 12 is a diagram showing an example of SSB-RO mapping when the extended rule for determining valid ROs is applied. [Figure 13] FIG. 13 is a diagram showing an example of SSB-RO mapping when the extended rule for determining valid ROs is applied. [Figure 14] FIG. 14 is a diagram showing an example of SSB-RO mapping when the extended rule for determining valid ROs is applied. [Figure 15] FIG. 15 is a diagram showing an example of SSB-RO mapping when the extended rule for determining valid ROs is applied. [Figure 16] FIG. 16 is a diagram illustrating an example of application of RACH repetition in SBFD symbols. [Figure 17] FIG. 17 is a diagram illustrating the fifth operation example. [Figure 18] FIG. 18 is a diagram illustrating the fifth operation example. [Figure 19] FIG. 19 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 20] FIG. 20 is a diagram illustrating an example of the configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

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

[0016] (1) Wireless communication system configuration 1 is a wireless communication system conforming to a scheme called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0017] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) as a bundle, and Dual Connectivity (DC), which communicates simultaneously with two base stations.

[0018] As shown in FIG. 1, a wireless communication system 10 includes a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) constituting a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as a 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 multiple network functions (NFs). The NFs are, for example, an access and mobility management function (AMF) and a 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. The NG-RAN 20 and the CN may be simply referred to as a "network."

[0019] The gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration having a distributed unit (DU) having a function for connecting to the UE200 and a central unit (CU) having a function for connecting to the network. In this case, the gNB100 may be read as a DU, a CU, or a DU and a CU. When read as a DU, the gNB100 may be called a gNB-DU. When read as a CU, the gNB100 may be called a gNB-CU. When read as a DU and a CU, the DU portion may be called a gNB-DU and the CU portion may be called a gNB-CU.

[0020] Furthermore, the wireless communication system 10 may support a plurality of frequency ranges (FRs). That is, as shown in FIG. 2, the wireless communication system 10 may support the following FRs:

[0021] FR1: 410MHz~7.125GHz FR2-1: 24.25GHz~52.6GHz ·FR2-2: More than 52.6GHz~71GHz In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used, and in FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0022] 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.

[0023] 3, one slot in the wireless communication system 10 is made up of 14 symbols. If this configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the SCS is not limited to the frequencies shown in FIG. 3, and may be, for example, 480 kHz, 960 kHz, or other frequencies.

[0024] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14, but may be, for example, 28 or 56. Furthermore, the number of slots per subframe may differ depending on the SCS.

[0025] (2) Functional block configuration of wireless communication system (2.1) Functional block configuration of the terminal As shown in FIG. 4, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0026] The radio signal transceiver 210 transmits and receives radio signals to and from the gNB 100. The radio signal transceiver 210 may be configured with a transmitter that transmits radio signals to the gNB 100 and a receiver that receives radio signals from the gNB 100. The radio signals may include data or may be interpreted as data. Transmission may be interpreted as report, notification, etc. Reception may be interpreted as setting (is set), instruction (is given), notification (is given), etc. Note that setting may be realized by configuration information (information element (IE)) of the radio resource control (RRC) layer, and instruction may be realized by a control element (CE) or downlink control information (DCI) of the medium access control (MAC) layer.

[0027] The radio signal transmitting and receiving unit 210 of the embodiment can execute random access (RA) to the gNB 100. Specifically, the radio signal transmitting and receiving unit 210 can transmit a preamble (Msg1) to the gNB 100. The RA may be a four-step random access using Msg1 to Msg4 (and a HARQ-ACK PUCCH for Msg4), or a two-step random access using MsgA and MsgB.

[0028] The radio signal transceiver 210 of the embodiment can transmit a preamble for starting random access at a valid random access opportunity. The random access opportunity may be interpreted as a timing for transmitting a preamble for starting an RA. The random access opportunity may also be referred to as a RACH Occasion (RO). The RO is set based on the RACH setting from the gNB 100. For details about a valid RO, see the description of the control unit 270.

[0029] The amplifier unit 220 is configured by a power amplifier (PA) / low noise amplifier (LNA), etc. The amplifier unit 220 amplifies the radio signal output from the radio signal transmitting / receiving unit 210. The amplifier unit 220 also amplifies the radio signal output from the modulation / demodulation unit 230.

[0030] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100 or another gNB100). CP-OFDM / DFT-S-OFDM may be applied to the modem unit 230. Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0031] The control signal / reference signal processing unit 240 performs processing related to control signals transmitted and received between the gNB 100, such as radio resource control (RRC) signaling.

[0032] The control signal / reference signal processing unit 240 performs processing related to reference signals transmitted and received between the gNB 100, such as 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).

[0033] The channels include control channels and data channels. The control channels include a physical uplink control channel (PUCCH), a physical downlink control channel (PDCCH), a physical random access channel (PRACH), a physical broadcast channel (PBCH), etc. The data channels include a physical uplink shared channel (PUSCH), a physical downlink shared channel (PDSCH), etc.

[0034] The encoding / decoding unit 250 performs division / concatenation and coding / decoding of data contained in the radio signal for each predetermined communication destination (gNB100 or another gNB100).

[0035] Specifically, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data. In addition, the encoding / decoding unit 250 divides the data output from the data transmitter / receiver 260 into pieces of a predetermined size and performs coding on the divided data.

[0036] The data transmitter / receiver 260 assembles and disassembles data units (Protocol Data Units (PDUs) / Service Data Units (SDUs)) that make up data between each layer. The multiple layers include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, etc. The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0037] The control unit 270 controls the UE 200. The control unit 270 controls, for example, transmission and reception of radio signals by the radio signal transmission and reception unit 210, amplification by the amplifier unit 220, data modulation / demodulation by the modem unit 230, signal processing by the control signal and reference signal processing unit 240, coding / decoding by the encoding / decoding unit 250, and assembly / disassembly of data units by the data transmission and reception unit 260.

[0038] The control unit 270 of the embodiment can determine the above-mentioned valid RO and an invalid RO, which is an invalid RO, based on the RACH configuration from the gNB 100. Specifically, the control unit 270 determines an RO to transmit a preamble from among the ROs configured based on the RACH configuration from the gNB 100, and further determines a valid RO and an invalid RO from among the determined ROs. Please refer to the description of the operation example for rules for determining a valid RO.

[0039] The RACH configuration may include a legacy RACH configuration for a time unit (non-SBFD slot / symbol) to which time division duplexing (TDD) is applied, and a RACH configuration for SBFD for a time unit (SBFD slot / symbol) in which multiple subbands constituting a TDD band can be used. The legacy RACH configuration and the RACH configuration for SBFD may be configured in the UE 200 as one RACH configuration, or may be configured in the UE 200 as separate configurations. That is, if the UE 200 is a legacy UE, the legacy RACH configuration may be configured, and if the UE 200 is an SBFD-aware UE, the RACH configuration for SBFD may be configured.

[0040] When a legacy RACH configuration and a RACH configuration for SBFD are included in one RACH configuration, the control unit 270 according to the embodiment can determine a valid RO and an invalid RO in two stages. In this case, the control unit 270 first determines a valid RO and an invalid RO based on the legacy RACH configuration, and then determines an additional valid RO from the invalid RO based on the RACH configuration for SBFD.

[0041] On the other hand, the control unit 270 according to the embodiment may determine a valid RO and an invalid RO based on a RACH configuration for SBFD that is different from the legacy RACH configuration. In this case, the control unit 270 may ignore the legacy RACH configuration.

[0042] When the control unit 270 of the embodiment determines a valid RO and an invalid RO in two stages, it can map the index of the synchronization signal block (SSB) to the valid RO and the additional valid RO individually. Furthermore, when the control unit 270 of the embodiment determines a valid RO based on a RACH configuration for SBFD that is different from the legacy RACH configuration, it can map the index of the SSB to the valid RO. Note that mapping of the index of the SSB to the valid RO (or the additional valid RO) may be interpreted as mapping of the valid RO (or the additional valid RO) to the index of the SSB.

[0043] The control unit 270 of the embodiment may map the additional valid ROs based on the same mapping rule as that for mapping the valid ROs. For details about the mapping rule, see the description of the operation example.

[0044] The control unit 270 of the embodiment may map, to the additional valid RO, an SSB index that is the same as the SSB index mapped to the first valid RO after the additional valid RO. On the other hand, the control unit 270 of the embodiment may map, to the additional valid RO, an SSB index that is the same as the SSB index mapped to the last valid RO before the additional valid RO. Note that "after" / "before" may be interpreted as "after" / "before" between slots / symbols. Also, the first / last valid RO may be interpreted as a valid RO in the first / last slot / symbol (see FIG. 14).

[0045] (2.2) Base station functional block configuration As shown in FIG. 5, the gNB 100 includes a radio signal transceiver unit 110 and a control unit 120.

[0046] The radio signal transmitting / receiving unit 110 transmits and receives radio signals to and from the UE 200. The radio signal transmitting / receiving unit 110 may be configured with a transmitting unit that transmits radio signals to the UE 200 and a receiving unit that receives radio signals from the UE 200. The radio signals may include data or may be interpreted as data. Transmission may be interpreted as configuration, instruction, notification, etc. Reception may be interpreted as (reported), notification, etc. Note that configuration may be realized by configuration information (information element (IE)) of a radio resource control (RRC) layer, and instruction may be realized by a control element (CE) or downlink control information (DCI) of a medium access control (MAC) layer.

[0047] The radio signal transmitting and receiving unit 110 according to the embodiment can transmit an SSB to the UE 200 so that the UE 200 can map a valid RO in an RA.

[0048] The radio signal transceiver 110 according to the embodiment can transmit (configure) a RACH configuration to the UE 200. As described above, the RACH configuration may include a legacy RACH configuration for a time unit (non-SBFD slot / symbol) to which time division duplexing (TDD) is applied, and a RACH configuration for SBFD for a time unit (SBFD slot / symbol) in which multiple subbands constituting a TDD band can be used.

[0049] The radio signal transmitting and receiving unit 110 of the embodiment can transmit one RACH configuration including a legacy RACH configuration and a RACH configuration for SBFD to the UE 200. On the other hand, the radio signal transmitting and receiving unit 110 of the embodiment can transmit the legacy RACH configuration to a legacy UE and transmit the RACH configuration for SBFD to the UE 200 (SBFD-aware UE).

[0050] The control unit 120 controls the gNB 100. The control unit 120 controls, for example, the transmission and reception of radio signals by the radio signal transmission and reception unit 110. The control unit 120 also performs scheduling for the UE 200.

[0051] The control unit 120 can control handover (HO) of the UE 200. HO may be understood as, for example, transition of the UE 200 from the gNB 100 to which it is connected to another gNB 100. Note that the gNB 100 to which the UE 200 is connected in HO may be interpreted as a cell or beam formed by the gNB 100. HO may also be interpreted as a term such as cell transition, cell change, or beam change.

[0052] (3)SBFD As shown in Fig. 6, SBFD may be applied to each slot / symbol. Note that, in addition to DL and UL, each slot / symbol may be set to Flexible (FL) that can be used as DL or UL, and then SBFD may be applied.

[0053] SBFD is a type of (full-duplex) duplexing scheme based on time division duplexing (TDD), enabling simultaneous use of multiple sub-bands that make up the TDD band. SBFD can be described as a duplexing scheme in which multiple sub-bands are specified within the TDD band, a duplexing scheme in which UL and DL are allocated non-overlapping in the frequency direction within the TDD time unit, or full-duplex duplexing of sub-bands.

[0054] A slot / symbol to which SBFD is applied is also called an SBFD slot / symbol. "SBFD is applied" may be interpreted as SBFD being applied to at least a part of scheduling. In other words, "slot / symbol to which SBFD is applied" may be interpreted as a slot / symbol to which SBFD is applied in scheduling to which SBFD is applied (SBFD slot / symbol). Also, "time unit to which non-SBFD is applied" may be interpreted as a slot / symbol to which SBFD is not applied in scheduling to which SBFD is applied (non-SBFD slot / symbol).

[0055] As shown in Figure 6, DL or UL is assigned to each subband (SBFD subband) constituting the SBFD slot / symbol. Hereinafter, a subband to which DL is assigned is also referred to as a DL subband, and a subband to which UL is assigned is also referred to as a UL subband. In Figure 6, 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. Note that slots / symbols marked with "F" in other figures are FL slots / symbols.

[0056] Below is a brief explanation of the terms related to SBFD.

[0057] SBFD DL symbol: A symbol indicated in DL by tdd-UL-DL-Configuration Common or tdd-UL-DL-Configuration Dedicated, in which an SBFD subband is configured SBFD FL symbol: A symbol indicated by FL in tdd-UL-DL-Configuration Common or tdd-UL-DL-Configuration Dedicated, in which an SBFD subband is configured. SBFD SSB symbol: A symbol set for SSB reception, in which the SBFD subband is set Non-SBFD symbol: Symbol for which SBFD sub-band is not set

[0058] (4) Operation of the wireless communication system (4.1) Issues In a cell where SBFD-aware UEs and Legacy UEs coexist, when an RO is configured in the SBFD symbol commonly in the cell, there is a risk that the recognizable valid RO may differ between the SBFD-aware UE and the Legacy UE. For example, when an RO is configured in the UL subband of the SBFD symbol, the SBFD-aware UE recognizes (determines) the RO configured in the UL subband as a valid RO, but the Legacy UE recognizes (determines) the same RO as an RO configured in the DL symbol, i.e., as an invalid RO. Therefore, there has been a problem in that the numbering of SSB indices mapped to valid ROs is also recognized differently between the SBFD-aware UE and the Legacy UE.

[0059] (4.2) Extended rules for determining valid ROs The extended rules for determining a valid RO will be described with reference to Figures 7 to 11. Legacy rules for determining a valid RO will also be described. In the figures, Legacy UE refers to a UE that cannot recognize an SBFD symbol, and SBFD-aware UE refers to a UE that can recognize an SBFD symbol. For example, for an SBFD symbol that is set to a DL symbol or an FL symbol, Legacy UE regards it as a DL symbol or an FL symbol, and SBFD-aware UE regards it as an SBFD symbol.

[0060] The legacy rule for determining a valid RO is that an RO in an UL symbol (UL sub-band) or an FL symbol (not configured for SSB) as seen from the UE is considered a valid RO, and an RO in a DL symbol (DL sub-band) or an FL symbol (configured for SSB) as seen from the UE is considered an invalid RO.

[0061] The extended rule for determining a valid RO may be configured by the conditions for determining a valid RO shown below. Note that the extended rule for determining a valid RO is a rule for a cell in which SBFD operation is configured on the gNB side. Note that Cond-X in the figure corresponds to condition X.

[0062] Condition 1: Each symbol is a UL symbol Condition 2: FL symbols that are not set for SSB Condition 3: Each symbol is a UL symbol or a FL symbol that is not configured for SSB (non-SBFD). Condition 4: Each symbol is an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol). Condition 5: Each symbol is an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol) or an UL symbol (or an FL symbol not configured for SSB, or an FL symbol not configured for SSB (non-SBFD)). Condition 6: At least N_gap symbols must be left after the last (non-SBFD) DL symbol, and / or at least N_gap symbols must be left after the last (non-SBFD) SSB symbol, and / or no SSB symbols must precede any SSB symbols in the same PRACH slot. Condition 7: Do not overlap with both non-SBFD symbols (e.g., UL symbols or non-SBFD FL symbols) and SBFD symbols (e.g., SBFD DL symbols, and / or SBFD FL symbols, and / or SBFD SSB symbols). Condition 8: Do not overlap with non-SBFD DL symbols or (non-SBFD) SSB symbols Condition 9: SBFD symbols (e.g., SBFD DL symbols, and / or SBFD FL symbols, and / or SBFD SSB symbols) do not overlap with RBs outside the UL subband. That is, the valid ROs in the extended rules for determining valid ROs may include ROs that satisfy one or more combinations of these conditions. One or more combinations of the above conditions may be predefined in the standard or may be set by the gNB. For example, the valid ROs may include the following ROs:

[0063] Example 1: RO that satisfies condition 1 (determined as valid RO even under legacy rules) Example 2: RO that satisfies conditions 2 / 3 and 6 Example 2-1: If the description in parentheses regarding non-SBFD in condition 6 does not apply, it will be determined as a valid RO even under legacy rules. Example 2-2: If the description in parentheses regarding non-SBFD applies in Condition 6, it may be determined as an invalid RO under the legacy rules. This is because the conditions for determining a valid RO in this case are more relaxed.

[0064] Example 3: RO that satisfies conditions 2 / 3 and 9 (and 6) Example 4: RO that satisfies condition 4 (and condition 6) Example 5: RO that satisfies conditions 4 and 9 (and 6) Example 6: RO that satisfies condition 5 (and condition 6) Example 7: RO that satisfies conditions 5 and 9 (and 6) Example 8: RO that satisfies condition 7 (and at least one of conditions 6 / 8) Example 9: RO that satisfies conditions 7 and 9 (and at least one of conditions 6 and 8) 7 shows an example (Example A-1) in which SBFD is applied to DL symbols. An RO that satisfies condition 4 (and does not satisfy condition 9) and an RO that satisfies condition 1 are determined as valid ROs.

[0065] 8 shows an example (Example A-2) in which SBFD is applied to DL symbols. An RO that satisfies conditions 4 and 9 and an RO that satisfies condition 1 are determined as valid ROs.

[0066] 9 shows an example (Example B-1) in which SBFD is applied to DL symbols and FL symbols. An RO that satisfies condition 4 (and does not satisfy condition 9), an RO that satisfies condition 1, and an RO that satisfies conditions 3 and 6 are determined as valid ROs.

[0067] 10 shows an example (Example B-2) in which SBFD is applied to DL symbols and FL symbols. An RO that satisfies condition 4 (when the SBFD symbol in condition 4 does not include an SBFD FL symbol) and condition 9, an RO that satisfies condition 1, and an RO that satisfies conditions 3 and 6 are determined as valid ROs.

[0068] 11 shows an example (Example B-3) in which SBFD is applied to DL symbols and FL symbols. An RO that satisfies condition 4 (when the SBFD symbol in condition 4 includes an SBFD FL symbol) and condition 9, an RO that satisfies condition 1, and an RO that satisfies conditions 3 and 6 are determined as valid ROs.

[0069] (4.3) Example of operation An example of operation will be described based on the above-mentioned extended rules for determining valid ROs.

[0070] (4.3.1) Example 1 Operation example 1 will be described with reference to Fig. 12 to Fig. 15. Operation example 1 is an operation example in which a valid RO is determined for random access (RA) in RRC_IDLE mode or IN_ACTIVE mode, or for RA based on cell-common RACH configuration (or RACH configuration indicated in SIB1).

[0071] (4.3.1.1) Option 1 Option 1 is a combination of a legacy RACH configuration and a legacy rule for determining a valid RO. Note that the legacy RACH configuration may be understood as a RACH configuration for non-SBFD symbols, and a configuration for determining an RO for non-SBFD symbols in particular. On the other hand, a RACH configuration for SBFD symbols may be performed and an RO for SBFD symbols in particular may be determined based on the legacy RACH configuration.

[0072] In option 1, the UE 200 may operate as follows.

[0073] Step 1: Determine the RO based on the legacy RACH configuration.

[0074] Step 2: From the determined ROs, determine the valid ROs according to the legacy rules.

[0075] Step 3: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules.

[0076] ·Step 4: Transmit the selected preamble at the selected RO.

[0077] In Step 4 above, the following extensions are possible:

[0078] Example 1-1: The UE 200 does not assume that any symbol (or at least one symbol) of the determined valid RO (and the N_gap symbols before the valid RO) is an SBFD FL symbol.

[0079] Example 1-2: The UE 200 does not assume valid ROs that overlap with RBs outside the UL subband within the SBFD FL symbol.

[0080] Example 1-3: When the determined valid RO overlaps with the SBFD FL symbol, the UE 200 does not transmit a preamble in the valid RO.

[0081] Example 1-4: When a determined valid RO overlaps with an outer RB of the UL subband within the SBFD FL symbol, the UE 200 does not transmit a preamble in the valid RO.

[0082] Example 1-5: The UE 200 does not assume that the determined valid RO overlaps both a non-SBFD symbol (eg, a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (eg, an SBFD FL symbol).

[0083] Example 1-6: If the determined valid RO overlaps both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD FL symbol), the UE 200 does not transmit a preamble in the valid RO.

[0084] (4.3.1.2) Option 2 Option 2 combines the legacy RACH configuration with extended rules for determining valid ROs.

[0085] In option 2, the UE 200 may operate as follows.

[0086] Step 1: Determine the RO based on the legacy RACH configuration.

[0087] Step 2: From the determined RO, determine the valid RO by the extension rule.

[0088] Step 3: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules.

[0089] ·Step 4: Transmit the selected preamble at the selected RO.

[0090] In Step 2 described above, the extended rule for determining valid ROs described in (4.2) can be used. Note that when Example A-1 shown in FIG. 7 is applied, the determined valid ROs can overlap with RBs outside the UL subband in the SBFD symbol. In this case, the extension in Step 4 described below is required.

[0091] In Step 4 above, the following extensions are possible:

[0092] Example 2-1: The UE 200 does not assume valid ROs that overlap with RBs outside the UL subband in the SBFD DL symbol (and / or SBFD SSB symbol) (and / or SBFD FL symbol).

[0093] Example 2-2: When the determined valid RO overlaps with an SBFD DL symbol (and / or an SBFD SSB symbol) (and / or an SBFD FL symbol), the UE 200 does not transmit a preamble in the valid RO.

[0094] Example 2-3: UE200 does not assume that the determined valid RO overlaps both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol).

[0095] Example 2-4: If the determined valid RO overlaps with both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol), the UE 200 does not transmit a preamble in that valid RO.

[0096] As a result, in option 2, different SSB indices can be mapped to the same RO between legacy UEs and SBFD-aware UEs, as shown in FIG.

[0097] (4.3.1.3) Option 3 Option 3 combines legacy RACH configuration with legacy and extended rules for determining valid ROs.

[0098] In option 3, the UE 200 may operate as follows.

[0099] Step 1: Determine the RO based on the legacy RACH configuration.

[0100] Step 2A-1: From the determined ROs, determine a valid RO according to the legacy rules. This valid RO may be called a legacy-valid RO.

[0101] Step 2A-2: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules.

[0102] Step 2B-1: From the determined ROs (within the SBFD DL symbol (and / or SBFD SSB symbol) or overlapping with the SBFD DL symbol (and / or SBFD SSB symbol)), determine additional valid ROs according to the extension rule.

[0103] Step 2B-2: The determined additional valid ROs are mapped to SSB indices.

[0104] Step 3: Transmit the selected preamble at the selected RO.

[0105] In Step 2B-1 described above, for the RO determined as invalid in Step 2A-1, an additional valid RO can be determined using the extended rule for determining a valid RO described in (4.2). This additional valid RO may be called an SBFD-valid RO.

[0106] In the above-mentioned Step 2B-2, SBFD-valid ROs may be mapped to SSB indices separately from legacy-valid ROs. Alt-1 will be described below with reference to Fig. 13, and Alt-2 will be described with reference to Fig. 14.

[0107] Alt-1: As shown in Figure 13, legacy SSB-RO mapping rules are applied to map SBFD-valid ROs to SSB indices. That is, the number of SSB indices per RO and the number of preambles per SSB index or per RO are based on the parameters of the legacy RACH configuration. The mapping order is first, ascending order of preamble index, second, ascending order of frequency resource index, and third, ascending order of PRACH slot.

[0108] Alt-2: As shown in Figure 14, an SBFD-valid RO is mapped to the same SSB index as the last / first legacy-valid RO before / after the SBFD-valid RO of the same frequency resource index.

[0109] In Step 3 above, you can use the extension in Step 4 of Option 2.

[0110] Analysis: According to Option 3, valid ROs determined by legacy rules are commonly understood by legacy UEs and SBFD-aware UEs. In addition, additional valid ROs determined by extended rules are understood by SBFD-aware UEs. Also, compared to Option 4 described later, RACH configuration can be one of the legacy RACH configurations.

[0111] (4.3.1.4) Option 4 Option 4 combines an additional / separate RACH configuration (to the legacy RACH configuration) (hereinafter also referred to as the RACH configuration for SBFD) with an extended rule for determining a valid RO, as shown in Fig. 15. The RACH configuration for SBFD may be interpreted as a RACH configuration for SBFD symbols, and as a configuration that specifically determines an RO for the SBFD symbols. On the other hand, a RACH configuration for non-SBFD symbols may be configured, and an RO for non-SBFD symbols may be specifically determined, based on the RACH configuration for SBFD.

[0112] In option 4, the UE 200 may operate as follows.

[0113] Step 1A: Determine the RO based on the legacy RACH configuration.

[0114] Step 2A: From the determined ROs, determine the valid ROs according to the legacy rules.

[0115] Step 3A: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules.

[0116] Step 1B: Determine the RO based on the RACH configuration for SBFD.

[0117] Step 2B: Determine a valid RO according to the legacy rule from the RO determined based on the RACH configuration for SBFD.

[0118] Step 3B: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules.

[0119] ·Step 4: Transmit the selected preamble at the selected RO.

[0120] Note that since an SBFD-aware UE uses only the RACH configuration for SBFD, Steps 1A to 3A may be omitted.

[0121] In Step 1B described above, a RACH configuration for SBFD is configured or indicated as an additional / separate RACH configuration, and the UE determines the RO based on the RACH configuration for SBFD.

[0122] RACH configuration for SBFD may be configured in the following IE:

[0123] Alt-1: May be set in additionalRACH-ConfigList. For example, the corresponding feature combination may be for "SBFD".

[0124] Alt-2: May be set in BWP-UplinkCommon. For example, RACH-ConfigCommon-SBFD-r19 and / or additionalRACH-ConfigList-SBFD-r19 and / or msgA-ConfigCommon-sbfd-r19 may be set for SBFD. Alternatively, RACH-ConfigCommonTwoStepRA-sbfd-r19 in msgA-ConfigCommon may be set for SBFD.

[0125] Variation: It may be possible that the RACH configuration for SBFD can be supported for a given feature combination (e.g., Msg 1 / 3 repetitions and / or RedCap and / or SDT).

[0126] Furthermore, the following variations may be realized based on the RACH configuration for SBFD.

[0127] · Alt-a: Only ROs within SBFD symbols or ROs overlapping SBFD symbols are determined, and ROs within non-SBFD symbols or ROs overlapping non-SBFD symbols are excluded from the determination.

[0128] · Alt-b: RACH configuration does not assume that RO is within or overlaps with a non-SBFD symbol.

[0129] Alt-c: All ROs are determined by legacy rules, i.e., whether they occur within or overlap with SBFD symbols or within or overlap with non-SBFD symbols.

[0130] In Step 2B above, the extended rules for determining valid ROs described in (4.2) can be used.

[0131] In Step 4 above, you can use the extension of Step 4 of Option 2.

[0132] Analysis: In Option 4, the RACH configuration for SBFD is independent from the legacy RACH configuration, so it does not affect legacy UEs. Compared to Option 3, this consumes more resources for the RACH, but in return, it allows for more flexible configuration.

[0133] (4.3.2) Example 2 Operation example 2 will be described. Operation example 2 is an operation example in which a valid RO is determined for random access (RA) in RRC_IDLE mode or IN_ACTIVE mode, or for RA based on dedicated configuration (e.g., RA for BFR based on BeamFailureRecoveryConfig, and / or contention-free random access (CFRA) based on RACH-ConfigDedicated, and / or RA for SI-RequestConfig).

[0134] Note that an RA based on a common configuration (cell-common RACH configuration) and an RA based on a dedicated configuration differ in the following respects: That is, an RA based on a common configuration requires consideration of how a Legacy UE understands or interprets the configuration, whereas an RA based on a dedicated configuration does not require consideration of how a Legacy UE understands or interprets the configuration.

[0135] (4.3.2.1) Option 1 Based on the rach-ConfigBFR conventionally configured in BeamFailureRecoveryConfig and / or cfra conventionally configured in RACH-ConfigDedicated and / or rach-ConfigSI conventionally configured in SI-RequestConfig, an SBFD-aware UE always uses the extended rules for determining valid ROs as described in (4.2).

[0136] (4.3.2.2) Option 2 Whether or not to always use the extended rules for determining valid ROs described in (4.2) is configured by the gNB based on rach-ConfigBFR, which is conventionally configured in BeamFailureRecoveryConfig, and / or cfra, which is conventionally configured in RACH-ConfigDedicated, and / or rach-ConfigSI, which is conventionally configured in SI-RequestConfig.

[0137] (4.3.2.3) Option 3 Additional / separate configuration is performed to configure RACH resources for SBFD, and to determine a valid RO for the RACH resource configuration for SBFD, the UE uses the extended rules for determining a valid RO described in (4.2).

[0138] Example: BeamFailureRecoveryConfig-sbfd-r19 is set. Or, BeamFailureRecoveryConfig is set to rach-ConfigBFR-sbfd-r19. Example: RACH-ConfigDedicated-sbfd-r19 is set. Or, cfra-sbfd-r19 is set in RACH-ConfigDedicated. Or, occasions-sbfd-r19 is set in CFRA. Or, ConfigGeneric-sbfd-r19 is set in occasions of CFRA. And / or CFRA-TwoStep-sbfd-r19 is set in RACH-ConfigDedicated. Alternatively, occasionsTwoStepRA-sbfd-r19 is set in CFRA-TwoStep. Alternatively, ConfigGenericTwoStepRA-sbfd-r19 is set in occasionsTwoStepRA-sbfd-r19 of CFRA-TwoStep. As a variation, two mask index values ​​are set in CFRA or CFRA-TwoStep, for SBFD and non-SBFD.

[0139] Example: SI-RequestConfig-sbfd-r19 is set. Alternatively, rach-OccasionsSI-sbfd-r19 is set in SI-RequestConfig. Alternatively, rach-ConfigSI-sbfd-r19 is set in rach-OccasionsSI of SI-RequestConfig. As a variation, two mask index values ​​are set in SI-RequestResources, one for SBFD and one for non-SBFD.

[0140] (4.3.3) Example 3 Operation example 3 will be described. Operation example 3 supports MsgA PUSCH transmission in SBFD symbols in 2-step RA. Specifically, it determines valid MsgA PUSCH occasions in SBFD symbols.

[0141] In determining a valid MsgA PUSCH occasion in an SBFD symbol, the extended rule for determining a valid RO described in (4.2) can be used by replacing "RO" in the description of (4.2) with "MsgA PUSCH occasion."

[0142] In MsgA PUSCH transmission based on cell common configuration, the content of Operation Example 1 can be reused by replacing "RO" with "MsgA PUSCH occasion" and "RACH configuration" with "MsgA configuration (or MsgA PUSCH configuration)" in the description of Operation Example 1 (including the description of the extended rule for determining valid RO in (4.2)). Furthermore, in MsgA PUSCH transmission based on dedicated configuration, the content of Operation Example 2 can be reused by making similar replacements as appropriate.

[0143] The extended rule for determining a valid RO in (4.2) may be applied not only to a 4-step RACH but also to a 2-step RACH (all of the operation examples 1 to 3 are possible), or may be applied only to a 4-step RACH (only operation examples 1 and 2 are possible), or may be applied only to a 2-step RACH (only operation example 3 is possible).

[0144] (4.3.4) Example 4 Operation example 4 will be described with reference to Fig. 16. Operation example 4 relates to whether or not to support both setting / enabling PRACH repetitions in RA and indicating / setting the time / frequency domain location of the SBFD subband. Note that repetitions may be interpreted as repeated transmission, and PRACH repetitions may be interpreted as repeated transmission of the PRACH in RA.

[0145] (4.3.4.1) Option 1 Option 1 of operation example 4 supports the combination of setting / enabling PRACH repetitions in RA and indicating / setting the time / frequency domain location of the SBFD subband in SBFD. Based on this support, Option 1-1 and Option 1-2 are also possible.

[0146] (4.3.4.1.1) Option 1-1 Option 1-1 is to support PRACH repetitions in SBFD symbols and / or non-SBFD symbols.

[0147] Option 1-1A: In PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only valid ROs restricted within SBFD symbols, or only valid ROs restricted within non-SBFD symbols.

[0148] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only SBFD-valid ROs or only legacy-valid ROs. For the meaning of SBFD-valid ROs and legacy-valid ROs, see Option 3 in Operation Example 1.

[0149] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only valid ROs based on an additional RACH configuration for SBFD, or only valid ROs based on a legacy RACH configuration. For example, this may be used when an additional RACH configuration for SBFD is configured.

[0150] Option 1-1B: In PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of valid ROs in SBFD symbols or non-SBFD symbols.

[0151] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of SBFD-valid RO or legacy-valid RO. For the meaning of SBFD-valid RO and legacy-valid RO, see Option 3 in Operation Example 1.

[0152] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions includes a valid RO based on an additional RACH configuration for SBFD or a valid RO based on a legacy RACH configuration. For example, this may be used when an additional RACH configuration for SBFD is configured.

[0153] (4.3.4.1.2) Option 1-2 Option 1-2 does not support PRACH repetitions in SBFD symbols, but supports PRACH repetitions in non-SBFD symbols.

[0154] In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only valid ROs that are restricted within non-SBFD symbols.

[0155] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only legacy-valid ROs. For the meaning of legacy-valid ROs, see option 3 in operation example 1.

[0156] Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of only valid ROs based on the legacy RACH configuration. For example, this may be used when an additional RACH configuration for SBFD is configured.

[0157] (4.3.4.1.3) Variation Which option to apply may be predefined by the standard or may be configured / instructed by the gNB.

[0158] (4.3.4.1.4) Analysis Option 1 makes more UL resources available for PRACH repetitions, which is beneficial for PRACH coverage.

[0159] (4.3.4.2) Option 2 Option 2 of operation example 4 does not support the combination of configuring / enabling PRACH repetitions in RA and indicating / configuring the time / frequency domain location of the SBFD subband. In this case, the UE does not expect that the time / frequency domain location of the SBFD subband is provided at the same time as configuring / enabling PRACH repetitions (Msg1 repetitions).

[0160] Finally, with reference to FIG. 16, Option 1 (Option 1-1A, Option 1-1B, and Option 1-2) will be described.

[0161] As shown in FIG. 16, in Option 1-1A, the RO group (i.e., a set of valid PRACH occasions) for four PRACH repetitions may be {RO#a-0, RO#a-1, RO#a-2, RO#a-3}, or {RO#a-4, RO#a-5, RO#a-6, RO#a-7}, or {RO#a-8, RO#a-9, RO#a-10, RO#a-11}, or {RO#b-0, RO#b-1, RO#b-2, RO#b-3}.

[0162] As shown in FIG. 16, in option 1-1B, the RO group (i.e., a set of valid PRACH occasions) for four PRACH repetitions may be {RO#a-0, RO#a-1, RO#a-2, RO#b-0}, or {RO#a-3, RO#a-4, RO#a-5, RO#b-1}, or {RO#a-6, RO#a-7, RO#a-8, RO#b-2}, or {RO#a-9, RO#a-10, RO#a-11, RO#b-3}.

[0163] As shown in FIG. 16, in option 1-2, the RO group (i.e., a set of valid PRACH occasions) for four PRACH repetitions may be {RO#b-0, RO#b-1, RO#b-2, RO#b-3}.

[0164] (4.3.5) Example 5 (4.3.5.1) Issues After careful consideration, the inventors have found that there may be cases in which the time resource of the RO is determined in the SBFD symbol to which SBFD is applied, and that in such cases, it is necessary to clarify the mechanism for determining the time resource of the RO.

[0165] In particular, it is necessary to clarify how the tables used to identify the time resources of the RO when SBFD is not assumed (hereinafter referred to as legacy tables) should be supplemented when SBFD is assumed. For example, the legacy tables may be Table 6.3.3.2-3 (FR1) or Table 6.3.3.2-3 (FR2) specified in 3GPP TS38.211.

[0166] To solve this problem, UE200 determines the time resource of a random access opportunity (RO) based on parameters assuming a duplexing method (SBFD) that allows simultaneous use of multiple subbands in a time unit to which time division duplexing (TDD) is applied.

[0167] (4.3.5.2) Example 5-1 In Operation Example 5-1, the parameter assuming SBFD may be a parameter associated with an existing index included in a table (legacy table) used to identify the time resource of the RO in the case where SBFD is not assumed. The existing index may be a PRACH Configuration Index. In other words, the parameter assuming SBFD may be a parameter represented by a column newly added to the legacy table. The following options are considered for Operation Example 5-1.

[0168] In Option 5-1-1, the parameter assuming SBFD may be an offset to the subframe number or an offset to the slot number. For example, the parameter assuming SBFD may be an offset to the subframe number represented by a new column added to Table 6.3.3.2-3 (FR1) specified in 3GPP TS38.211. The parameter assuming SBFD may be an offset to the slot number represented by a new column added to Table 6.3.3.2-4 (FR2) specified in 3GPP TS38.211.

[0169] For example, for the PRACH configuration index, the newly added column provides K_offset, which is the offset for the subframe number {S_1, .., S_n} stored in the column included in the legacy table (FR1). For the PRACH configuration index, the newly added column provides K_offset, which is the offset for the slot number {S_1, .., S_n} stored in the column included in the legacy table (FR2).

[0170] Under this assumption, when a PRACH configuration index is configured by the RACH configuration for SBFD (additional / individual RACH configuration), the UE 200 determines the subframe number or slot number of the PRACH in accordance with one of the following: The subframe number or slot number of the PRACH is an example of a time resource of the RO.

[0171] ·{S_1 + K_offset, .., S_n + K_offset} ·{(S_1 + K_offset) mod N, .., (S_n + K_offset) mod N}, (where N is defined by specification, eg N=10) ·{S_1 - K_offset, .., S_n - K_offset} ·{(S_1 - K_offset) mod N, .., (S_n - K_offset) mod N}, (where N is defined by specification, eg N=10) For example, taking Table 6.3.3.2-3 (FR1), the parameter assuming SBFD is the offset to the subframe number included in the legacy table, as shown in option 5-1-1 in Figure 17. The values ​​provided or defined in the new columns in option 5-1-1 in Figure 17 are only examples.

[0172] In Option 5-1-2, the parameter assuming SBFD may be a subframe number or a slot number. For example, the parameter assuming SBFD may be a subframe number represented by a new column added to Table 6.3.3.2-3 (FR1) specified in 3GPP TS38.211. The subframe number may contain a value different from the subframe number stored in the column included in the legacy table. The parameter assuming SBFD may be a slot number represented by a new column added to Table 6.3.3.2-4 (FR2) specified in 3GPP TS38.211. The slot number may contain a value different from the slot number stored in the column included in the legacy table.

[0173] For example, for the PRACH configuration index, the newly added column provides {K_1, .., K_n}, which may contain values ​​different from the subframe numbers {S_1, .., S_n} stored in the column included in the legacy table (FR1). For the PRACH configuration index, the newly added column provides {K_1, .., K_n}, which may contain values ​​different from the slot numbers {S_1, .., S_n} stored in the column included in the legacy table (FR2).

[0174] For example, in Table 6.3.3.2-3 (FR1), the parameter assuming SBFD is the subframe number defined separately from the subframe number included in the legacy table, as shown in option 5-1-2 in Figure 17. The values ​​provided or defined in the new column in option 5-1-2 in Figure 17 are only examples.

[0175] In the operation example 5-1, the values ​​of the new column may be values ​​corresponding to all of the PRACH configuration indexes included in the legacy table, or may be values ​​corresponding to some of the PRACH configuration indexes included in the legacy table.

[0176] In the operation example 5-1, the values ​​provided or defined in the new column along with the PRACH configuration index may be different between the table for FR1 and the table for FR2.

[0177] (4.3.5.3) Example 5-2 In operation example 5-2, parameters assuming SBFD are set or indicated by the random access channel configuration. The random access channel configuration may be a RACH configuration for SBFD (an additional / separate RACH configuration). That is, in operation example 5-2, parameters assuming SBFD are not newly added rows to the legacy table as in operation example 5-1, but are parameters set or indicated by the RACH configuration for SBFD. The following options are possible for operation example 5-2.

[0178] In Option 5-2-1, the parameter assuming SBFD may be an offset relative to the subframe number or an offset relative to the slot number. For example, the parameter assuming SBFD may be an offset that complements Table 6.3.3.2-3 (FR1) specified in 3GPP TS38.211. The parameter assuming SBFD may be an offset that complements Table 6.3.3.2-4 (FR2) specified in 3GPP TS38.211.

[0179] For example, for a PRACH configuration index, the RACH configuration for SBFD provides K_offset, which is an offset for the subframe number {S_1, .., S_n} stored in a column included in the legacy table (FR1). For a PRACH configuration index, the RACH configuration for SBFD provides K_offset, which is an offset for the slot number {S_1, .., S_n} stored in a column included in the legacy table (FR2).

[0180] Under this assumption, when a PRACH configuration index is configured by the RACH configuration for SBFD (additional / individual RACH configuration), the UE 200 determines the subframe number or slot number of the PRACH in accordance with one of the following: The subframe number or slot number of the PRACH is an example of a time resource of the RO.

[0181] ·{S_1 + K_offset, .., S_n + K_offset} ·{(S_1 + K_offset) mod N, .., (S_n + K_offset) mod N}, (where N is defined by specification, eg N=10) ·{S_1 - K_offset, .., S_n - K_offset} ·{(S_1 - K_offset) mod N, .., (S_n - K_offset) mod N}, (where N is defined by specification, eg N=10) In Option 5-2-2, the parameter assuming SBFD may be a subframe number or a slot number. For example, the parameter assuming SBFD may be a subframe number that complements Table 6.3.3.2-3 (FR1) specified in 3GPP TS38.211. The subframe number configured or indicated by the RACH configuration for SBFD may include a value different from the subframe number stored in a column included in the legacy table. The parameter assuming SBFD may be a slot number represented by a new column added to Table 6.3.3.2-4 (FR2) specified in 3GPP TS38.211. The slot number configured or indicated by the RACH configuration for SBFD may include a value different from the slot number stored in a column included in the legacy table.

[0182] For example, for the PRACH configuration index, the RACH configuration for SBFD provides {K_1, .., K_n}, where {K_1, .., K_n} may include a value different from the subframe number {S_1, .., S_n} stored in the column included in the legacy table (FR1). For the PRACH configuration index, the RACH configuration for SBFD provides {K_1, .., K_n}, where {K_1, .., K_n} may include a value different from the slot number {S_1, .., S_n} stored in the column included in the legacy table (FR2).

[0183] In operation example 5-2, the values ​​set or indicated by the RACH configuration for SBFD may be values ​​corresponding to all of the PRACH configuration indices included in the legacy table, may be values ​​corresponding to each of the PRACH configuration indices included in the legacy table, or may be values ​​corresponding to any of the PRACH configuration indices included in the legacy table. Alternatively, UE 200 may assume that parameters assuming SBFD are set or indicated for a certain range of PRACH configuration indices among the PRACH configuration indices included in the legacy table.

[0184] (4.3.5.4) Example 5-3 In Operation Example 5-3, the parameter assuming SBFD is a parameter associated with a new index newly added to a table (legacy table) used to identify the time resource of the RO in the case where SBFD is not assumed. The new index may be a PRACH Configuration Index. In other words, the parameter assuming SBFD may be an entry newly added to the legacy table (hereinafter referred to as a new entry). The following options are considered for Operation Example 5-3.

[0185] Option 5-3-1 explains the new entry for Table 6.3.3.2-3 (FR1) specified in 3GPP TS38.211.

[0186] In Alternative 5-3-1-1, the new entry may include a PRACH format. The PRACH format of the new entry may include one or more values ​​selected from PRACH format 0, PRACH format 1, PRACH format 2, PRACH format A1, PRACH format A2, PRACH format A3, PRACH format B1, PRACH format B4, PRACH format C0, PRACH format C2, PRACH format A1 / B1, PRACH format A2 / B2, and PRACH format A3 / B3.

[0187] In Alt. 5-3-1-2, the new entry may include Values ​​of (x, y). The x value of the new entry may include one or more values ​​selected from 16, 8, 4, 2, and 1. The y value of the new entry may include one or more values ​​selected from 0 and 1.

[0188] In Alt. 5-3-1-3, the new entry may include a subframe number. To configure RO in an SBFD DL slot taking into account a typical TDD UL-DL configuration, the new entry preferably includes the subframe number. For SBFD RACH configuration, there is no need to configure RO in an UL slot / subframe. The subframe number in the new entry may include one or more values ​​selected from 0, 1, 2, 3, 4, 5, 6, and 8.

[0189] For example, for a new entry in PRACH format 1, the subframe number may be {0}, {1}, {2}, {3}, {4}, {5}, or {6}. For example, for a new entry in PRACH format 1, the subframe number may be {0}, {1}, {2}, {3}, {4}, or {5}. Note that for other PRACH formats, various combinations or possibilities may exist.

[0190] In Alt. 5-3-1-4, a new entry may include a Starting symbol. The Starting symbol of a new entry may include one or more values ​​selected from 0, 2, 6, 7, and 8.

[0191] In Alternative 5-3-1-5, the new entry may include the number of PRACH slots within a subframe. For new entries of PRACH formats A1, A2, A3, B1, B4, C0, C2, A1 / B1, A2 / B2, and A3 / B3, the number of PRACH slots within a subframe may include one or more values ​​selected from 1 and 2.

[0192] In Alternative 5-3-1-6, the new entry may include the number of time-domain PRACH occasions within a PRACH slot. For new entries of PRACH formats A1, A2, A3, B1, B4, C0, C2, A1 / B1, A2 / B2, and A3 / B3, the number of time-domain PRACH occasions within a PRACH slot may include one or more values ​​selected from 1, 2, 3, 6, and 7.

[0193] In Alt. 5-3-1-7, the new entry may include the PRACH duration. For a new entry of PRACH formats A1, A1 / B1, or B1, the PRACH duration may be 2. For a new entry of PRACH formats A2 or A2 / B2, the PRACH duration may be 4. For a new entry of PRACH formats A3 or A3 / B3, the PRACH duration may be 6. For a new entry of PRACH format B4, the PRACH duration may be 12. For a new entry of PRACH format C0, the PRACH duration may be 2. For a new entry of PRACH format C2, the PRACH duration may be 6.

[0194] For example, in Table 6.3.3.2-3(FR1), the parameters assuming SBFD are a new entry associated with a new index (PRACH configuration index) as shown in Figure 18. The new entry may include the PRACH format, Values ​​of (x, y), Subframe number, Starting symbol, Number of PRACH slots within a subframe, Number of time-domain PRACH occasions within a PRACH slot, PRACH duration, etc.

[0195] Option 5-3-2 explains the new entry for Table 6.3.3.2-4 (FR2) specified in 3GPP TS38.211.

[0196] In Alternative 5-3-2-1, the new entry may include a PRACH format. The PRACH format of the new entry may include one or more values ​​selected from PRACH format A1, PRACH format A2, PRACH format A3, PRACH format B1, PRACH format B4, PRACH format C0, PRACH format C2, PRACH format A1 / B1, PRACH format A2 / B2, and PRACH format A3 / B3.

[0197] In Alt. 5-3-2-2, the new entry may include Values ​​of (x, y). The x value of the new entry may include one or more values ​​selected from 16, 8, 4, 2, and 1. The y value of the new entry may include one or more values ​​selected from 0 and 1.

[0198] In Alt. 5-3-2-3, the new entry may include a slot number. The slot number of the new entry may include an integer of 1 or greater selected from 0-39.

[0199] In Alt. 5-3-2-4, a new entry may include a Starting symbol. The Starting symbol of a new entry may include one or more values ​​selected from 0, 2, 6, 7, and 8.

[0200] In Alternative 5-3-2-5, the new entry may include the number of PRACH slots within a 60 kHz slot. The number of PRACH slots within a 60 kHz slot of the new entry may include one or more values ​​selected from 1 and 2.

[0201] In Alternative 5-3-2-6, the new entry may include the number of time-domain PRACH occasions within a PRACH slot. The number of time-domain PRACH occasions within a PRACH slot of the new entry may include one or more values ​​selected from 1, 2, 3, 6, and 7.

[0202] In Alt. 5-3-2-7, the new entry may include the PRACH duration. For a new entry of PRACH formats A1, A1 / B1, or B1, the PRACH duration may be 2. For a new entry of PRACH formats A2 or A2 / B2, the PRACH duration may be 4. For a new entry of PRACH formats A3 or A3 / B3, the PRACH duration may be 6. For a new entry of PRACH format B4, the PRACH duration may be 12. For a new entry of PRACH format C0, the PRACH duration may be 2. For a new entry of PRACH format C2, the PRACH duration may be 6.

[0203] (4.3.5.5) Example 5-4 In Operation Example 5-4, an index associated with a parameter assuming SBFD is provided by a random access channel configuration. The random access channel configuration may be a RACH configuration for SBFD (an additional / separate RACH configuration). That is, Operation Example 5-4 describes the interpretation of a PRACH configuration index provided by a RACH configuration for SBFD. The following options are considered for Operation Example 5-4.

[0204] In option 5-4-1, the interpretation of the PRACH configuration index provided by the RACH configuration for SBFD is predefined in the wireless communication system 10. In other words, the fact that the PRACH configuration index is associated with parameters assuming SBFD is predefined in the wireless communication system 10. The following examples are considered as such cases.

[0205] In Example 5-4-1-1, it is defined that for FR1 / FR2, the wireless communication system 10 interprets the PRACH configuration index provided by the RACH configuration for SBFD using the legacy tables for FR1 / FR2 and TDD.

[0206] In Example 5-4-1-2, the wireless communication system 10 defines that for FR1 / FR2, the PRACH configuration index provided by the RACH setting for SBFD is interpreted using an extended table for FR1 / FR2 and TDD with a new entry (Operation Example 5-3).

[0207] In Example 5-4-1-3, the wireless communication system 10 defines that for FR1 / FR2, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted using an extended table for FR1 / FR2 and TDD with new columns (Operation Example 5-1).

[0208] In Example 5-4-1-4, it is defined that for FR1, the wireless communication system 10 interprets the PRACH configuration index provided by the RACH configuration for SBFD using the legacy table for FR1 and FDD.

[0209] In option 5-4-2, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted based on the value of the PRACH configuration index provided by the RACH configuration for SBFD. In other words, the fact that the PRACH configuration index is associated with parameters assuming SBFD is specified by the value of the index (PRACH configuration index). The following examples are considered as such cases.

[0210] In Example 5-4-2-1, for FR1 / FR2, if the PRACH configuration index provided by the RACH configuration for SBFD is a certain value or if the PRACH configuration index provided by the RACH configuration for SBFD is within a certain range of values, the legacy tables for FR1 / FR2 and TDD are used to interpret the PRACH configuration index provided by the RACH configuration for SBFD. The "certain value" and "certain value range" may be predefined in the wireless communication system 10, or may be set or instructed by the gNB 100.

[0211] In Example 5-4-2-2, for FR1, when the PRACH configuration index provided by the RACH configuration for SBFD is a certain value or when the PRACH configuration index provided by the RACH configuration for SBFD is within a certain range of values, the legacy tables for FR1 and FDD are used to interpret the PRACH configuration index provided by the RACH configuration for SBFD. The "certain value" and "certain range of values" may be predefined in the wireless communication system 10, or may be set or instructed by the gNB 100.

[0212] In Example 5-4-2-3, for FR1 / FR2, when the PRACH configuration index provided by the RACH configuration for SBFD is a certain value or when the PRACH configuration index provided by the RACH configuration for SBFD is within a certain range of values, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted using the extended table for FR1 / FR2 and TDD with a new column (Operational Example 5-1). The "certain value" and "certain value range" may be predefined in the wireless communication system 10, or may be set or instructed by the gNB 100.

[0213] In Example 5-4-2-4, for FR1 / FR2, if the PRACH configuration index provided by the RACH configuration for SBFD is a certain value, or if the PRACH configuration index provided by the RACH configuration for SBFD is within a certain range of values, for FR1 / FR2, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted using the extended table for FR1 / FR2 and TDD with a new entry (Operation Example 5-3). The "certain value" and "certain range of values" may be a new index (PRACH configuration index) corresponding to the new entry.

[0214] In option 5-4-3, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted by explicit parameters included in the RACH configuration for SBFD. In other words, the fact that the PRACH configuration index is associated with parameters assuming SBFD is specified by explicit parameters included in the RACH configuration for SBFD. The following examples are considered as such cases.

[0215] The explicit parameter may specify the table to be used to identify the time resources of the RO. The explicit parameter may be referred to as RACH-config-table-sbfd-r19. The following example is an example of such a case:

[0216] In Example 5-4-3-1, when an explicit parameter specifies FDD-FR1-Table, the legacy tables for FR1 and FDD are used to interpret the PRACH configuration index provided by the RACH configuration for SBFD.

[0217] In Example 5-4-3-2, when an explicit parameter specifies the TDD-FR1-Table or the TDD-FR2-Table, the legacy tables for FR1 / FR2 and TDD are used to interpret the PRACH configuration index provided by the RACH configuration for SBFD.

[0218] In Example 5-4-3-3, when an explicit parameter specifies enhanced-new-col-TDD-FR1-table or enhanced-new-col-TDD-FR2-table, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted using the tables for extended FR1 / FR2 and TDD with new columns (Operation Example 5-1).

[0219] In Example 5-4-3-4, when an explicit parameter specifies enhanced-new-entry-TDD-FR1-table or enhanced-new-entry-TDD-FR2-table, the PRACH configuration index provided by the RACH configuration for SBFD is interpreted using the tables for extended FR1 / FR2 and TDD with new entries (Operation Example 5-3).

[0220] (4.3.6) Example 6 (4.3.6.1) Issues As a result of careful consideration, the inventors have found that when a RACH configuration assuming SBFD is assumed, it is necessary to clarify the details of the parameters included in the RACH configuration assuming SBFD.

[0221] To solve this problem, UE200 assumes the following example of operation for parameters included in a random access channel configuration (RACH configuration for SBFD) assuming a duplexing method (SBFD) that allows simultaneous use of multiple subbands in a time unit to which time division duplexing (TDD) is applied.

[0222] The RACH configuration for SBFD may be RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, or may be rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon.

[0223] The RACH configuration for SBFD may include all or some of the parameters included in the legacy RACH configuration, or may include new parameters not included in the legacy RACH configuration. The legacy RACH configuration may be RACH-ConfigCommon-SBFD or RACH-ConfigGeneric.

[0224] (4.3.6.2) Example 6-1 In operation example 6-1, an overview of parameters included in the RACH configuration for SBFD will be described. As an overview of parameters included in the RACH configuration for SBFD, the following options are possible.

[0225] In option 6-1-1, the present type of a parameter included in the RACH configuration for SBFD may be mandatory present or optionally present. Mandatory present means that the parameter is required to be included, and optionally present may mean that the parameter does not need to be required to be included but may be included as necessary. Different present types may be set for different parameters.

[0226] In Option 6-1-2, the candidate values ​​of the values ​​that the parameters included in the RACH configuration for SBFD (hereinafter referred to as SBFD candidate values) can take may be the same as or different from the candidate values ​​of the values ​​that the parameters included in the legacy RACH configuration (hereinafter referred to as legacy candidate values). The relationship (different / same) between the SBFD candidate values ​​and the legacy candidate values ​​may be different for different parameters.

[0227] Note that the SBFD value candidates may be applied to parameters included in the legacy RACH configuration. Whether the SBFD value candidates or the legacy value candidates are applied may differ for different parameters.

[0228] In option 6-1-3, the values ​​provided by the parameters included in the RACH configuration for SBFD and the values ​​provided by the parameters included in the legacy RACH configuration may have certain restrictions.

[0229] For example, if a parameter included in the RACH configuration for SBFD is included in the legacy RACH configuration, the UE 200 may assume that the values ​​provided by the parameters included in the RACH configuration for SBFD and the legacy RACH configuration are the same.

[0230] For example, when a parameter included in the RACH configuration for SBFD is included in a legacy RACH configuration, UE 200 may assume that the value provided by the parameter included in the RACH configuration for SBFD is greater than, not greater than, less than, or not less than the value provided by the parameter included in the legacy RACH configuration.

[0231] Note that certain restrictions may apply to parameters included in the legacy RACH configuration, and certain restrictions may be different for different parameters.

[0232] In option 6-1-4, for parameters not included in the RACH configuration for SBFD, the following Atl. may be assumed:

[0233] In Atl.6-1-4-1, default parameters are defined for parameters not included in the RACH configuration for SBFD, and the default parameters may be applied.

[0234] In Atl.6-1-4-2, parameters included in the legacy RACH configuration may be applied to parameters not included in the RACH configuration for SBFD.

[0235] Note that the above-mentioned Alternatives may be applied to parameters included in the legacy RACH configuration. The above-mentioned Alternatives may be different for different parameters.

[0236] (4.3.6.3) Example 6-2 In the operation example 6-2, the parameters included in the RACH configuration for SBFD may be parameters related to the time resources of the RO. That is, the UE 200 may assume that the parameters included in the RACH configuration for SBFD are parameters related to the time resources of the RO.

[0237] In option 6-2-1, the parameters related to the time resource of the RO may include an index of a PRACH configuration (e.g., prach-ConfigurationIndex). The present type of prach-ConfigurationIndex may be mandatory present or optionally present.

[0238] If the present type of prach-ConfigurationIndex is optionally present and prach-ConfigurationIndex is not included in the RACH configuration for SBFD, the following options may be assumed:

[0239] In Alt.6-2-1-1, the parameters included in the legacy RACH configuration (prach-ConfigurationIndex set in RACH-ConfigCommon of BWP-UplinkCommon) may be applied.Alt.6-2-1-1 may be applied when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon.

[0240] In Alt.6-2-1-2, parameters included in the legacy RACH configuration (prach-ConfigurationIndex of rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.Alt.6-2-1-2 may be applied when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon.

[0241] The candidate values ​​of prach-ConfigurationIndex included in the RACH configuration for SBFD may be values ​​between 0 and the maximum value, or may be a subset of values ​​between 0 and the maximum value.

[0242] In option 6-2-2, the RO's time resource parameters may include an offset (e.g., prach-ConfigurationSOffset-sbfd-r19) to the subframe number or slot number specified by prach-ConfigurationIndex. The offset may be set by the RRC as described in option 5-2-1 of operation example 5-2.

[0243] The present type of prach-ConfigurationSOffset-sbfd-r19 may be mandatory present or optionally present. If the present type of prach-ConfigurationSOffset-sbfd-r19 is optionally present and prach-ConfigurationSOffset-sbfd-r19 is not included in the RACH configuration for SBFD, a default value (for example, 0) may be used.

[0244] If the RACH configuration for SBFD includes prach-ConfigurationSOffset-sbfd-r19, as described in option 5-2-1 of operation example 5, prach-ConfigurationSOffset-sbfd-r19 is applied to the subframe number or slot number specified by prach-ConfigurationIndex.

[0245] In option 6-2-2, the parameter related to the time resource of the RO may be the subframe number or slot number of the RO (e.g., prach-ConfigurationSOnumber-sbfd-r19). prach-ConfigurationSOnumber-sbfd-r19 may be set by the RRC as described in option 5-2-2 of operation example 5-2.

[0246] The present type of prach-ConfigurationSOnumber-sbfd-r19 may be mandatory present or optionally present. When the present type of prach-ConfigurationSOnumber-sbfd-r19 is optionally present and prach-ConfigurationSOnumber-sbfd-r19 is not included in the RACH configuration for SBFD, the subframe number or slot number specified by prach-ConfigurationIndex may be applied.

[0247] If the RACH configuration for SBFD includes prach-ConfigurationSOnumber-sbfd-r19, as described in option 5-2-1 of operation example 5, prach-ConfigurationSOnumber-sbfd-r19 specifies the subframe number or slot number of the RO, and the subframe number or slot number specified by prach-ConfigurationIndex is ignored.

[0248] (4.3.6.4) Example 6-3 In the operation example 6-3, the parameters included in the RACH configuration for SBFD may be parameters related to the frequency resources of the RO. That is, the UE 200 may assume that the parameters included in the RACH configuration for SBFD are parameters related to the frequency resources of the RO.

[0249] In Option 6-3-1, the parameters related to the frequency resource of the RO may include a parameter (e.g., msg1-FrequencyStart) specifying the start RB of the lowest RO. The present type of msg1-FrequencyStart may be mandatory present or optionally present.

[0250] If the present type of msg1-FrequencyStart is optionally present and msg1-FrequencyStart is not included in the RACH configuration for SBFD, the following options may be assumed:

[0251] In Alt. 6-3-1-1, the parameter (msg1-FrequencyStart) included in the legacy RACH configuration may be applied.

[0252] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, msg1-FrequencyStart of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0253] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, msg1-FrequencyStart set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0254] In Alt. 6-3-1-1, in the frequency domain, the start RB of the lowest RO may be the start / lowest RB of the UL usable PRBs (UL subband).

[0255] msg1-FrequencyStart may be interpreted as the offset value of the starting RB of the lowest RO relative to PRB0, or as the offset value of the starting RB of the lowest RO corresponding to the start / lowest RB of UL usable PRBs (UL subband).

[0256] msg1-FrequencyStart may be set so that all FDMed ROs configured by the RACH configuration for SBFD are within UL usable PRBs (UL subbands).

[0257] In option 6-3-2, the parameters related to the frequency resources of ROs may include a parameter (e.g., msg1-FDM) specifying the number of FDMed ROs in one time instance, and the present type of msg1-FDM may be mandatory present or optionally present.

[0258] When the present type of msg1-FDM is optionally present and the RACH configuration for SBFD does not include msg1-FDM, the following options may be assumed:

[0259] In Alt.6-3-2-1, a default value (e.g., 1) may be applied.

[0260] In Alt. 6-3-2-2, the parameters (msg1-FDM) included in the legacy RACH configuration may be applied.

[0261] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, msg1-FDM of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0262] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, msg1-FDM configured in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0263] The maximum value of msg1-FDM included in the RACH configuration for SBFD may be 2, 4, or 8. Candidate values ​​of msg1-FDM included in the RACH configuration for SBFD may be {1, 2, 4, 8}, {1, 2, 4}, or {1, 2}.

[0264] The UE 200 may assume that the value of msg1-FDM included in the RACH configuration for SBFD is smaller or not larger than the value of msg1-FDM included in the legacy RACH configuration.

[0265] For example, UE 200 may assume that the value of msg1-FDM included in the RACH configuration for SBFD is smaller or not larger than the value of msg1-FDM of RACH-ConfigCommon included in BWP-UplinkCommon.

[0266] For example, UE 200 may assume that the value of msg1-FDM included in the RACH configuration for SBFD is smaller or not larger than the value of msg1-FDM of rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD.

[0267] (4.3.6.5) Example 6-4 In operation example 6-4, the parameters included in the RACH configuration for SBFD may be parameters (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB) related to mapping between random access opportunities and synchronization signal blocks (SSB-RO mapping). That is, the UE 200 may assume the parameters related to SSB-RO mapping as the parameters included in the RACH configuration for SBFD. ssb-perRACH-OccasionAndCB-PreamblesPerSSB may be mandatory present or may be optionally present.

[0268] When ssb-perRACH-OccasionAndCB-PreamblesPerSSB is optionally present and ssb-perRACH-OccasionAndCB-PreamblesPerSSB is not included in the RACH configuration for SBFD, ssb-perRACH-OccasionAndCB-PreamblesPerSSB configured by the legacy RACH configuration may be applied to ROs in the SBFD slot or symbol configured by the RACH configuration for SBFD. For example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB configured by RACH-ConfigCommon included in BWP-UplinkCommon may be applied.

[0269] Valid ROs in SBFD slots / symbols that are not associated with an SSB index after an integer number of association periods (valid ROs configured by the RACH configuration for SBFD) may not be used for PRACH transmission.

[0270] The set of SSB indices may be configured by the RACH configuration for SBFD. The ROs in the SBFD slots / symbols configured by the RACH configuration for SBFD may be mapped to the set of SSB indices.

[0271] The relationship between the SSB-RO mapping for the SSB index of a valid RO configured by the RACH configuration for SBFD and the SSB-RO mapping for the SSB index of a valid RO configured by the legacy RACH configuration may be as follows:

[0272] First, there may be a relationship in association period between the SSB-RO mapping for the SSB index of a valid RO configured by the RACH configuration for SBFD and the SSB-RO mapping for the SSB index of a valid RO configured by the legacy RACH configuration. For example, in UE 200, the association period of the SSB-RO mapping for the SSB index of a valid RO configured by the RACH configuration for SBFD may be a divisor (value obtained by dividing by an integer), a multiple (value obtained by multiplying by an integer), or the same value as the association period of the SSB-RO mapping for the SSB index of a valid RO configured by the legacy RACH configuration.

[0273] Second, there may be a relationship in association pattern period between the SSB-RO mapping for the SSB index of a valid RO configured by the RACH configuration for SBFD and the SSB-RO mapping for the SSB index of a valid RO configured by the legacy RACH configuration. For example, in UE 200, the association pattern period of the SSB-RO mapping for the SSB index of a valid RO configured by the RACH configuration for SBFD may be a divisor (value obtained by dividing by an integer), a multiple (value obtained by multiplying by an integer), or the same value as the association pattern period of the SSB-RO mapping for the SSB index of a valid RO configured by the legacy RACH configuration.

[0274] (4.3.6.6) Example 6-5 In the operation example 6-5, the parameter included in the RACH configuration for SBFD may be a parameter related to the transmission power of a preamble. That is, the UE 200 may assume that the parameter included in the RACH configuration for SBFD is a parameter related to the transmission power of a preamble.

[0275] In Option 6-5-1, the parameters related to the transmission power of the preamble may include a parameter specifying the transmission power of the PRACH transmitted in the RO configured by the RACH configuration for SBFD (e.g., preambleReceivedTargetPower). The preambleReceivedTargetPower may be mandatory present or optionally present.

[0276] When preambleReceivedTargetPower is optionally present and the RACH configuration for SBFD does not include preambleReceivedTargetPower, the preambleReceivedTargetPower set by the legacy RACH configuration may be applied to determine the transmission power of the PRACH to be transmitted in the RO in the SBFD slot or symbol set by the RACH configuration for SBFD.

[0277] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the preambleReceivedTargetPower of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0278] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the preambleReceivedTargetPower set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0279] The UE 200 may assume that the value of preambleReceivedTargetPower included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleReceivedTargetPower included in the legacy RACH configuration.

[0280] For example, UE 200 may assume that the value of preambleReceivedTargetPower included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleReceivedTargetPower of RACH-ConfigCommon included in BWP-UplinkCommon.

[0281] For example, UE200 may assume that the value of preambleReceivedTargetPower included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleReceivedTargetPower of rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD.

[0282] In option 6-5-2, the parameter related to the transmission power of the preamble may include the maximum number of times (e.g., preambleTransMax) that the preamble is transmitted in the RO configured by the RACH configuration for SBFD. preambleTransMax may be mandatory present or optionally present.

[0283] If preambleTransMax is optionally present and the RACH configuration for SBFD does not include preambleTransMax, the preambleTransMax configured by the legacy RACH configuration may be applied.

[0284] For example, the preambleTransMax set by the legacy RACH configuration may be applied to determine the maximum number of preambles to be transmitted in RO in the SBFD slots or symbols set by the RACH configuration for SBFD, without distinguishing between SBFD slots / symbols and non-SBFD slots / symbols.

[0285] For example, assuming that the number of preambles transmitted in RO in each of SBFD slots / symbols and non-SBFD slots / symbols is counted separately (assuming that there is a separate counter for each of SBFD slots / symbols and non-SBFD slots / symbols), the preambleTransMax set by the legacy RACH configuration may be applied to determine the maximum number of preambles transmitted in RO in the SBFD slots or symbols set by the RACH configuration for SBFD.

[0286] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the preambleTransMax of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0287] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the preambleTransMax set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0288] The UE 200 may assume that the value of preambleTransMax included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleTransMax included in the legacy RACH configuration.

[0289] For example, UE 200 may assume that the value of preambleTransMax included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleTransMax of RACH-ConfigCommon included in BWP-UplinkCommon.

[0290] For example, UE200 may assume that the value of preambleTransMax included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of preambleTransMax in rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD.

[0291] In Option 6-5-3, the parameter related to the transmission power of the preamble may include a power ramping step (e.g., powerRampingStep) of the PRACH transmission transmitted in the RO configured by the RACH configuration for SBFD. The powerRampingStep may be mandatory or optionally present.

[0292] If powerRampingStep is optionally present and the RACH configuration for SBFD does not include powerRampingStep, the powerRampingStep set by the legacy RACH configuration may be applied to determine the power ramping of PRACH transmissions sent in ROs in SBFD slots or symbols configured by the RACH configuration for SBFD.

[0293] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the powerRampingStep of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0294] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the powerRampingStep set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0295] The UE 200 may assume that the value of powerRampingStep included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of powerRampingStep included in the legacy RACH configuration.

[0296] For example, UE 200 may assume that the value of powerRampingStep included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of powerRampingStep of RACH-ConfigCommon included in BWP-UplinkCommon.

[0297] For example, UE200 may assume that the value of powerRampingStep included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of powerRampingStep in rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD.

[0298] (4.3.6.7) Example 6-6 In operation example 6-6, the parameters included in the RACH configuration for SBFD may be parameters related to parameters related to a window used in random access. That is, UE 200 may assume that the parameters included in the RACH configuration for SBFD are parameters related to a window used in random access.

[0299] In option 6-6-1, the parameter related to the window used in random access may be a parameter (ra-ResponseWindow) that specifies the window of RAR (Random Access Response) waiting for RAR in response to the transmission of the preamble. The ra-ResponseWindow may be mandatory present, optionally present, or not present.

[0300] When the ra-ResponseWindow is optionally present or not present and the RACH configuration for SBFD does not include the ra-ResponseWindow, the ra-ResponseWindow set by the legacy RACH configuration may be applied to determine the window of the RAR for random access set by the RACH configuration for SBFD.

[0301] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the ra-ResponseWindow of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0302] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the ra-ResponseWindow set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0303] The UE 200 may assume that the value of the ra-ResponseWindow included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of the ra-ResponseWindow included in the legacy RACH configuration.

[0304] For example, UE 200 may assume that the value of ra-ResponseWindow included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of ra-ResponseWindow in RACH-ConfigCommon included in BWP-UplinkCommon.

[0305] For example, UE200 may assume that the value of ra-ResponseWindow included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of ra-ResponseWindow of rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD.

[0306] In option 6-6-2, the parameter related to the window used in random access may be a parameter (ContentionResolutionTimer) that specifies the length of the collision resolution window for waiting for Mg.4 in response to the transmission of Mg.3. ContentionResolutionTimer may be mandatory present, optionally present, or not present.

[0307] When the ContentionResolutionTimer is optionally present or not present and the RACH configuration for SBFD does not include the ContentionResolutionTimer, the ContentionResolutionTimer configured by the legacy RACH configuration may be applied to determine the length of the collision resolution window for random access configured by the RACH configuration for SBFD.

[0308] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the ContentionResolutionTimer of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0309] The UE 200 may assume that the value of the ContentionResolutionTimer included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of the ContentionResolutionTimer included in the legacy RACH configuration.

[0310] For example, UE 200 may assume that the value of ContentionResolutionTimer included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the value of ContentionResolutionTimer in RACH-ConfigCommon included in BWP-UplinkCommon.

[0311] (4.3.6.8) Example 6-7 In operation example 6-7, the parameters included in the RACH configuration for SBFD may be parameters (featureCombinationPreamblesList) related to features associated with random access. That is, UE 200 may assume that the parameters included in the RACH configuration for SBFD are parameters related to features associated with random access. featureCombinationPreamblesList may be mandatory present, optionally present, or not present.

[0312] When featureCombinationPreamblesList is optionally present or not present and the RACH configuration for SBFD does not include featureCombinationPreamblesList, the featureCombinationPreamblesList configured by the legacy RACH configuration may be applied.

[0313] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the featureCombinationPreamblesList of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0314] (4.3.6.9) Example 6-8 In the operation example 6-7, the parameters included in the RACH configuration for SBFD may be other parameters. That is, the UE 200 may assume other parameters as parameters included in the RACH configuration for SBFD.

[0315] In Option 6-8-1, another parameter may be a parameter (zeroCorrelationZoneConfig) that specifies the N-CS configuration of the RO configured by the RACH configuration for SBFD. The zeroCorrelationZoneConfig may be mandatory present, optionally present, or not present.

[0316] When zeroCorrelationZoneConfig is optionally present or not present and the RACH configuration for SBFD does not include zeroCorrelationZoneConfig, the zeroCorrelationZoneConfig configured by the legacy RACH configuration may be applied.

[0317] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, zeroCorrelationZoneConfig of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0318] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, zeroCorrelationZoneConfig set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0319] The UE 200 may assume that the zeroCorrelationZoneConfig included in the RACH configuration for SBFD is the same as the zeroCorrelationZoneConfig included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0320] In option 6-8-2, another parameter may be a parameter (groupBconfigured) that specifies the configuration of group B in the preamble. groupBconfigured may be mandatory present, optionally present, or not present.

[0321] When groupBconfigured is optionally present or not present and groupBconfigured is not included in the RACH configuration for SBFD, groupBconfigured configured by the legacy RACH configuration may be applied.

[0322] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, groupBconfigured of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0323] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, groupBconfigured set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0324] The UE 200 may assume that the groupB configured included in the RACH configuration for SBFD is the same as the groupB configured included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0325] In Option 6-8-3, another parameter may be a parameter (rsrp-ThresholdSSB) that specifies the RSRP threshold of the RO (SBFD slot / symbol) configured by the RACH configuration for SBFD. rsrp-ThresholdSSB may be mandatory present, optionally present, or not present.

[0326] When rsrp-ThresholdSSB is optionally present or not present and rsrp-ThresholdSSB is not included in the RACH configuration for SBFD, rsrp-ThresholdSSB configured by the legacy RACH configuration may be applied.

[0327] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, rsrp-ThresholdSSB of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0328] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the rsrp-ThresholdSSB set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0329] The UE 200 may assume that the rsrp-ThresholdSSB included in the RACH configuration for SBFD is the same as, smaller than, not smaller than, larger than, or not larger than the rsrp-ThresholdSSB included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0330] In Option 6-8-4, another parameter may be a parameter (prach-RootSequenceIndex) that specifies the PRACH root sequence index of the PRACH transmitted in the RO (SBFD slot / symbol) configured by the RACH configuration for SBFD. The prach-RootSequenceIndex may be mandatory present, optionally present, or not present.

[0331] When prach-RootSequenceIndex is optionally present or not present and prach-RootSequenceIndex is not included in the RACH configuration for SBFD, the prach-RootSequenceIndex configured by the legacy RACH configuration may be applied.

[0332] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the prach-RootSequenceIndex of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0333] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the prach-RootSequenceIndex set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0334] The UE 200 may assume that the prach-RootSequenceIndex included in the RACH configuration for SBFD is the same as the prach-RootSequenceIndex included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0335] In Option 6-8-5, another parameter may be a parameter (msg1-SubcarrierSpacing) that specifies the SCS of the RO configured by the RACH configuration for SBFD. The msg1-SubcarrierSpacing may be mandatory present, optionally present, or not present.

[0336] When msg1-SubcarrierSpacing is optionally present or not present and msg1-SubcarrierSpacing is not included in the RACH configuration for SBFD, the msg1-SubcarrierSpacing configured by the legacy RACH configuration may be applied.

[0337] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the msg1-SubcarrierSpacing of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0338] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the msg1-SubcarrierSpacing set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0339] The UE 200 may assume that the msg1-SubcarrierSpacing included in the RACH configuration for SBFD is the same as the msg1-SubcarrierSpacing included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0340] In Option 6-8-6, another parameter may be a parameter (msg3-transformPrecoder) that specifies the waveform configuration of Msg.3 corresponding to the PRACH transmitted in the RO (SBFD slot / symbol) configured by the RACH configuration for SBFD. The msg3-transformPrecoder may be mandatory present, optionally present, or not present.

[0341] When msg3-transformPrecoder is optionally present or not present and msg3-transformPrecoder is not included in the RACH configuration for SBFD, the msg3-transformPrecoder configured by the legacy RACH configuration may be applied.

[0342] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, the msg3-transformPrecoder of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0343] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, the msg3-transformPrecoder set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0344] The UE 200 may assume that the msg3-transformPrecoder included in the RACH configuration for SBFD is the same as the msg3-transformPrecoder included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0345] In option 6-8-7, another parameter may be a parameter (restrictedSetConfig) that specifies a restricted set type configuration configured by the RACH configuration for SBFD. The restrictedSetConfig may be mandatory present, optionally present, or not present.

[0346] When restrictedSetConfig is optionally present or not present and restrictedSetConfig is not included in the RACH configuration for SBFD, restrictedSetConfig configured by the legacy RACH configuration may be applied.

[0347] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, restrictedSetConfig of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0348] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, restrictedSetConfig set to the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0349] The UE 200 may assume that the restrictedSetConfig included in the RACH configuration for SBFD is the same as the restrictedSetConfig included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0350] In option 6-8-8, another parameter may be a parameter (ra-PrioritizationForAccessIdentity) that specifies PRACH prioritization for access identities of the RO configured by the RACH configuration for SBFD. ra-PrioritizationForAccessIdentity may be mandatory present, optionally present, or not present.

[0351] When ra-PrioritizationForAccessIdentity is optionally present or not present and ra-PrioritizationForAccessIdentity is not included in the RACH configuration for SBFD, ra-PrioritizationForAccessIdentity configured by the legacy RACH configuration may be applied.

[0352] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, ra-PrioritizationForAccessIdentity of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0353] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, ra-PrioritizationForAccessIdentity set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0354] The UE 200 may assume that the ra-PrioritizationForAccessIdentity included in the RACH configuration for SBFD is the same as the ra-PrioritizationForAccessIdentity included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0355] In Option 6-8-9, another parameter may be a parameter (ra-PrioritizationForSlicing) that specifies PRACH prioritization for slicing of PRACH transmission transmitted in an RO configured by the RACH configuration for SBFD. ra-PrioritizationForSlicing may be mandatory present, optionally present, or not present.

[0356] When ra-PrioritizationForSlicing is optionally present or not present and ra-PrioritizationForSlicing is not included in the RACH configuration for SBFD, ra-PrioritizationForSlicing configured by the legacy RACH configuration may be applied.

[0357] For example, when the RACH configuration for SBFD is configured by RACH-ConfigCommon-SBFD-r19 included in BWP-UplinkCommon, ra-PrioritizationForSlicing of the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon) may be applied.

[0358] For example, when the RACH configuration for SBFD is configured by rach-ConfigGeneric-sbfd-r19 included in RACH-ConfigCommon, ra-PrioritizationForSlicing set in the legacy RACH configuration (rach-ConfigGeneric included in the same RACH-ConfigCommon as the RACH configuration for SBFD) may be applied.

[0359] The UE 200 may assume that the ra-PrioritizationForSlicing included in the RACH configuration for SBFD is the same as the ra-PrioritizationForSlicing included in the legacy RACH configuration (RACH-ConfigCommon included in BWP-UplinkCommon).

[0360] (4.3.7) Example 7 As described above, in addition to the RACH configuration that does not assume SBFD (legacy RACH configuration), it is expected that a RACH configuration that assumes SBFD (RACH configuration for SBFD) will be introduced.

[0361] Under such circumstances, the inventors have conducted extensive research and found that it is necessary to clarify whether or not the RACH setting for SBFD is valid for non-SBFD symbols.

[0362] Hereinafter, an RO configured based on a legacy RACH configuration for a non-SBFD symbol may be referred to as a first RO. An RO configured based on a RACH configuration for SBFD for a non-SBFD symbol may be referred to as a second RO. The legacy RACH configuration may be referred to as a first RACH configuration, and the RACH configuration for SBFD may be referred to as a second RACH configuration.

[0363] Operation Example 7 may be an operation example that is premised on at least one of the above-described Operation Examples 1 to 6. The SBFD symbol may be read as the SBFD slot.

[0364] In the seventh operational example, the UE 200 determines whether to select a random access opportunity (RO) in a first symbol (non-SBFD symbol) that does not assume the duplexing method (SBFD) based on a second random access channel configuration (RACH configuration for SBFD) that assumes SBFD. The following Alt can be considered as a method for determining whether to select an RO in a non-SBFD symbol based on the RACH configuration for SBFD.

[0365] In Alt 7-1, whether or not to select an RO based on the RACH configuration for SBFD in a non-SBFD symbol, in other words, whether or not the RO (those ROs / second RO) configured based on the RACH configuration for SBFD in a non-SBFD symbol is valid may be predefined in the wireless communication system 10.

[0366] For example, those ROs may be predefined in the wireless communication system 10 as being invalid.

[0367] For example, it may be predefined in the wireless communication system 10 that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0368] In Alt 7-2, whether or not to select an RO based on the RACH configuration for SBFD in a non-SBFD symbol, in other words, whether or not an RO (those ROs / second RO) configured based on the RACH configuration for SBFD in a non-SBFD symbol is valid may be configured or indicated by a network (e.g., the gNB 100). The following Alts are possible as Alt 7-2.

[0369] In Alt 7-2-1, the setting or instruction by gNB100 may be an explicit setting or instruction.

[0370] For example, a new RRC parameter (higher layer parameter) included in the RACH configuration for SBFD may configure or indicate whether those ROs may be invalid or valid. If the new RRC parameter is "Invalid", those ROs may be invalid. If the new RRC parameter is "Valid", it is determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to the legacy rule for determining valid ROs.

[0371] In Alt 7-2-2, the setting or instruction by gNB100 may be an implicit setting or instruction.

[0372] For example, if different power control parameters (e.g., at least one of preambleReceivedTargetPower, preambleTransMax, and powerRampingStep) are set by the RACH configuration for SBFD between SBFD symbols and non-SBFD symbols, it is determined that those ROs may be valid, and UE200 may determine whether those ROs are valid according to legacy rules for determining valid ROs.

[0373] In Alt 7-3, whether or not to select an RO based on the RACH configuration for SBFD in a non-SBFD symbol, in other words, whether or not an RO (those ROs / second RO) configured based on the RACH configuration for SBFD in a non-SBFD symbol is valid may be determined based on a rule. The following Alts are possible as Alt 7-3.

[0374] In Alt 7-3-1, the rule may be determined based on whether those ROs overlap with the valid RO of the first RO (hereinafter referred to as the legacy valid RO or the first valid RO). The following Alts are possible for Alt 7-3-1:

[0375] In Alt 7-3-1A, if those ROs overlap with a legacy valid RO, all those ROs may be determined to be invalid. The overlap may include overlap in the frequency domain or overlap in the time domain.

[0376] For example, if any (at least one) of those ROs overlaps with a valid legacy RO, all of those ROs may be determined to be invalid. If none of those ROs overlaps with a valid legacy RO, those ROs may be determined to be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0377] In Alt 7-3-1B, when those ROs overlap with a valid legacy RO, only those ROs that overlap with the valid legacy RO may be determined to be invalid. The overlap may include overlap in the frequency domain or overlap in the time domain.

[0378] For example, among those ROs, an RO that overlaps with a valid legacy RO may be invalid, whereas among those ROs, an RO that does not overlap with a valid legacy RO may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0379] In Alt 7-3-2, the rule may be determined based on whether those ROs overlap with RBs outside of UL usable RBs.

[0380] For example, if any (at least one) of those ROs overlaps with an RB outside the UL usable RBs, all of those ROs may be determined to be invalid. If none of those ROs overlaps with an RB outside the UL usable RBs, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to the legacy rule for determining valid ROs.

[0381] In Alt 7-4, whether or not to select an RO based on the RACH configuration for SBFD in a non-SBFD symbol, in other words, whether or not an RO (those ROs / second RO) configured based on the RACH configuration for SBFD in a non-SBFD symbol is valid may be determined based on a parameter configured by the RACH configuration for SBFD. As Alt 7-4, the following Alts are possible.

[0382] In Alt 7-4-1, the parameter may be a preamble format for setting up a RACH for SBFD.

[0383] For example, if the preamble format for configuring the RACH for SBFD is a certain preamble format, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO. If the preamble format for configuring the RACH for SBFD is not a certain preamble format, it may be determined that those ROs are invalid. The certain preamble format may be predetermined in the wireless communication system 10 or may be set by the network.

[0384] In Alt 7-4-2, the parameter may be RO periodicity for RACH configuration for SBFD.

[0385] For example, if the RO periodicity for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the RO periodicity for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO. The certain value may be predetermined in the wireless communication system 10 or may be set by the network.

[0386] For example, if the RO periodicity for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the RO periodicity for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO. The certain value may be predetermined in the wireless communication system 10 or may be set by the network.

[0387] In Alt 7-4-3, the parameter may be the preamble length for setting up the RACH for SBFD.

[0388] For example, if the preamble length for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the preamble length for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO. The certain value may be predetermined in the wireless communication system 10 or may be set by the network.

[0389] For example, if the preamble length for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the preamble length for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO. The certain value may be predetermined in the wireless communication system 10 or may be set by the network.

[0390] In Alt 7-4-4, the parameter may be the RO frequency resource for RACH configuration for SBFD.

[0391] For example, if the number of FDMeD ROs for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, those ROs may be determined to be invalid. If the number of FDMeD ROs for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, those ROs may be determined to be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs. The certain value may be predetermined in the wireless communication system 10 or set by the network.

[0392] For example, if the number of FDMeD ROs for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, those ROs may be determined to be invalid. If the number of FDMeD ROs for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, those ROs may be determined to be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs. The certain value may be predetermined in the wireless communication system 10 or set by the network.

[0393] In Alt 7-4-5, the parameter may be PRACH subcarrier spacing for RACH configuration for SBFD.

[0394] For example, if the PRACH subcarrier spacing for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the PRACH subcarrier spacing for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs. The certain value may be predetermined in the wireless communication system 10 or set by the network.

[0395] For example, if the PRACH subcarrier spacing for configuring the RACH for SBFD is not greater than, less than, or equal to a certain value, it may be determined that those ROs are invalid. If the PRACH subcarrier spacing for configuring the RACH for SBFD is greater than, less than, or equal to a certain value, it may be determined that those ROs may be valid, and the UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs. The certain value may be predetermined in the wireless communication system 10 or may be set by the network.

[0396] In Alt 7-5, whether or not to select an RO based on the RACH configuration for SBFD in a non-SBFD symbol, in other words, whether or not an RO (those ROs / second RO) configured based on the RACH configuration for SBFD in a non-SBFD symbol is valid may be determined based on the relationship between parameters configured by the legacy RACH configuration and parameters configured by the RACH configuration for SBFD. The following Alts are possible as Alt 7-5.

[0397] In Alt 7-5-1, the parameters may be preamble formats for legacy RACH configuration and RACH configuration for SBFD.

[0398] For example, if the preamble format for the RACH configuration for SBFD is the same as the preamble format for the legacy RACH configuration, it may be determined that those ROs are invalid. If the preamble format for the RACH configuration for SBFD is not the same as the preamble format for the legacy RACH configuration, it may be determined that those ROs may be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0399] In Alt 7-5-2, the parameter may be RO periodicity for legacy RACH configuration and for SBFD RACH configuration.

[0400] For example, if the RO periodicity for the SBFD-based RACH configuration is greater than, less than, or equal to the RO periodicity for the legacy RACH configuration, it may be determined that those ROs are invalid. If the RO periodicity for the SBFD-based RACH configuration is not greater than, less than, or equal to the RO periodicity for the legacy RACH configuration, it may be determined that those ROs may be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0401] For example, if the RO periodicity for the SBFD-based RACH configuration is not greater than, not less than, or not equal to the RO periodicity for the legacy RACH configuration, those ROs may be determined to be invalid. If the RO periodicity for the SBFD-based RACH configuration is greater than, less than, or equal to the RO periodicity for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0402] In Alt 7-5-3, the parameter may be the preamble length for legacy RACH configuration and RACH configuration for SBFD.

[0403] For example, if the preamble length for the RACH configuration for SBFD is greater than, less than, or equal to the preamble length for the legacy RACH configuration, those ROs may be determined to be invalid. If the preamble length for the RACH configuration for SBFD is not greater than, less than, or equal to the preamble length for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0404] For example, if the preamble length for the RACH configuration for SBFD is not greater than, not less than, or not equal to the preamble length for the legacy RACH configuration, those ROs may be determined to be invalid. If the preamble length for the RACH configuration for SBFD is greater than, less than, or equal to the preamble length for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining a valid RO.

[0405] In Alt 7-5-4, the parameter may be the RO frequency resource for legacy RACH configuration and for SBFD RACH configuration.

[0406] For example, if the number of FDMeD ROs for the SBFD RACH configuration is greater than, less than, or equal to the number of FDMeD ROs for the legacy RACH configuration, those ROs may be determined to be invalid. If the number of FDMeD ROs for the SBFD RACH configuration is not greater than, less than, or equal to the number of FDMeD ROs for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs.

[0407] For example, if the number of FDMeD ROs for the SBFD RACH configuration is not greater than, not less than, or not equal to the number of FDMeD ROs for the legacy RACH configuration, those ROs may be determined to be invalid. If the number of FDMeD ROs for the SBFD RACH configuration is greater than, less than, or equal to the number of FDMeD ROs for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs.

[0408] In Alt 7-5-5, the parameter may be PRACH subcarrier spacing for legacy RACH configuration and for SBFD RACH configuration.

[0409] For example, if the PRACH subcarrier spacing for the RACH configuration for SBFD is larger than, smaller than, or equal to the PRACH subcarrier spacing for the legacy RACH configuration, those ROs may be determined to be invalid. If the PRACH subcarrier spacing for the RACH configuration for SBFD is not larger than, smaller than, or equal to the PRACH subcarrier spacing for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs.

[0410] For example, if the PRACH subcarrier spacing for the RACH configuration for SBFD is not larger than, not smaller than, or not the same as the PRACH subcarrier spacing for the legacy RACH configuration, those ROs may be determined to be invalid. If the PRACH subcarrier spacing for the RACH configuration for SBFD is larger than, smaller than, or the same as the PRACH subcarrier spacing for the legacy RACH configuration, those ROs may be determined to be valid, and UE 200 may determine whether those ROs are valid according to a legacy rule for determining valid ROs.

[0411] (4.3.8) Example 8 In operation example 8, UE200 may perform separate power control between the first symbol (Non-SBFD symbol) and the second symbol (SBFD symbol) for a random access opportunity (RO) selected based on the second random access channel setting (RACH setting for SBFD).

[0412] Operation Example 8 may be an operation example that is premised on at least one of the above-described Operation Examples 1 to 7. The SBFD symbol may be read as the SBFD slot. As Operation Example 8, the following Alt. is possible.

[0413] In Alt 8-1, two sets of power control parameters are configured by the RACH configuration for SBFD.

[0414] For example, the RACH configuration for SBFD may include separate power control parameters for SBFD and non-SBFD (e.g., at least one of preambleReceivedTargetPower, preambleTransMax, and powerRampingStep). UE 200 may apply corresponding power control parameters to ROs of SBFD symbols and non-SBFD symbols.

[0415] In Alt 8-2, one set of power control parameters is configured by the RACH configuration for SBFD.

[0416] For example, the RACH configuration for SBFD may include power control parameters for SBFD (for example, at least one of preambleReceivedTargetPower, preambleTransMax, and powerRampingStep). UE 200 applies the power control parameters included in the RACH configuration for SBFD to the RO of the SBFD symbol.

[0417] In Alt 8-2, UE 200 may apply power control parameters (for example, at least one of preambleReceivedTargetPower, preambleTransMax, and powerRampingStep) included in the legacy RACH configuration for RO of non-SBFD symbols.

[0418] (4.3.9) UE capability To apply the above-described operation examples 1 to 8, new UE capabilities and report signaling (and RRC settings) shown below may be defined for each UE / FR / FC, etc.

[0419] Whether to support SBFD subband time and frequency domain location recognition Whether to support PRACH transmission in SBFD symbols Whether to support enhanced RO validation rules for determining valid ROs for SBFD Whether to support PRACH transmission in SBFD symbols for CFRA Whether to support extended FR1 / FR2 and TDD tables with new columns (Example 5-1) Whether or not the setting or indication of parameters (offset, subframe number / slot number) assuming SBFD by setting RACH for SBFD (Operation example 5-2) is supported Whether or not the extended FR1 / FR2 and TDD tables with new entries (Operation Example 5-3) are supported for one or more PRACH formats selected from PRACH format 0, PRACH format 1, PRACH format 2, PRACH format A1, PRACH format A2, PRACH format A3, PRACH format B1, PRACH format B4, PRACH format C0, PRACH format C2, PRACH format A1 / B1, PRACH format A2 / B2, and PRACH format A3 / B3 Whether to support the use of a table for FDD used to interpret the PRACH configuration index provided by the RACH configuration for SBFD Whether or not to support determining the table used to interpret the PRACH configuration index provided by the RACH configuration for SBFD based on the value of the PRACH configuration index (option 5-4-2 in operation example 5-4) Whether or not to support the determination of the table used to interpret the PRACH configuration index provided by the RACH configuration for SBFD based on explicit parameters included in the RACH configuration for SBFD (option 5-4-3 in operation example 5-4) Whether or not to support the table instruction used to interpret the PRACH configuration index provided by the RACH configuration for SBFD (option 5-4-3 in operation example 5-4) Whether or not to support the operation of selecting RO based on SBFD RACH configuration in non-SBFD symbols (Operation Example 7) In Example 7, whether or not at least one of Alt 7-1 to Alt 7-5 is supported Whether separate power control is supported between non-SBFD symbols and SBFD symbols for the RO selected by the SBFD RACH configuration

[0420] (5) Actions and Effects According to the above-described embodiment, the UE 200 can recognize the numbering of SSB indices in SBFD while maintaining a common understanding with the Legacy UE regarding the numbering of SSB indices in non-SBFD.

[0421] According to the above-described embodiment, the UE 200 determines the time resource of the RO based on parameters assuming SBFD (Operation Example 5). With such a configuration, the mechanism for determining the time resource of the RO is clarified, and the legacy table can be appropriately supplemented.

[0422] According to the above-described embodiment, UE 200 assumes at least one of a parameter related to a frequency resource of an RO and a parameter related to a window (RAR window or collision resolution window) as a parameter included in a RACH configuration for SBFD that assumes SBFD (Operation Example 6-3, Operation Example 6-6). Such a configuration clarifies the details of the parameters included in a RACH configuration for SBFD that assumes SBFD, and enables appropriate execution of random access configured by the RACH configuration for SBFD.

[0423] According to the above-described embodiment, the UE 200 determines whether to select an RO for a non-SBFD symbol based on the RACH configuration for SBFD (Operation Example 7). Such a configuration clarifies whether the RACH configuration for SBFD (the RO selected based on the RACH configuration) is valid, and therefore, when the legacy RACH configuration and the RACH configuration for SBFD are assumed, it is possible to appropriately select a valid RO for a non-SBFD symbol.

[0424] According to the above-described embodiment, the UE 200 performs separate power control between the non-SBFD symbol and the SBFD symbol for the RO selected based on the RACH configuration for SBFD (Operation Example 8). With this configuration, assuming a case in which a valid RO is selected based on the RACH configuration for SBFD, it is possible to appropriately perform power control for each of the non-SBFD symbol and the SBFD symbol.

[0425] (6) Other embodiments The present invention has been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0426] The above-described operation example may be applied to the UE 200 in the RRC_IDLE mode or the UE 200 in the IN_ACTIVE mode.

[0427] The above-described operation example may be applied to CBRA or CFRA.

[0428] In the above disclosure, different operation examples or options may be applied to UE 200 in RRC_IDLE mode and UE 200 in IN_ACTIVE mode.

[0429] In the above disclosure, different operation examples or options may be applied to UE 200 in RRC_IDLE mode and UE 200 in IN_ACTIVE mode.

[0430] In the above disclosure, different operation examples or options may be applied for each RA type (e.g., CBRA / CFRA), different operation examples or options may be applied for each RACH triggering method (e.g., RACH initiated by PDCCH order / MAC entity / RRC), and different operation examples or options may be applied for each RACH purpose (RACH for initial access / SI request / handover).

[0431] In the above disclosure, different operation examples or options may be applied for each frequency range (eg, FR1 / FR2).

[0432] The PRACH repetitions in the above-described fourth operational example may be replaced with repetitions of other messages in RA, for example, Msg3 PUSCH repetitions or HARQ-ACK PUCCH for Msg4 repetitions.

[0433] The above-described operation examples may be combined and applied in a composite manner, as long as no contradiction occurs.

[0434] The block diagrams used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

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

[0436] For example, the base station 100, the terminal 200, and the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 19 is a diagram illustrating an example of the hardware configuration of the base station 100 and the terminal 200 according to an embodiment of the present disclosure. The base station 100 and the terminal 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

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

[0438] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

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

[0440] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, although the above-mentioned various processes have been described as being executed by one processor 1001, 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 programs may be transmitted from a network via a telecommunications line.

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

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

[0443] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD), for example.

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

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

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

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

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

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

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

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

[0452] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

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

[0454] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

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

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

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

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

[0463] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head, RRH)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication service within this coverage.

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

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

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

[0467] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0468] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the aspects / embodiments of the present 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, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 200 may be configured to have the functions of the base station 100 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0469] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 100 may be configured to have the functions of the terminal 200 described above.

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

[0471] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0472] The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0473] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an Electronic Control Unit (ECU).

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

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

[0476] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

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

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

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

[0481] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0482] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

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

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

[0485] The reference signal may also be abbreviated as RS, and may be called a pilot depending on the applicable standard.

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

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

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

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

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

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

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

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

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

[0495] 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 minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1 to 13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

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

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

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

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

[0502] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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

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

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

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

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

[0509] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0512] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0513] (Addendum) The above disclosure may be expressed as follows:

[0514] A first feature is a terminal including: a communication unit that communicates with a cell to which a duplexing method is applied, which is capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band; and a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplexing method based on a second random access channel setting that assumes the duplexing method.

[0515] A second feature is the terminal of the first feature, wherein whether to select the random access opportunity based on the second random access channel configuration is determined based on a rule that is predefined, set or instructed by a network, or determined based on a parameter set by the second random access channel configuration, or based on a relationship between a parameter set by a first random access channel configuration that does not assume the duplex mode and a parameter set by the second random access channel configuration.

[0516] A third feature is the terminal according to the first feature or the second feature, wherein the control unit performs separate power control between the first symbol and the second symbol that does not assume the duplexing method, for the random access opportunity selected based on the second random access channel configuration.

[0517] A fourth feature is a base station including: a communication unit that communicates with a terminal via a duplex cell that can perform simultaneous communication of an uplink signal and a downlink signal within a time division duplex band; and a control unit that assumes that, in a first symbol that does not assume the duplex method, the terminal determines whether to select the random access opportunity based on a second random access channel setting that assumes the duplex method.

[0518] A fifth feature is a wireless communication system including a terminal and a base station, wherein the terminal includes: a communication unit that communicates with a cell to which a duplexing scheme is applied that can perform simultaneous communication of uplink signals and downlink signals within a time division duplex band; and a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplexing scheme based on a second random access channel setting that assumes the duplexing scheme.

[0519] A sixth feature is a wireless communication method including: a step of communicating with a cell to which a duplexing method capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band is applied; and a step of determining, in a first symbol that does not assume the duplexing method, whether to select the random access opportunity based on a second random access channel setting that assumes the duplexing method. [Explanation of symbols]

[0520] 10. Wireless communication systems 20 NG-RAN 100 base stations 110 Radio signal transmitter / receiver 120 control section 200 devices 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a communication unit that communicates with a cell to which a duplex system capable of simultaneously communicating an uplink signal and a downlink signal is applied within a time division duplex band; a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplex mode based on a second random access channel configuration that assumes the duplex mode.

2. 2. The terminal according to claim 1, wherein whether to select the random access opportunity based on the second random access channel configuration is determined based on a rule that is predefined, set or instructed by a network, or determined based on a parameter set by the second random access channel configuration, or determined based on a relationship between a parameter set by a first random access channel configuration that does not assume the duplex mode and a parameter set by the second random access channel configuration.

3. 2. The terminal according to claim 1, wherein the control unit performs separate power control between the first symbol and the second symbol that does not assume the duplex mode for the random access opportunity selected based on the second random access channel configuration.

4. a communication unit that communicates with a terminal via a duplex cell that can simultaneously communicate an uplink signal and a downlink signal within a time division duplex band; a control unit that assumes that, in a first symbol that does not assume the duplex mode, the terminal decides whether to select the random access opportunity based on a second random access channel configuration that assumes the duplex mode.

5. A terminal and a base station are provided, The terminal a communication unit that communicates with a cell to which a duplex system capable of simultaneously communicating an uplink signal and a downlink signal is applied within a time division duplex band; a control unit that determines whether to select the random access opportunity in a first symbol that does not assume the duplex mode based on a second random access channel configuration that assumes the duplex mode.

6. A step of communicating with a cell to which a duplex system capable of simultaneously communicating an uplink signal and a downlink signal is applied within a time division duplex band; and determining whether to select the random access opportunity in a first symbol that does not assume the duplex mode based on a second random access channel configuration that assumes the duplex mode.

Images