Terminal and communication method

Abstract

Provided is a terminal in which featureCombinationPreamble is appropriately configured and interpreted in a legacy-RO and an additional-RO. According to the present invention, a plurality of SBFD ROs or non-SBFD ROs associated with a prescribed SSB are present. An index value indicating an available SBFD RO or an available non-SBFD RO is determined according to whether the terminal assists in a specific function. Whether the index value is determined commonly or individually in the SBFD RO and the non-SBFD RO is determined. The terminal configures a valid RO among the available SBFD RO or the available non-SBFD RO on the basis of the index value and whether the terminal assists in the specific function.

Description

Terminal and Communication Method

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

[0002] 3GPP (registered trademark) has specified the 5th generation mobile communication system (also referred to as 5G, New Radio (NR) or Next Generation (NG)), and is further promoting the specification of a next-generation mobile communication system called Beyond 5G, 5G Evolution or 6G.

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

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

[0005] Note that a terminal (hereinafter also referred to as "user equipment (UE)") determines a random access opportunity (RO) for transmitting a preamble that initiates RA based on RACH communication from a base station (hereinafter also referred to as "gNodeB (gNB)"), and further determines a valid RO from among the ROs.

[0006] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 20233GPP TS 38.321 V18.5.0 (2025-03)3GPP TS 38.300 V18.5.0 (2025-03)3GPP TS 38.331 V18.5.0 (2025-03)

[0007] There are two types of UEs: "SBFD-aware UEs" that support SBFD operation and "Legacy UEs" that do not. Similarly, there are two types of ROs: "legacy-RO" and "additional-RO". SBFD-aware UEs can send preambles using both legacy-RO and additional-RO. Legacy UEs, on the other hand, 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 use a preamble or RO to make the network aware of whether or not it supports a particular function.

[0009] However, it is currently unclear how the shared / individual RO mask index configurations for legacy-RO and additional-RO should be configured and interpreted in featureCombinationPreamble.

[0010] If the featureCombinationPreamble is not properly set and interpreted in legacy-RO and additional-RO, the UE will not be able to properly select RO in RA.

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

[0012] A terminal according to one aspect of this disclosure includes a control unit that sets an effective random access opportunity from among a first random access opportunity set in a first time unit that allows simultaneous use of the downlink and uplink by a plurality of subbands constituting a time-division duplex band, and a second random access opportunity set in a second time unit that applies the time-division duplex band and allows either the downlink or uplink to be used, and a transmission unit that transmits a random access preamble using the effective random access opportunity, wherein there are multiple first random access opportunities or second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block), and an index value indicating the available first random access opportunity or second random access opportunity is determined depending on whether the terminal supports a particular function, and it is determined whether the index value is set commonly for the first random access opportunity and the second random access opportunity or individually, and the control unit sets the effective random access opportunity from among the available first random access opportunities or second random access opportunities based on whether the terminal supports a particular function and the index value.

[0013] This is a schematic diagram of the overall configuration of a wireless communication system. This is a diagram showing the frequency range used in the wireless communication system. This is a diagram showing an example of the configuration of wireless frames, subframes, slots, and symbols used in the wireless communication system. This is a diagram showing an example of the TDD settings specified up to Rel-16. This is a diagram showing an example of the SBFD configuration. This is a diagram showing an example of SBFD operation. This is a diagram showing an example of an existing TDD setting. This is a diagram showing an example of TDD including the SBFD setting. This is a sequence diagram showing an example of the CBRA procedure. This is a sequence diagram showing another example of the CBRA procedure. This is a sequence diagram showing an example of the CFRA procedure. This is a diagram showing an example of the RACH configuration options. This is a diagram of IE RACH-ConfigCommon. This is a diagram of IE FeatureCombinationPreambles. This is a diagram of IE featureCombination. This is a diagram showing a table of PRACH Mask index values. This is a diagram showing an example of option 1-1 proposed in this disclosure. This is a diagram showing an example of option 1-2 proposed in this disclosure. This is a diagram showing an example of option 2-1 proposed in this disclosure. This is a block diagram showing an example of the base station configuration. This is a block diagram showing an example of the terminal configuration. This is a diagram showing an example of the base station and terminal hardware configuration. This is a diagram showing an example of the vehicle configuration.

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

[0015] <Configuration of the Wireless Communication System> The wireless communication system 10 shown in Figure 1 is a wireless communication system that conforms to a method called 5G. On the other hand, the wireless communication system 10 may also be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.

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

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

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

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

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

[0021] Note that SCS may also be interpreted as numerology. Numerology is defined in §5.1 of Non-Patent Document 3, etc., and corresponds to a single 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] Figure 3 shows an example of the configuration of wireless frames (system frames), subframes, and slots used in the wireless communication system 10. As shown in Figure 3, one slot consists 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 Figure 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 could be 28 or 56 symbols, etc.). In addition, the number of slots per subframe may differ depending on the SCS.

[0025] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0026] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of the cells (or physical channels) formed by the gNB100. Coverage enhancement may provide mechanisms to increase the success rate of reception of various physical channels.

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

[0028] Furthermore, for example, UE200 transmits PRACH (physical random access channel) to gNB100 using resources such as RACH Occasion (RO), which is a resource for transmitting a random access preamble, as a UL signal.

[0029] The UL signal may include, for example, UL data signals and control information. For example, the UL signal may include information about the processing capabilities of the UE200 (e.g., UE capability). The UL signal may also include reference signals.

[0030] The channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, the UE200 transmits control information using PUCCH and transmits UL data signals using PUSCH. Note that PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. Shared channels may also be called data channels.

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

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

[0033] For example, gNB100 receives PRACH from UE200 as a UL signal.

[0034] The channels used to transmit DL signals include, for example, a data channel and a control channel. 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, gNB100 transmits control information to UE200 using the PDCCH and transmits DL data signals using the PDSCH. Note that PDSCH is an example of a Downlink Shared Channel, and PDCCH is an example of a Downlink Control Channel. Note that 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 location information. For example, reference signals such as DMRS and PTRS are used to demodulate the DL data signal and are transmitted using PDSCH.

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

[0037] <SBFD Operation> Considering the transmission / reception time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel-16, there may be cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE200 may not be able to transmit UL signals / channels frequently, raising concerns about transmission delays for important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, in TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of techniques such as transmission-based UL coverage extension.

[0038] In future wireless communication systems (e.g., Rel-18 and beyond), the introduction of a time-frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is being considered.

[0039] Examples of such time-frequency division duplexing methods include XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) of the TDD band (allowing simultaneous use of DL and UL).

[0040] Figure 4A shows an example of a TDD configuration as defined up to Rel-16. In the example shown in Figure 4A, a TDD slot or symbol is set in the 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 FIG. 4A, the time ratio between DL slots and UL slots is 4:1. In such a conventional slot or symbol configuration in TDD, sufficient UL time resources cannot be secured, which may cause UL transmission delay or degrade 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. According to such a resource configuration, more UL resources can be secured, and resource utilization efficiency can be improved.

[0043] For example, as in the example shown in FIG. 4B, both ends of the frequency domain may be configured as DL resources, and the UL resources may be sandwiched between these DL resources. This can avoid and mitigate the occurrence of Cross Link Interference (CLI) with neighboring carriers. In addition, a guard region may be provided at the boundary between DL resources and UL resources.

[0044] Considering the complexity of self-interference processing, it can be considered that only the gNB 100 uses DL resources and UL resources simultaneously. That is, for radio resources in which DL and UL overlap in time, one UE 200 may use DL resources, and another UE 200 may use UL resources.

[0045] FIG. 5 is a diagram showing an example of SBFD operation. In the example shown in FIG. 5, a part of DL resources of a TDD band is configured as UL resources, and 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 a plurality of UEs 200 (UE1 and UE2 in FIG. 5) receives DL channels / signals.

[0047] Furthermore, in a period where DL and UL temporally overlap, 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, in a UL-only period, each of a plurality of UEs 200 (UE1 and UE2 in Fig. 5) transmits a UL channel / signal.

[0049] In existing NR (for example, specified 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 another DL / UL frequency resource, configurations of a plurality of BWPs and a BWP adaptation mechanism are required.

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

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

[0052] Fig. 6B is a diagram showing an example of an existing TDD configuration. In Fig. 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. The same notation may be used in the following figures.

[0053] The SBFD symbol may be a symbol that is notified or set as UL (or DL) on one frequency resource (subband), or notified or set for UL transmission (or DL ​​reception), while on another frequency resource (subband), it may be a symbol that is notified or set as DL (or UL) or notified or set for DL ​​reception (or UL transmission), as shown in Figure 6B. Alternatively, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a portion of the frequency resource, or notified or set for UL transmission (or DL ​​reception). Alternatively, the SBFD symbol may be a symbol that is notified or set as DL (or UL) on a portion of the frequency resource, or notified or set for DL ​​reception (or UL transmission).

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

[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 / subslot that does not contain or overlap SBFD symbols, or a group of symbols / slots / subslots that do not contain or overlap SBFD symbols, and may also be called a non-SBFD time unit.

[0056] As mentioned above, SBFD may be applied to each slot / symbol. In addition, each slot / symbol may be set to DL, UL, or Flexible (FL) which can be used as DL or UL, and then SBFD may be applied.

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

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

[0059] Furthermore, UEs that support SBFD operation (SBFD-aware UEs) are described as SBFD-aware UEs or SBFD-capable UEs, while UEs that do not support SBFD operation are described as Legacy UEs. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in that 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 Procedures> NR's random access procedures are performed for various purposes, such as initial access, beam fault recovery, and handover. Random access procedures include the CBRA (Contention Based Random Access) procedure, which is a collision-type random access procedure, and the CFRA (Contention Free Random Access) procedure, which is a non-collision-type random access procedure. Since the CBRA procedure is initiated spontaneously by the UE200, collisions may occur if multiple UE200s initiate the random access procedure simultaneously. On the other hand, with CFRA, the gNB100 can instruct connected UE200s to execute the random access procedure in a way that avoids collisions between multiple UE200s.

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

[0062] Figure 7 is a sequence diagram showing an example of the CBRA procedure.

[0063] gNB100 transmits an SSB for each beam, for example, and UE200 monitors the SSB for each beam. UE200 selects an SSB from among several SSBs whose received power (RSRP: Reference Signal Received Power) is greater than (or equal to) a threshold, and uses the RO associated with the selected SSB to send a random access preamble to gNB100 via PRACH (step S101). The random access preamble (RA Preamble) may be appropriately referred to as a preamble, PRACH preamble (RACH Preamble), message 1, Msg1, etc.

[0064] gNB100 sends a response message to Msg1 as a second message to UE200 via PDSCH (step S102). This response message (second message) may be appropriately referred to as a Random Access Response (RAR), RA Response, Message2, Msg2, etc. After sending Msg1, UE200 may monitor PDCCH, which is used for scheduling PDSCH including Msg2. Msg2 may include an Uplink Grant (UL Grant) (RAR Uplink Grant) used for scheduling PUSCH, which includes a third message sent by UE200.

[0065] UE200 sends a PUSCH scheduled by the RAR uplink grant as a third message (step S103). For example, UE200 sends a Radio Resource Control (RRC) connection request, an RRC connection re-establishment request, etc., to gNB100 via this PUSCH. This third message may be appropriately referred to as Message3, Msg3, RRC Connection Request, etc.

[0066] gNB100 transmits a contention resolution message as the fourth message via the PDSCH (step S104). This contention resolution message (fourth message) may be appropriately referred to as message 4, Msg4, etc. After transmitting Msg3, UE200 may monitor the PDCCH used for scheduling the PDSCH containing Msg4. Msg4 may include a contention resolution ID (UE contention resolution ID). The contention resolution ID may be used to resolve a conflict in which multiple UE200s transmit signals using the same radio resource. If the contention resolution ID contained in the Msg4 received by UE200 is the same value as the ID used to identify UE200, UE200 may determine that the contention resolution was successful and set the value of C-RNTI (Temporary Cell-Radio Network Temporary Identifier) ​​in the C-RNTI (Cell-Radio Network Temporary Identifier) ​​field. When the value C-RNTI is set in the C-RNTI field, the UE200 may consider the RRC connection to be complete. Msg4 may also be referred to as RRC Connection Setup, etc.

[0067] Once the RRC connection is established, UE200 may send an Ack (Acknowledgement) via PUCCH (PUCCH resource) indicated by the PUCCH resource instruction field included in the PDCCH that scheduled Msg4, in order to notify gNB100 that the RRC connection has been established. After the RRC connection is established, UE200 may also send UE capability to gNB100. The random access procedure described above may also be referred to as Type 1 RACH procedure, 4-step RACH procedure, Type 1 RACH, 4-step RACH, etc.

[0068] Figure 8 is a sequence diagram showing another example of the CBRA procedure.

[0069] UE200 sends a message containing an RA preamble and data to gNB100 (step S201). For example, UE200 selects an RO (Route of Receptor) in the same manner as RO selection in the 4-step RACH procedure, sends the RA preamble at that RO, and sends the data at the PUSCH resource associated with that RO. This message may be appropriately referred to as MessageA, MsgA, etc. The RA preamble and data here may correspond to Msg1 and Msg3 in the 4-step RACH procedure, respectively. MsgA contains one RA preamble (referred to as MsgA PRACH) and one data (referred to as MsgA PUSCH), and MsgA PRACH and MsgA PUSCH are transmitted using time-division multiplexing. More specifically, MsgA PRACH is a preamble with a preamble index within a MsgA RACH occasion (RO), and MsgA PUSCH is a PUSCH with a PUSCH resource unit (PRU) within a MsgA PUSCH occasion (PO) according to the MsgA PUSCH configuration. Note that in this procedure, the resources for transmitting data are not limited to PUSCH resources, but may be resources of any channel for transmitting data (or control information).

[0070] gNB100 sends a response message to UE200 as a second message (step S202). This response message (second message) may be appropriately referred to as MessageB, MsgB, etc. The contents of MessageB may correspond, for example, to Msg2 and Msg4 in the 4-step RACH procedure. MsgB includes one PDSCH (and one PDCCH that schedules said PDSCH). From the perspective of the physical layer, the contents of Msg2 and Msg4 are simply integrated into MsgB.

[0071] Once the RRC connection is established, UE200 may send an Ack via PUCCH (PUCCH resource) to notify gNB100 that the RRC connection is complete. Furthermore, after the RRC connection is established, UE200 may send UE capability to gNB100. The above random access procedure may also be referred to as Type 2 RACH procedure, 2-step RACH procedure, Type 2 RACH, 2-step RACH, etc. 2-step RACH is supported to reduce RACH delay.

[0072] Figure 9 is a sequence diagram showing an example of the CFRA procedure.

[0073] UE200 is requested by gNB100 to send an RA preamble (Msg1). Here, gNB100 allocates the RA preamble (Msg1) via dedicated signaling (step S301). A PDCCH for such dedicated signaling may be called a PDCCH order. UE200 may monitor the PDCCH (PDCCH order) for performing the resource allocation of Msg1.

[0074] UE200 sends the aforementioned Msg1 to gNB100 (step S302).

[0075] The gNB100 sends the above-mentioned Msg2 to the UE200 (step S303). Once the RRC connection is established, the UE200 may send an Ack via PUCCH (PUCCH resource) to notify the gNB100 that the RRC connection is complete. After the RRC connection is established, the UE200 may also send the UE capability to the gNB100.

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

[0077] In the random access described above, the UE determines the random access opportunity to send a preamble to initiate random access, and from among the determined ROs, it determines which ROs are valid (and which are invalid). The random access opportunity may also be called a RACH Occasion.

[0078] Next, we will explain the power control of PRACH and Msg3 transmitted by UE200 in the random access procedure shown in Figure 7, and MsgA transmitted by UE200 in the random access procedure shown in Figure 8. Note that Msg3 and MsgA are transmitted via PUSCH, and may therefore be written as Msg3 PUSCH and MsgA PUSCH, respectively.

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

[0080] SBFD symbol: A symbol set in the SBFD subband. Non-SBFD symbol: A symbol not set in the SBFD subband. DL (or semistatic D) symbol: A symbol indicated as DL by t-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated. UL (or semistatic U) symbol: A symbol indicated as UL by tdd-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated. Flexible (or semistatic F, or flexible) symbol: A symbol indicated as flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated. SBFD DL symbol: A symbol designated as Downlink (DL) by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, in which the SBFD subband is set within the symbol. SBFD Flexible (FL) symbol: A symbol designated as Flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, in which the SBFD subband is set within the symbol.

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

[0082] "additional-RO" represents valid ROs set by the legacy PRACH configuration within the SBFD DL symbol, or valid ROs set across the entire SBFD DL and SBFD FL symbols, if no additional PRACH configuration for SBFD is set. If an additional PRACH configuration for SBFD is set, it represents valid ROs within the SBFD symbol set by the additional PRACH configuration for SBFD.

[0083] <Agreement Item 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 on 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, ROs within the UL subband of the SBFD symbol may be valid for SBFD-aware UEs.

[0085] In Option 2, ROs within the UL subband within the SBFD symbol configured by the additional PRACH configuration may be valid for SBFD-aware UEs.

[0086] Figure 10 shows examples of RACH configuration options. Figure 10 shows examples of RACH configurations for each of the two options. In Figure 10, the horizontal axis represents the time axis and the vertical axis represents the frequency axis for each option. In Figure 10, the RO set for each option is shown for both SBFD symbols and non-SBFD symbols. In Figure 10, "DL" represents the DL subband of the SBFD DL symbol or the DL symbol of the non-SBFD symbol, "UL" represents the UL subband of the SBFD DL symbol or the UL symbol of the non-SBFD symbol, and "F" represents the FL symbol of the non-SBFD symbol.

[0087] As shown in Figure 10, in Option 1, the ROs for both SBFD symbols and non-SBFD symbols are set by the legacy RACH configuration. As shown in Figure 10, in Option 2, the RO for SBFD symbols is set as additional-RO by the additional RACH configuration, and the RO for non-SBFD symbols is set as legacy-RO by the legacy RACH configuration.

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

[0089] Specifically, for SBFD-aware UEs in the 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 enabling both options simultaneously for the UE is not supported. Furthermore, the UE is not required to support both options.

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

[0092] For RO verification of RACH configuration Option 1 using Alt 1-1, RO between SBFD symbols configured as downlink and SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon is treated the same as RO within an SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon. • RO includes at least one DL symbol configured by tdd-UL-DL-ConfigurationCommon.

[0093] In other words, for each option in 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: Legacy valid ROs (including ROs within UL symbols or FL symbols) ・additional-RO: ROs within SBFD DL symbols, or ROs spanning SBFD DL symbols and SBFD FL symbols

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

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

[0097] In RACH configuration Option 1, the RO mask index configuration is selected from the following two alternatives: • Alt-1: A common ssb-SharedRO-MaskIndex configuration is used for 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 the RACH-ConfigCommon information element (IE) contains a FeatureCombinationPreambleList (Figure 11). Non-patent document 4 also shows that parameters such as featureCombination, startPreambleForThisPartition, and ssb-SharedRO-MaskIndex are set in the FeatureCombinationPreambles within featureCombinationPreamblesList (Figure 12).

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

[0100] As shown in Figure 13, featureCombination indicates whether the UE supports each feature, such as RedCap, by sending a RACH based on the featureCombinationPreamble setting. When the UE sends a RACH to the gNB based on the featureCombinationPreamble setting during RACH, the gNB can understand the capabilities (supported features) of the UE as set in featureCombination.

[0101] If you want the UE to report whether or not it supports a particular feature based on the preamble, then in startPreambleForThisPartition, the number of the first preamble available to UEs that support that particular feature will be set in a sequence of 64 preambles. For example, if startPreambleForThisPartition is "32", then UEs that support the particular feature will use preambles 32 through 63, and UEs that do not support the particular feature will use preambles 0 through 31.

[0102] If a UE is required to report whether or not it supports a particular function based on the distinction of the RO, then, assuming that there are multiple ROs associated with a given SSB, the ssb-SharedRO-MaskIndex will be configured to show the ROs that UEs supporting a particular function can use to send the preamble (Allowed PRACH occasion(s) of SSB).

[0103] The intent behind each index value X in ssb-SharedRO-MaskIndex is shown in Table 7.4-1 of Non-Patent Literature 2 (Figure 14). • If X=0, UEs supporting a specific function can use all ROs for sending the preamble. • If X=1 to 8, UEs supporting a specific function can use the RO at index X for sending the preamble. • If X=9, UEs supporting a specific function can use the RO at even-numbered indices for sending the preamble. • If X=10, UEs supporting a specific function can use the RO at odd-numbered indices for sending the preamble.

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

[0105] Furthermore, as mentioned above, if you want the UE to report whether or not it supports a particular feature based on the RO distinction, use the parameter ssb-SharedRO-MaskIndex.

[0106] Furthermore, as mentioned above, at the 3GPP RAN1#120 meeting, the following two alternatives regarding the RO mask index configuration in the case of RACH configuration Option 1 were discussed: • Alt-1: A common ssb-SharedRO-MaskIndex configuration is used for 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 to the RO mask index configuration agreed upon at the 3GPP RAN1#120 meeting, it is currently unclear how the featureCombinationPreamble will be handled, that is, how the reporting will be based on whether or not the UE supports a particular feature.

[0108] Therefore, in the <Proposal> of this embodiment, we will explain specific proposals to clarify the points mentioned above.

[0109] <Proposal> (Option 1) Option 1 is based on the Alt-2 approach, one of the two alternatives discussed at the 3GPP RAN1#120 meeting, and stipulates that one FeatureCombinationPreamble is associated with only one type of RO (i.e., either legacy-RO or additional-RO). In other words, the network configures FeatureCombinationPreambles individually for each type of RO and has the UE report whether or not it supports a particular function based on the RO's classification.

[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, a new featureCombinationPreamblesList for additional-RO (e.g., featureCombinationPreamblesList-sbfd-r19) may be used to configure the RO and / or preamble (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition) for each FeatureCombinationPreamble associated with that featureCombinationPreamblesList, and these may be applied to RACH transmissions in additional-RO (Figure 15).

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

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

[0114] For example, a parameter indicating the RO type (e.g., RO-type-sbfd-r19) may be supported within FeatureCombinationPreambles to indicate whether the RO and / or preamble configuration within FeatureCombinationPreambles (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition) 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, featureCombinationPreamblesList may include FeatureCombinationPreambles associated with legacy-RO and / or additional-RO.

[0116] (Variation of Option 1-2) If ssb-SharedRO-MaskIndex does not exist in the FeatureCombinationPreambles associated with legacy-RO (or additional-RO), all legacy-RO (or additional-RO) configured by RACH-ConfigCommon may be made available for reporting support for features configured in featureCombination.

[0117] (Option 2) Option 2 is based on the Alt-1 concept, one of the two alternatives discussed at the 3GPP RAN1#120 meeting, and stipulates that one FeatureCombinationPreamble can be associated with a maximum of two types of ROs (i.e., legacy-RO and additional-RO). In other words, the network will configure FeatureCombinationPreambles commonly for a maximum of two types of ROs and report whether or not the UE supports a particular feature based on the distinction of the RO.

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

[0119] If only one set of RO and / or preamble configurations is set within FeatureCombinationPreambles, one of the following alternatives may be adopted. The choice of which alternative to adopt may be defined in the specifications beforehand.

[0120] (Alt-a) FeatureCombinationPreambles are associated with only one RO type. That is, only one RO type is used for the feature combination (i.e., either legacy-RO or additional-RO).

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

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

[0123] For example, if ssb-SharedRO-MaskIndex is determined to be legacy-RO (or additional-RO), then a subset of legacy-RO (or additional-RO) indicated by ssb-SharedRO-MaskIndex may be used for RACH submissions to report features configured in featureCombination. On the other hand, a subset of all additional-RO (or legacy-RO) may not be used for RACH submissions to report features configured in featureCombination.

[0124] (Alt-b) FeatureCombinationPreambles are associated with two RO types. That is, two RO types of ROs can be used to send RACH for reporting the features configured in featureCombination.

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

[0126] All other types of ROs can be made available for RACH submissions to report features configured in featureCombination. For example, if ssb-SharedRO-MaskIndex is determined to be a legacy-RO (or additional-RO), then a subset of legacy-ROs (or additional-ROs) indicated by ssb-SharedRO-MaskIndex can be used for RACH submissions to report features configured in featureCombination. Also, all additional-ROs (or legacy-ROs) can be used for RACH submissions to report features configured in featureCombination.

[0127] (Option 2-2) In Option 2-2, a set of RO and / or preamble configurations (including ssb-SharedRO-MaskIndex, startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition) are configured within FeatureCombinationPreambles and are typically applied to additional-RO and legacy-RO.

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

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

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

[0131] (Effects) As explained above, in this proposal, there are multiple additional-ROs or legacy-ROs associated with a given SSB, and the PRACH Mask index value indicating the available additional-ROs or legacy-ROs is determined depending on whether the UE supports a particular function. It is also determined whether the PRACH Mask index value is set commonly for additional-ROs and legacy-ROs or individually. As a result, the featureCombinationPreamble is appropriately set and interpreted in the legacy-RO and additional-ROs in the UE. Therefore, the UE can appropriately select a valid RO in the RA.

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

[0133] The capabilities of the UE described above and the configuration of this proposal are closely related, and if the functionality of each option in the proposal depends on the capabilities of the UE, the gNB may select or permit the functionality of each option based on the capabilities reported by the UE.

[0134] Next, the configurations of gNB100 and UE200 will be described. Note that the configurations of gNB100 and UE200 described below are examples of functions related to this embodiment. gNB100 and UE200 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited, as long as the function performs the operations related to this embodiment.

[0135] <Base Station Configuration> Figure 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 transmitting unit 101, a receiving unit 102, and a control unit 103. The gNB 100 communicates wirelessly with the UE 200 (see Figure 19).

[0136] The transmitter 101 transmits downlink (DL) signals to the UE200. For example, the transmitter 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, acknowledgment, etc., as described above) under the control of the control unit 103.

[0137] The DL signal may include, for example, data signals for the downlink and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission for the UE200 (e.g., UL grant). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). The DL signal may also include a reference signal. Additionally, the DCI that triggers random access may include the PRACH Mask Index value.

[0138] The channels used to transmit 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, gNB100 transmits downlink control information to UE200 using the PDCCH and transmits downlink data signals using the PDSCH.

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

[0140] The receiving unit 102 receives uplink (UL) signals transmitted from the UE200. For example, the receiving unit 102 receives UL signals (e.g., the requests and notifications mentioned above) under the control of the control unit 103.

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

[0142] The control unit 103 controls the communication operation of the gNB100, including the transmission process of the transmission unit 101 and the reception process 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 transmission unit 101. The control unit 103 also outputs the data and control information received from the reception 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 signals received from the UE200 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to the UE200.

[0145] <Terminal Configuration> Figure 19 is a block diagram showing an example of the configuration of the UE200 according to this embodiment. The UE200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The UE200 communicates with, for example, the gNB100 wirelessly.

[0146] The transmitter 202 transmits the UL signal to the gNB100. For example, the transmitter 202 transmits the UL signal under the control of the control unit 203. For example, the transmitter 202 may transmit MsgA PRACH in a valid MsgA RO determined by the control unit 203, or MsgA PUSCH in a valid MsgA PO determined by the control unit 203.

[0147] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of the UE200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0148] The channels used to transmit UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes PUCCH (Physical Uplink Control Channel). For example, UE200 transmits uplink control information to gNB100 using PUCCH and transmits uplink data signals using 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, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).

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

[0151] The control unit 203 controls the communication operation of the UE200, including the receiving process in the receiving unit 201 and the transmitting process in the transmitting unit 202.

[0152] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

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

[0154] For example, the receiving unit 201, or the 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 the additional-RO of an SBFD symbol or the legacy-RO of a non-SBFD symbol, based on whether the UE200 supports a particular function and the index value included in the DCI that triggers random access.

[0156] With the above configuration, when multiple subbands constituting the time-division duplex band are available, the control unit 203 of the UE200 can appropriately select valid ROs of SBFD symbols or non-SBFD symbols when transmitting a random access preamble.

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

[0158] The configuredGrantConfig, push-Config, and activation DCI for CG PUSCH, and the sps-Config and activation DCI for SPS PDSCH, transmitted from the gNB (base station) to the UE (terminal), may also be referred to as information concerning periodic or semi-persistent signals or channels. The configuration information concerning PDSCH repetitions transmitted from the gNB to the UE may also be referred to as information concerning periodic or semi-persistent signals or channels. In the following, the UE may receive from the gNB information concerning periodic or semi-persistent signals or channels, and information concerning time units (SBFD symbols, SBFD slots, etc.) for which multiple subbands constituting the time-division duplex bands are available.

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

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

[0161] For example, a base station, terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 20 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The gNB100 and UE200 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0162] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of gNB100 and UE200 may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

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

[0164] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0165] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 203 of the UE200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

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

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

[0168] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be implemented by the communication device 1004.

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

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

[0171] Furthermore, gNB100 and UE200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0172] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

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

[0174] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

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

[0176] <Direction of Input / Output> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes.

[0177] <Handling of Input / Output Information, etc.> Input and output information, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, etc. may be overwritten, updated, or appended to. Output information, etc. may be deleted. Input information, etc. may be transmitted to other devices.

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

[0179] <Variations of Embodiments, etc.> Each embodiment / appearance described in this disclosure may be used individually, in combination, or switched between during implementation. Furthermore, notification of predetermined information (for example, notification that "it is X") is not limited to explicit notification, but may also be implicit (for example, by not providing notification of the predetermined information).

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

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

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

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

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

[0185] <Systems and Networks> The terms “systems” and “networks” as used in this disclosure are interchangeable.

[0186] <Parameters, Channel Names> Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, wireless resources may be indicated by an index.

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

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

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

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

[0191] <Mobile Station> In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" 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 several other appropriate terms.

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

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

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

[0196] Figure 21 shows an example of the configuration of vehicle 2001. As shown in Figure 21, 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 this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0197] The drive unit 2002 consists of, for example, 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, which is operated by the user.

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

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

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

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

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

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

[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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

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

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

[0207] <Meaning and Interpretation of Terms> As used in this disclosure, the terms “determining” and “decision” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, “determining” may include resolving, selecting, choosing, establishing, and comparing. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

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

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

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

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

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

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

[0214] <Time units such as TTI, frequency units such as RB, and radio frame configuration> A radio frame may consist of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

[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 mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0220] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

[0223] A TTI with a time length of 1 ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

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

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

[0228] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0229] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

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

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

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

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

[0234] <Articles> In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may also include the fact that the noun following these articles is plural.

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

[0236] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2025-057285, filed on 28 March 2025, are incorporated herein by reference.

[0237] One aspect of this disclosure is useful for wireless communication systems.

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

Claims

1. A terminal comprising: a control unit that sets an effective random access opportunity from among a first random access opportunity set in a first time unit that allows simultaneous use of the downlink and uplink by multiple subbands constituting the time-division duplex band, and a second random access opportunity set in a second time unit that applies the time-division duplex band and allows either the downlink or uplink to be used; and a transmission unit that transmits a random access preamble using the effective random access opportunity, wherein there are multiple first random access opportunities or second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block), an index value indicating an available first random access opportunity or second random access opportunity is determined depending on whether the terminal supports a specific function, the index value is determined to be set in common for the first random access opportunity and the second random access opportunity or is determined individually, and the control unit sets an effective random access opportunity from among the available first random access opportunities or second random access opportunities based on whether the terminal supports a specific function and the index value.

2. The terminal according to claim 1, wherein, when the index values ​​are determined separately for the first random access opportunity and the second random access opportunity, a first list for indicating whether or not the first random access opportunity supports the specific function and a second list for indicating whether or not the second random access opportunity supports the specific function are supported.

3. The terminal according to claim 1, wherein, if the index value is determined separately for the first random access opportunity and the second random access opportunity, a parameter indicating whether it is for the first random access opportunity or the second random access opportunity is set in the list for indicating whether or not the specific function is supported.

4. The terminal according to claim 1, wherein, if the index value is determined in common 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 or not the specific function is supported.

5. A communication method comprising: a terminal setting a valid random access opportunity from among a first random access opportunity set in a first time unit that allows simultaneous use of the downlink and uplink by multiple subbands constituting the time-division duplex band, and a second random access opportunity set in a second time unit that allows the use of either the downlink or uplink by applying the time-division duplex band; transmitting a random access preamble using the valid random access opportunity; there being multiple first random access opportunities or second random access opportunities associated with a predetermined SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block); an index value indicating the available first random access opportunity or second random access opportunity is determined depending on whether the terminal supports a specific function; the index value is determined to be common to the first random access opportunity and the second random access opportunity or determined individually; and setting the valid random access opportunity from among the available first random access opportunities or second random access opportunities based on whether the terminal supports a specific function and the index value.

Images