Terminal and communication method

Abstract

To provide a terminal in which the featureCombinationPreamble is properly set and interpreted in legacy-RO and additional-RO.SOLUTION: There are multiple SBFD ROs or non-SBFD ROs associated with a specific SSB, and an index value indicating the usable SBFD RO or non-SBFD RO is determined depending on whether the terminal supports a specific function. The index value can be determined either commonly for the SBFD RO and non-SBFD RO or individually, and the terminal configures a valid RO from among the usable SBFD RO or non-SBFD RO on the basis of whether the terminal supports a specific function and the index value.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

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

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

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

[0005] In addition, the terminal (hereinafter also referred to as "user equipment (UE)") determines a random access opportunity (RO) for transmitting a preamble that starts an RA based on RACH communication from the base station (hereinafter also referred to as "gNodeB (gNB)"), and further determines a valid RO from among the ROs. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 [Non-patent document 2] 3GPP TS 38.321 V18.5.0 (2025-03) [Non-patent document 3] 3GPP TS 38.300 V18.5.0 (2025-03) [Non-patent document 4] 3GPP TS 38.331 V18.5.0 (2025-03) Summary of the Invention

[0007] There are two types of UE: "SBFD-aware UE" that supports SBFD operation and "legacy UE" that does not. There are also two types of RO: "legacy-RO" and "additional-RO". SBFD-aware UE can send preambles using both legacy-RO and additional-RO. On the other hand, legacy UE cannot use additional-RO and can only send preambles using legacy-RO.

[0008] Non-patent document 4 defines a featureCombinationPreamble, which is an information element (IE) for a function that allows a UE to recognize whether or not a specific function is supported by the network using a preamble or an RO.

[0009] However, it is not clear at present how to set and interpret the shared / individual RO mask index configuration of legacy-RO and additional-RO in the featureCombinationPreamble.

[0010] If the featureCombinationPreamble is not properly configured and interpreted in the legacy-RO and additional-RO, the UE cannot properly select an RO in an RA.

[0011] One aspect of the present disclosure contributes to a terminal that can appropriately select an RO in an RA by appropriately setting and interpreting a featureCombinationPreamble in a legacy-RO and an additional-RO.

[0012] A terminal according to one embodiment of the present disclosure includes: a control unit that selects a valid random access opportunity from among a first random access opportunity that is set in a first time unit in which simultaneous use of the downlink and the uplink is possible using a plurality of subbands that constitute a time division duplex band; and a second random access opportunity that is set in a second time unit in which one of the downlink and the uplink is usable by applying the time division duplex band; and a transmission unit that transmits a random access preamble using the valid random access opportunity, wherein there are a plurality of the first random access opportunities or the second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block), and an index value indicating the usable first random access opportunity or the second random access opportunity is determined depending on whether the terminal supports a specific function, and it is determined whether the index value is determined commonly for the first random access opportunity and the second random access opportunity or whether it is determined individually for the first random access opportunity and the second random access opportunity, and the control unit selects the valid random access opportunity from among the usable first random access opportunities or the second random access opportunities based on whether the terminal supports the specific function and the index value. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] FIG. 1 is a diagram illustrating an example of TDD settings defined up to Rel-16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of a CBRA procedure. [Figure 8] FIG. 10 is a sequence diagram illustrating another example of the CBRA procedure. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a CFRA procedure. [Figure 10] A diagram showing examples of RACH configuration options. [Figure 11] Diagram showing IE RACH-ConfigCommon [Figure 12] Diagram showing IE FeatureCombinationPreambles [Figure 13] Diagram showing IE featureCombination [Figure 14] Table showing PRACH Mask index values [Figure 15] FIG. 1 shows an example of Option 1-1 proposed in this disclosure. [Figure 16] FIG. 1 shows an example of options 1-2 proposed in this disclosure. [Figure 17] FIG. 1 shows an example of Option 2-1 proposed in this disclosure. [Figure 18] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 19] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 20] FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 21] FIG. 1 is a diagram illustrating an example of a configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0016] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) by bundling them together, and Dual Connectivity (DC), which communicates with two base stations simultaneously. In this specification, "and / or" may be simply written as " / ".

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

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

[0019] Furthermore, the wireless communication system 10 may support a plurality of frequency ranges (FRs). That is, as shown in FIG. 2, the wireless communication system 10 may support the following FRs: FR1: 410MHz~7.125GHz FR2-1: 24.25GHz~52.6GHz ·FR2-2: More than 52.6GHz~71GHz

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

[0021] Note that SCS may be interpreted as numerology, which is defined in §5.1 of Non-Patent Document 3 and corresponds to one subcarrier interval in the frequency domain.

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

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

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

[0025] The time direction (t) shown in Fig. 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.

[0026] The wireless communication system 10 may support coverage enhancement (CE) that expands the coverage of a cell (or physical channel) formed by the gNB 100. In coverage enhancement, a mechanism may be provided to increase the success rate of reception of various physical channels.

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

[0028] Furthermore, for example, the UE 200 transmits a PRACH (physical random access channel) as an UL signal to the gNB 100 using a RACH (transmission) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble. For example, the UE 200 transmits the PRACH as an UL signal to the gNB 100.

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

[0030] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels may include a Physical Uplink Shared Channel (PUSCH), and the control channels 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 channels may also be called data channels.

[0031] The reference signal included in the UL signal may include at least one of, for example, 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 positioning 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.

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

[0033] Furthermore, for example, the gNB 100 receives a PRACH as an UL signal from the UE 200. For example, the gNB 100 receives a PRACH as an UL signal from the UE 200.

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

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

[0036] Next, SBFD, CG (Configured Grant), codebook-based uplink transmission, non-codebook-based uplink transmission, and mTRP will be described.

[0037] <SBFD operation> Considering the time ratio of transmission and reception by time division duplex (TDD) up to Rel-16 (for example, DL:UL = 4:1), there may be a case where the transmission opportunity of the UL signal / channel becomes less than that of the DL signal / channel reception opportunity. In such a case, the UE200 cannot transmit the UL signal / channel frequently, and there is a concern that a transmission delay of an important UL signal / channel may occur. Also, since the UL transmission opportunity is less than the DL reception opportunity, congestion of the signal / channel in the UL transmission opportunity is also a concern. Furthermore, in TDD, since the time resource for transmitting the UL signal / channel is limited, for example, the application of UL coverage extension technology by transmission is also limited.

[0038] In future wireless communication systems (for example, after Rel-18), it is being considered to introduce a time-frequency division duplex method that combines TDD and frequency division duplex (FDD) for UL and DL.

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

[0040] Figure 4A is a diagram showing an example of the TDD configuration defined up to Rel-16. In the example shown in Figure 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 serving cell) or bandwidth portion (BWP).

[0041] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. This conventional TDD slot or symbol configuration does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.

[0042] Fig. 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 such a resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.

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

[0044] Considering the complexity of handling self-interference, it may be considered that only the gNB 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.

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

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

[0047] Furthermore, during a period in which DL and UL 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 gNB 100 performs simultaneous transmission and reception of DL and UL.

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

[0049] In existing NR (e.g., those defined up to Rel-15 / 16 / 17), DL frequency resources and UL frequency resources in a UE carrier are configured as DL BWP and UL BWP, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP configurations and a BWP adaptation mechanism are required.

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

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

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

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

[0054] Here, the time unit may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots, i.e., the 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.

[0055] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol, also called a non-SBFD symbol), a slot / sub-slot that does not contain or overlap an SBFD symbol, or a group of symbols / slots / sub-slots that do not contain or overlap an SBFD symbol, and may also be called a non-SBFD time unit.

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

[0057] 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 in the TDD time unit, or a duplexing scheme in which all two sub-bands are overlapped.

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

[0059] Furthermore, a UE that supports SBFD operation (SBFD-compatible UE) 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. On the other hand, a legacy UE cannot recognize the UL subband in this SBFD symbol and recognizes it as a normal DL symbol.

[0060] <Random access procedure> NR random access procedures are performed for various purposes, such as initial access, recovery from beam interference, and handover. Random access procedures include a contention-based random access (CBRA) procedure, which is a contention-based random access procedure, and a contention-free random access (CFRA) procedure, which is a contention-free random access procedure. Since the CBRA procedure is initiated autonomously by the UE 200, collisions may occur when multiple UEs 200 simultaneously initiate the random access procedure. On the other hand, the CFRA procedure allows the gNB 100 to instruct the connected UE 200 to execute the random access procedure in a manner that prevents collisions from occurring among the multiple UEs 200.

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

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

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

[0064] The gNB 100 transmits a response message to the Msg1 as a second message to the UE 200 via the PDSCH (step S102). The response message (second message) may be appropriately referred to as a Random Access Response (RAR), an RA Response, Message 2, Msg2, or the like. After transmitting the Msg1, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including the Msg2. The 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 referred to as a Message 3, Msg 3, an RRC Connection Request, or the like, as appropriate.

[0066] The gNB 100 transmits a contention resolution message as a fourth message via the PDSCH (step S104). The contention resolution message (fourth message) may be referred to as Message 4, Msg4, or the like as appropriate. After transmitting Msg3, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including Msg4. Msg4 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 Msg4 received by the UE 200 has the same value as an ID for identifying the UE 200, the UE 200 may determine that contention resolution is successful and set a value of a Temporary Cell-Radio Network Temporary Identifier (C-RNTI) in a Cell-Radio Network Temporary Identifier (C-RNTI) field. When the value of C-RNTI is set in the C-RNTI field, the UE 200 may consider the RRC connection to be completed. Msg4 may be referred to as RRC Connection Setup, etc.

[0067] After the RRC connection is completed, the UE 200 may transmit an Ack (Acknowledgement) via a PUCCH (PUCCH resource) indicated by a PUCCH resource indication field included in the PDCCH that scheduled the Msg4, in order to notify the gNB 100 that the RRC connection has been completed. 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 1 RACH procedure, a 4-step RACH procedure, Type 1 RACH, 4-step RACH, etc.

[0068] FIG. 8 is a sequence diagram illustrating 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 a 4-step RACH procedure, and transmits an RA preamble on the RO and transmits data on a PUSCH resource associated with the RO. This message may be appropriately referred to as Message A, MsgA, etc. Note that the RA preamble and data here may correspond to Msg1 and Msg3 in the 4-step RACH procedure, respectively. MsgA includes one RA preamble (referred to as MsgA PRACH) and one piece of data (referred to as MsgA PUSCH), and the MsgA PRACH and MsgA PUSCH are time-division multiplexed and transmitted. More specifically, the MsgA PRACH is one preamble with one preamble index in an MsgA RACH occasion (RO: RACH occasion), and the MsgA PUSCH is one PUSCH with one PUSCH resource unit (PRU: PUSCH resource unit) in an MsgA PUSCH occasion (PO: PUSCH occasion) according to the MsgA PUSCH configuration. Note that in this procedure, 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 referred to as Message B, MsgB, or the like as appropriate. The content included in Message B may correspond to Msg2 and Msg4 in a 4-step RACH procedure, for example. MsgB includes one PDSCH (and one PDCCH for scheduling 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 a PUCCH (PUCCH resource) to notify the gNB 100 that the RRC connection has been completed. 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. 9 is a sequence diagram illustrating an example of the 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 a UE capability to the gNB100.

[0076] In this embodiment, in order to extend coverage in a 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. 7 and the CFRA procedure shown in Fig. 9. 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. 8.

[0077] In the above-described random access, the UE determines a random access opportunity for transmitting a preamble for starting 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.

[0078] Next, a description will be given of power control of PRACH and Msg3 transmitted by UE 200 in the random access procedure shown in Fig. 7, and of MsgA transmitted by UE 200 in the random access procedure shown in Fig. 8. Note that Msg3 and MsgA are transmitted in PUSCHs, respectively, and therefore may be referred to as Msg3 PUSCH and MsgA PUSCH.

[0079] <Terminology> The following explains the definitions of terms related to SBFD.

[0080] SBFD symbol: Symbol set in SBFD sub-band Non-SBFD symbols: Symbols that are not configured in the SBFD sub-bands DL (or semi-static D) symbol: A symbol indicated as DL by t-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated UL (or semi-static U) symbol: A symbol designated as UL by tdd-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated Flexible (or Semi-Static F, or Flexible) Symbol: A symbol designated as flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated SBFD DL symbol: A symbol indicated as downlink (DL) by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which the SBFD subband is configured SBFD Flexible (FL) Symbol: A symbol indicated as flexible by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which SBFD sub-bands are configured.

[0081] <Notation> "Legacy-RO" represents a valid RO in a UL symbol or FL symbol set by the legacy RACH configuration based on the legacy-RO validation rules.

[0082] "additional-RO" refers to a valid RO set by the legacy PRACH configuration in the SBFD DL symbol or a valid RO set across the SBFD DL symbol and the SBFD FL symbol when an additional PRACH configuration for SBFD is not configured, and refers to a valid RO in the SBFD symbol set by the additional PRACH configuration for SBFD when an additional PRACH configuration for SBFD is configured.

[0083] <Agreement 1> At the 3GPP RAN1#116 meeting, two options (Option 1 and Option 2) were considered for determining valid ROs within SBFD symbols for random access operations of SBFD-aware UEs in the RRC CONNECTED state. Option 1: Use one single PRACH configuration with possible extensions. Option 2: Use two separate RACH configurations, including one legacy RACH configuration and one additional PRACH configuration.

[0084] In Option 1, RO in the UL subband within the SBFD symbol may be valid for SBFD-aware UEs.

[0085] In Option 2, RO in UL subbands within SBFD symbols configured by the additional PRACH configuration may be valid for SBFD-aware UEs.

[0086] Fig. 10 is a diagram showing examples of RACH configuration options. Fig. 10 shows examples of RACH configurations for each of two options. The horizontal axis of each option in Fig. 10 indicates the time axis, and the vertical axis indicates the frequency axis. Each option in Fig. 10 indicates the RO set for SBFD symbols and non-SBFD symbols. In Fig. 10, "DL" indicates the DL subband of an SBFD DL symbol or the DL symbol of a non-SBFD symbol, "UL" indicates the UL subband of an SBFD DL symbol or the UL symbol of a non-SBFD symbol, and "F" indicates the FL symbol of a non-SBFD symbol.

[0087] As shown in Fig. 10, the ROs for SBFD symbols and non-SBFD symbols are both configured according to the legacy RACH configuration in Option 1. As shown in Fig. 10, in Option 2, the ROs for SBFD symbols are configured as additional-ROs according to the additional RACH configuration, and the ROs for non-SBFD symbols are configured as legacy-ROs according to the legacy RACH configuration.

[0088] <Agreement 2> At the 3GPP RAN1#118 meeting, it was agreed that the above Option 1 (with Alt 1-1) and Option 2 would be supported.

[0089] Specifically, for an SBFD-aware UE in RRC CONNECTED state, both RACH configuration Option 1 and Alt 1-1 (i.e., using one RACH configuration and based only on the existing parameters of that single RACH configuration) and RACH configuration Option 2 (i.e., using two separate RACH configurations, including one legacy RACH configuration and one additional RACH configuration) are supported.

[0090] Note that it is not supported to have both options enabled for a UE at the same time, and a UE is not required to support both options.

[0091] For the purposes of the RAN1 discussion, "additional-RO" is defined as follows: For RACH configuration Option 1, additional-RO includes RO within SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon and RO across SBFD symbols configured as downlink and flexible by tdd-UL-DL-ConfigurationCommon. For RACH configuration Option 2, additional-RO is the RO configured by the additional RACH configuration.

[0092] Regarding RO validation for RACH configuration Option 1 using Alt 1-1, RO between SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon and SBFD symbols configured as flexible is treated the same as RO within SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon. ·RO contains at least one DL symbol configured according to tdd-UL-DL-ConfigurationCommon.

[0093] That is, for each option of the RACH configuration, "legacy-RO" and "additional-RO" are defined as follows:

[0094] [RACH configuration Option 1 with Alt 1-1 (i.e., single RACH configuration)] · legacy-RO: RO that is valid as a legacy (including RO in a UL symbol or an FL symbol) additional-RO: RO within the SBFD DL symbol, or RO spanning the SBFD DL symbol and the SBFD FL symbol

[0095] [RACH configuration Option 2 (i.e., additional RACH configuration for SBFD)] legacy-RO: Valid RO set by legacy RACH configuration additional-RO: RO in SBFD symbols set by additional RACH configuration

[0096] <Agreement 3> At the 3GPP RAN1#120 meeting, RO mask index configuration was discussed and the following agreement was reached:

[0097] For RACH configuration Option 1, the RO mask index configuration is selected from the following two alternatives: · Alt-1: The ssb-SharedRO-MaskIndex configuration is common to additional-RO and legacy-RO. · Alt-2: Separate ssb-SharedRO-MaskIndex configurations are used for additional-RO and legacy-RO.

[0098] <RA feature combination> Non-Patent Document 4 shows that FeatureCombinationPreambleList is included in the information element (IE) RACH-ConfigCommon (FIG. 11). Non-Patent Document 4 also shows that parameters such as featureCombination, startPreambleForThisPartition, and ssb-SharedRO-MaskIndex are set in FeatureCombinationPreambles in featureCombinationPreamblesList (FIG. 12).

[0099] The featureCombinationPreamble is an information element for a function that uses the RA preamble or random access opportunity (RO) to let the network know whether the UE supports a specific function before reporting the UE capability to the gNB.

[0100] As shown in Fig. 13, featureCombination indicates whether the UE can report whether it supports each function such as RedCap by transmitting a RACH based on the setting of featureCombinationPreamble. When transmitting a RACH, the UE transmits a RACH to the gNB based on the setting of featureCombinationPreamble, so that the gNB can grasp the UE's capabilities (supported functions) set in featureCombination.

[0101] When a UE reports whether it supports a specific function by distinguishing preambles, the startPreambleForThisPartition parameter specifies the first preamble number that a UE that supports the specific function can use in a sequence of 64 preambles. For example, if startPreambleForThisPartition is set to "32", a UE that supports the specific function will use preambles from 32 to 63, and a UE that does not support the specific function will use preambles from 0 to 31.

[0102] When reporting whether a UE supports a specific function by distinguishing ROs, assuming that there are multiple ROs associated with a specific SSB, the ROs (Allowed PRACH occasion(s) of SSB) that a UE supporting the specific function can use to transmit a preamble are set in ssb-SharedRO-MaskIndex.

[0103] The meaning of each index value X of ssb-SharedRO-MaskIndex is shown in Table 7.4-1 of Non-Patent Document 2 (FIG. 14). · If X=0, a UE supporting the specific feature can use all ROs for transmitting preambles. · If X=1 to 8, UEs supporting the specific feature can use the RO with index X for transmitting the preamble. · If X=9, UEs supporting the specific feature can use ROs with even indices for preamble transmission. · When X=10, UEs supporting specific features can use ROs with odd indices for preamble transmission.

[0104] <Analysis> In RACH configuration Option 1, when there are two types of RO, additional-RO on SBFD symbols and legacy-RO on non-SBFD symbols, it has already been agreed that mapping between SSB and RO is performed for each of additional-RO and legacy-RO.

[0105] Also, as described above, when reporting whether the UE supports a specific function based on the RO distinction, the parameter ssb-SharedRO-MaskIndex is used.

[0106] As described above, the following two alternatives were discussed regarding the RO mask index configuration in the case of RACH configuration Option 1 at the 3GPP RAN1#120 meeting. · Alt-1: The ssb-SharedRO-MaskIndex configuration is common to additional-RO and legacy-RO. · Alt-2: Separate ssb-SharedRO-MaskIndex configurations are used for additional-RO and legacy-RO.

[0107] In each of the two alternatives for the RO mask index configuration agreed upon at the 3GPP RAN1#120 meeting, it is not clear at this time how the featureCombinationPreamble should be handled, i.e., how the RO should report whether or not the UE supports a specific feature.

[0108] Therefore, in the "Proposal" of this embodiment, a specific proposal for clarifying the above points will be described.

[0109] <Proposal> (Option 1) Option 1 is based on the concept of Alt-2 among the two alternatives discussed at the 3GPP RAN1#120 meeting, and one FeatureCombinationPreambles is associated with one type of RO (i.e., only one of legacy-RO and additional-RO). That is, the network configures FeatureCombinationPreambles for each type of RO separately, and the UE reports whether it supports a specific feature by distinguishing the RO.

[0110] (Option 1-1) In option 1-1, the configuration of featureCombinationPreamblesList (in RACH-ConfigCommon) for legacy-RO and the configuration of featureCombinationPreamblesList (in RACH-ConfigCommon) for additional-RO may be supported separately.

[0111] In this case, in a new featureCombinationPreamblesList for additional-RO (e.g., featureCombinationPreamblesList-sbfd-r19), the RO and / or preamble configuration (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition) is set in each FeatureCombinationPreamble associated with the featureCombinationPreamblesList, and these may be applied to RACH transmission in additional-RO (Figure 15).

[0112] (Variation of Option 1-1) If ssb-SharedRO-MaskIndex does not exist in the FeatureCombinationPreambles corresponding to the legacy-RO (or additional-RO), all legacy-RO (or additional-RO) configured by RACH-ConfigCommon may be used to report support for the features configured in the featureCombination.

[0113] (Option 1-2) In option 1-2, the configuration of FeatureCombinationPreambles (in featureCombinationPreamblesList) for legacy-RO and the configuration of FeatureCombinationPreambles (in featureCombinationPreamblesList) for additional-RO may be supported separately.

[0114] For example, a parameter indicating the RO type (e.g., RO-type-sbfd-r19) may be supported in FeatureCombinationPreambles to indicate whether the RO and / or preamble configuration (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition) in FeatureCombinationPreambles applies to legacy-RO or additional-RO (Figure 16). In this case, if the parameter indicating the RO type is not set in FeatureCombinationPreambles, the default RO type may be legacy-RO (or additional-RO).

[0115] In this case, the featureCombinationPreamblesList may include FeatureCombinationPreambles associated with the legacy-RO and / or additional-RO.

[0116] (Variation of Option 1-2) If ssb-SharedRO-MaskIndex is not present in the FeatureCombinationPreambles associated with a legacy-RO (or additional-RO), all legacy-ROs (or additional-ROs) configured by RACH-ConfigCommon may be used to report support for the features configured in the featureCombination.

[0117] (Option 2) Option 2 is based on the concept of Alt-1 among the two alternatives discussed at the 3GPP RAN1#120 meeting, and one FeatureCombinationPreambles is associated with up to two types of ROs (i.e., legacy-RO and additional-RO). That is, the network configures FeatureCombinationPreambles for up to two types of ROs in common, and the UE reports whether it supports a specific feature by distinguishing the ROs.

[0118] (Option 2-1) In option 2-1, two sets of RO and / or preamble configurations (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition) associated with additional-RO and legacy-RO, respectively, may be configured within FeatureCombinationPreambles (Figure 17).

[0119] If there is only one set of RO and / or preamble configurations set in FeatureCombinationPreambles, one of the following alternatives may be adopted. Which alternative is adopted may be defined in advance in the specifications.

[0120] (Alt-a) FeatureCombinationPreambles are bound to only one RO type, i.e., only one RO type (i.e., either legacy-RO or additional-RO) can be used for a feature combination.

[0121] In Alt-a, the RO type used for the feature combination may be any of the following sub-alternatives: · Alt-a-1: May be applied to legacy-RO (or additional-RO) by default. Alt-a-2: Whether a configuration set applies to a legacy-RO or an additional-RO may be determined from the name of the information element (IE). For example, in the case of a parameter set for an additional-RO, a new parameter name different from the existing one (e.g., ssb-SharedRO-MaskIndex-sbfd-r19) is used.

[0122] In Alt-a, a subset of ROs indicated in ssb-SharedRO-MaskIndex of the corresponding RO type may be used, in which case all ROs of other types may not be used for RACH transmission for reporting of features configured in featureCombination.

[0123] For example, if ssb-SharedRO-MaskIndex is determined as legacy-RO (or additional-RO), a subset of legacy-RO (or additional-RO) indicated by ssb-SharedRO-MaskIndex may be used for RACH transmission for reporting the feature set in featureCombination, while a subset of all additional-RO (or legacy-RO) may not be used for RACH transmission for reporting the feature set in featureCombination.

[0124] (Alt-b) The FeatureCombinationPreambles is associated with two RO types, that is, ROs of two RO types can be used for RACH transmission to report the features configured in the featureCombination.

[0125] ssb-SharedRO-MaskIndex applies to one RO type. In this case, the above Alt-a-1 / Alt-a-2 can be used to determine the corresponding RO type.

[0126] All other types of ROs may be enabled for RACH transmission for reporting of features configured in featureCombination. For example, if ssb-SharedRO-MaskIndex is determined as legacy-RO (or additional-RO), a subset of legacy-RO (or additional-RO) indicated by ssb-SharedRO-MaskIndex may be used for RACH transmission for reporting the features configured in featureCombination, and all additional-RO (or legacy-RO) may also be used for RACH transmission for reporting the features configured in featureCombination.

[0127] (Option 2-2) In option 2-2, one set of RO and / or preamble configuration (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition) is configured in FeatureCombinationPreambles and typically applies to additional-RO and legacy-RO.

[0128] (Analysis of Option 2-2) Option 2-2 does not affect the RRC configuration. The new UE behavior is based on the existing configuration.

[0129] (Variation of Option 2-2) The UE assumes that the ssb-SharedRO-MaskIndex is applicable to both additional-RO and legacy-RO.

[0130] (Variations of the entire proposal) The options to be applied may be configured by the gNB.

[0131] (effect) As described above, in this proposal, there are multiple additional-ROs or legacy-ROs associated with a specific SSB, and the PRACH Mask index value indicating the available additional-RO or legacy-RO is determined depending on whether the UE supports a specific function. The PRACH Mask index value is determined to be either commonly defined for the additional-RO and the legacy-RO or defined individually. This allows the UE to appropriately configure and interpret the featureCombinationPreamble in the legacy-RO and additional-RO. Therefore, the UE can appropriately select a valid RO in an RA.

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

[0133] The above UE capabilities and the configuration of this proposal are closely related, and if the functions related to each option in the proposal depend on the UE capabilities, the gNB may select or enable the functions related to each option based on the capabilities reported by the UE.

[0134] Next, the configurations of the gNB100 and the UE200 will be described. Note that the configurations of the gNB100 and the UE200 described below are examples of functions related to the present embodiment. The gNB100 and the UE200 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 the present embodiment.

[0135] <Base station configuration> Fig. 18 is a block diagram showing an example of the configuration of a base station 100 (gNodeB (gNB) 100) according to this embodiment. The gNB 100 includes, for example, a transmitter 101, a receiver 102, and a controller 103. The gNB 100 communicates with a UE 200 (see Fig. 19) wirelessly.

[0136] The transmitter 101 transmits a downlink (DL) signal to the UE 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.).

[0137] 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 the UE 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. The DCI that triggers random access may also include a PRACH Mask Index value.

[0138] 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 gNB 100 transmits downlink control information to the UE 200 using the PDCCH and transmits downlink data signals using the PDSCH.

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

[0140] The receiver 102 receives an uplink (UL) signal transmitted from the UE 200. For example, under the control of the controller 103, the receiver 102 receives an UL signal (for example, the above-mentioned request, notification, etc.).

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

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

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

[0144] 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 a signal (e.g., data and control information, etc.) received from the UE 200 and / or data and control information, etc. acquired from an upper layer. Information on the allocated resources may be included in control information transmitted to the UE 200.

[0145] <Device configuration> 19 is a block diagram showing an example of the configuration of UE 200 according to the present embodiment. UE 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. UE 200 communicates with gNB 100, for example, by radio.

[0146] The transmitter 202 transmits an UL signal to the gNB 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, and may transmit an MsgA PUSCH in a valid MsgA PO determined by the controller 203.

[0147] 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 UE 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

[0148] The 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, the UE 200 transmits uplink control information to the gNB 100 using the PUCCH and transmits an uplink data signal using the PUSCH.

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

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

[0151] The control unit 203 controls the communication operations of the UE 200, including the reception processing in the reception unit 201 and the transmission processing in the transmission unit 202.

[0152] For example, the control unit 203 acquires information such as data and control information from a higher 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 higher layer.

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

[0154] For example, the receiving unit 201, or a communication unit consisting of the receiving unit 201 and the transmitting unit 202, may receive a DCI that triggers random access.

[0155] For example, the control unit 203 may set a valid RO from among an additional-RO of an SBFD symbol or a legacy-RO of a non-SBFD symbol based on whether the UE 200 supports a specific function and the index value included in the DCI that triggers random access.

[0156] With the above configuration, when a plurality of subbands constituting a time division duplex band are available, control unit 203 of UE 200 can appropriately select a valid RO of an SBFD symbol or a non-SBFD symbol in transmitting a random access preamble.

[0157] <Other> In the above, SBFD symbols and non-SBFD symbols may be read as SBFD slots and non-SBFD slots, respectively.

[0158] The configuredGrantConfig, pusch-Config, and activation DCI for the CG PUSCH, and the sps-Config and activation DCI for the SPS PDSCH, which are transmitted from a gNB (base station) to a UE (terminal), may be referred to as information about a periodic or semi-persistent signal or channel, etc. Configuration information about PDSCH repetition, etc., transmitted from a gNB to a UE may be referred to as information about a periodic or semi-persistent signal or channel, etc. Hereinafter, a UE may receive, from a gNB, information about a periodic or semi-persistent signal or channel, and information about a time unit (SBFD symbol, SBFD slot, etc.) in which multiple subbands constituting a time division duplex band can be used.

[0159] <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 the single device or multiple devices with software.

[0160] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, 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.

[0161] 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. Figure 20 is a diagram showing an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The gNB 100 and UE 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0162] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the gNB100 and the UE200 may be configured to include one or more of the apparatuses shown in the figures, or may be configured to exclude some of the apparatuses.

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

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

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

[0166] 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 read-only memory (EPROM), an electrically erasable programmable read-only memory (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.

[0167] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0168] 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, or a communication module. 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.

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

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

[0171] Furthermore, the gNB 100 and the UE 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

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

[0173] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), 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.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

[0174] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed 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.

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

[0176] <Input / output direction> Information, etc. (see the section on information and signals) 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0189] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

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

[0193] <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 devices mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

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

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

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

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

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

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

[0202] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

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

[0206] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance 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.

[0207] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, 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. 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.

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

[0209] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

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

[0212] <Means> In the configuration of each of the above devices, the "means" may be replaced with "section", "circuit", "device", etc.

[0213] <Open format> In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0214] <Time units such as TTI, frequency units such as RB, 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 referred to as 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 does not depend on numerology.

[0215] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology 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 configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

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

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

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

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

[0220] 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. However, the definition of TTI is not limited to this.

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

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

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

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

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

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

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

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

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

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

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

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

[0233] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0236] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0237] 10. Wireless communication systems 20 NG-RAN 100 base stations (gNB) 200 User Equipment (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. a control unit that sets a valid random access opportunity from a first random access opportunity that is set in a first time unit in which a downlink and an uplink can be used simultaneously by a plurality of sub-bands that constitute a time division duplex band, and a second random access opportunity that is set in a second time unit in which one of the downlink and the uplink can be used by applying the time division duplex band; a transmitter that transmits a random access preamble using the available random access opportunity; Equipped with There are a plurality of the first random access opportunities or the second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block), An index value indicating the first random access opportunity or the second random access opportunity that can be used is determined depending on whether a terminal supports a specific function, It is determined whether the index value is commonly determined for the first random access opportunity and the second random access opportunity or is determined individually for the first random access opportunity and the second random access opportunity; The control unit sets the valid random access opportunity from among available first random access opportunities or second random access opportunities based on whether the terminal supports a specific function and the index value. Terminal.

2. When the index value is determined separately for the first random access opportunity and the second random access opportunity, a first list is supported for indicating whether the specific function for the first random access opportunity is supported, and a second list is supported for indicating whether the specific function for the second random access opportunity is supported. The terminal of claim 1.

3. When the index value is determined separately for the first random access opportunity and the second random access opportunity, a parameter indicating whether the index value is for the first random access opportunity or the second random access opportunity is set in a list for indicating whether the specific function is supported. The terminal of claim 1.

4. When the index value is commonly determined for the first random access opportunity and the second random access opportunity, a parameter indicating a first index value for the first random access opportunity and a parameter indicating a second index value for the second random access opportunity are set in a list for indicating whether the specific function is supported. The terminal of claim 1.

5. The device is setting a valid random access opportunity from among a first random access opportunity set in a first time unit in which downlink and uplink can be used simultaneously by a plurality of sub-bands constituting a time division duplex band, and a second random access opportunity set in a second time unit in which one of downlink and uplink can be used by applying the time division duplex band; transmitting a random access preamble using the valid random access opportunity; There are a plurality of the first random access opportunities or the second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block), An index value indicating the first random access opportunity or the second random access opportunity that can be used is determined depending on whether the terminal supports a specific function, It is determined whether the index value is commonly determined for the first random access opportunity and the second random access opportunity or is determined individually for the first random access opportunity and the second random access opportunity; determining whether the terminal supports a specific function and the index value, and selecting the valid random access opportunity from among the available first random access opportunities or the available second random access opportunities; Communication method.

Images