terminal

Abstract

To provide a terminal capable of appropriately selecting an RO even in separate SSB-to-RO mapping.SOLUTION: A terminal includes a reception part for receiving downlink control information for triggering random access, a control part for selecting at least one between a first random access occasion set on the basis of first random access channel setting to a first time unit that applies time division duplex and a second random access occasion set on the basis of second random access channel setting to a second time unit that can use a plurality of subbands constituting the time division duplex on the basis of a mask index included in the downlink control information, and a transmission part for transmitting a preamble of the random access in the selected first random access occasion or the second random access occasion.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a terminal that supports subband non-overlapping full duplex (SBFD). [Background technology]

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

[0003] Release 18 discusses a duplexing scheme that enables simultaneous use of 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

[0007] A cell formed by a gNB that supports SBFD operation may be accessed by UEs that support SBFD operation, or by UEs that do not support SBFD operation. Hereinafter, the former are referred to as SBFD-aware UEs, and the latter are referred to as Legacy UEs. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol, but a Legacy UE recognizes this SBFD symbol as a normal DL symbol.

[0008] It is desirable that SBFD-aware UE and Legacy UE have the same understanding of SSB-to-RO mapping. For this reason, separate RACH configurations may be applied to SBFD symbols and non-SBFD symbols. Hereinafter, the RACH configuration applied to SBFD symbols is also referred to as additional RACH configuration, and the RACH configuration applied to non-SBFD symbols is also referred to as legacy RACH configuration. As a result, an RO (additional RO) overlapping an SBFD symbol (UL subband within an SBFD symbol) and an RO (legacy RO) overlapping a non-SBFD symbol (FL symbol or DL ​​symbol) may be configured separately. In other words, an RO overlapping an SBFD symbol may be mapped to an SSB separately from an RO overlapping a non-SBFD symbol. Such SSB-to-RO mapping is called separate SSB-to-RO mapping.

[0009] In the PDCCH-order RA (PDCCH-order RACH) that triggers UE random access by DCI (DCI format 1_0), a PRACH mask index is used. As described in 3GPP TS38.212, the PRACH mask index is a field that indicates the RO (RO index) associated with the SSB indicated by the SSB index.

[0010] However, in separate SSB-to-RO mapping, two types of RACH configurations (additional RACH configuration / legacy RACH configuration) are applied, so it is unclear whether the PRACH mask index in the PDCCH-order RACH indicates an additional RO (RO index) or a legacy RO (RO index). Even in such a case, the UE must select an appropriate RO for PRACH transmission in the PDCCH-order RACH.

[0011] Therefore, an object of the present disclosure is to provide a terminal that can appropriately select an RO even in separate SSB-to-RO mapping.

[0012] One aspect of the disclosure is a terminal including: a receiver (radio signal transceiver 210) that receives downlink control information that triggers random access; a controller (controller 270) that selects, based on a mask index included in the downlink control information, at least one of a first random access opportunity that is set based on a first random access channel setting for a first time unit to which time division duplex is applied, and a second random access opportunity that is set based on a second random access channel setting for a second time unit in which multiple subbands that make up the time division duplex band are available; and a transmitter (radio signal transceiver 210) that transmits the random access preamble at the selected first random access opportunity or the selected second random access opportunity. [Brief explanation of the drawings]

[0013] [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 an example of an extended PRACH mask index table. [Figure 18] FIG. 18 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 19] FIG. 19 is a diagram illustrating an example of the configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] (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.

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

[0017] 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."

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

[0019] 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: FR1: 410MHz~7.125GHz FR2-1: 24.25GHz~52.6GHz ·FR2-2: More than 52.6GHz~71GHz

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

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

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

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

[0024] (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.

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

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

[0027] The radio signal transceiver 210 of the embodiment can transmit a preamble for initiating random access at a valid random access opportunity. The random access opportunity may be interpreted as a timing for transmitting a preamble for initiating 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.

[0028] The radio signal transceiver 210 of the embodiment can receive downlink control information (DCI) that triggers random access. Such random access may be called a PDCCH order(ed) RACH or a PDCCH order(ed) PRACH. The DCI format of this DCI may be DCI format 1_0. This DCI may include a 4-bit PRACH mask index (also simply referred to as a mask index). As described in 3GPP TS38.212, the PRACH mask index is a field indicating an RO (RO index) associated with an SSB indicated by an SSB index. The PRACH mask index indicates an RO index for each mapping cycle as shown in Table 7.4-1 of 3GPP TS38.321. Table 7.4-1 of 3GPP TS38.321 will be described later.

[0029] The radio signal transmitting / receiving unit 210 of the embodiment can receive the DCI that triggers random access using either a non-SBFD symbol or an SBFD symbol. Note that the non-SBFD symbol may be interpreted as a first time unit to which time division duplexing (TDD) is applied. The SBFD symbol may be interpreted as a second time unit in which multiple subbands constituting a TDD band can be used.

[0030] The radio signal transmitting and receiving unit 210 of the embodiment can transmit a random access preamble at the first random access opportunity or the second random access opportunity selected by the control unit 270. Furthermore, the radio signal transmitting and receiving unit 210 of the embodiment can transmit a random access preamble at both the first random access opportunity and the second random access opportunity selected by the control unit 270.

[0031] The first random access opportunity may be interpreted as a random access opportunity (RO) configured based on a first random access channel configuration (legacy RACH configuration, described later) for a non-SBFD symbol. The second random access opportunity may be interpreted as a random access opportunity (RO) configured based on a second random access channel configuration (additional RACH configuration, described later) for an SBFD symbol. The first random access opportunity may also be referred to as a legacy RO. The second random access opportunity may also be referred to as an additional RO. The additional RACH configuration may also be referred to as a RACH configuration for SBFD or an additional RACH configuration for SBFD.

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

[0033] 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. DFT-S-OFDM may also be used not only for the uplink (UL) but also for the downlink (DL).

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

[0035] 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).

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

[0037] 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).

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

[0039] 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).

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

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

[0042] 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. In the latter case, 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.

[0043] When a legacy RACH configuration and a RACH configuration for SBFD are included in one RACH configuration, the control unit 270 of 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.

[0044] On the other hand, the control unit 270 of the embodiment can also determine valid ROs and invalid ROs 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.

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

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

[0047] 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).

[0048] The control unit 270 of the embodiment can select at least one of a first random access opportunity (legacy RO) set based on a first random access channel configuration (legacy RACH configuration) for a first time unit (non-SBFD symbol) to which TDD is applied, and a second random access opportunity (additional RO) set based on a second random access channel configuration (additional RACH configuration) for a second time unit (SBFD symbol) in which multiple subbands constituting the TDD band can be used, based on a mask index included in the above-mentioned DCI. Note that the legacy RO / additional RO selected here may be interpreted as a valid RO.

[0049] The control unit 270 of the embodiment can select the earlier random access opportunity in terms of time between the first random access opportunity and the second random access opportunity. Also, the control unit 270 of the embodiment can select the later random access opportunity in terms of time between the first random access opportunity and the second random access opportunity.

[0050] The control unit 270 of the embodiment can select one of the first random access opportunity and the second random access opportunity based on the configuration of the radio resource control layer (RRC).

[0051] The control unit 270 of the embodiment can select the first random access opportunity when the radio signal transmitting / receiving unit 210 receives DCI that triggers random access in the first time unit (non-SBFD symbol). On the other hand, the control unit 270 of the embodiment can select the second random access opportunity when the radio signal transmitting / receiving unit 210 receives DCI that triggers random access in the second time unit (SBFD symbol).

[0052] The control unit 270 of the embodiment can select both the first random access opportunity and the second random access opportunity.

[0053] (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.

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

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

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

[0057] 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).

[0058] The wireless signal transmitting / receiving unit 110 of the embodiment can receive information transmitted by the above-described wireless signal transmitting / receiving unit 210. In addition, the wireless signal transmitting / receiving unit 110 can transmit information received by the above-described wireless signal transmitting / receiving unit 210.

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

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

[0061] (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.

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

[0063] 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).

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

[0065] Below, we will briefly explain the terms related to SBFD. SBFD symbol: Symbol to which SBFD sub-band is set 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 flexibly (FL) by the tdd-UL-DL-Configuration Common or tdd-UL-DL-Configuration Dedicated, in which the SBFD subband is configured. Non-SBFD symbol: Symbol for which SBFD sub-band is not set DL (or semi-static D) symbol: A symbol designated DL by TDD-UL-DL-Configuration Common and / or TDD-UL-DL-Configuration Dedicated. UL (or semi-static U) symbol: A symbol designated by UL by TDD-UL-DL-Configuration Common and / or TDD-UL-DL-Configuration Dedicated. FL (or semi-static F, or flexible) symbol: A symbol designated as flexible (FL) by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated.

[0066] (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.

[0067] In separate SSB-to-RO mapping, two types of RACH configurations (additional RACH configuration / legacy RACH configuration) are applied, so it was unclear whether the PRACH mask index in the PDCCH-order RACH indicated an additional RO (RO index) or a legacy RO (RO index). Even in such a case, the UE had to select an appropriate RO for PRACH transmission in the PDCCH-order RACH.

[0068] (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.

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

[0070] The extended rule for determining a valid RO may be configured by the following conditions for determining a valid RO. 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.

[0071] 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)).

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

[0073] That is, 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, valid ROs may include the following ROs:

[0074] 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. 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)

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

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

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

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

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

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

[0081] (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).

[0082] (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.

[0083] In option 1, the UE 200 may operate as follows. Step 1: Determine the RO based on the legacy RACH configuration. Step 2: From the determined ROs, determine the valid ROs according to the legacy rules. Step 3: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. ·Step 4: Transmit the selected preamble at the selected RO.

[0084] In Step 4 above, the following extensions are possible: 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. Example 1-2: The UE 200 does not assume valid ROs that overlap with RBs outside the UL subband within the SBFD FL symbol. 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. 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. 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). 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.

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

[0086] In option 2, the UE 200 may operate as follows. Step 1: Determine the RO based on the legacy RACH configuration. Step 2: From the determined RO, determine the valid RO by the extension rule. Step 3: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. ·Step 4: Transmit the selected preamble at the selected RO.

[0087] In Step 2 described above, the extended rule for determining valid ROs explained 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.

[0088] In Step 4 above, the following extensions are possible: 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). 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. 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). 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 the valid RO.

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

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

[0091] In option 3, the UE 200 may operate as follows. Step 1: Determine the RO based on the legacy RACH configuration. 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. Step 2A-2: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. 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. Step 2B-2: The determined additional valid ROs are mapped to SSB indices. Step 3: Transmit the selected preamble at the selected RO.

[0092] 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 valid ROs described in (4.2). This additional valid RO may be called an SBFD-valid RO.

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

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

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

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

[0097] Analysis: According to Option 3, valid ROs determined by the legacy rules are commonly understood by legacy UEs and SBFD-aware UEs. In addition, additional valid ROs determined by the 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.

[0098] (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.

[0099] In option 4, the UE 200 may operate as follows. Step 1A: Determine the RO based on the legacy RACH configuration. Step 2A: From the determined ROs, determine the valid ROs according to the legacy rules. Step 3A: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. Step 1B: Determine the RO based on the RACH configuration for SBFD. Step 2B: Determine a valid RO according to the legacy rule from the RO determined based on the RACH configuration for SBFD. Step 3B: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. ·Step 4: Transmit the selected preamble at the selected RO. Note that since an SBFD-aware UE uses only the RACH configuration for SBFD, Steps 1A to 3A may be omitted.

[0100] 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. RACH configuration for SBFD may be configured in the following IE: Alt-1: May be set in additionalRACH-ConfigList. For example, the corresponding feature combination may be for "SBFD". 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. · 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).

[0101] Furthermore, the following variations may be realized based on the RACH configuration for SBFD. · 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. · Alt-b: The RACH configuration does not assume that the RO is within or overlaps a non-SBFD symbol. 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.

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

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

[0104] Analysis: According to 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.

[0105] (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).

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

[0107] (4.3.2.1) Option 1 Based on the rach-ConfigBFR conventionally configured in BeamFailureRecoveryConfig and / or the cfra conventionally configured in RACH-ConfigDedicated and / or the 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).

[0108] (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.

[0109] (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). 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. 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.

[0110] (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.

[0111] 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."

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

[0113] 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).

[0114] (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.

[0115] (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.

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

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

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

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

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

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

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

[0123] (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.

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

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

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

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

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

[0129] (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).

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

[0131] 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}.

[0132] 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}.

[0133] 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}.

[0134] (4.3.5) Example 5 Next, a description will be given of operation example 5. Operation example 5 is an operation example in which the UE correctly recognizes whether the mask index in the PDCCH-ordered RACH indicates the RO index of additional RO or the RO index of legacy RO.

[0135] In this specification, a legacy RO refers to a valid RO of a UL or FL symbol that is configured by a legacy RACH configuration based on a legacy RO validation rule for determining a valid RO.

[0136] In this specification, additional RO indicates any of the following: If no additional RACH configuration for SBFD is configured, the valid RO of the SBFD UL symbol or the valid RO across the SBFD UL symbol and the SBFD FL symbol is set by the legacy RACH configuration. When an additional RACH setting for SBFD is configured, the valid RO of the SBFD symbol set by the additional RACH setting for SBFD

[0137] In this specification, "RACH setting" and "PRACH setting" are interchangeable, and "RO" and "PRACH opportunity" are interchangeable.

[0138] (4.3.5.1) Option 1 In Option 1, the terms "additional RO corresponding to PRACH mask index" and "legacy RO corresponding to PRACH mask index" may be interpreted as follows. Additional RO corresponding to PRACH mask index: The next available PRACH opportunity among the additional ROs corresponding to the selected SSB, which is allowed by the conditions of the PRACH mask index field indicated in the PDCCH order. Legacy RO corresponding to PRACH mask index: The next available PRACH opportunity among the legacy ROs corresponding to the selected SSB, as allowed by the conditions of the PRACH mask index field indicated in the PDCCH order.

[0139] Option 1 is an aspect in which a conventional PRACH mask index table is reused in a PDCCH ordered PRACH. Note that the conventional PRACH mask index table may also be referred to as a conventional PRACH mask value table. The conventional PRACH mask index table may be interpreted as being that shown in Table 7.4-1 of 3GPP TS38.321. Specifically, when the PRACH mask index (code point) is X, the allowed PRACH opportunities of the SSB may be indicated as follows: · If X=0, the allowed SSB PRACH opportunities are all PRACH opportunities. · For X=1 to 8, the allowed SSB PRACH opportunity is the PRACH opportunity with index X. · For X=9, the allowed SSB PRACH opportunities are all even-indexed PRACH opportunities. · When X=10, the allowed SSB PRACH opportunities are all odd-indexed PRACH opportunities. ·X=11~15 is reserved.

[0140] Table 7.4-1 of 3GPP TS38.321 may be interpreted as a table in which the underlined parts in the table shown in FIG. 17 (described later) have been deleted and the PRACH mask indexes (code points) 11 to 15 in the table have been replaced with Reserved.

[0141] In Option 1, the RO type (additional RO / legacy RO) of the RO mapped to the PRACH mask index (codepoint) is not fixed, i.e., each PRACH mask index codepoint may be applied to either an additional RO or a legacy RO.

[0142] As option 1-1, the UE 200 may select one RO for PRACH transmission from among an additional RO corresponding to a PRACH mask index and a legacy RO corresponding to a PRACH mask index. Specifically, the UE 200 may select one RO as follows.

[0143] Option 1-1a: The UE 200 selects an earlier RO or a later RO (in terms of time) from among an additional RO corresponding to a PRACH mask index and a legacy RO corresponding to a PRACH mask index. Variation: UE200 selects the earlier or later RO (in time) that has the smallest time offset after the PDCCH order (the offset may be predetermined, configured by RRC, or determined based on a predetermined rule).

[0144] Option 1-1b: The UE 200 selects the RO based on its own implementation.

[0145] Option 1-1c: The UE 200 selects an RO based on an RRC configuration. For example, whether to use a legacy RO or an additional RO for a PDCCH-ordered PRACH may be configured by the RRC. For example, if a new parameter (e.g., sbfd-RO-type-pdcch-order) is set (to a predetermined value such as 'sbfd'), the UE 200 may select an additional RO corresponding to the PRACH mask index. Otherwise, the UE 200 may select a legacy RO corresponding to the PRACH mask index.

[0146] Option 1-1d: The UE 200 selects an RO based on an explicit DCI field indication, for example, a bit in the Reserved field may indicate either legacy RO or additional RO. For example, if the bit value is 0 (or conversely, if it is not 0 (1)), the UE 200 may select the additional RO corresponding to the PRACH mask index. Otherwise, the UE 200 may select the legacy RO corresponding to the PRACH mask index.

[0147] Option 1-1e: The UE 200 selects an RO based on predetermined / configured rules. For example, if the PDCCH that triggers the PRACH transmission is transmitted in an SBFD symbol, the UE 200 may select an additional RO corresponding to the PRACH mask index. Otherwise, the UE 200 may select a legacy RO corresponding to the PRACH mask index.

[0148] As option 1-2, the UE 200 may perform PRACH transmission in both the additional RO corresponding to the PRACH mask index and the legacy RO corresponding to the PRACH mask index.

[0149] (4.3.5.2) Option 2 Option 2 extends the conventional PRACH mask index table for PDCCH-ordered PRACH. As shown in Figure 17, in the extended PRACH mask index table, each PRACH mask index codepoint is applied to an additional RO or a legacy RO. Note that the extended PRACH mask index table may also be referred to as an extended PRACH mask table.

[0150] As shown in FIG. 17, in the extended PRACH mask index table, some code points (e.g., 0 to 10) may be mapped to legacy ROs, and other code points (e.g., 11 to 15) may be mapped to additional ROs. Variation: The number (maximum number) of code points that indicate legacy RO / additional RO may be defined by the standard. Variation: The code point value (number) indicating legacy RO / additional RO may be defined by a standard. Variation: The values ​​corresponding to each code point (i.e., the allowed PRACH opportunities in the right column of Figure 17) (indicating legacy RO / additional RO) may be defined by the standard or set by the RRC. For example, in the conventional PRACH mask index table (Table 7.4-1 of 3GPP TS38.321), existing valid code points (0 to 10) may be mapped to legacy ROs, and reserved code points (11 to 15) may be mapped to additional ROs.

[0151] In Option 2, the RO type (additional RO / legacy RO) of the RO used for PRACH transmission is implicitly determined by the PRACH mask index field. For example, in the extended PRACH mask index table shown in Fig. 17, when PRACH mask index codepoints 0 to 11 are indicated, it is implied that legacy RO is indicated, and when PRACH mask index codepoints 12 to 15 are indicated, it is implied that additional RO is indicated.

[0152] Note that the values ​​of each row / entry shown in Fig. 17 are merely examples and may be other values. Each row / entry may indicate either additional RO or legacy RO. For example, all of the extended PRACH mask index codepoints (0 to 15) may indicate only either additional RO or legacy RO. In that case, the extended PRACH mask index codepoints 11 to 15 may be reserved, similar to the conventional PRACH mask index table (Table 7.4-1 of 3GPP TS38.321).

[0153] (4.3.6) UE capability To apply the above-described operation examples 1 to 5, new UE capabilities and report signaling (and RRC settings) shown below may be defined for each UE / FR / FC, etc. 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

[0154] (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.

[0155] According to the above-described embodiment, the UE 200 can appropriately select an RO even in separate SSB-to-RO mapping.

[0156] (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.

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

[0158] The UE may report the following capabilities to the BS: - Capability information for each operation example - Information on the capabilities of each option in the operation example, or the capabilities of the option combination - Capability information for each modification in the operation example, or capability information for a combination of modifications

[0159] The UE can report the above capability information for each frequency, specifically, for each UE, for each FR1, for each FR2, for each FR2-1, for each FR2-2, for each FR3, for each SCS, for each band, for each BC, for each FC, or for each FSPC.

[0160] The UE can report the capability information for each cell, specifically, for each UE / cell / each TDD and FDD.

[0161] In the present disclosure, whether or not to apply an operation example / which operation example to apply and / or which option or modification to use may be any of the following. Set by upper layer parameters. Determined by relevant higher layer parameters. · As directed by MAC CE or DCI. Determined based on one or more UE capabilities. - To be stated in the specifications. - Based on the conditions stated in the specifications. Determined by higher layer parameter configuration / MAC CE / DCI and reported UE capability (combination of the above decisions).

[0162] In the present disclosure, multiple options and variations may be combined into one option / variation.

[0163] In the present disclosure, the measurement RS may be a QCL resource RS in an active TCI state / instructed TCI state.

[0164] In the present disclosure, the UE may receive the following types of information from the network (in the present disclosure, the network can be referred to as a gNB): Information via higher layer signaling (e.g. RRC messages, LPP messages) MAC CE MAC CE with new LCID in subheader Extensions to existing MAC CE (e.g., introduction of new octets) DCI DCI Fields: Existing / Newly introduced DCI fields RNTI: DCI with CRC scrambled by the existing / newly introduced RNTI DCI Formats: Existing / Newly introduced DCI formats A combination of these

[0165] In the present disclosure, the UE may receive information from the network with the following periodicity types: ·Periodic Semi-persistent (triggered by UE or gNB instruction) Aperiodic (triggered by UE or gNB instructions)

[0166] In the present disclosure, the UE may receive information from the network on the following QCL rules: QCL type A QCL type B QCL type C QCL type D

[0167] In the present disclosure, the QCL resource RS of each QCL type may be as follows: SSB ·CSI-RS with / without repetition TRS PDCCH / PDSCH DMRS

[0168] In the present disclosure, information from the network may be set / instructed as follows: UE common / UE dedicated Cell specific / Cell common Per UE / Per CC / Per BWP / Per band / Per cell / Per CG

[0169] In the present disclosure, the UE may report information to the network in the following types (in the present disclosure, the network can be referred to as a gNB): Information via higher layer signaling (e.g. RRC messages, LPP messages) MAC CE MAC CE with new LCID in subheader Extensions to existing MAC CEs (e.g., introduction of new ocsets) UCI UCI on PUCCH or PUSCH A combination of these

[0170] In the present disclosure, the UE may report information to the network with the following periodicity types: ·Periodic Semi-persistent (triggered by UE or gNB instruction) Aperiodic (triggered by UE or gNB instructions)

[0171] The above-described operation examples and options may be combined and applied in a composite manner unless a contradiction occurs.

[0172] For example, when option 1 and option 2 in operation example 5 are combined, it may be determined in advance which option is to be prioritized. For example, if it is determined that option 1 is to be prioritized, UE 200 may select an RO according to each option of option 1, ignoring the additional RO / legacy RO indicated by the PRACH mask index of option 2. On the other hand, if it is determined that option 2 is to be prioritized, UE 200 may select the additional RO / legacy RO indicated by the PRACH mask index of option 2 without performing the operation defined in each option of option 1.

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

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

[0175] 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. 18 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.

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

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

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

[0179] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, although the above-described 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.

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

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

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

[0183] 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).

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

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

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

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

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

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

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

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

[0192] 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).

[0193] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0209] Fig. 19 shows an example of the configuration of a vehicle 2001. As shown in Fig. 19, 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.

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

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

[0212] 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).

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

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

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

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

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

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

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

[0220] 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)).

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

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

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

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

[0225] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0245] 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."

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

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

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

[0249] 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."

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

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

[0252] A first feature may be a terminal including: a receiving unit that receives downlink control information that triggers random access; a control unit that selects, based on a mask index included in the downlink control information, at least one of a first random access opportunity that is set based on a first random access channel setting for a first time unit to which time division duplex is applied, and a second random access opportunity that is set based on a second random access channel setting for a second time unit in which a plurality of subbands that constitute a band of the time division duplex are available; and a transmitting unit that transmits the random access preamble at the selected first random access opportunity or the selected second random access opportunity.

[0253] A second feature may be that, in the first feature, the control unit selects an earlier random access opportunity from the first random access opportunity and the second random access opportunity.

[0254] A third feature may be the terminal in the first feature, wherein the control unit selects a later random access opportunity from the first random access opportunity and the second random access opportunity.

[0255] A fourth feature may be, in the terminal of the first feature, the control unit selecting one of the first random access opportunity and the second random access opportunity based on a configuration of a radio resource control layer.

[0256] A fifth feature may be, in the terminal of the first feature, the receiver unit receiving the downlink control information in the second time unit, and the controller selecting the second random access opportunity.

[0257] A sixth feature may be, in the terminal of the first feature, wherein the control unit selects both the first random access opportunity and the second random access opportunity, and the transmission unit transmits the random access preamble at both the selected first random access opportunity and the selected second random access opportunity. [Explanation of symbols]

[0258] 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 receiving unit for receiving downlink control information that triggers random access; a control unit that selects, based on a mask index included in the downlink control information, at least one of a first random access opportunity that is set based on a first random access channel configuration for a first time unit to which time division duplex is applied, and a second random access opportunity that is set based on a second random access channel configuration for a second time unit in which a plurality of subbands that constitute a band of the time division duplex are available; a transmitter configured to transmit the random access preamble at the selected first random access opportunity or the selected second random access opportunity; A terminal comprising:

2. the control unit selects an earlier random access opportunity from the first random access opportunity and the second random access opportunity. The terminal according to claim 1 .

3. the control unit selects a later random access opportunity from the first random access opportunity and the second random access opportunity. The terminal according to claim 1 .

4. the control unit selects one of the first random access opportunity and the second random access opportunity based on a configuration of a radio resource control layer. The terminal according to claim 1 .

5. the receiving unit receives the downlink control information in the second time unit; The control unit selects the second random access opportunity. The terminal according to claim 1 .

6. the control unit selects both the first random access opportunity and the second random access opportunity; The transmitter transmits the random access preamble at both the selected first random access opportunity and the selected second random access opportunity. The terminal according to claim 1 .

Images