Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives first setting information and second setting information pertaining to two-step random access; and a control unit that determines, on the basis of the first setting information, a valid first transmission opportunity for transmitting a preamble in a first step in a time unit that includes a first time unit during which a plurality of sub-bands forming a time-division duplex band are available, and determines, on the basis of the first setting information and the second setting information, a valid second transmission opportunity for transmitting data in the first step, the valid second transmission opportunity being associated with the valid first transmission opportunity.

Description

Terminal and communication method

[0001] The present disclosure relates to a terminal and a communication method.

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

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

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

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

[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] Random access includes four-step random access and two-step random access. It has been agreed to support four-step random access in the SBFD symbol, but it is not yet determined whether two-step random access in the SBFD symbol will be supported. If the SBFD symbol can be extended to two-step random access, a reduction in random access delay can be achieved.

[0008] However, when the SBFD symbol is extended for two-step random access, there is room for consideration as to how to transmit the preamble and data (for example, how to determine the transmission resources). If the resources for transmitting the preamble and data are not clarified, the preamble and data cannot be transmitted appropriately, and there is a risk that the reduction in delay cannot be achieved.

[0009] One aspect of the present disclosure provides a terminal and a communication method capable of appropriately transmitting a preamble and data in a two-step random access procedure.

[0010] A terminal according to one aspect of the present disclosure includes a receiving unit that receives first setting information and second setting information related to two-step random access, and a control unit that determines, based on the first setting information, a valid first transmission opportunity for transmitting a preamble in the first step in a time unit that includes a first time unit in which multiple subbands that constitute a time division duplex band are available, and that determines, based on the first setting information and the second setting information, a valid second transmission opportunity that is associated with the valid first transmission opportunity and is used to transmit data in the first step.

[0011] 1 is a diagram showing an overall schematic configuration of a wireless communication system. 2 is a diagram showing a frequency range used in the wireless communication system. 3 is a diagram showing an example of the configuration of a radio frame, subframe, slot, and symbol used in the wireless communication system. 4 is a diagram showing an example of TDD configuration specified up to Rel. 16. 5 is a diagram showing an example of the configuration of SBFD. 6 is a diagram showing an example of SBFD operation. 7 is a diagram showing an example of existing TDD configuration. 8 is a diagram showing an example of TDD including SBFD configuration. 9 is a diagram showing a pure time unit and an SBFD time unit. 10 is a diagram showing a pure time unit and an SBFD time unit. 11 is a diagram showing a pure time unit and an SBFD time unit. 12 is a diagram showing a pure time unit and an SBFD time unit. 13 is a sequence diagram showing an example of a CBRA procedure. 14 is a sequence diagram showing another example of the CBRA procedure. 15 is a sequence diagram showing an example of a CFRA procedure. 16 is a diagram showing an example of application of an extended rule for determining a valid RO. 17 is a diagram showing an example of application of an extended rule for determining a valid RO. 18 is a diagram showing an example of application of an extended rule for determining a valid RO. 19 is a diagram showing an example of application of an extended rule for determining a valid RO. Fig. 1 is a diagram showing an example of application of an extended rule for determining a valid RO. Fig. 2 is a diagram showing an example of SSB-RO mapping when an extended rule for determining a valid RO is applied. Fig. 3 is a diagram showing an example of SSB-RO mapping when an extended rule for determining a valid RO is applied. Fig. 4 is a diagram showing an example of SSB-RO mapping when an extended rule for determining a valid RO is applied. Fig. 5 is a diagram showing an example of SSB-RO mapping when an extended rule for determining a valid RO is applied. Fig. 6 is a diagram showing an overview of Msg A PO determination. Fig. 7 is a diagram showing an overview of MsgA RO-preamble-PO mapping. Fig. 8 is a diagram showing an overview of a conventional procedure in which a terminal determines an MsgA RO and an MsgA PO, and maps an MsgA RO preamble to an MsgA PO. Fig. 9 is a diagram summarizing valid MsgA ROs and valid MsgA POs determined based on a configuration related to option 1-1 of proposal 1.Figure 1 shows an overview of the procedure for SBFD according to Option 1-1 of Proposal 1, in which a terminal determines an MsgA RO and MsgA PO and maps an MsgA RO preamble to the MsgA PO; Figure 2 shows a summary of a valid MsgA RO and a valid MsgA PO determined based on a configuration according to Options 1-2 of Proposal 1; Figure 3 shows an overview of the procedure for SBFD according to Option 1-2 of Proposal 1, in which a terminal determines an MsgA RO and MsgA PO and maps an MsgA RO preamble to the MsgA PO; Figure 4 shows a summary of a valid MsgA RO and a valid MsgA PO determined based on a configuration according to Options 1-3 of Proposal 1; Figure 5 shows an overview of the procedure for SBFD according to Options 1-3 of Proposal 1, in which a terminal determines an MsgA RO and MsgA PO and maps an MsgA RO preamble to the MsgA PO; Figure 10 summarizes valid MsgA RO and valid MsgA PO determined based on the configuration according to Options 1-4 of Proposal 1. Figure 11 summarizes the procedure according to Options 1-4 of Proposal 1, in which a terminal determines MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO. Figure 10 summarizes valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 2-1 of Proposal 2. Figure 11 summarizes the procedure for SBFD according to Option 2-1 of Proposal 2, in which a terminal determines MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO. Figure 10 summarizes valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 2-2 of Proposal 2. Figure 1 shows an overview of a procedure for SBFD according to Option 2-2 of Proposal 2, in which a terminal determines an MsgA RO and an MsgA PO, and maps an MsgA RO preamble to an MsgA PO. Figure 2 also shows a summary of valid MsgA ROs and valid MsgA POs determined based on a configuration according to Option 2-3 of Proposal 2.FIG. 1 is a diagram showing an overview of a procedure for SBFD according to option 2-3 of proposal 2, in which a terminal determines an MsgA RO and an MsgA PO, and maps an MsgA RO preamble to the MsgA PO. FIG. 2 is a diagram summarizing a valid MsgA RO and a valid MsgA PO determined based on a configuration according to option 2-4 of proposal 2. FIG. 3 is a diagram showing an overview of a procedure according to option 2-4 of proposal 2, in which a terminal determines an MsgA RO and an MsgA PO, and maps an MsgA RO preamble to the MsgA PO. FIG. 4 is a flowchart showing an example of the operation of a terminal. FIG. 5 is a block diagram showing an example of the configuration of a base station. FIG. 6 is a block diagram showing an example of the configuration of a terminal. FIG. 7 is a diagram showing an example of the hardware configuration of a base station and a terminal. FIG.

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

[0013] 1 is a wireless communication system conforming to a method called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

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

[0015] As shown in FIG. 1 , the wireless communication system 10 includes a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) constituting a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as a user equipment (UE) 200) that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) (not shown). The CN is composed of multiple network functions (NFs). The NFs are, for example, an access and mobility management function (AMF) and a network data analytics function (NWDAF). The AMF performs, for example, registration of the UE 200. The NWDAF performs, for example, optimization of the CN. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1 . The NG-RAN 20 and the CN may be simply referred to as a "network."

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

[0017] The wireless communication system 10 may also support multiple frequency ranges (FR). That is, as shown in Fig. 2, the wireless communication system 10 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

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

[0019] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS 38.300 and corresponds to one subcarrier spacing in the frequency domain.

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

[0021] 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in FIG. 3, one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in FIG. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

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

[0023] 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0024] The wireless communication system 10 may support coverage enhancement (CE) that expands the coverage of a cell (or a physical channel) formed by the gNB 100. In coverage enhancement, a mechanism for increasing the success rate of reception of various physical channels, such as repeated transmission (repetition) of a PRACH (physical random access channel), may be provided.

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

[0026] Further, for example, UE 200 transmits PRACH as an UL signal to gNB 100 using a RACH occasion, i.e., a RACH (transmission) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble. For example, UE 200 repeatedly transmits PRACH as an UL signal to gNB 100.

[0027] The UL signal may include, for example, a UL data signal and control information. For example, the UL signal may include information related to the processing capability of the UE 200 (e.g., UE capability). The UL signal may also include a reference signal.

[0028] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a physical uplink shared channel (PUSCH), and the control channel may include a physical uplink control channel (PUCCH). For example, the UE 200 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel, and the PUCCH is an example of an uplink control channel. The shared channel may also be called a data channel.

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

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

[0031] Also, for example, gNB100 receives PRACH as an UL signal from UE200. For example, gNB100 repeatedly receives PRACH from UE200 as an UL signal.

[0032] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the gNB 100 transmits control information to the UE 200 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel, and the PDCCH is an example of a downlink control channel. Note that the PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.

[0033] The reference signal included in the DL signal may include, for example, at least one of a DMRS, a PTRS, a CSI-RS, an SRSRS, and a PRS for location information. For example, the reference signal such as the DMRS or the PTRS is used for demodulating the DL data signal and is transmitted using the PDSCH.

[0034] Support for random access (RA) in SBFD is being considered for Release 19. The following describes SBFD and random access.

[0035] <SBFD Operation> Considering the time ratio of transmission and reception (e.g., DL:UL = 4:1) using Time Division Duplex (TDD) up to Rel. 16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL ​​signals / channels. In such cases, UE 200 cannot frequently transmit UL signals / channels, and there is a concern that transmission delays of important UL signals / channels may occur. In addition, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also a concern that signal / channel congestion may occur during UL transmission opportunities. Furthermore, in TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques, for example, through repetition transmission.

[0036] In future wireless communication systems (for example, Rel. 18 and later), the introduction of a time-frequency division duplexing method that combines TDD and frequency division duplexing (FDD) for UL and DL is being considered.

[0037] Examples of the time-frequency division duplexing method include XDD (Cross Division Duplex) or Subband Non-Overlapping Full Duplex (SBFD). XDD or SBFD may refer to a duplexing method in which DL and UL are frequency-division multiplexed within one component carrier (CC) of the TDD band (DL and UL can be used simultaneously).

[0038] Fig. 4A is a diagram showing an example of TDD configuration defined up to Rel. 16. In the example shown in Fig. 4A, TDD slots or symbols are configured for a UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or a serving cell) or bandwidth portion (BWP).

[0039] In the example shown in Fig. 4A, the time ratio of DL slots to UL slots is 4: 1. In such a conventional TDD slot or symbol setting, UL time resources cannot be sufficiently secured, which may result in UL transmission delays and degradation of coverage performance.

[0040] 4B is a diagram showing an example of the configuration of SBFD. In the example shown in FIG. 4B, within one component carrier (CC), resources used for DL ​​reception and resources used for UL transmission overlap in time. With this resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.

[0041] For example, as shown in the example of Fig. 4B, both ends of the frequency domain may be set as DL resources, and these DL resources may sandwich UL resources. This may prevent or mitigate cross link interference (CLI) with neighboring carriers. Furthermore, a guard region may be set at the boundary between the DL resource and the UL resource.

[0042] Considering the complexity of processing self-interference, it may be considered that only the base station 100 uses the DL resource and the UL resource simultaneously. That is, in radio resources where the DL and UL overlap in time, one UE 200 may use the DL resource and another UE 200 may use the UL resource.

[0043] Fig. 5 is a diagram showing an example of SBFD operation. In the example shown in Fig. 5, part of the DL resources of the TDD band is configured as UL resources, and the DL and UL are configured to partially overlap in the time domain.

[0044] In the example shown in FIG. 5, during the DL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) receives the DL channel / signal.

[0045] In addition, during a period in which the DL and UL channels overlap in time, one UE 200 (UE1 in the example of FIG. 5) receives a DL channel / signal, and another UE 200 (UE2 in the example of FIG. 5) transmits a UL channel / signal. During this period, the base station 100 performs simultaneous transmission and reception of the DL and UL channels.

[0046] Furthermore, during the UL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) transmits a UL channel / signal.

[0047] In the existing NR (for example, as defined by Rel. 15 / 16 / 17), the DL frequency resource and the UL frequency resource in the UE carrier are configured as the DL BWP and the UL BWP, respectively. In order to switch the DL / UL frequency resource to another DL / UL frequency resource, multiple BWP configurations and a BWP adaptation mechanism are required.

[0048] 6A is a diagram showing an example of an existing TDD configuration. In FIG. 6A, slots / symbols marked with "D" are DL slots / symbols, slots / symbols marked with "U" are UL slots / symbols, and slots / symbols marked with "F" are flexible (hereinafter also referred to as FL) slots / symbols. Note that similar notations may be used in the following figures.

[0049] In the existing NR, as shown in FIG. 6A, the time resources (time units such as symbols, slots, etc.) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.

[0050] 6B is a diagram showing an example of an existing TDD configuration. In FIG. 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL ​​subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Note that similar notations may be used in the following figures.

[0051] As shown in FIG. 6B , the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on some frequency resources (subbands), and signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on other frequency resources (subbands). Alternatively, the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on a portion of the frequency resources. Alternatively, the SBFD symbol may be a symbol that is signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on a portion of the frequency resources.

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

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

[0054] Furthermore, for an SBFD time unit, DL resources and UL resources may have various allocation patterns in the frequency domain. For example, an SBFD time unit of frequency domain pattern #1 may have an allocation pattern as shown in FIG. 7C . An SBFD time unit of frequency domain pattern #2 may have an allocation pattern as shown in FIG. 7D . An SBFD time unit of frequency domain pattern #3 may have an allocation pattern as shown in FIG. 7E . These allocation patterns are merely exemplary, and other allocation patterns may be used. The frequency domain pattern of an SBFD time unit may refer to a resource repetition pattern in the frequency domain for the SBFD time unit.

[0055] As described above, SBFD may be applied to each slot / symbol. Note that each slot / symbol may be set to DL, UL, or Flexible (FL) that can be used as DL or UL, and then SBFD may be applied.

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

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

[0058] Furthermore, a UE that supports SBFD operation is referred to as an SBFD-aware UE or an SBFD-capable UE, and a UE that does not support SBFD operation is referred to as a legacy UE. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol, but a legacy UE recognizes this SBFD symbol as a normal DL symbol.

[0059] The following explains the terms related to SBFD. SBFD DL symbol: A symbol indicated as DL by the tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, and for which an SBFD subband is configured SBFD FL symbol: A symbol indicated as FL by the tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, and for which an SBFD subband is configured SBFD SSB symbol: A symbol configured for SSB reception, and for which an SBFD subband is configured non-SBFD symbol: A symbol for which an SBFD subband is not configured, and / or a symbol for which SBFD operation is not performed on the gNB side

[0060] <Random Access Procedure> The NR random access procedure is performed for various purposes such as initial access, recovery from beam interference, handover, etc. The random access procedure includes a CBRA (Contention Based Random Access) procedure as a contention-based random access procedure and a CFRA (Contention Free Random Access) procedure as a contention-free random access procedure. Since the CBRA procedure is initiated by the UE 200 voluntarily, collisions may occur when multiple UEs 200 simultaneously initiate the random access procedure. On the other hand, CFRA allows the gNB 100 to instruct the connected UE 200 to perform the random access procedure so that collisions do not occur between multiple UEs 200.

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

[0062] FIG. 8 is a sequence diagram illustrating an example of a CBRA procedure.

[0063] For example, the gNB 100 transmits an SSB for each beam, and the UE 200 monitors the SSB of each beam. The UE 200 selects an SSB from among the multiple SSBs whose received power (RSRP: Reference Signal Received Power) is greater than a threshold (or is equal to or greater than a threshold), and transmits a random access preamble to the gNB 100 via a PRACH using an RO associated with (corresponding to) the selected SSB (step S101). The random access preamble (sometimes abbreviated as an RA preamble or RA preamble) may be appropriately referred to as a preamble, a PRACH preamble, a message 1, an Msg1, or the like.

[0064] The gNB 100 transmits a response message to Msg1 as a second message to the UE 200 via the PDSCH (step S102). This response message (second message) may be appropriately referred to as a random access response (RAR), RA Response, message 2 (Message 2), Msg2, or the like. After transmitting Msg1, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including Msg2. Msg2 may include an uplink grant (UL Grant) (RAR uplink grant) used for scheduling the PUSCH including the third message transmitted by the UE 200.

[0065] The UE 200 transmits the PUSCH scheduled by the RAR uplink grant as a third message (step S103). For example, the UE 200 transmits a radio resource control (RRC) connection request, an RRC connection re-establishment request, or the like to the gNB 100 via the PUSCH. The third message may be appropriately referred to as a message 3, Msg 3, an RRC connection request, or the like.

[0066] The gNB 100 transmits a contention resolution message (Contention Resolution Message) as a fourth message via the PDSCH (step S104). This contention resolution message (fourth message) may be referred to as Message 4, Msg 4, or the like, as appropriate. After transmitting Msg 3, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including Msg 4. Msg 4 may include a contention resolution ID (UE contention resolution ID). The contention resolution ID may be used to resolve contention between multiple UEs 200 transmitting signals using the same radio resources. If the contention resolution ID included in the Msg 4 received by the UE 200 is the same value as the ID for identifying the UE 200, the UE 200 determines that contention resolution is successful and may set the value of the Temporary Cell-Radio Network Temporary Identifier (TC-RNTI) in the Cell-Radio Network Temporary Identifier (C-RNTI) field. When the value of the TC-RNTI is set in the C-RNTI field, the UE 200 may consider that the RRC connection is completed. Msg4 may be referred to as an RRC connection setup, etc.

[0067] UE200, whose RRC connection has been completed, may transmit an Ack (Acknowledgement) via the PUCCH (PUCCH resource) indicated by the PUCCH resource indication field included in the PDCCH that scheduled Msg4 in order to notify gNB100 that the RRC connection has been completed. Also, after the RRC connection is established, UE200 may transmit UE capability to gNB100. The above-described random access procedure may be referred to as a Type 1 RACH procedure, a 4-step RACH procedure, a Type 1 RACH, a 4-step RACH, or the like.

[0068] FIG. 9 is a sequence diagram showing another example of the CBRA procedure.

[0069] The UE 200 transmits a message including an RA preamble and data to the gNB 100 (step S201). As an example, the UE 200 selects an RO in the same manner as selecting an RO in the 4-step RACH procedure, transmits an RA preamble in the RO, and transmits data in a PUSCH resource associated with the RO. This message may be appropriately referred to as Message A, Msg A, etc. Note that the RA preamble and data here may correspond to Msg 1 and Msg 3 in the 4-step RACH procedure, respectively. Msg A includes one RA preamble (referred to as Msg A PRACH) and one piece of data (referred to as Msg A PUSCH), and the Msg A PRACH and Msg A PUSCH are time-division multiplexed and transmitted. More specifically, the MsgA PRACH is one preamble with one preamble index in the MsgA RACH occasion (RO), and the MsgA PUSCH is one PUSCH with one PUSCH resource unit (PRU) in the MsgA PUSCH occasion (PO) according to the MsgA PUSCH configuration. Note that in this procedure, the resources for transmitting data are not limited to PUSCH resources, and may be resources of any channel for transmitting data (or control information).

[0070] The gNB 100 transmits the response message to the UE 200 as a second message (step S202). This response message (second message) may be appropriately referred to as Message B, Msg B, or the like. The content included in Message B may correspond to, for example, Msg2 and Msg4 in the 4-step RACH procedure. MsgB includes one PDSCH (and one PDCCH that schedules the PDSCH). From the perspective of the physical layer, the content of Msg2 and Msg4 is simply integrated into MsgB.

[0071] The UE 200, whose RRC connection has been completed, may transmit an Ack via the PUCCH (PUCCH resource) to notify the gNB 100 that the RRC connection has been completed. Also, after the RRC connection is established, the UE 200 may transmit UE capability to the gNB 100. The above-described random access procedure may be referred to as a Type 2 RACH procedure, a 2-step RACH procedure, a Type 2 RACH, a 2-step RACH, or the like. The 2-step RACH is supported to shorten the RACH delay.

[0072] FIG. 10 is a sequence diagram illustrating an example of a CFRA procedure.

[0073] The UE 200 is requested to transmit an RA preamble (Msg1) from the gNB 100. Here, the gNB 100 allocates the RA preamble (Msg1) via dedicated signaling (step S301). The PDCCH for such dedicated signaling may be referred to as a PDCCH order. The UE 200 may monitor the PDCCH (PDCCH order) to perform resource allocation for Msg1.

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

[0075] The gNB100 transmits the above-mentioned Msg2 to the UE200 (step S303). After the RRC connection is completed, the UE200 may transmit an Ack via the PUCCH (PUCCH resource) to notify the gNB100 that the RRC connection has been completed. After the RRC connection is established, the UE200 may transmit the UE capability to the gNB100.

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

[0077] In the above-mentioned random access, the UE determines a random access opportunity to transmit a preamble to start the random access, and determines a valid RO (and an invalid RO) from the determined ROs. Note that the random access opportunity may also be referred to as a RACH Occasion. Next, the determination of a valid RO will be described.

[0078] <Regarding Valid RO Determination> The extended rules for determining a valid RO will be described with reference to Figures 11 to 15. Legacy rules for determining a valid RO will also be described. In the figures, Legacy UE refers to a UE that cannot recognize an SBFD symbol, and SBFD-aware UE refers to a UE that can recognize an SBFD symbol. For example, for an SBFD symbol set to a DL symbol or an FL symbol, Legacy UE regards it as a DL symbol or an FL symbol, and SBFD-aware UE regards it as an SBFD symbol. Hereinafter, the extended rules for determining a valid RO will also be referred to as extended RO validity verification rules, etc., and the legacy rules for determining a valid RO will also be referred to as legacy validity verification rules, legacy rules, etc.

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

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

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

[0082] Condition 6: At least N_gap symbols must be spaced after the last (non-SBFD) DL symbol, and / or at least N_gap symbols must be spaced after the last (non-SBFD) SSB symbol, and / or must not precede an SSB symbol in the same PRACH slot (a non-SBFD symbol). Condition 7: No overlap with both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol). Condition 8: No overlap with a non-SBFD DL symbol or a (non-SBFD) SSB symbol. Condition 9: No overlap with an RB (Resource Block) outside the UL subband in an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol).

[0083] That is, valid ROs in the extended rules for determining valid ROs may include ROs that satisfy one or more combinations of these conditions. One or more combinations of the above conditions may be predefined in the standard or may be set by the gNB. For example, valid ROs may include the following ROs:

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

[0085] 11 shows an example (Example A-1) in which SBFD is applied to DL symbols. An RO that satisfies condition 4 (and does not satisfy condition 9) and an RO that satisfies condition 1 are determined as valid ROs.

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

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

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

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

[0090] An example of operation will be described based on the above-mentioned extended rules for determining valid ROs.

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

[0092] As Option 1, an example in which a legacy RACH configuration and a legacy rule for determining a valid RO will be described. Note that the legacy RACH configuration may be understood as a RACH configuration for non-SBFD symbols, and a configuration for determining an RO for non-SBFD symbols in particular. On the other hand, a RACH configuration for SBFD symbols may be performed, and an RO for SBFD symbols in particular may be determined, based on the legacy RACH configuration.

[0093] In option 1, the UE 200 may operate as follows: Step 1: Determine an RO based on the legacy RACH configuration. Step 2: Determine a valid RO from the determined RO according to the legacy rule. Step 3: Map the determined valid RO to an SSB index according to the legacy SSB-RO mapping rule. Step 4: Transmit the selected preamble on the selected RO.

[0094] The following extensions are possible in Step 4 described above. Example 1-1: The UE 200 does not assume that any symbol (or at least one symbol) of the determined valid RO (and the N_gap symbols before the valid RO) is an SBFD FL symbol. Example 1-2: The UE 200 does not assume that a valid RO overlaps with an RB outside the UL subband within the SBFD FL symbol. Example 1-3: The UE 200 does not transmit a preamble in the determined valid RO if the determined valid RO overlaps with an RB outside the UL subband within the SBFD FL symbol. Example 1-4: The UE 200 does not transmit a preamble in the determined valid RO if the determined valid RO overlaps with an RB outside the UL subband within the SBFD FL symbol. Example 1-5: The UE 200 does not assume that the determined valid RO overlaps with both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD FL symbol). Example 1-6: If the determined valid RO overlaps both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD FL symbol), the UE 200 does not transmit a preamble in the valid RO.

[0095] As option 2, an example of combining legacy RACH configuration with extended rules for determining valid ROs will be described.

[0096] In option 2, the UE 200 may operate as follows: Step 1: Determine an RO based on the legacy RACH configuration. Step 2: Determine a valid RO from the determined RO by the extended rule. Step 3: Map the determined valid RO to an SSB index according to the legacy SSB-RO mapping rule. Step 4: Transmit the selected preamble on the selected RO.

[0097] In the above-mentioned Step 2, the above-mentioned extended rule for determining valid ROs can be used. Note that when Example A-1 shown in Fig. 11 is applied, the determined valid ROs can overlap with the outer overlap of the UL subband in the SBFD symbol. In this case, the extension in Step 4 described below is required.

[0098] The following extensions are possible in Step 4 described above. Example 2-1: UE200 does not assume a valid RO that overlaps with an RB outside the UL subband in an SBFD DL symbol (and / or SBFD SSB symbol) (and / or SBFD FL symbol). Example 2-2: UE200 does not transmit a preamble in a determined valid RO if the determined valid RO overlaps with an SBFD DL symbol (and / or SBFD SSB symbol) (and / or SBFD FL symbol). Example 2-3: UE200 does not assume that the determined valid RO overlaps with both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol). Example 2-4: UE200 does not transmit a preamble in a determined valid RO if the determined valid RO overlaps both a non-SBFD symbol (e.g., a UL symbol or a non-SBFD FL symbol) and an SBFD symbol (e.g., an SBFD DL symbol, and / or an SBFD FL symbol, and / or an SBFD SSB symbol).

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

[0100] As option 3, an example of combining legacy RACH configuration with legacy and extended rules for determining valid ROs will be described.

[0101] In option 3, UE 200 may operate as follows: Step 1: Determine an RO based on the legacy RACH configuration. Step 2A-1: From the determined RO, determine a valid RO according to the legacy rule. This valid RO may be called a legacy-valid RO. Step 2A-2: The determined valid RO is mapped to an SSB index according to the legacy SSB-RO mapping rule. Step 2B-1: From the determined RO (within or overlapping the SBFD DL symbol (and / or SBFD SSB symbol)), determine additional valid ROs according to the extended rule. Step 2B-2: The determined additional valid ROs are mapped to SSB indexes. Step 3: Transmit a selected preamble on the selected RO.

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

[0103] In Step 2B-2 described above, SBFD-valid ROs may be mapped to SSB indices separately from legacy-valid ROs. Alt-1 will be described below with reference to Fig. 17, and Alt-2 will be described with reference to Fig. 18.

[0104] Alt-1: Apply the legacy SSB-RO mapping rule to map SBFD-valid ROs to SSB indices as shown in Figure 17. That is, the number of SSB indices per RO and the number of preambles per SSB index or per RO are based on the parameters of the legacy RACH configuration. Also, the mapping order is first, ascending order of preamble index, second, ascending order of frequency resource index, and third, ascending order of PRACH slot.

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

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

[0107] Option 4 describes an example in which an additional / separate RACH configuration (to the legacy RACH configuration) (hereinafter also referred to as the RACH configuration for SBFD) is combined with an extended rule for determining a valid RO, as shown in Fig. 19. The RACH configuration for SBFD may be interpreted as a RACH configuration for SBFD symbols, and as a configuration that particularly determines an RO for the SBFD symbols. On the other hand, a RACH configuration for non-SBFD symbols may be performed, or an RO for non-SBFD symbols may be particularly determined, based on the RACH configuration for SBFD.

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

[0109] In Step 1B described above, a RACH configuration for SBFD is configured or indicated as an additional / separate RACH configuration, and the UE determines the RO based on the RACH configuration for SBFD. The RACH configuration for SBFD may be configured in the following IEs: Alt-1: It may be configured in additionalRACH-ConfigList. For example, the corresponding feature combination may be set for "SBFD". Alt-2: It may be configured in BWP-UplinkCommon. For example, RACH-ConfigCommon-SBFD-r19 and / or additionalRACH-ConfigList-SBFD-r19 and / or msgA-ConfigCommon-sbfd-r19 may be configured for SBFD. Alternatively, RACH-ConfigCommonTwoStepRA-sbfd-r19 in msgA-ConfigCommon may be configured for SBFD. Variation: It may be possible that the RACH configuration for SBFD can be supported for a given feature combination (e.g., Msg 1 / 3 repetitions and / or RedCap and / or SDT).

[0110] Furthermore, the following variations may be realized based on the RACH configuration for SBFD: Alt-a: Only ROs within SBFD symbols or ROs overlapping SBFD symbols are determined, and ROs within non-SBFD symbols or ROs overlapping non-SBFD symbols are excluded from the determination. Alt-b: It is not assumed that ROs are within non-SBFD symbols or overlapping non-SBFD symbols due to the RACH configuration. Alt-c: All ROs are determined by legacy rules, i.e., ROs are determined regardless of whether they are within SBFD symbols or overlap with SBFD symbols, or within non-SBFD symbols or overlap with non-SBFD symbols.

[0111] In the above-mentioned Step 2B, the above-mentioned extended rules for determining valid ROs can be used.

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

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

[0114] Note that an RA based on a common configuration (cell-common RACH configuration) and an RA based on a dedicated configuration differ in the following respects: That is, an RA based on a common configuration needs to take into consideration how a Legacy UE understands or interprets the configuration, whereas an RA based on a dedicated configuration does not need to take into consideration how a Legacy UE understands or interprets the configuration.

[0115] In option 1, based on the rach-ConfigBFR conventionally configured in BeamFailureRecoveryConfig and / or the cfra conventionally configured in RACH-ConfigDedicated and / or the rach-ConfigSI conventionally configured in SI-RequestConfig, an SBFD-aware UE always uses the extended rules for determining valid ROs described above.

[0116] In option 2, the gNB configures whether or not to always use the extended rules for determining valid ROs described above based on the rach-ConfigBFR conventionally configured in BeamFailureRecoveryConfig and / or the cfra conventionally configured in RACH-ConfigDedicated and / or the rach-ConfigSI conventionally configured in SI-RequestConfig.

[0117] In option 3, additional / separate configuration for RACH resource configuration for SBFD is performed, and the UE uses the extended rule for determining valid ROs described above to determine valid ROs 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 occasions of CFRA. And / or ・CFRA-TwoStep-sbfd-r19 is configured in RACH-ConfigDedicated. Alternatively, occasionsTwoStepRA-sbfd-r19 is set in CFRA-TwoStep. Alternatively, ConfigGenericTwoStepRA-sbfd-r19 is set in occasionsTwoStepRA-sbfd-r19 in CFRA-TwoStep. As a variation, two mask index values ​​are set for SBFD and non-SBFD in CFRA or CFRA-TwoStep. - Example: SI-RequestConfig-sbfd-r19 is set. Alternatively, rach-OccasionsSI-sbfd-r19 is set in SI-RequestConfig. Alternatively, rach-ConfigSI-sbfd-r19 is set in rach-OccasionsSI in SI-RequestConfig. As a variation, two mask index values ​​are set for SBFD and non-SBFD in SI-RequestResources.

[0118] Next, a description will be given of Operation Example 3. Operation Example 3 supports MsgA PUSCH transmission in SBFD symbols in 2-step RA. Specifically, it determines valid MsgA PUSCH occasions in SBFD symbols.

[0119] In determining a valid MsgA PUSCH occasion in an SBFD symbol, the above-described extended rule for determining a valid RO can be used by replacing the above-described "RO" with "MsgA PUSCH occasion." This extended rule is also referred to as an extended PO validity verification rule, etc.

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

[0121] <Mapping Between SSB and RO> Next, mapping between SSB and RO (SSB-to-RO mapping) will be described. For ROs that overlap with UL slots / symbols, it is desirable to have the same understanding of mapping between SSB and RO between SBFD-aware UE and Legacy UE. Therefore, RACH configuration may be distinguished in advance between SBFD slots / symbols and non-SBFD slots / symbols. This may allow for distinguishing in advance between ROs that overlap with SBFD slots / symbols and ROs that overlap with non-SBFD slots / symbols. In other words, while ROs are mapped to SSBs, ROs that overlap with SBFD slots / symbols may be mapped to SSBs separately from ROs that overlap with non-SBFD slots / symbols.

[0122] Distinguishing RACH configuration between SBFD slots / symbols and non-SBFD slots / symbols may be achieved, for example, as follows.

[0123] In addition to the RACH configuration for non-SBFD slots / symbols (conventional RACH configuration), parameters such as RACH-ConfigCommon-For-SBFD, RACH-ConfigCommonTwoStepRA-For-SBFD, RACH-ConfigDedicated-For-SBFD, RACH-ConfigGeneric-For-SBFD, and RACH-ConfigGenericTwoStepRA-For-SBFD may be indicated by SIB 1 or configured by RRC as the RACH configuration for SBFD slots / symbols.

[0124] This allows SBFD-aware UEs to distinguish between ROs that overlap SBFD slots / symbols, and therefore allows legacy UEs to have the same understanding of SSB and RO mapping for ROs that overlap non-SBFD slots / symbols.

[0125] When a PDCCH ordered RACH is used, it may be necessary to clarify whether the PRACH Mask index is for a non-SBFD slot / symbol or for a SBFD slot / symbol. For this purpose, the following means may be used.

[0126] - One bit from the reserved bits of DCI1_0 for RACH ordering may be used to indicate whether the RACH is configured for non-SBFD slots / symbols or for SBFD slots / symbols. - It may be set as a non-SBFD slot / symbol (or for SBFD slots / symbols) by default. - Since the order of ROs for non-SBFD slots / symbols and ROs for SBFD slots / symbols for the same SSB is the same, the PRACH Mask index may be used to indicate the ROs in the configured order.

[0127] Alternatively, the understanding of mapping between SSB and RO may be completely different between SBFD-aware UE and legacy UE. That is, selectable ROs may be distinguished in advance between SBFD-aware UE and legacy UE. In this case, SBFD-aware UE selects an RO for SBFD-aware UE, and legacy UE selects an RO for legacy UE.

[0128] <Regarding Determination of MsgA PUSCH Occasion> Next, determination of the MsgA PUSCH occasion (PO: PUSCH occasion) in current wireless communication systems will be described (for details, see section 8.1A of TS 38.213).

[0129] The UE determines the Msg A PO based on the PRACH slot set by the MsgA PRACH configuration and the following parameters included in the MsgA PUSCH configuration, for example:

[0130] For time domain resources, the UE is provided with the Start and Length Indicator Value (SLIV) for PUSCH transmission (startSymbolAndLengthMsgA-PO or startSymbolAndLength) and the PUSCH mapping type (MsgA-POmappingTypeMsgA-PUSCH) to determine the symbol allocation for Msg A PUSCH. To map the preamble of the PRACH slot to the PO, the UE determines the first slot of the first PUSCH from msgA-PUSCH-TimeDomainOffset, which provides the offset to the PRACH slot. The number of PUSCH slots is provided by nrofSlotsMsgA-PUSCH, and the number of PUSCHs included in each PUSCH slot is provided by nrofMsgA-PO-perSlot.

[0131] Regarding frequency domain resources, the first RB is provided by frequencyStartMsgA-PUSCH, the number of RBs in one PO is provided by nrofPRBs-perMsgA-PO, and the number of POs to be frequency-multiplexed is provided by nrofMsgA-PO-FDM.

[0132] For spatial domain resources, the DMRS resources are provided by msgA-DMRS-Config.

[0133] The above-mentioned Msg A PO determination is outlined in FIG.

[0134] <Regarding valid MsgA PO> Next, a valid MsgA RO that is valid as an MsgA PO in current wireless communication systems will be described (for details, see section 8.1A of TS 38.213).

[0135] The UE determines a valid PO to be a PO that does not overlap in the time domain and frequency domain with any valid PRACH occasion (RO) associated with either Type-1 random access or Type-2 random access.

[0136] Furthermore, if the UE is provided with tdd-UL-DL-ConfigurationCommon, the UE determines as a valid PO a PO in an UL symbol or a PO that starts at least Ngap symbols after the last DL symbol and at least Ngap symbols after the last SS / PBCH block symbol, and does not precede the SS / PBCH in a PUSCH slot.

[0137] <MsgA RO-preamble-to-PO mapping> Next, mapping between the MsgA RO-preamble and the PO (MsgA RO-preamble-to-PO mapping) will be described (for details, see section 8.1A of TS 38.213).

[0138] Npreamble preamble indices from valid ROs in a PRACH slot are mapped to valid POs and associated DMRS resources.

[0139] Mapping includes one-to-one mapping and multiple-to-one mapping. In one-to-one mapping, MsgA PUSCHs do not collide between UEs unless MsgA PRACHs collide between UEs. Multiple-to-one mapping achieves a high success rate for MsgA PRACHs and low overhead for MsgA PUSCH resources. The mapping ratio X (i.e., X-to-1 mapping) is implicitly derived by the total number of valid preambles and valid PRUs in the SSB-RO association pattern period.

[0140] The above MsgA RO-preamble-PO mapping is outlined in FIG.

[0141] The procedure based on the above-mentioned <Determining MsgA PUSCH occasion>, <Valid MsgA PO>, and <MsgA RO-preamble-PO mapping> will be described.

[0142] FIG. 22 is a diagram showing an overview of a conventional procedure in which a terminal determines an MsgA RO and an MsgA PO and maps an MsgA RO preamble to an MsgA PO.

[0143] Conventionally, a PRACH slot is determined based on a (legacy) MsgA PRACH configuration, an MsgA PO according to these configurations (legacy configurations) is determined based on the PRACH slot (i.e., the MsgA PRACH configuration) and the MsgA PUSCH configuration, and a valid MsgA PO (within a non-SBFD symbol) is determined from the determined MsgA PO. Meanwhile, a valid MsgA RO (within a non-SBFD symbol) is determined based on the (legacy) MsgA PRACH configuration. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0144] <Analysis> In the 3GPP RAN1#116 meeting, it was agreed that for SBFD aware UEs in an RRC connected state, Type 1 RACH will be supported in SBFD symbols. It was also agreed to consider the option of using a single RACH configuration or two separate RACH configurations, one legacy RACH configuration and one additional RACH configuration, for random access operation of SBFD aware UEs in an RRC connected state.

[0145] In 3GPP, random access in SBFD symbols for terminals in RRC idle / inactive mode will be further studied and will be specified for terminals in RRC connected mode. However, it is not yet determined whether Type 2 RACH in SBFD symbols will be supported. Supporting Type 2 RACH in SBFD symbols would be useful because it can reduce random access delay.

[0146] As described above, in the current wireless communication system, for Type 2 RACH, the relationship between MsgA PRACH transmission and MsgA PUSCH transmission in non-SBFD symbols is specified. However, the relationship between MsgA PRACH transmission and MsgA PUSCH transmission in SBFD symbols has not been clarified. If the resources for MsgA PRACH transmission and MsgA PUSCH transmission are not clarified, the MsgA PRACH and MsgA PUSCH cannot be transmitted appropriately, and delay reduction may not be achieved.

[0147] Therefore, proposals (Proposals 1 and 2) that clarify the details of whether / how to support MsgA PRACH transmission and MsgA PUSCH transmission in SBFD symbols are described in detail below.

[0148] Proposal 1 relates to the case where MsgA PRACH and MsgA PUSCH are supported in SBFD symbols, and Proposal 2 relates to the case where MsgA PRACH is supported in SBFD symbols but MsgA PUSCH is not supported in SBFD symbols.

[0149] There may be a case where MsgA PRACH in SBFD symbols is not supported, but MsgA PUSCH in SBFD symbols is supported, but this will not be discussed in this specification.

[0150] The items described in the following Proposal 1 and Proposal 2 may be combined as appropriate as long as no contradiction occurs.

[0151] In the following, SBFD symbols and non-SBFD symbols may be read as SBFD slots and non-SBFD slots, respectively.

[0152] In the following, mapping may be replaced with association, correspondence, linkage, etc.

[0153] Hereinafter, MsgA may be referred to as the first message, the first message, the first step message, etc. in two-step random access.

[0154] Hereinafter, the MsgA PRACH may be referred to as a preamble in two-step random access, a preamble in the first step, etc., and the MsgA PUSCH may be referred to as data in two-step random access, data in the first step, etc.

[0155] Hereinafter, the MsgA PRACH configuration may be referred to as information (first information) or setting (information) (first setting (information)) regarding two-step random access / regarding MsgA in two-step random access / regarding PRACH in two-step random access / for transmitting PRACH in two-step random access, etc.

[0156] Hereinafter, the MsgA PUSH configuration may be referred to as information (second information) or setting (information) (second setting (information)) regarding two-step random access / regarding MsgA in two-step random access / regarding PUSH in two-step random access / for transmitting PUSH in two-step random access, etc.

[0157] In the following, MsgA RO may be referred to as a (transmission) opportunity, a (transmission) opportunity for transmitting PRACH, etc., and MsgA PO may be referred to as a (transmission) opportunity, a (transmission) opportunity for transmitting PUSCH, etc.

[0158] <Proposal 1> First, Proposal 1 will be described, which relates to the case where MsgA PRACH and MsgA PUSCH are supported in the SBFD symbol.

[0159] [Option 1-1] In option 1-1, there may be separate MsgA PRACH configurations for legacy and SBFD, and there may be separate MsgA PUSCH configurations for legacy and SBFD.

[0160] Regarding the MsgA PRACH configuration, for example, there may be an existing MsgA-ConfigCommon for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for newly provided SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration). The additional MsgA PRACH configuration may be, for example, MsgA-ConfigCommon-sbfd-r19 (a configuration similar to MsgA-ConfigCommon-r16) and / or CFRA-TwoStep-sbfd-r19 (a configuration similar to CFRA-TwoStep-r16).

[0161] Regarding the MsgA PUSCH configuration, for example, there may be an existing MsgA-PUSCH-Config for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply as a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply as an additional PUSCH configuration).

[0162] As another example, as a configuration for MsgA PRACH, a legacy configuration (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration) may exist in an existing MsgA-ConfigCommon. The existing configuration in MsgA-ConfigCommon may be used as the legacy configuration. The newly provided additional MsgA PRACH configuration may be, for example, RACH-ConfigCommonTwoStepRA-sbfd-r19 (a configuration similar to RACH-ConfigCommonTwoStepRA-r16) and / or occasionsTwoStepRA-sbfd-r19 (a configuration similar to occasionsTwoStepRA-r16).

[0163] Furthermore, as a configuration for MsgA PUSCH, a legacy configuration (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply an additional PUSCH configuration) may exist in the existing MsgA-ConfigCommon. The existing configuration in MsgA-ConfigCommon may be used as the legacy configuration. The newly provided additional MsgA PUSCH configuration may be, for example, RACH-msgA-PUSCH-Config-sbfd-r19 (a configuration similar to msgA-PUSCH-Config-r16) and / or msgA-CFRA-PUSCH-sbfd-r19 (a configuration similar to msgA-CFRA-PUSCH-r16).

[0164] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0165] For the MsgA RO configured by the legacy PRACH configuration and the MsgA RO configured by the additional PRACH configuration, the terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0166] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0167] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0168] On the other hand, for SBFD, terminal 200 may determine the MsgA PO according to the additional configuration based on the PRACH slots set by the additional PRACH configuration and the additional PUSCH configuration for SBFD. Terminal 200 may determine the MsgA PO according to the additional configuration according to the mapping rules described in Alt-1A to Alt-1D below.

[0169] Alt-1A: A valid MsgA RO in an SBFD symbol with an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol with an additional configuration.

[0170] Alt-1B: A valid MsgA RO in an SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol and a non-SBFD symbol according to an additional configuration.

[0171] Alt-1C: A valid MsgA RO in an SBFD symbol and a non-SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol according to an additional configuration.

[0172] Alt-1D: A valid MsgA RO in an SBFD symbol and a non-SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol and a non-SBFD symbol according to an additional configuration.

[0173] The "valid MsgA RO according to the additional PRACH configuration" described in Alt-1A to Alt-1D may be determined, for example, as described below. - With regard to Alt-1A and Alt-1B, terminal 200 may determine a valid MsgA RO in an SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above. - With regard to Alt-1C and Alt-1D, terminal 200 may determine a valid MsgA RO in an SBFD symbol and a non-SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above.

[0174] Furthermore, the "valid MsgA PO according to additional configuration" described in Alt-1A to Alt-1D may be determined, for example, as described below: - With regard to Alt-1A and Alt-1C, terminal 200 may determine a valid MsgA PO including an MsgA PO according to additional configuration that is within an SBFD symbol (not overlapping with RBs outside the UL subband) that does not overlap in the time domain and frequency domain with any valid RO associated with either the Type 1 RACH or the Type 2 RACH. With respect to Alt-1B and Alt-1D, the terminal 200 may determine valid MsgA POs including (i) MsgA POs according to additional configurations that are located within SBFD symbols (that do not overlap with RBs outside the UL subband) and that do not overlap in the time and frequency domains with any valid ROs associated with either the Type 1 RACH or the Type 2 RACH, and (ii) MsgA POs that are located within non-SBFD symbols that do not overlap with DL / SSB symbols (and that do not overlap in the time and / or frequency domains with valid MsgA POs determined by the legacy MsgA configuration and legacy rules).

[0175] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0176] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) based on the MsgA PRACH configuration. Furthermore, terminal 200 may determine a valid MsgA PO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0177] FIG. 23 is a diagram summarizing valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 1-1 of Proposal 1.

[0178] FIG. 24 is a diagram showing an overview of a procedure for SBFD according to Option 1-1 of Proposal 1, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0179] In Option 1-1 of Proposal 1, a PRACH slot is determined based on an additional MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the additional MsgA PRACH configuration) and the additional MsgA PUSCH configuration, and a valid MsgA PO in an SBFD symbol (and in a non-SBFD symbol) is determined from the determined MsgA PO based on an extended PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol (and in a non-SBFD symbol) is determined based on the additional MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0180] [Option 1-2] In option 1-2, there may be separate MsgA PRACH configurations for legacy and SBFD, and there may be a common (i.e., single) MsgA PUSCH configuration for legacy and SBFD.

[0181] As configurations for MsgA PRACH, a legacy configuration (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration) may exist in the existing MsgA-ConfigCommon. As the legacy configuration, the existing configuration in MsgA-ConfigCommon may be used. The newly provided additional MsgA PRACH configuration may be, for example, RACH-ConfigCommonTwoStepRA-sbfd-r19 and / or occasionsTwoStepRA-sbfd-r19.

[0182] Regarding the MsgA PUSCH configuration, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration).

[0183] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0184] For the MsgA RO configured by the legacy PRACH configuration and the MsgA RO configured by the additional PRACH configuration, the terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0185] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0186] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0187] On the other hand, for SBFD, terminal 200 may determine the MsgA PO according to the additional configuration based on the PRACH slots set by the additional PRACH configuration and the legacy PUSCH configuration for SBFD. Terminal 200 may determine the MsgA PO according to the additional configuration according to the mapping rules described in Alt-2A to Alt-2D below.

[0188] Alt-2A: A valid MsgA RO in an SBFD symbol with an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol with an additional configuration.

[0189] Alt-2B: A valid MsgA RO in an SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol and a non-SBFD symbol according to an additional configuration.

[0190] Alt-2C: A valid MsgA RO in an SBFD symbol and a non-SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol according to an additional configuration.

[0191] Alt-2D: A valid MsgA RO in an SBFD symbol and a non-SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol and a non-SBFD symbol according to an additional configuration.

[0192] The "valid MsgA RO according to the additional PRACH configuration" described in Alt-2A to Alt-2D may be determined, for example, as described below. - With regard to Alt-2A and Alt-2B, the terminal 200 may determine a valid MsgA RO in an SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above. - With regard to Alt-2C and Alt-2D, the terminal 200 may determine a valid MsgA RO in an SBFD symbol and a non-SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above.

[0193] Furthermore, the "valid MsgA PO according to additional configuration" described in Alt-2A to Alt-2D may be determined, for example, as described below: - With regard to Alt-2A and Alt-2C, terminal 200 may determine a valid MsgA PO including an MsgA PO according to additional configuration that is within an SBFD symbol (that does not overlap with RBs outside the UL subband) and that does not overlap in the time domain and frequency domain with any valid RO associated with either Type 1 RACH or Type 2 RACH. With respect to Alt-2B and Alt-2D, the terminal 200 may determine valid MsgA POs including (i) MsgA POs according to additional configurations that are located within SBFD symbols (that do not overlap with RBs outside the UL subband) and that do not overlap in the time and frequency domains with any valid ROs associated with either the Type 1 RACH or the Type 2 RACH, and (ii) MsgA POs that are located within non-SBFD symbols that do not overlap with DL / SSB symbols (and that do not overlap in the time and / or frequency domains with valid MsgA POs determined by the legacy MsgA configuration and legacy rules).

[0194] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0195] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) based on the MsgA PRACH configuration. Furthermore, terminal 200 may determine a valid MsgA PO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0196] FIG. 25 is a diagram summarizing valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 1-2 of Proposal 1.

[0197] FIG. 26 is a diagram showing an overview of a procedure for SBFD according to Option 1-2 of Proposal 1, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0198] In Option 1-2 of Proposal 1, a PRACH slot is determined based on an additional MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the additional MsgA PRACH configuration) and the legacy MsgA PUSCH configuration, and a valid MsgA PO in an SBFD symbol (and in a non-SBFD symbol) is determined from the determined MsgA PO based on an extended PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol (and in a non-SBFD symbol) is determined based on the additional MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0199] [Option 1-3] In option 1-3, there may be a common (i.e., single) MsgA PRACH configuration for legacy and SBFD, and separate MsgA PUSCH configurations for legacy and SBFD.

[0200] As a configuration for MsgA PRACH, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration).

[0201] As a configuration for MsgA PUSCH, a legacy configuration (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply an additional PUSCH configuration) may exist in the existing MsgA-ConfigCommon. As the legacy configuration, the existing configuration in MsgA-ConfigCommon may be used. The newly provided additional MsgA PUSCH configuration may be, for example, RACH-msgA-PUSCH-Config-sbfd-r19 and / or msgA-CFRA-PUSCH-sbfd-r19.

[0202] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0203] For MsgA RO in SBFD symbols and non-SBFD symbols configured by the legacy PRACH configuration, terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0204] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0205] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0206] On the other hand, for SBFD, terminal 200 may determine the MsgA PO according to the additional configuration based on the PRACH slots configured by the legacy PRACH configuration and the additional PUSCH configuration for SBFD. Terminal 200 may determine the MsgA PO according to the additional configuration according to the mapping rules described in Alt-3A to Alt-3B below.

[0207] Alt-3A: A valid MsgA RO in an SBFD symbol according to the legacy PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol according to the additional configuration.

[0208] Alt-3B: A valid MsgA RO in an SBFD symbol according to the legacy PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol and a non-SBFD symbol according to the additional configuration.

[0209] The "valid MsgA RO according to the legacy PRACH configuration" described in Alt-3A to Alt-3B may be determined, for example, as described below: - The terminal 200 may determine a valid MsgA RO in the SBFD symbol set by the legacy PRACH configuration based on the extended RO validity verification rule described above.

[0210] Furthermore, the "valid MsgA PO according to additional configuration" described in Alt-3A to Alt-3B may be determined, for example, as follows: - With regard to Alt-3A, terminal 200 may determine a valid MsgA PO including an MsgA PO according to additional configuration that is within an SBFD symbol (that does not overlap with RBs outside the UL subband) and that does not overlap in the time domain and frequency domain with any valid RO associated with either Type 1 RACH or Type 2 RACH. With respect to Alt-3B, the terminal 200 may determine valid MsgA POs including (i) MsgA POs according to additional configurations that are located within SBFD symbols (that do not overlap with RBs outside the UL subband) and that do not overlap in the time and frequency domains with any valid ROs associated with either the Type 1 RACH or the Type 2 RACH, and (ii) MsgA POs that are located within non-SBFD symbols that do not overlap with DL / SSB symbols (and that do not overlap in the time and / or frequency domains with valid MsgA POs determined by the legacy MsgA configuration and legacy rules).

[0211] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0212] Terminal 200 may determine a valid MsgA RO in an SBFD symbol based on the MsgA PRACH configuration as described above. Terminal 200 may also determine a valid MsgA PO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration as described above.

[0213] FIG. 27 is a diagram summarizing the valid MsgA RO and valid MsgA PO determined based on the configuration according to options 1-3 of Proposal 1.

[0214] Figure 28 shows an overview of the procedures for SBFD according to options 1-3 of Proposal 1, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0215] In Options 1-3 of Proposal 1, a PRACH slot is determined based on the legacy MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the legacy MsgA PRACH configuration) and the additional MsgA PUSCH configuration, and a valid MsgA PO in an SBFD symbol (and in a non-SBFD symbol) is determined from the determined MsgA PO based on the extended PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol (and in a non-SBFD symbol) is determined based on the legacy MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0216] [Option 1-4] In option 1-4, there may be a common (i.e., single) MsgA PRACH configuration for legacy and SBFD, and a common (i.e., single) MsgA PUSCH configuration for legacy and SBFD.

[0217] As a configuration for MsgA PRACH, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration).

[0218] Regarding the MsgA PUSCH configuration, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration).

[0219] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0220] For MsgA RO in SBFD symbols and non-SBFD symbols configured by the legacy PRACH configuration, terminal 200 may apply separate SSB-RO mapping and RO-RO-preamble-PO mapping, where the mappings described in <Determining a Valid RO> and <Mapping Between SSB and RO> may be used for the separate SSB-RO mapping.

[0221] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0222] On the other hand, for SBFD, the terminal 200 may determine the MsgA PO according to the legacy configuration based on the PRACH slots set by the legacy PRACH configuration and the legacy PUSCH configuration for SBFD. The terminal 200 may determine the MsgA PO according to the legacy configuration according to the following mapping rule: A valid MsgA RO in an SBFD symbol according to the legacy PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol according to the legacy configuration.

[0223] Furthermore, terminal 200 may determine a valid MsgA RO in an SBFD symbol configured by the legacy PRACH configuration based on the extended RO validity verification rule described above.

[0224] Terminal 200 may also determine a valid MsgA PO, including an MsgA PO according to a legacy configuration, within an SBFD symbol (not overlapping with RBs outside the UL subband) that does not overlap in the time domain or frequency domain with any valid RO associated with either Type 1 RACH or Type 2 RACH.

[0225] As described above, terminal 200 may determine a valid MsgA RO within an SBFD symbol based on the MsgA PRACH configuration. Also, terminal 200 may determine a valid MsgA PO within an SBFD symbol that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0226] FIG. 29 is a diagram summarizing the valid MsgA RO and valid MsgA PO determined based on the configuration according to options 1-4 of Proposal 1.

[0227] FIG. 30 shows an overview of the procedure according to options 1-4 of Proposal 1, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0228] In Options 1-4 of Proposal 1, a PRACH slot is determined based on the legacy MsgA PRACH configuration, an MsgA PO according to these configurations (legacy configurations) is determined based on the PRACH slot (i.e., the legacy MsgA PRACH configuration) and the legacy MsgA PUSCH configuration, and a valid MsgA PO in an SBFD symbol is determined from the determined MsgA PO based on the extended PO validity verification rule. Also, a valid MsgA PO in a non-SBFD symbol is determined from the determined MsgA PO based on the legacy validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol is determined based on the legacy MsgA PRACH configuration and the extended RO validity verification rule. Furthermore, a valid MsgA RO in a non-SBFD symbol is determined based on the legacy MsgA PRACH configuration and the legacy RO validity verification rule, and the preamble of the valid MsgA RO in the SBFD symbol is mapped to a valid MsgA PO in the SBFD symbol, and the preamble of the valid MsgA RO in a non-SBFD symbol is mapped to a valid MsgA PO in the non-SBFD symbol.

[0229] <Proposal 2> Next, we will describe Proposal 2 for the case where MsgA PRACH in SBFD symbols is supported but MsgA PUSCH in SBFD symbols is not supported. Therefore, in Proposal 2, a valid MsgA RO in an SBFD symbol may be mapped to a valid MsgA PO in a non-SBFD symbol (i.e., a valid MsgA PO determined based on the legacy validity verification rules).

[0230] [Option 2-1] In option 2-1, there may be separate MsgA PRACH configurations for legacy and SBFD, and there may be separate MsgA PUSCH configurations for legacy and SBFD.

[0231] Regarding the MsgA PRACH configuration, for example, there may be an existing MsgA-ConfigCommon for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for newly provided SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration). The additional MsgA PRACH configuration may be, for example, MsgA-ConfigCommon-sbfd-r19 and / or CFRA-TwoStep-sbfd-r19.

[0232] With regard to the MsgA PUSCH configuration (MsgA-PUSCH-Config), for example, there may be an existing configuration for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply an additional PUSCH configuration).

[0233] As another example, as a configuration for MsgA PRACH, a legacy configuration (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration) may exist in the existing MsgA-ConfigCommon. The existing configuration in MsgA-ConfigCommon may be used as the legacy configuration. The newly provided additional MsgA PRACH configuration may be, for example, RACH-ConfigCommonTwoStepRA-sbfd-r19 and / or occasionsTwoStepRA-sbfd-r19.

[0234] Furthermore, as configurations for the MsgA PUSCH, a legacy configuration (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply an additional PUSCH configuration) may exist in the existing MsgA-ConfigCommon. The existing configuration in MsgA-ConfigCommon may be used as the legacy configuration. The newly provided additional MsgA PUSCH configuration may be, for example, RACH-msgA-PUSCH-Config-sbfd-r19 and / or msgA-CFRA-PUSCH-sbfd-r19.

[0235] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0236] For the MsgA RO configured by the legacy PRACH configuration and the MsgA RO configured by the additional PRACH configuration, the terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0237] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0238] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0239] On the other hand, for SBFD, terminal 200 may determine an MsgA PO according to an additional configuration based on a PRACH slot set by an additional PRACH configuration and an additional PUSCH configuration for SBFD. Terminal 200 may determine an MsgA PO according to an additional configuration according to mapping rules described in Alt-1A to Alt-1B below.

[0240] Alt-1A: A valid MsgA RO in an SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO (in a non-SBFD symbol) according to an additional configuration.

[0241] Alt-1B: Valid MsgA ROs in SBFD symbols and non-SBFD symbols according to the additional PRACH configuration may be mapped to valid MsgA POs (in non-SBFD symbols) according to the additional configuration.

[0242] The "valid MsgA RO according to the additional PRACH configuration" described in Alt-1A to Alt-1B may be determined, for example, as described below. - Regarding Alt-1A, terminal 200 may determine a valid MsgA RO in an SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above. - Regarding Alt-1B, terminal 200 may determine a valid MsgA RO in an SBFD symbol and a non-SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above.

[0243] Furthermore, the "valid MsgA PO according to additional configuration" described in Alt-1A to Alt-1B may be determined, for example, as described below: - With regard to Alt-1A and Alt-1B, the terminal 200 may determine a valid MsgA PO (in a non-SBFD symbol) from the MsgA PO according to additional configuration based on the legacy validity verification rules described above. - With respect to Alt-1A and Alt-1B, additionally or alternatively, terminal 200 may determine valid MsgA POs in non-SBFD symbols, including additional configured MsgA POs, that do not overlap in the time and frequency domains with any valid ROs associated with either Type 1 RACH or Type 2 RACH, that do not overlap with DL / SSB symbols (and that do not overlap in the time and / or frequency domains with valid MsgA POs determined by legacy MsgA configurations and legacy rules).

[0244] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0245] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) based on the MsgA PRACH configuration. Also, as described above, terminal 200 may determine a valid MsgA PO in a non-SBFD symbol that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0246] FIG. 31 is a diagram summarizing valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 2-1 of Proposal 2.

[0247] FIG. 32 is a diagram showing an overview of a procedure for SBFD according to Option 2-1 of Proposal 2, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0248] In Option 2-1 of Proposal 2, a PRACH slot is determined based on an additional MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the additional MsgA PRACH configuration) and the additional MsgA PUSCH configuration, and a valid MsgA PO in a non-SBFD symbol is determined from the determined MsgA PO based on the legacy PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol (and in a non-SBFD symbol) is determined based on the additional MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0249] [Option 2-2] In option 2-2, there may be separate MsgA PRACH configurations for legacy and SBFD, and there may be a common (i.e., single) MsgA PUSCH configuration for legacy and SBFD.

[0250] As configurations for MsgA PRACH, a legacy configuration (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PRACH configuration or simply an additional PRACH configuration) may exist in the existing MsgA-ConfigCommon. As the legacy configuration, the existing configuration in MsgA-ConfigCommon may be used. The newly provided additional MsgA PRACH configuration may be, for example, RACH-ConfigCommonTwoStepRA-sbfd-r19 and / or occasionsTwoStepRA-sbfd-r19.

[0251] Regarding the MsgA PUSCH configuration, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration).

[0252] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0253] For the MsgA RO configured by the legacy PRACH configuration and the MsgA RO configured by the additional PRACH configuration, the terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0254] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0255] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0256] On the other hand, for SBFD, terminal 200 may determine the MsgA PO according to the additional configuration based on the PRACH slots set by the additional PRACH configuration and the legacy PUSCH configuration for SBFD. Terminal 200 may determine the MsgA PO according to the additional configuration according to the mapping rules described in Alt-2A to Alt-2B below.

[0257] Alt-2A: A valid MsgA RO in an SBFD symbol according to an additional PRACH configuration may be mapped to a valid MsgA PO (in a non-SBFD symbol) according to an additional configuration.

[0258] Alt-2B: Valid MsgA ROs in SBFD symbols and non-SBFD symbols according to the additional PRACH configuration may be mapped to valid MsgA POs (in non-SBFD symbols) according to the additional configuration.

[0259] The "valid MsgA RO according to the additional PRACH configuration" described in Alt-2A to Alt-2B may be determined, for example, as described below. - Regarding Alt-2A, terminal 200 may determine a valid MsgA RO in an SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above. - Regarding Alt-2B, terminal 200 may determine a valid MsgA RO in an SBFD symbol and a non-SBFD symbol configured by the additional PRACH configuration based on the extended RO validity verification rule described above.

[0260] Furthermore, the "valid MsgA PO with additional configuration" described in Alt-2A to Alt-2B may be determined, for example, as described below: - With regard to Alt-2A and Alt-2B, the terminal 200 may determine a valid MsgA PO (in a non-SBFD symbol) from the MsgA PO with additional configuration based on the legacy validity verification rules described above. - With respect to Alt-2A and Alt-2B, additionally or alternatively, terminal 200 may determine valid MsgA POs in non-SBFD symbols, including additional configured MsgA POs, that do not overlap in the time and frequency domains with any valid ROs associated with either Type 1 RACH or Type 2 RACH, that do not overlap with DL / SSB symbols (and that do not overlap in the time and / or frequency domains with valid MsgA POs determined by legacy MsgA configurations and legacy rules).

[0261] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0262] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol (or an SBFD symbol and a non-SBFD symbol) based on the MsgA PRACH configuration. Also, as described above, terminal 200 may determine a valid MsgA PO in a non-SBFD symbol that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0263] FIG. 33 is a diagram summarizing valid MsgA RO and valid MsgA PO determined based on the configuration according to Option 2-2 of Proposal 2.

[0264] Figure 34 shows an overview of the procedure for SBFD according to Option 2-2 of Proposal 2, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0265] In Option 2-2 of Proposal 2, a PRACH slot is determined based on an additional MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the additional MsgA PRACH configuration) and the legacy MsgA PUSCH configuration, and a valid MsgA PO in a non-SBFD symbol is determined from the determined MsgA PO based on the legacy PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol (and in a non-SBFD symbol) is determined based on the additional MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0266] [Option 2-3] In option 2-3, there may be a common (i.e., single) MsgA PRACH configuration for legacy and SBFD, and separate MsgA PUSCH configurations for legacy and SBFD.

[0267] As a configuration for MsgA PRACH, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration).

[0268] As a configuration for MsgA PUSCH, a legacy configuration (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration) and an additional configuration for SBFD (which may be referred to as an additional MsgA PUSCH configuration or simply an additional PUSCH configuration) may exist in the existing MsgA-ConfigCommon. As the legacy configuration, the existing configuration in MsgA-ConfigCommon may be used. The newly provided additional MsgA PUSCH configuration may be, for example, RACH-msgA-PUSCH-Config-sbfd-r19 and / or msgA-CFRA-PUSCH-sbfd-r19.

[0269] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0270] For MsgA RO in SBFD symbols and non-SBFD symbols configured by the legacy PRACH configuration, terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0271] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0272] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0273] On the other hand, for SBFD, the terminal 200 may determine an MsgA PO according to the additional configuration based on the PRACH slots set by the legacy PRACH configuration and the additional PUSCH configuration for SBFD. The terminal 200 may determine an MsgA PO according to the additional configuration according to a mapping rule described below. A valid MsgA RO in an SBFD symbol according to the legacy PRACH configuration may be mapped to a valid MsgA PO (in a non-SBFD symbol) according to the additional configuration.

[0274] The "valid MsgA RO according to the legacy PRACH configuration" in the above may be determined, for example, as described below: - The terminal 200 may determine a valid MsgA RO in the SBFD symbol set by the legacy PRACH configuration based on the extended RO validity verification rule described above.

[0275] The "valid MsgA PO according to the additional configuration" in the above may be determined, for example, as described below. - The terminal 200 may determine a valid MsgA PO (in a non-SBFD symbol) from the MsgA PO according to the additional configuration based on the legacy validity verification rules described above. - Additionally or alternatively, the terminal 200 may determine a valid MsgA PO in a non-SBFD symbol including an MsgA PO according to the additional configuration that is in a non-SBFD symbol that does not overlap in the time domain and frequency domain with any valid RO associated with either the Type 1 RACH or the Type 2 RACH and does not overlap with DL / SSB symbols (and does not overlap in the time domain and / or frequency domain with a valid MsgA PO determined by the legacy MsgA configuration and legacy rules).

[0276] Additionally or alternatively, the terminal 200 may not assume that the determined valid MsgA PO overlaps (may assume no overlap) with the valid MsgA PO determined by the legacy MsgA configuration in the time domain and / or frequency domain.

[0277] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol based on the MsgA PRACH configuration. Also, terminal 200 may determine a valid MsgA PO in a non-SBFD symbol that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0278] FIG. 35 is a diagram summarizing valid MsgA RO and valid MsgA PO determined based on the configuration according to option 2-3 of proposal 2.

[0279] Figure 36 shows an overview of the procedure for SBFD according to option 2-3 of Proposal 2, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0280] In Option 2-3 of Proposal 2, a PRACH slot is determined based on the legacy MsgA PRACH configuration, an MsgA PO according to these configurations (additional configurations) is determined based on the PRACH slot (i.e., the legacy MsgA PRACH configuration) and the additional MsgA PUSCH configuration, and a valid MsgA PO in a non-SBFD symbol is determined from the determined MsgA PO based on the legacy PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol is determined based on the legacy MsgA PRACH configuration and the extended RO validity verification rule. Then, the preamble of the valid MsgA RO is mapped to the valid MsgA PO.

[0281] [Option 2-4] In option 2-4, there may be a common (i.e., single) MsgA PRACH configuration for legacy and SBFD, and a common (i.e., single) MsgA PUSCH configuration for legacy and SBFD.

[0282] As a configuration for MsgA PRACH, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PRACH configuration or simply a legacy PRACH configuration).

[0283] Regarding the MsgA PUSCH configuration, for example, there may be a single existing configuration for legacy use (which may be referred to as a legacy MsgA PUSCH configuration or simply a legacy PUSCH configuration).

[0284] Terminal 200 may receive the above-described MsgA PRACH configuration and MsgA PUSCH configuration from base station 100.

[0285] For MsgA RO in SBFD symbols and non-SBFD symbols configured by the legacy PRACH configuration, terminal 200 may apply separate SSB-RO mapping and RO-preamble-PO mapping, as described in <Determining a Valid RO> and <Mapping Between SSB and RO>.

[0286] For non-SBFD (i.e., legacy), terminal 200 may apply the legacy rules for determining MsgA PUSCH occasion, valid MsgA PO, and MsgA RO-preamble-PO mapping as well as those described in FIG. 22 for the legacy PRACH configuration and legacy PUSCH configuration.

[0287] Also, with respect to non-SBFD, additionally or alternatively, terminal 200 may not assume any valid MsgA PO in an SBFD symbol according to the legacy MsgA configuration (legacy PRACH configuration and / or legacy PUSCH configuration), and may consider (may assume) a symbol including a valid MsgA PO according to the legacy MsgA configuration as a non-SBFD symbol.

[0288] On the other hand, for SBFD, the terminal 200 may determine the MsgA PO according to the legacy configuration based on the PRACH slots set by the legacy PRACH configuration and the legacy PUSCH configuration for SBFD. The terminal 200 may determine the MsgA PO according to the legacy configuration according to the following mapping rule: A valid MsgA RO in an SBFD symbol according to the legacy PRACH configuration may be mapped to a valid MsgA PO in an SBFD symbol according to the legacy configuration.

[0289] As described above, terminal 200 may determine a valid MsgA RO in an SBFD symbol based on the MsgA PRACH configuration. Also, terminal 200 may determine a valid MsgA PO in a non-SBFD symbol that is mapped to a valid MsgA RO based on the MsgA PRACH configuration and the MsgA PUSCH configuration.

[0290] FIG. 37 is a diagram summarizing the valid MsgA RO and valid MsgA PO determined based on the configuration according to options 2-4 of proposal 2.

[0291] FIG. 38 shows an overview of the procedure according to Option 2-4 of Proposal 2, in which the terminal determines the MsgA RO and MsgA PO and maps the MsgA RO preamble to the MsgA PO.

[0292] In Option 2-4 of Proposal 2, a PRACH slot is determined based on the legacy MsgA PRACH configuration, an MsgA PO according to these configurations (legacy configurations) is determined based on the PRACH slot (i.e., the legacy MsgA PRACH configuration) and the legacy MsgA PUSCH configuration, and a valid MsgA PO in a non-SBFD symbol is determined from the determined MsgA PO based on the legacy PO validity verification rule. Meanwhile, a valid MsgA RO in an SBFD symbol is determined based on the legacy MsgA PRACH configuration and the extended RO validity verification rule. Also, a valid MsgA RO in a non-SBFD symbol is determined based on the legacy MsgA PRACH configuration and the legacy RO validity verification rule. Then, the preamble of a valid MsgA RO in an SBFD symbol is mapped to a valid MsgA PO in a non-SBFD symbol, and the preamble of a valid MsgA RO in a non-SBFD symbol is mapped to a valid MsgA PO in a non-SBFD symbol.

[0293] <Operation of Wireless Communication System> Next, an example of operation of the wireless communication system 10 will be described with reference to FIG.

[0294] FIG. 39 is a flowchart showing an example of the operation of the terminal 200.

[0295] In step S11, the terminal 200 receives first setting information and second setting information related to two-step random access from the base station 100. The first setting information may be the above-described MsgA PRACH configuration, and the second setting information may be the above-described MsgA PUSCH configuration.

[0296] In step S12, the terminal 200 determines, based on the received first configuration information, a first valid transmission opportunity for transmitting a preamble in the first step in a time unit including a first time unit in which multiple subbands constituting a time division duplex band are available, and determines, based on the received first and second configuration information, a second valid transmission opportunity associated with the first valid transmission opportunity and for transmitting data in the first step. The first transmission opportunity may be the above-mentioned MsgA RO, and the second transmission opportunity may be the above-mentioned MsgA PO.

[0297] Although the present proposal has been described above, the present proposal may be applied to the terminal 200 in a connected mode and / or an RRC idle mode. The present proposal may also be applied to CBRA and CRFA.

[0298] <UE capability> UE capability indicating the capabilities of a terminal may include the following information indicating the capabilities of the terminal. For example, new UE capabilities and report signaling (and RRC settings) shown below may be defined for each UE / FR / FC, etc. Terminal 200 may report the following information indicating the capabilities of the terminal to base station 100. Note that the information indicating the capabilities of the terminal may correspond to information defining the capabilities of the terminal. - Whether MsgA PRACH transmission in SBFD symbols is supported - Whether MsgA PUSCH transmission in SBFD symbols is supported - Whether mapping of MsgA PRACH occasions in SBFD symbols to MsgA PUSCH occasions in SBFD symbols is supported - Whether mapping of MsgA PRACH occasions in SBFD symbols to MsgA PUSCH occasions in non-SBFD symbols is supported

[0299] Next, the configurations of the base station 100 and the terminal 200 will be described. Note that the configurations of the base station 100 and the terminal 200 described below are examples of functions related to this embodiment. The base station 100 and the terminal 200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0300] <Configuration of Base Station> Fig. 40 is a block diagram showing an example of the configuration of base station 100 according to this embodiment. Base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 100 communicates with terminal 200 (see Fig. 41) wirelessly.

[0301] The transmitter 101 transmits a downlink (DL) signal to the terminal 200. For example, under the control of the controller 103, the transmitter 101 transmits a DL signal (for example, the above-mentioned RRC, SIB, MAC CE, DCI, notification, confirmation, etc.).

[0302] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of terminal 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0303] The channels used for transmitting DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 100 transmits downlink control information to the terminal 200 using the PDCCH and transmits downlink data signals using the PDSCH.

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

[0305] The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 200. For example, the receiving unit 102 receives an UL signal (for example, the above-mentioned request, notification, etc.) under the control of the control unit 103.

[0306] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.

[0307] The control unit 103 controls the communication operations of the base station 100 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0308] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

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

[0310] <Configuration of Terminal> Fig. 41 is a block diagram showing an example of the configuration of terminal 200 according to this embodiment. Terminal 200 includes, for example, receiving section 201, transmitting section 202, and control section 203. Terminal 200 communicates with base station 100, for example, wirelessly.

[0311] The transmitter 202 transmits an UL signal to the base station 100. For example, the transmitter 202 transmits the UL signal under the control of the controller 203. For example, the transmitter 202 may transmit an MsgA PRACH in a valid MsgA RO determined by the controller 203, or may transmit an MsgA PUSCH in a valid MsgA PO determined by the controller 203.

[0312] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the terminal 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

[0313] Channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, terminal 200 transmits uplink control information to base station 100 using the PUCCH and transmits uplink data signals using the PUSCH.

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

[0315] The receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.

[0316] The control unit 203 controls the communication operations of the terminal 200 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0317] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

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

[0319] For example, the receiving unit 201 may receive first setting information and second setting information related to two-step random access, and the control unit 203 may determine, based on the first setting information, a valid first transmission opportunity for transmitting a preamble in the first step in a time unit including a first time unit in which multiple subbands constituting a time division duplex band are available, and may determine, based on the first setting information and the second setting information, a valid second transmission opportunity associated with the valid first transmission opportunity and for transmitting data in the first step. The first setting information may include third setting information for time units in which multiple subbands constituting a time division duplex band are available, and the control unit 203 may determine, based on the third setting information, a valid first transmission opportunity in the first time unit. The time unit may include a second time unit in which time division duplex is applied. The first setting information may include fourth setting information for time units in which time division duplex is applied, and the control unit 203 may determine, based on the fourth setting information, a valid first transmission opportunity in the first time unit or the second time unit. The second transmission opportunity may be within a third time unit in which multiple subbands constituting a time division duplex band are available and / or within a fourth time unit in which time division duplex is applied.

[0320] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned example. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0321] With the above configuration, the preamble and data can be transmitted appropriately in the two-step random access procedure.

[0322] Summary of Embodiment As described above, according to one aspect of the present disclosure, there is provided a terminal including: a receiving unit that receives first setting information and second setting information related to two-step random access; and a control unit that determines, based on the first setting information, a first valid transmission opportunity for transmitting a preamble in a first step in a time unit that includes a first time unit in which a plurality of subbands that constitute a time division duplex band are available, and that determines, based on the first setting information and the second setting information, a second valid transmission opportunity that is associated with the first valid transmission opportunity and is used to transmit data in the first step.

[0323] The above configuration makes it possible to determine valid transmission opportunities for transmitting a preamble and valid transmission opportunities for transmitting data, thereby enabling appropriate transmission of the preamble and data in a two-step random access procedure.

[0324] In one example, the first setting information includes third setting information for a time unit in which multiple subbands that constitute the time division duplex band are available, and the control unit determines the effective first transmission opportunity in the first time unit based on the third setting information.

[0325] With the above configuration, it is possible to flexibly set the time unit (for example, SBFD symbol) in which a plurality of subbands can be used based on the third setting information and transmit a preamble.

[0326] In one example, the time unit includes a second time unit in which the time division duplex is applied.

[0327] With the above configuration, it is possible to transmit a preamble even in a time unit in which multiple subbands are not available (for example, a non-SBFD symbol).

[0328] In one example, the first setting information includes fourth setting information for a time unit to which the time division duplex is applied, and the control unit determines the valid first transmission opportunity in the first time unit or the second time unit based on the fourth setting information.

[0329] With the above configuration, a preamble can be transmitted by flexibly setting the time units in which multiple subbands are available (e.g., SBFD symbols) and / or the time units in which multiple subbands are not available (e.g., non-SBFD symbols) based on the fourth setting information.

[0330] In one example, the second transmission opportunity is within a third time unit in which multiple subbands constituting the time division duplex band are available and / or a fourth time unit in which the time division duplex is applied.

[0331] With the above configuration, data can be transmitted in time units where multiple subbands are available (e.g., SBFD symbols) and / or in time units where multiple subbands are not available (e.g., non-SBFD symbols).

[0332] According to one aspect of the present disclosure, a communication method is provided in which a terminal receives first setting information and second setting information related to two-step random access, determines, based on the first setting information, a valid first transmission opportunity for transmitting a preamble in the first step in a time unit including a first time unit in which multiple subbands constituting a time division duplex band are available, and determines, based on the first setting information and the second setting information, a valid second transmission opportunity associated with the valid first transmission opportunity for transmitting data in the first step.

[0333] The above configuration makes it possible to determine valid transmission opportunities for transmitting a preamble and valid transmission opportunities for transmitting data, thereby enabling appropriate transmission of the preamble and data in a two-step random access procedure.

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

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

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

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

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

[0339] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

[0340] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

[0343] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

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

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

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

[0347] (Supplementary Notes on the Embodiments) Although the embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing procedures described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of a base station in accordance with an embodiment of the present disclosure, and the software operated by the processor of a terminal in accordance with an embodiment of the present disclosure may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0349] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0350] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

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

[0352] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0353] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

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

[0355] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0356] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

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

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

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

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

[0361] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0362] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

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

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

[0365] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

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

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

[0370] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal may be configured to have the functions of the base station described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

[0372] Fig. 43 shows an example configuration of a vehicle 2001. As shown in Fig. 43, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

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

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

[0378] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

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

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

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

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

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

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

[0387] "First," "Second" Any reference to an element using designations such as "first," "second," etc., 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 method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

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

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

[0390] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

[0395] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0409] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0412] One aspect of the present disclosure is useful in wireless communication systems.

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

Claims

1. A terminal comprising: a receiving unit that receives first setting information and second setting information related to two-step random access; and a control unit that determines, based on the first setting information, a valid first transmission opportunity for transmitting a preamble in the first step in a time unit that includes a first time unit in which multiple subbands that make up a time division duplex band can be used, and that determines, based on the first setting information and the second setting information, a valid second transmission opportunity that is associated with the valid first transmission opportunity and is used to transmit data in the first step.

2. The terminal according to claim 1, wherein the first setting information includes third setting information for a time unit in which multiple subbands constituting the time division duplex band are available, and the control unit determines the effective first transmission opportunity in the first time unit based on the third setting information.

3. The terminal according to claim 1, wherein the time unit includes a second time unit to which the time division duplex is applied.

4. The terminal described in claim 3, wherein the first setting information includes fourth setting information for a time unit to which the time division duplex is applied, and the control unit determines the effective first transmission opportunity in the first time unit or the second time unit based on the fourth setting information.

5. The terminal according to claim 1, wherein the second transmission opportunity is within a third time unit in which a plurality of subbands constituting the time division duplex band are available and / or a fourth time unit in which the time division duplex is applied.

6. A communication method in which a terminal receives first setting information and second setting information related to two-step random access, determines a valid first transmission opportunity for transmitting a preamble in the first step in a time unit including a first time unit in which multiple subbands constituting a time division duplex band are available based on the first setting information, and determines a valid second transmission opportunity associated with the valid first transmission opportunity for transmitting data in the first step based on the first setting information and the second setting information.

Images