Terminal

Abstract

This terminal comprises: a receiving unit that receives downlink control information that triggers random access; a control unit that, on the basis of a mask index included in the downlink control information, selects at least one of a first random access opportunity set on the basis of a first random access channel setting for a first time unit to which time division duplexing is applied, and a second random access opportunity set on the basis of a second random access channel setting for a second time unit in which a plurality of sub-bands constituting a band of the time division duplexing is available; and a transmitting unit that transmits the random access preamble in the selected first random access opportunity or second random access opportunity.

Description

Terminal

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

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)). Furthermore, it is also proceeding with the specification of the next - generation mobile communication systems called Beyond 5G, 5G Evolution or 6G.

[0003] In Release 18, a duplexing method that enables simultaneous use of the downlink (DL) and the uplink (UL) by using a plurality of sub - bands that constitute the time - division duplex (TDD) band is being discussed. Such a duplexing method is called subband non - overlapping full duplex (SBFD). Note that the symbol to which SBFD is applied may be called an SBFD symbol. Also, in the SBFD symbol, the sub - band used for DL may be called a DL sub - band, and the sub - band used for UL may be called a UL sub - band.

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

[0005] The terminal (hereinafter also referred to as the user device (UE)) determines random access opportunities (ROs) to send a preamble to initiate random access (RA) based on the RACH settings from the base station (hereinafter also referred to as the gNodeB (gNB)). Furthermore, from among the determined ROs, it determines which ROs are valid (and which are invalid). In addition, valid ROs are mapped to the index of the synchronization signal block (SSB index) based on the SSB-to-RO mapping.

[0006] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023

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

[0008] It is desirable that SBFD-aware UEs and Legacy UEs have the same understanding (recognition) of SSB-to-RO mapping. For this reason, separate RACH settings may be applied to SBFD symbols and non-SBFD symbols. In the following, the RACH settings applied to SBFD symbols will be referred to as additional RACH settings, and the RACH settings applied to non-SBFD symbols will be referred to as legacy RACH settings. This allows for separate settings for ROs that overlap with SBFD symbols (UL subbands within SBFD symbols) (additional ROs) and ROs that overlap with non-SBFD symbols (FL symbols or DL ​​symbols) (legacy ROs). In other words, ROs that overlap with SBFD symbols may be mapped to SSB separately from ROs that overlap with non-SBFD symbols. Such SSB-to-RO mapping is called separate SSB-to-RO mapping.

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

[0010] However, in separate SSB-to-RO mapping, two types of RACH settings (additional RACH settings / legacy RACH settings) are applied, making it unclear whether the PRACH mask index in PDCCH order RACH represents the additional RO (RO index) or the legacy RO (RO index). Even in such cases, the UE had to appropriately select the RO for PRACH transmission in PDCCH order RACH.

[0011] Therefore, this disclosure aims to provide a terminal that can appropriately select RO even in separate SSB-to-RO mapping.

[0012] One aspect of the disclosure is a terminal comprising: a receiving unit (wireless signal transmitting / receiving unit 210) that receives downlink control information that triggers random access; a control unit (control unit 270) that selects at least one of a first random access opportunity set based on a first random access channel setting for a first time unit to which time division duplexing is applied, and a second random access opportunity set based on a second random access channel setting for a second time unit in which a plurality of subbands constituting the time division duplexing band are available, based on a mask index included in the downlink control information; and a transmitting unit (wireless signal transmitting / receiving unit 210) that transmits the random access preamble in the selected first random access opportunity or the second random access opportunity.

[0013] Figure 1 is an overall schematic diagram of the wireless communication system. Figure 2 is a diagram showing the frequency range used in the wireless communication system. Figure 3 is a diagram showing an example of the configuration of wireless frames, subframes, slots, and symbols used in the wireless communication system. Figure 4 is a functional block diagram of a terminal. Figure 5 is a functional block diagram of a base station. Figure 6 is a diagram showing an example of SBFD slots / symbols. Figure 7 is a diagram showing an example of applying the extended rules for valid RO determination. Figure 8 is a diagram showing an example of applying the extended rules for valid RO determination. Figure 9 is a diagram showing an example of applying the extended rules for valid RO determination. Figure 10 is a diagram showing an example of applying the extended rules for valid RO determination. Figure 11 is a diagram showing an example of applying the extended rules for valid RO determination. Figure 12 is a diagram showing an example of SSB-RO mapping when the extended rules for valid RO determination are applied. Figure 13 is a diagram showing an example of SSB-RO mapping when the extended rules for valid RO determination are applied. Figure 14 is a diagram showing an example of SSB-RO mapping when the extended rules for valid RO determination are applied. Figure 15 is a diagram showing an example of SSB-RO mapping when the extended rules for valid RO determination are applied. Figure 16 shows an example of applying RACH repetition in SBFD symbols. Figure 17 shows an example of an extended PRACH mask index table. Figure 18 shows an example of a base station and terminal hardware configuration. Figure 19 shows an example of a vehicle configuration.

[0014] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0015] (1) Wireless communication system configuration The wireless communication system 10 shown in Diagram 1 is a wireless communication system that follows a method called 5G. On the other hand, wireless communication system 10 may also be a wireless communication system that follows a method called Beyond 5G, 5G Evolution, or 6G.

[0016] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates a more directional beam by controlling the wireless signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication with two base stations.

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

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

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

[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. 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] Furthermore, as shown in Figure 3, one slot in the wireless communication system 10 consists of 14 symbols. If this configuration is maintained, the larger (wider) the SCS becomes, the shorter the symbol period (and slot period). Note that the SCS is not limited to the frequencies shown in Figure 3, and may be other frequencies such as 480 kHz or 960 kHz.

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

[0024] (2) Functional block configuration of the wireless communication system (2.1) Functional block configuration of the terminal As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception 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 transmission / reception unit 260, and a control unit 270.

[0025] The wireless signal transceiver 210 transmits and receives wireless signals to and from the gNB 100. The wireless signal transceiver 210 may consist of a transmitting unit that transmits wireless signals to the gNB 100 and a receiving unit that receives wireless signals from the gNB 100. The wireless signal may include data or may be interpreted as data. Transmission may be interpreted as reporting, notifying, etc. Reception may be interpreted as setting, instructing, notifying, etc. Setting may be implemented by setting information (information element (IE)) of the wireless resource control (RRC) layer, and instruction may be implemented by control element (CE) or downlink control information (DCI) of the media access control (MAC) layer.

[0026] The wireless signal transceiver 210 of this embodiment can perform random access (RA) to the gNB100. Specifically, the wireless signal transceiver 210 can transmit a preamble (Msg1) to the gNB100. The RA may be a four-step random access using Msg1 to Msg4 (and HARQ-ACK PUCCH for Msg4), or a two-step random access using MsgA and MsgB.

[0027] The wireless signal transceiver 210 of this embodiment can transmit a preamble to initiate random access during a valid random access opportunity. A random access opportunity may be understood as the timing at which a preamble to initiate RA is transmitted. A random access opportunity may also be called a RACH Occasion (RO). ROs are set based on the RACH setting from gNB100. For information on valid ROs, please refer to the description of the control unit 270.

[0028] The wireless signal transceiver 210 of the embodiment can receive downlink control information (DCI) that triggers random access. Such random access may be called PDCCH order(ed) RACH or 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 called a mask index). The PRACH mask index is a field that indicates the RO (RO index) associated with the SSB indicated by the SSB index, as described in 3GPP TS38.212. The PRACH mask index indicates the 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 wireless signal transceiver 210 of this embodiment can receive the DCI that triggers random access as a non-SBFD symbol or as an SBFD symbol. 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 to which multiple subbands constituting the TDD band are available.

[0030] The wireless signal transmitting / receiving unit 210 of the embodiment can transmit a random access preamble during a first random access opportunity or a second random access opportunity selected by the control unit 270. Furthermore, the wireless signal transmitting / receiving unit 210 of the embodiment can transmit a random access preamble during 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 understood as a random access opportunity (RO) established based on the first random access channel setting for non-SBFD symbols (legacy RACH setting described later). The second random access opportunity may be understood as a random access opportunity (RO) established based on the second random access channel setting for SBFD symbols (additional RACH setting described later). The first random access opportunity may also be called legacy RO. The second random access opportunity may also be called additional RO. The additional RACH setting may also be called RACH setting for SBFD, or additional RACH setting for SBFD.

[0032] The amplifier section 220 consists of a Power Amplifier (PA) and a Low Noise Amplifier (LNA), among other components. The amplifier section 220 amplifies the wireless signal output from the wireless signal transmission / reception unit 210. The amplifier section 220 also amplifies the wireless signal output from the modulation / demodulation unit 230.

[0033] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB100). CP-OFDM / DFT-S-OFDM may be applied in the modulation / demodulation unit 230. Furthermore, DFT-S-OFDM may 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 to and from the gNB100, such as radio resource control (RRC) signaling.

[0035] The control signal / reference signal processing unit 240 performs processing on reference signals transmitted to and from the gNB100, such as the 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] Channels include control channels and data channels. Control channels include physical uplink control channels (PUCCH), physical downlink control channels (PDCCH), physical random access channels (PRACH), and physical broadcast channels (PBCH). Data channels include physical uplink sharing channels (PUSCH) and physical downlink sharing channels (PDSCH).

[0037] The encoding / decoding unit 250 performs data splitting / concatenation and coding / decoding for each predetermined communication destination (gNB100 or other gNB100).

[0038] Specifically, the encoding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data. The encoding / decoding unit 250 also divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs coding on the divided data.

[0039] The data transmission / reception unit 260 performs assembly / decomposition of data units (Protocol Data Units (PDUs) / Service Data Units (SDUs)) that constitute the data between each layer. The multiple layers include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer. The data transmission / reception unit 260 also performs error correction and retransmission control of the data based on the Hybrid Automatic Repeat Request (HARQ).

[0040] The control unit 270 controls the UE200. For example, the control unit 270 controls the transmission and reception of wireless signals by the wireless signal transmission / reception unit 210, amplification by the amplifier unit 220, data modulation / demodulation by the modulation / demodulation unit 230, signal processing by the control signal / reference signal processing unit 240, coding / decoding by the encoding / decoding unit 250, and assembly / disassembly of data units by the data transmission / reception unit 260.

[0041] The control unit 270 of this embodiment can determine the valid ROs and invalid ROs based on the RACH settings from the gNB100. Specifically, the control unit 270 determines which ROs will send a preamble from among the ROs set based on the RACH settings from the gNB100, and further determines which ROs are valid and which are invalid from among the determined ROs. For the rules for determining valid ROs, please refer to the description of the operation example.

[0042] The RACH configuration may include a legacy RACH configuration for a time unit (non-SBFD slot / symbol) to which time division duplex (TDD) is applied, and an RACH configuration for SBFD for a time unit (SBFD slot / symbol) that can utilize a plurality of sub-bands constituting the TDD band. The legacy RACH configuration and the RACH configuration for SBFD may be set in the UE200 as one RACH configuration, or may be set in the UE200 as individual configurations. In the latter case, when the UE200 is a Legacy UE, the legacy RACH configuration may be set, and when the UE200 is an SBFD-aware UE, the RACH configuration for SBFD may be set.

[0043] When the legacy RACH configuration and the RACH configuration for SBFD are included in one RACH configuration, the control unit 270 of the embodiment can determine valid RO and invalid RO in two steps. In this case, the control unit 270 first determines valid RO and invalid RO based on the legacy RACH configuration, and further determines 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 RO and invalid RO based on the RACH configuration for SBFD different from the legacy RACH configuration. In this case, the control unit 270 may ignore the legacy RACH configuration.

[0045] In this embodiment, if the control unit 270 determines valid ROs and invalid ROs in two stages, it can individually map the indices of the synchronization signal blocks (SSBs) to the valid ROs and any additional valid ROs. Furthermore, if the control unit 270 determines a valid RO based on an SBFD RACH setting different from the legacy RACH setting, it can map the SSB index to that valid RO. Note that the mapping of the SSB index to a valid RO (or additional valid RO) may be interpreted as the mapping of a valid RO (or additional valid RO) to an SSB index.

[0046] The control unit 270 in this embodiment may perform additional valid RO mapping based on the same mapping rules as the valid RO mapping. For details on the mapping rules, please refer to the description of the operation example.

[0047] The control unit 270 of the embodiment may map an additional valid RO to the same SSB index as the SSB index mapped to the first valid RO after the additional valid RO. Alternatively, the control unit 270 of the embodiment may map an additional valid RO to the same SSB index as the SSB index mapped to the last valid RO before the additional valid RO. Note that "after" and "before" may be understood as "after" and "before" in relation to slots / symbols. Also, "first" and "last" may be understood as "valid RO within the first and last slot / symbol" (see Figure 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 setting (legacy RACH setting) 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 setting (additional RACH setting) for a second time unit (SBFD symbol) that can utilize a plurality of sub-bands constituting the TDD band, based on the mask index included in the above-described DCI. Here, the selected legacy RO / additional RO may be regarded 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 setting of the radio resource control layer (RRC).

[0051] When the control unit 270 of the embodiment receives DCI for triggering random access by the radio signal transceiver unit 210 in the first time unit (non-SBFD symbol), it can select the first random access opportunity. On the other hand, when the control unit 270 of the embodiment receives DCI for triggering random access by the radio signal transceiver unit 210 in the second time unit (SBFD symbol), it can select the second random access opportunity.

[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) As shown in the functional block diagram 5 of the base station, the gNB100 comprises a radio signal transmitting and receiving unit 110 and a control unit 120.

[0054] The wireless signal transceiver 110 transmits and receives wireless signals to and from the UE 200. The wireless signal transceiver 110 may consist of a transmitting unit that transmits wireless signals to the UE 200 and a receiving unit that receives wireless signals from the UE 200. The wireless signal may include data, or may be interpreted as data. Transmission may be interpreted as setting, instruction, notification, etc. Reception may be interpreted as reporting, notifying, etc. Settings may be implemented by setting information (information elements (IE)) of the Wireless Resource Control (RRC) layer, and instructions may be implemented by control elements (CE) or downlink control information (DCI) of the Media Access Control (MAC) layer.

[0055] The wireless signal transmission / reception unit 110 of this embodiment can transmit SSB to the UE200 in order for the UE200 to map a valid RO in the RA.

[0056] The wireless signal transceiver 110 of the embodiment can transmit (set) RACH settings to the UE200. As described above, the RACH settings may include legacy RACH settings for time units (non-SBFD slots / symbols) to which time division duplexing (TDD) is applied, and SBFD RACH settings for time units (SBFD slots / symbols) in which multiple subbands constituting the TDD bands are available.

[0057] The wireless signal transceiver 110 of this embodiment can transmit a single RACH setting to the UE200, which includes a legacy RACH setting and an SBFD-aware RACH setting. On the other hand, the wireless signal transceiver 110 of this embodiment can transmit a legacy RACH setting to a Legacy UE and an SBFD-aware RACH setting to the UE200 (SBFD-aware UE).

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

[0059] The control unit 120 controls the gNB100. The control unit 120 controls, for example, the transmission and reception of wireless signals by the wireless signal transmission / reception unit 110. The control unit 120 also performs scheduling for the UE200.

[0060] The control unit 120 can control the handover (HO) of the UE200. HO may be understood as, for example, a transition from one gNB100 to which the UE200 is connected to another gNB100. Note that the gNB100 to which the UE200 is connected in HO may be interpreted as the cell or beam formed by the gNB100. Furthermore, HO may be interpreted as cell transition, cell change, beam change, or other similar terms.

[0061] (3) SBFD As shown in Figure 6, each slot / symbol may be subjected to SBFD. In addition to DL and UL, each slot / symbol may be set to Flexible (FL), which can be used as DL or UL, and then SBFD may be applied.

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

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

[0064] As shown in Figure 6, each subband (SBFD subband) that constitutes an SBFD slot / symbol is assigned either DL or UL. Hereafter, subbands assigned DL will also be called DL subbands, and subbands assigned UL will also be called UL subbands. 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. In other figures, slots / symbols marked with "F" are FL slots / symbols.

[0065] The following provides a brief explanation of terms related to SBFD. • SBFD symbol: A symbol in which an SBFD subband is set. • SBFD DL symbol: A symbol instructed to DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, in which an SBFD subband is set. • SBFD FL symbol: A symbol flexibly (FL) instructed by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, in which an SBFD subband is set. • non-SBFD symbol: A symbol in which an SBFD subband is not set. • DL (or semi-static D) symbol: A symbol instructed to DL by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated. • UL (or semi-static U) symbol: A symbol instructed to UL by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated. • FL (or semi-static F, or Flexible) Symbol: A symbol that is flexibly (FL) indicated by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated.

[0066] (4) Operation of the wireless communication system (4.1) Problems When considering a situation in a cell where SBFD-aware UEs and Legacy UEs are mixed, where ROs are set to SBFD symbols in common to the cell, there is a risk that the recognizable valid ROs may differ between SBFD-aware UEs and Legacy UEs. For example, when an RO is set to the UL subband of an SBFD symbol, an SBFD-aware UE recognizes (determines) the RO set to the UL subband as a valid RO, but a Legacy UE recognizes (determines) the same RO as an RO set to a DL symbol, i.e., an invalid RO. Consequently, there was a problem in that the numbering of the SSB index mapped to a valid RO was also recognized differently between SBFD-aware UEs and Legacy UEs.

[0067] In separate SSB-to-RO mapping, two types of RACH settings (additional RACH settings / legacy RACH settings) are applied, making it unclear whether the PRACH mask index in PDCCH order RACH represents the additional RO (RO index) or the legacy RO (RO index). Even in such cases, the UE had to appropriately select the RO for PRACH transmission in PDCCH order RACH.

[0068] (4.2) Extended Rules for Determining Valid ROs The extended rules for determining valid ROs will be explained with reference to Figures 7 to 11. The legacy rules for determining valid ROs will also be explained. In the figures, Legacy UE refers to a UE that cannot recognize SBFD symbols, and SBFD-aware UE refers to a UE that can recognize SBFD symbols. For example, for an SBFD symbol set as a DL symbol or FL symbol, a Legacy UE will consider it as a DL symbol or FL symbol, and an SBFD-aware UE will consider it as an SBFD symbol.

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

[0070] The extended rules for determining valid RO may consist of the conditions for determining valid RO shown below. Note that the extended rules for determining valid RO are rules for cells where SBFD operation is set on the gNB side. In the diagram, Cond-X corresponds to condition X.

[0071] Condition 1: Each symbol is a UL symbol. Condition 2: Each symbol is an FL symbol not configured for SSB. Condition 3: Each symbol is a UL symbol or an FL symbol 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 a 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 after the last (non-SBFD) DL symbol, and / or at least N_gap symbols after the last (non-SBFD) SSB symbol, and / or not preceding an SSB symbol within the same PRACH slot (for non-SBFD symbols) Condition 7: Does 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: Does not overlap with non-SBFD DL symbols or (non-SBFD) SSB symbols Condition 9: Does not overlap with RB outside the UL subband in SBFD symbols (e.g., SBFD DL symbols, and / or SBFD FL symbols, and / or SBFD SSB symbols)

[0073] In other words, a valid RO in the extended rules for determining a valid RO 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 set by the gNB. For example, a valid RO may include the following ROs:

[0074] ・Example 1: An RO that satisfies condition 1 (which will also be determined as a valid RO under legacy rules) ・Example 2: An RO that satisfies conditions 2 / 3 and condition 6 Example 2-1: If the parenthetical statement regarding non-SBFD does not apply under condition 6, it will also be determined as a valid RO under legacy rules Example 2-2: If the parenthetical statement regarding non-SBFD applies under condition 6, it may be determined as an invalid RO under legacy rules. This is because the conditions for determining a valid RO in this case are more relaxed. ・Example 3: An RO that satisfies conditions 2 / 3 and condition 9 (and condition 6) ・Example 4: An RO that satisfies condition 4 (and condition 6) ・Example 5: An RO that satisfies conditions 4 and condition 9 (and condition 6) ・Example 6: An RO that satisfies condition 5 (and condition 6) ・Example 7: An RO that satisfies conditions 5 and condition 9 (and condition 6) ・Example 8: An RO that satisfies condition 7 (and at least one of conditions 6 / 8) ・Example 9: An RO that satisfies conditions 7 and condition 9 (and at least one of conditions 6 / 8)

[0075] Figure 7 shows an example (Example A-1) where SBFD is applied to DL symbols. ROs that satisfy condition 4 (and not condition 9) and ROs that satisfy condition 1 are determined as valid ROs.

[0076] Figure 8 shows an example (Example A-2) where SBFD is applied to DL symbols. ROs that satisfy both condition 4 and condition 9, and ROs that satisfy condition 1, are determined to be valid ROs.

[0077] Figure 9 shows an example (Example B-1) where SBFD is applied to DL symbols and FL symbols. ROs that satisfy condition 4 (and not condition 9), ROs that satisfy condition 1, and ROs that satisfy conditions 3 and 6 are determined to be valid ROs.

[0078] Figure 10 shows an example (Example B-2) where SBFD is applied to DL symbols and FL symbols. ROs that satisfy condition 4 (when the SBFD symbol in condition 4 does not contain an SBFD FL symbol) and condition 9, ROs that satisfy condition 1, and ROs that satisfy conditions 3 and 6 are determined to be valid ROs.

[0079] Figure 11 shows an example (Example B-3) where SBFD is applied to DL symbols and FL symbols. ROs that satisfy condition 4 (when the SBFD symbol in condition 4 includes an SBFD FL symbol) and condition 9, ROs that satisfy condition 1, and ROs that satisfy conditions 3 and 6 are determined to be valid ROs.

[0080] (4.3) Example of Operation Based on the extended rules for determining valid RO described above, an example of operation will be explained.

[0081] (4.3.1) Operation Example 1 Operation Example 1 will be described with reference to Figures 12 to 15. Operation Example 1 is an example of determining valid RO for random access (RA) in RRC_IDLE mode or IN_ACTIVE mode, or for RA based on a cell common RACH setting (or a RACH setting instructed by SIB1).

[0082] (4.3.1.1) Option 1 Option 1 combines legacy RACH settings with legacy rules for determining valid ROs. The legacy RACH settings are RACH settings for non-SBFD symbols, and may be understood as settings that determine ROs specifically for non-SBFD symbols. Alternatively, RACH settings for SBFD symbols may be made based on the legacy RACH settings, or ROs specifically for SBFD symbols may be determined.

[0083] In Option 1, the UE200 may operate as follows: • Step 1: Determine the RO based on the legacy RACH setting. • Step 2: Determine the valid RO from the determined RO using legacy rules. • Step 3: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. • Step 4: Send the selected preamplifier at the selected RO.

[0084] In Step 4 described above, the following extensions are possible: • Example 1-1: UE200 does not assume that any of the symbols (or at least one symbol) of the determined valid RO (and the N_gap symbol preceding the valid RO) are SBFD FL symbols. • Example 1-2: UE200 does not assume that a valid RO overlaps with an RB outside the UL subband within an SBFD FL symbol. • Example 1-3: UE200 does not transmit a preamble for a determined valid RO if it overlaps with an SBFD FL symbol. • Example 1-4: UE200 does not transmit a preamble for a determined valid RO if it overlaps with an RB outside the UL subband within an SBFD FL symbol. • Example 1-5: UE200 does not assume that a determined valid RO overlaps with both non-SBFD symbols (e.g., UL symbols or non-SBFD FL symbols) and SBFD symbols (e.g., SBFD FL symbols). - Example 1-6: If the determined valid RO overlaps with both non-SBFD symbols (e.g., UL symbols or non-SBFD FL symbols) and SBFD symbols (e.g., SBFD FL symbols), the UE200 will not send a preamble for that valid RO.

[0085] (4.3.1.2) Option 2 Option 2 combines legacy RACH settings with extended rules for determining valid RO.

[0086] In Option 2, the UE200 may operate as follows: • Step 1: Determine the RO based on the legacy RACH setting. • Step 2: Determine the valid RO from the determined RO using the extended rules. • Step 3: The determined valid RO is mapped to the SSB index according to the legacy SSB-RO mapping rules. • Step 4: Send the selected preamplifier at the selected RO.

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

[0088] In Step 4 described above, the following extensions are possible: • Example 2-1: UE200 does not assume valid ROs that overlap with RBs outside the UL subband within SBFD DL symbols (and / or SBFD SSB symbols) (and / or SBFD FL symbols). • Example 2-2: UE200 does not transmit a preamble for a determined valid RO if it overlaps with an SBFD DL symbol (and / or SBFD SSB symbol) (and / or SBFD FL symbol). • Example 2-3: UE200 does not assume that a determined valid RO overlaps 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). Example 2-4: If the determined valid RO overlaps 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), the UE200 will not send a preamble for that valid RO.

[0089] As a result, in Option 2, different SSB indices can be mapped to the same RO between the legacy UE and the SBFD-aware UE, as shown in Figure 12.

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

[0091] In Option 3, the UE200 may operate as follows: • Step 1: Determine the RO based on the legacy RACH setting. • Step 2A-1: From the determined RO, determine a valid RO using legacy rules. This valid RO may be called the 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 RO (within or overlapping with SBFD DL symbols (and / or SBFD SSB symbols)), determine additional valid ROs using extended rules. • Step 2B-2: The determined additional valid RO is mapped to an SSB index. • Step 3: Send the selected preamplifier at the selected RO.

[0092] In Step 2B-1 described above, additional valid ROs can be determined for ROs that were determined to be invalid in Step 2A-1 by using the extended rules for determining valid ROs described in (4.2). These additional valid ROs may also be called SBFD-valid ROs.

[0093] In Step 2B-2 described above, SBFD-valid ROs may be mapped to SSB indices separately from legacy-valid ROs. Alt-1 will be explained below with reference to Figure 13, and Alt-2 will be explained with reference to Figure 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 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, SBFD-valid ROs are mapped to the same SSB index as the last / first legacy-valid RO before / after an SBFD-valid RO of the same frequency resource index.

[0096] In Step 3 described above, the extension of Step 4 in Option 2 can be used.

[0097] Analysis: According to Option 3, valid ROs determined by legacy rules are commonly understood by both the legacy UE and the SBFD-aware UE. Furthermore, additional valid ROs determined by extended rules are understood by the SBFD-aware UE. Also, compared to Option 4, which will be discussed later, the RACH setting can be treated as one of the legacy RACH settings.

[0098] (4.3.1.4) Option 4 Option 4, as shown in Figure 15, combines an additional / individual RACH setting (hereinafter also referred to as the RACH setting for SBFD) with an extended rule for determining valid RO. The RACH setting for SBFD is a RACH setting for SBFD symbols, and may be understood as a setting that determines RO for SBFD symbols in particular. On the other hand, a RACH setting for non-SBFD symbols may be made based on the RACH setting for SBFD, or RO for non-SBFD symbols may be determined in particular.

[0099] In Option 4, the UE200 may operate as follows: ・Step 1A: Determine the RO based on the legacy RACH setting. ・Step 2A: Determine a valid RO from the determined RO using 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 SBFD RACH setting. ・Step 2B: Determine a valid RO from the RO determined based on the SBFD RACH setting using legacy rules. ・Step 3B: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rules. ・Step 4: Send the selected preamble at the selected RO. Note that SBFD-aware UE only uses the SBFD RACH setting, so Steps 1A to 3A may be omitted.

[0100] In Step 1B described above, an additional / individual RACH setting for SBFD is set or instructed, and the UE determines the RO based on the RACH setting for SBFD. The RACH setting for SBFD may be set in the following IEs: Alt-1: It may be set in additionalRACH-ConfigList. For example, the corresponding feature combination may be for "SBFD". Alt-2: It 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: The RACH setting for SBFD may be supported for a given feature combination (e.g., Msg 1 / 3 repetitions and / or RedCap and / or SDT).

[0101] Furthermore, based on the RACH settings for SBFD, the following variations may be implemented: • Alt-a: Only ROs within SBFD symbols or ROs overlapping with SBFD symbols are determined, while ROs within non-SBFD symbols or ROs overlapping with non-SBFD symbols are excluded from determination. • Alt-b: The RACH settings do not assume that ROs are within or overlapping with non-SBFD symbols. • Alt-c: All ROs are determined by legacy rules. That is, ROs are determined regardless of whether they are within or overlapping with SBFD symbols, or within or overlapping with non-SBFD symbols.

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

[0103] In Step 4 described above, the extension of Step 4 in Option 2 can be used.

[0104] Analysis: According to Option 4, the RACH settings for SBFD are independent of the legacy RACH settings and therefore do not affect the Legacy UE. Compared to Option 3 mentioned above, this option consumes more resources for RACH, but in return, it allows for more flexible configuration.

[0105] (4.3.2) Operation Example 2 Operation Example 2 will be described below. Operation Example 2 is an example of determining a valid RO for random access (RA) in RRC_IDLE mode or IN_ACTIVE mode, or for RA based on dedicated settings (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] Furthermore, RAs based on common settings (cell common RACH settings) and RAs based on dedicated settings differ in the following respects: RAs based on common settings require consideration of how the Legacy UE understands or interprets the settings, while RAs based on dedicated settings do not require consideration of how the Legacy UE understands or interprets the settings.

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

[0108] (4.3.2.2) Option 2: gNB determines whether to always use the extended rules for valid RO determination described in (4.2) based on the rach-ConfigBFR, which is set as before in BeamFailureRecoveryConfig, and / or the cfra, which is set as before in RACH-ConfigDedicated, and / or the rach-ConfigSI, which is set as before in SI-RequestConfig.

[0109] (4.3.2.3) Option 3 Additional / individual configurations are made to configure RACH resources for SBFD, and the UE uses the extended rules for valid RO determination described in (4.2) to determine a valid RO for RACH resource configuration for SBFD. - Example: BeamFailureRecoveryConfig-sbfd-r19 is configured. Or, rach-ConfigBFR-sbfd-r19 is configured in BeamFailureRecoveryConfig. - Example: RACH-ConfigDedicated-sbfd-r19 is configured. Or, cfra-sbfd-r19 is configured in RACH-ConfigDedicated. Or, occasions-sbfd-r19 is configured in CFRA. Or, ConfigGeneric-sbfd-r19 is configured in CFRA's occasions. and / or - CFRA-TwoStep-sbfd-r19 is configured in RACH-ConfigDedicated. Alternatively, CFRA-TwoStep may have occurrencesTwoStepRA-sbfd-r19 set. Alternatively, CFRA-TwoStep may have ConfigGenericTwoStepRA-sbfd-r19 set in occurrencesTwoStepRA-sbfd-r19. As a variation, CFRA or CFRA-TwoStep may have two mask index values ​​set for SBFD and non-SBFD. For example, SI-RequestConfig-sbfd-r19 may be set. Alternatively, SI-RequestConfig may have trach-OccasionsSI-sbfd-r19 set. Alternatively, SI-RequestConfig may have trach-ConfigSI-sbfd-r19 set in trach-OccasionsSI. As a variation, SI-RequestResources may have two mask index values ​​set for SBFD and non-SBFD.

[0110] (4.3.3) Operation Example 3 Operation Example 3 will be explained. Operation Example 3 supports MsgA PUSCH transmission in SBFD symbols in 2-step RA. Specifically, it determines a valid MsgA PUSCH occasion in SBFD symbols.

[0111] In determining a valid MsgA PUSCH occasion in an SBFD symbol, the extended rules for determining a valid RO described in (4.2) can be reused by replacing "RO" with "MsgA PUSCH occasion" in the explanation in (4.2).

[0112] In sending MsgA PUSCH messages based on common cell settings, the content of Operation Example 1 can be reused by replacing "RO" with "MsgA PUSCH occasion" and "RACH setting" with "MsgA setting (or MsgA PUSCH setting)" in the explanation of Operation Example 1 (including the explanation of the extended rules for determining valid RO in (4.2)). Furthermore, in sending MsgA PUSCH messages based on dedicated settings, the content of Operation Example 2 can be reused by making similar substitutions as appropriate.

[0113] The extended rules for determining valid RO in (4.2) may be applied to 2-step RACH as well as 4-step RACH (any of operation examples 1 to 3 are possible), or they may be applied only to 4-step RACH (only operation examples 1 and 2 are possible), or they may be applied only to 2-step RACH (only operation example 3 is possible).

[0114] (4.3.4) Operation Example 4 Operation Example 4 will be explained with reference to Figure 16. Operation Example 4 concerns whether or not to support the simultaneous setting / enabling of PRACH repetitions in RA and the instruction / setting of the time / frequency domain position of the SBFD subband. Note that repetitions may be understood as repeated transmissions, and PRACH repetitions may be understood as repeated transmissions of PRACH in RA.

[0115] (4.3.4.1) Option 1 Option 1 in Operation Example 4 supports the simultaneous setting / enabling of PRACH repetitions in RA and the indication / setting of the time / frequency domain position of the SBFD subband in SBFD. Based on this support, Options 1-1 and 1-2 are also possible.

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

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

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

[0119] • Variation: In a set of PRACH repetitions with N preamble repetitions, a set of valid PRACH occasions consists only of valid ROs based on additional RACH settings for SBFD, or only of valid ROs based on legacy RACH settings. For example, this may be used when additional RACH settings for SBFD are configured.

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

[0121] • Variation: In a PRACH transmission (PRACH repetitions) with N preamble repetitions, a set of valid PRACH occasions consists of either SBFD-valid ROs or legacy-valid ROs. For the meaning of SBFD-valid ROs and legacy-valid ROs, please refer to option 3 in Operation Example 1.

[0122] • Variation: In a PRACH transmission with N preamble repetitions (PRACH repetitions), a set of valid PRACH occasions consists of valid ROs based on additional RACH settings for SBFD or valid ROs based on legacy RACH settings. For example, this may be used when additional RACH settings for SBFD are 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 (PRACH repetitions) involving N preamble repetitions, a set of valid PRACH occasions consists only of valid ROs that are limited to non-SBFD symbols.

[0125] • Variation: In a PRACH transmission (PRACH repetitions) with N preamble repetitions, a set of valid PRACH occasions consists only of legacy-valid ROs. For the meaning of legacy-valid RO, please refer to option 3 in Operation Example 1.

[0126] • Variation: In a PRACH transmission (PRACH repetitions) with N preamble repetitions, a set of valid PRACH occasions consists only of valid ROs based on legacy RACH settings. This may be used, for example, when additional RACH settings for SBFD are configured.

[0127] (4.3.4.1.3) Which variation option to apply may be predefined by the standard or set / indicated 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 simultaneous setting / enabling of PRACH repetitions in RA and the instruction / setting of the time / frequency domain position of the SBFD subband. In this case, the UE does not assume that the time / frequency domain position of the SBFD subband will be provided at the same time that PRACH repetitions (Msg1 repetitions) are set / enable.

[0130] Option 1 (Options 1-1A, 1-1B, and 1-2) will be explained with reference to Figure 16.

[0131] As shown in Figure 16, in Option 1-1A, the RO group for the four PRACH repetitions (i.e., a set of valid PRACH occasions) may be {RO#a-0, RO#a-1, RO#a-2, RO#a-3}, {RO#a-4, RO#a-5, RO#a-6, RO#a-7}, {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 Figure 16, in Option 1-1B, the RO group for the four PRACH repetitions (i.e., a set of valid PRACH occasions) may be {RO#a-0, RO#a-1, RO#a-2, RO#b-0}, {RO#a-3, RO#a-4, RO#a-5, RO#b-1}, {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 Figure 16, in option 1-2, the RO groups for the four PRACH repetitions (i.e., a set of valid PRACH occasions) may be {RO#b-0, RO#b-1, RO#b-2, RO#b-3}.

[0134] (4.3.5) Operation Example 5 Operation Example 5 will be explained. Operation Example 5 is an example of how the UE correctly recognizes whether the mask index in PDCCH order RACH represents the RO index of additional RO or the RO index of legacy RO.

[0135] In this specification, legacy RO refers to a valid RO with a UL or FL symbol, which is set by the legacy RACH setting based on the legacy RO validation rule.

[0136] In this specification, additional RO refers to any of the following: • If no additional RACH settings for SBFD are configured, the valid RO of an SBFD UL symbol or a valid RO spanning both an SBFD UL symbol and an SBFD FL symbol, as configured by the legacy RACH settings. • If additional RACH settings for SBFD are configured, the valid RO of an SBFD symbol, as configured by the additional RACH settings 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 following available PRACH opportunities among the additional ROs corresponding to selected SSBs, permitted by the conditions of the PRACH mask index field shown in the PDCCH order. • Legacy RO corresponding to PRACH mask index: The following available PRACH opportunities among the legacy ROs corresponding to selected SSBs, permitted by the conditions of the PRACH mask index field shown in the PDCCH order.

[0139] Option 1 is a configuration in which the conventional PRACH mask index table is reused in the PDCCH ordered PRACH. The conventional PRACH mask index table may also be called the conventional PRACH mask value table. The conventional PRACH mask index table may be understood to be the one shown in Table 7.4-1 of 3GPP TS38.321. Specifically, when the PRACH mask index (code point) is X, the allowed SSB PRACH opportunities may be shown as follows: ・When X=0, the allowed SSB PRACH opportunities are all PRACH opportunities. ・When X=1~8, the allowed SSB PRACH opportunities are the PRACH opportunities for index X. ・When X=9, the allowed SSB PRACH opportunities are the PRACH opportunities for all even-numbered indexes. ・When X=10, the allowed SSB PRACH opportunities are the PRACH opportunities for all odd-numbered indexes. ・X=11~15 are Reserved.

[0140] It may also be understood that Table 7.4-1 of 3GPP TS38.321 has the underlined portion of the table shown in Figure 17 (described later) removed, and PRACH mask indices (code points) 11-15 of that table replaced with "Reserved".

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

[0142] As option 1-1, the UE200 may select one RO for PRACH transmission from either an additional RO corresponding to the PRACH mask index or a legacy RO corresponding to the PRACH mask index. Specifically, one RO may be selected as follows:

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

[0144] Option 1-1b: UE200 selects RO based on its own implementation (UE implementation).

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

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

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

[0148] As an option 1-2, the UE200 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 in PDCCH ordered PRACH. As shown in Figure 17, in the extended PRACH mask index table, each PRACH mask index code point is applied to either additional RO or legacy RO. The extended PRACH mask index table may also be called the extended PRACH mask table.

[0150] As shown in Figure 17, in the extended PRACH mask index table, some code points (e.g., 0-10) may be mapped to legacy ROs, and other code points (e.g., 11-15) may be mapped to additional ROs. Variation: The number (maximum) of code points indicating legacy ROs / additional ROs may be defined by the standard. Variation: The value (number) of the code points indicating legacy ROs / additional ROs may be defined by the standard. Variation: The value corresponding to each code point (indicating a legacy RO / additional RO) (i.e., the permitted PRACH opportunity in the right column of Figure 17) may be defined by the standard or set by the RRC. Example: In a conventional PRACH mask index table (Table 7.4-1 of 3GPP TS38.321), existing valid code points (0-10) may be mapped to legacy ROs, and reserved code points (11-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 Figure 17, if PRACH mask index code points 0 to 11 are shown, it is implicitly indicated that legacy RO is shown, and if PRACH mask index code points 12 to 15 are shown, it is implicitly indicated that additional RO is shown.

[0152] Note that the values ​​for each row / entry shown in Figure 17 are examples, and other values ​​are acceptable. Each row / entry only needs to be able to indicate either an additional RO or a legacy RO. For example, all of the extended PRACH mask index code points (0-15) may indicate only one of either an additional RO or a legacy RO. In that case, as with the conventional PRACH mask index table (Table 7.4-1 of 3GPP TS38.321), extended PRACH mask index code points 11-15 may be reserved.

[0153] (4.3.6) UE capability In order to apply to the above examples 1 to 5, new UE capabilities and report signaling (and RRC settings) may be defined for each UE / FR / FC, etc., as shown below: - Whether or not to support recognition of the time and frequency domain position of the SBFD subband - Whether or not to support PRACH transmission in SBFD symbols - Whether or not to support an enhanced RO validation rule for SBFD - Whether or not to support PRACH transmission in SBFD symbols for CFRA

[0154] (5) Effects and Functions According to the embodiments described above, the UE200 can recognize the SSB index numbering in SBFD while maintaining a common understanding with the Legacy UE regarding the SSB index numbering in non-SBFD.

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

[0156] (6) Other Embodiments Although the contents of the present invention have been described above in accordance with the embodiments, 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] In the above example 4, the PRACH repetitions may be replaced with repetitions of other messages in RA. For example, they may be replaced with Msg3 PUSCH repetitions and HARQ-ACK PUCCH for Msg4 repetitions.

[0158] The UE may report the following capability information to the BS: • Capability information for each operational example • Capability information for each option in the operational example, or for combinations of options • Capability information for each variation in the operational example, or for combinations of variations

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

[0160] The UE can report the above capability information for each cell. Specifically, it can report the above capability information for each UE, each cell, and each TDD and FDD.

[0161] In this disclosure, whether or not to apply an example of operation, which example of operation to apply, and / or which option or variation to use may be any of the following: • Set by a higher-layer parameter. • Determined by the relevant higher-layer parameter. • Indicated by MAC CE or DCI. • Determined based on one or more UE capabilities. • As described in the specification. • Based on conditions described in the specification. • Determined by the setting of a higher-layer parameter / MAC CE / DCI and the reported UE capability (a combination of the above determinations).

[0162] In this disclosure, multiple options and variations may be combined as a single option / variation.

[0163] In this disclosure, the measurement RS may be a QCL resource RS in an active TCI state or a specified TCI state.

[0164] In this disclosure, the UE may receive information from the network in the following types (in this disclosure, the network may be referred to as the gNB): • Information via upper-layer signaling (e.g., RRC messages, LPP messages) • MAC CE • MAC CE with a new LCID in the subheader • Extensions to existing MAC CEs (e.g., introduction of a new octet) • DCI • DCI field: existing / newly introduced DCI field • RNTI: DCI with a CRC scrambled by an existing / newly introduced RNTI • DCI format: existing / newly introduced DCI format • Combinations of these

[0165] In this disclosure, the UE may receive information from the network in the following periodic types: • Periodic • Semi-persistent (triggered by instructions from the UE or gNB) • Aperiodic (triggered by instructions from the UE or gNB)

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

[0167] In this disclosure, the QCL resource RS for each QCL type may be one of the following: • SSB • CSI-RS with / without repetition • TRS • PDCCH / PDSCH DMRS

[0168] In this disclosure, information from the network may be configured / 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 this disclosure, the UE may report information to the network in the following types (in this disclosure, the network may be referred to as the gNB): • Information via upper-layer signaling (e.g., RRC messages, LPP messages) • MAC CE • MAC CE with a new LCID in the subheader • Extensions to existing MAC CEs (e.g., introduction of a new ocset) • UCI • UCI on PUCCH or PUSCH • A combination of these

[0170] In this disclosure, the UE may report information to the network in the following periodic types: • Periodic • Semi-persistent (triggered by instructions from the UE or gNB) • Aperiodic (triggered by instructions from the UE or gNB)

[0171] The above-mentioned examples of operation and options may be applied in combination and in combination, as long as no inconsistencies arise.

[0172] For example, when options 1 and 2 of operation example 5 are combined, it is possible to decide in advance which option to prioritize. For example, if it is decided to prioritize option 1, the UE200 may ignore the additional RO / legacy RO indicated by the PRACH mask index of option 2 and select RO according to each option of option 1. On the other hand, if it is decided to prioritize option 2, the UE200 may not perform the operations specified for each option of option 1 and instead select the additional RO / legacy RO indicated by the PRACH mask index of option 2.

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

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

[0175] For example, the base station 100 and terminal 200 in one embodiment of the present disclosure may function as computers that process the wireless communication method of the present disclosure. Figure 18 is a diagram showing an example of the hardware configuration of the base station 100 and terminal 200 according to one embodiment of the present disclosure. The above-mentioned base station 100 and terminal 200 may be physically configured as computer devices including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0176] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 100 and terminal 200 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

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

[0178] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0179] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Furthermore, although it has been explained that the above processes are 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 program may also be transmitted from a network via a telecommunications line.

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

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

[0182] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

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

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

[0185] Furthermore, the 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), and a field programmable gate array (FPGA), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0186] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper 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 combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

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

[0188] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

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

[0190] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0191] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

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

[0193] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

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

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

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

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

[0198] The terms “system” and “network” as used in this disclosure are interchangeable.

[0199] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

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

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

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

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

[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 several other appropriate terms.

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

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

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

[0209] Figure 19 shows an example of the configuration of vehicle 2001. As shown in Figure 19, 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, which is operated by the user.

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

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

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

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

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

[0217] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between 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, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029 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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

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

[0220] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The information service unit 2012 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013).

[0221] Furthermore, the communication module 2013 stores various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2029, etc., which are provided in the vehicle 2001.

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

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

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

[0225] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

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

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

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

[0230] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

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

[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. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 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 unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal to allocate radio resources (such as the frequency bandwidth and transmission power available to each terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

[0238] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in LTE Rel. 8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a subslot, or a slot.

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

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

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

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

[0243] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area of ​​one subcarrier and one symbol. A bandwidth part (BWP) (also called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

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

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

[0247] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0248] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

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

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

[0251] (Note) The disclosure described above may also be expressed as follows:

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

[0253] The second feature is that, in the first feature, the control unit may be a terminal that selects the earlier random access opportunity from the first random access opportunity and the second random access opportunity.

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

[0255] A fourth feature is that, in the first feature, the control unit may be a terminal that selects one of the first random access opportunity and the second random access opportunity based on the settings of the wireless resource control layer.

[0256] A fifth feature is that, in the first feature, the receiving unit may be a terminal that receives the downlink control information in the second time unit, and the control unit may select the second random access opportunity.

[0257] A sixth feature is that, in the first feature, the control unit may select both the first random access opportunity and the second random access opportunity, and the transmission unit may transmit the random access preamble in both of the selected first and second random access opportunities.

[0258] This patent application claims priority based on Japanese Patent Application No. 2024-181963, filed on 17 October 2024, and the entire contents of Japanese Patent Application No. 2024-181963 are incorporated herein by reference.

[0259] 10 Wireless communication system 20 NG-RAN 100 Base station 110 Wireless signal transmission / reception unit 120 Control unit 200 Terminal 210 Wireless signal transmission / reception unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmission / reception unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

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

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

3. The terminal according to claim 1, wherein the control unit selects the random access opportunity that is later in time from the first random access opportunity and the second random access opportunity.

4. The terminal according to claim 1, wherein the control unit selects one of the first random access opportunity and the second random access opportunity based on the settings of the wireless resource control layer.

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

6. The terminal according to claim 1, 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 in both the selected first random access opportunity and the second random access opportunity.

Images