Terminal and communication method

Abstract

This terminal comprises: a control unit that, when downlink reception occasions in different slots are within a subband non-overlapping full duplex (SBFD) symbol, determines frequency resources to be used for reception on the assumption that frequency resources allocated within frequency resources that can be used for the downlink within the SBFD symbol are valid frequency resources; and a communication unit that receives the downlink reception occasions by using the frequency resources determined by the control unit.

Description

Terminal and communication method

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

[0002] 3GPP (registered trademark) is standardizing the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and is also promoting the standardization of the next-generation mobile communication system called Beyond 5G, 5G Evolution or 6G.

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

[0004] Furthermore, for Release 19, extensions regarding UL transmission and DL reception over SBFD symbols and non-SBFD symbols in different slots are being studied (Non-Patent Document 1).

[0005] “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.214 V18.3.0 (2024-06)3GPP TS 38.300 V18.2.0 (2024-06)3GPP TS 38.331 V18.1.0 (2024-03)3GPP TR 38.858 V18.1.0 (2024-03)

[0006] In cases where multiple transmission and / or reception occasions occur (multiple transmission / reception occasions), there is room for consideration regarding the behavior depending on the type of symbol in which the occasion occurs.

[0007] One aspect of this disclosure contributes to providing a terminal that can appropriately perform actions according to the type of symbol in which an occasion occurs, in cases where multiple transmission / reception occasions occur.

[0008] A terminal according to one aspect of the present disclosure includes a control unit that determines a frequency resource to be used for reception, assuming that a frequency resource allocated within the frequency resources available for the downlink within the Subband non-overlapping Full Duplex (SBFD) symbol is a valid frequency resource when the downlink reception occasions in different slots are within the SBFD symbol, and a communication unit that receives the downlink reception occasions using the frequency resource determined by the control unit.

[0009] 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 diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the periodicity of CG PUSCH. This is a diagram showing the periodicity of SPS PDSCH. This is a diagram showing multi-PUSCH scheduling by NR. This is a diagram illustrating the counting of PUSCH repetitions based on physical slots. This is a diagram illustrating the counting of PUSCH repetitions based on available slot basis. This is a diagram explaining TBoMS. This is a diagram explaining the time domain resource allocation of TBoMS. This is a diagram explaining TBoMS repetitions. This figure shows examples of resources for the DL subband and UL subband when SBFD is applied. This figure illustrates Configuration 1. This figure illustrates Configuration 2. This is a block diagram showing an example of a base station configuration. This is a block diagram showing an example of a terminal configuration. This figure shows an example of a base station and terminal hardware configuration. This figure shows an example of a vehicle configuration.

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

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

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

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

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

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

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

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

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

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

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

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

[0022] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of the cell (or physical channel) formed by the gNB100. Coverage enhancement may provide mechanisms to improve the reception success rate of various physical channels, such as repetition (repeated transmission) of PRACH (physical random access channel).

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

[0024] Furthermore, for example, UE200 transmits PRACH to gNB100 using a RACH occasion, or RACH (transmit) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble as a UL signal. For example, UE200 replicates PRACH to gNB100 as a UL signal.

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

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

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

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

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

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

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

[0032] Next, we will explain SBFD, CG (Configured Grant), PUSCH / SPS (Semi-Persistent Scheduling), and PDSCH.

[0033] <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 UL coverage extension techniques such as repetition transmission.

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

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

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

[0037] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. With such conventional TDD slot or symbol settings, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and reduced coverage performance.

[0038] Figure 4B shows an example of an SBFD configuration. In the example shown in Figure 4B, within a single component carrier (CC), the resources used for receiving DL and the resources used for transmitting UL overlap in time. With such a resource configuration, more UL resources can be secured, and the efficiency of resource utilization can be improved.

[0039] For example, as shown in the example in Figure 4B, the ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This can help avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources.

[0040] Considering the complexity of handling self-interference, it is conceivable that only the gNB100 would use both DL and UL resources simultaneously. In other words, for wireless resources where DL and UL overlap in time, one UE200 may use the DL resource and another UE200 may use the UL resource.

[0041] Figure 5 shows an example of SBFD operation. In the example shown in Figure 5, a portion of the DL resources in the TDD band are set as UL resources, and the DL and UL are configured to partially overlap in the time domain.

[0042] In the example shown in FIG. 5, during the DL-only period, each of the plurality of UEs 200 (UE1 and UE2 in FIG. 5) receives DL channels / signals.

[0043] Also, during the period when DL and UL overlap in time, one UE 200 (UE1 in the example of FIG. 5) receives DL channels / signals, and another UE 200 (UE2 in the example of FIG. 5) transmits UL channels / signals. During this period, gNB 100 performs simultaneous transmission and reception of DL and UL.

[0044] Further, during the UL-only period, each of the plurality of UEs 200 (UE1 and UE2 in FIG. 5) transmits UL channels / signals.

[0045] In existing (e.g., defined up to Rel-15 / 16 / 17) NR, the DL frequency resources and UL frequency resources in the UE carrier are set as DL BWP and UL BWP, respectively. To switch the DL / UL frequency resources to another DL / UL frequency resource, a mechanism for setting multiple BWPs and adapting the BWP is required.

[0046] FIG. 6A is a diagram showing an example of an existing TDD configuration. In FIG. 6A, the slot / symbol with "D" attached is a DL slot / symbol, the slot / symbol with "U" attached is a UL slot / symbol, and the slot / symbol with "F" attached is a flexible (hereinafter also referred to as FL) slot / symbol. Note that the same description may be used in the following figures.

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

[0048] Figure 6B shows an example of an existing TDD setting. In Figure 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL ​​subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Similar notation may be used in the following figures.

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

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

[0051] 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. For example, a pure time unit may be referred to as a time unit consisting only of DLs on a frequency resource, as shown in Figure 7A, or as a time unit consisting only of ULs on a frequency resource, as shown in Figure 7B.

[0052] Furthermore, with respect to the SBFD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the SBFD time unit of frequency domain pattern #1 may have the arrangement pattern shown in Figure 7C. The SBFD time unit of frequency domain pattern #2 may have the arrangement pattern shown in Figure 7D. The SBFD time unit of frequency domain pattern #3 may have the arrangement pattern shown in Figure 7E. These arrangement patterns are merely examples, and other arrangement patterns may be used. The frequency domain pattern of the SBFD time unit may mean the resource recency pattern in the frequency domain for the SBFD time unit.

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

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

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

[0056] 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 this SBFD symbol, but a Legacy UE will recognize this SBFD symbol as a regular DL symbol.

[0057] <CG PUSCH> There are two types of CG PUSCH: Type 1 CG PUSCH and Type 2 CG PUSCH. In Type 1 CG PUSCH, only RRC configuration is performed (i.e., it does not rely on DCI), and transmission parameters are provided by configuredGrantConfig, push-Config, and rrc-ConfiguredUplinkGrant. On the other hand, in Type 2 CG PUSCH, RRC configuration and DCI activation / deactivation are performed, one DCI can activate only one CG PUSCH configuration, and one DCI can deactivate multiple CG PUSCH configurations, and transmission parameters are provided by configuredGrantConfig, push-Config, and activation DCI. (See Figure 8.) configuredGrantConfig, push-Config, and activation DCI may also be referred to as information about periodic or semi-persistent signals or channels.

[0058] <SPS PDSCH> Rel-16 supports multiple SPS configurations. SPS can be activated / deactivated by DCI. Transmit parameters for SPS PDSCH are provided by sps-Config and activation DCI. (See Figure 9.) sps-Config and activation DCI may also be referred to as information about periodic or semi-persistent signals or channels.

[0059] <Multi-PUSCH Scheduling> When scheduling multiple PUSCHs, DCI 0_1 is used as the DCI format. For example, as shown in Figure 10, PUSCH #1 to #4 can be scheduled by a single DCI. Here, 120, 480, and 960 kHz SCS are supported, and the maximum number of PUSCHs that can be scheduled by a single DCI is specified to be 8. In addition, for TDRA, a separate {SLIV, mapping type, scheduling offset K2} may be applied to each PUSCH in the row of the TDRA table. If a PUSCH conflicts with a semi-static UL symbol or SSB symbol, that PUSCH will be canceled, but it is not expected that all PUSCHs will be canceled.

[0060] Furthermore, the MCS, NDI, and RV in the first TB field appear only once and apply to the first TB of each PUSCH. The HPN field applies to the first valid PUSCH and is incremented by 1 for subsequent PUSCHs, but is not incremented for invalid PUSCHs (i.e., PUSCHs that conflict with semi-static DL symbols or SSB symbols).

[0061] <Coverage Extension> Rel-17 specifies several techniques for extending the coverage of uplink signals. For example, it specifies available slot counting (available slot basis) for PUSCH repetition and TB processing over multi-slot (TBoMS). The following explains available slot basis and TBoMS.

[0062] <Coverage Expansion: Available Slot Basis> Figure 11A illustrates the counting of PUSCH repetitions based on physical slots. In Rel-15 / 16, the count for PUSCH repetitions is based on physical slots. Therefore, as shown in Figure 11A, if the number of PUSCH repetitions is 16, up to four actual PUSCH repetitions are set for the TDD (Time Division Duplex) pattern "DDDDU".

[0063] To increase actual PUSCH repetitions, Rel-17 introduced an available slot basis (available slot counting).

[0064] Figure 11B illustrates the counting of Pusch repetitions based on the available slot basis. In the available slot basis, Pusch repetitions are determined based on the following two steps.

[0065] Step 1: The terminal determines the available slot based on RRC configurations such as tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst, and TDRA in DCI scheduling.

[0066] Step 2: The terminal decides whether or not to drop the PUSCH repetition according to a predetermined drop rule, such as the PUSCH drop rule in Rel-15 / 16.

[0067] In the available slot basis, the number of repetitions is counted based on the available slots. Therefore, as shown in Figure 11B, if the number of PUSCH repetitions is 4, four actual PUSCH repetitions are set for the TDD pattern "DDDDU".

[0068] <Coverage Extension: TBoMS> TBoMS transmits a single TB (Transport Block) across multiple slots. The TB size is determined based on the PUSCH resource elements across N slots.

[0069] TBoMS may offer the following advantages: • Improved channel coding gain due to longer code sequences – Code block segmentation is not supported when TBoMS is enabled. • High power spectral density at low code rates – 1 TB can be allocated to multiple slots in the time domain, reducing the number of Resource Blocks (RBs) required to transmit a specific TB.

[0070] Figure 12 is a diagram illustrating TBoMS. Figure 12 shows an example where one TB is transmitted across three slots.

[0071] Figure 12 shows the relationship between the bits transmitted in each slot and the position of the bits in the circular buffer. The circular buffer stores, for example, an encoded bit sequence corresponding to one TB. In the example in Figure 12, bit selection is performed as shown by arrows A10a, A10b, and A10c, and one TB is transmitted across three slots (three PUSCHs).

[0072] The number of slots (N) allocated to a single TB is indicated by numberOfSlotsTBoMS. numberOfSlotsTBoMS is communicated by higher-layer signaling, such as RRC signaling.

[0073] Figure 13 illustrates the time domain resource allocation of TBoMS. Figure 13 shows an example where numberOfSlotsTBoMS=4. Each slot (PUSCH) is assigned the same symbol.

[0074] In TBoMS, a TBoMS with repetitions is introduced to reduce the burden on the terminal, as the terminal stores the location of the circular buffer. The number of slots allocated to single TBoMS (N) and repetition TBoMS (K) is indicated by numberOfSlotsTBoMS and numberOfRepetitions, respectively. numberOfSlotsTBoMS and numberOfRepetitions are communicated by higher-layer signaling, such as RRC signaling.

[0075] The Redundancy Version (RV) determination for each repetition is the same as for Rel-15 / 16 repetitions. The RV index cycles through [0, 2, 3, 1] in the PUSCH scheduled by DCI. The RV index also cycles through [0, 0, 0, 0], [0, 3, 0, 3], or [0, 2, 3, 1] according to the RRC parameter (repK-RV) of the configured grant PUSCH (CG-PUSCH).

[0076] Figure 14 illustrates the repetition of a TBoMS. Figure 14 shows an example of a single TBoMS with 2 slots, 3 repetitions, and an RV sequence of [0, 2, 3, 1].

[0077] <PUSCH repetition Type A> PUSCH repetition Type A is a form in which PUSCH assigned to a slot is transmitted as repetition. PUSCH repetition Type A can be considered as repetition at the slot level. PUSCH repetition Type A may also be referred to as repetition Type A.

[0078] <FDRA Types> The UE uses the resource allocation field detected by the PDCCH DCI to determine resource block allocation in the frequency domain. According to §6.1.2.2 of Non-Patent Literature 2, Type 0 and Type 1 are supported as UL resource allocation schemes in the frequency domain.

[0079] 1. UL Resource Allocation Type 0: The UL resource allocation information for UL resource allocation Type 0 in FDRA includes a bitmap indicating the resource block group (RBG) to be allocated to the scheduled UE. An RBG is a collection of contiguous virtual resource blocks. Transform precoding cannot be used with this method.

[0080] The size of the bitmap is N RGB Each RGB has one bitmap bit, and each RGB is addressable. RGBs are indexed from the lowest frequency in increasing order of bandwidth frequency. The order of the RGB bitmaps is RBG 0 to RBG N. RGB -1 ensures that the bitmap is mapped from MSB to LSB. If the corresponding bit value of the bitmap is 1, RGB is assigned to UE; otherwise, RGB is not assigned to UE.

[0081] 2. UL Resource Allocation Type 1 The UL resource allocation information for UL resource allocation Type 1 in FDRA is set to the scheduled UE, size N. BWF size Within the active bandwidth portion of the PRB, a set of contiguously allocated, non-interleaved virtual resource blocks is shown.

[0082] The resource allocation field for UL Type 1 is the Start Virtual Resource Block (RB). start The resource instruction value (RIV) corresponding to the resource, and the length (L) of the contiguously allocated resource block. RBｓ It consists of the following. The resource instruction value is defined by the following formula. The UE assumes that UL resource allocation Type 1 will be used if the scheduling PDCCH DCI is received in DCI format 0_0.

[0083] <Consideration of Duplex Extension for Rel-19> As mentioned above, for Rel-18, consideration has been given to enabling the simultaneous existence of downlink and uplink (full duplex, more specifically subband non-overlapping full duplex) on the gNB side within the conventional TDD band. Regarding SBFD, the impact on specifications, performance evaluation results, implementation feasibility, and impact on RF requirements are summarized in Non-Patent Document 5.

[0084] Non-patent document 1 focuses on the expansion of subband non-overlapping full duplex (SBFD) operation on the gNB side within a TDD carrier. The objectives of the study toward Rel-19 are as follows: (1) In RRC_CONNECTED mode, consider the specification for semi-static indication of the time position of the SBFD subband to the UE. The indication of the time position of the SBFD subband in SIB is not excluded. (2) In RRC_CONNECTED mode, consider the specification for semi-static indication of the frequency domain position of the SBFD subband to the UE. The indication of the frequency domain position of the SBFD subband in SIB is not excluded. (3) Consider the specification for SBFD operations to support random access of SBFD symbols by the UE in RRC CONNECTED mode. (4) Consider SBFD operations to support random access by the UE in RRC_IDLE / INACTIVE mode, and define the specification if appropriate. Confirm whether to proceed with standardization work in RAN#104. (5) Consider the specification for the operation and procedure of UE transmission / reception and measurement of SBFD symbols and / or non-SBFD symbols for SBFD-aware UEs. DL and / or flexible symbols as shown by TDD-UL-DL-ConfigCommon. Transmit / receive operation in the SBFD subband configured as (symbol) UL transmission only within the UL subband DL reception only within the DL subband (excluding CLI measurements by UE outside the DL subband) Note: When flexible symbols are used, it is not expected that the legacy uplink symbols will be converted to downlink / SBFD symbols. Enhanced frequency domain resource allocation in the following SBFD symbols Frequency domain resource allocation of PDSCH / CSI-RS spanning two DL subbands in the SBFD symbol SBFD subband and RBG (Resource Block)Handling of boundary inconsistencies between Group, CSI Report subband, CSI-RS resources, and PRG (Precoding Resource block Group) - Enhancements to physical channels / signals and procedures spanning SBFD and non-SBFD symbols in different slots, where each transmit / receive in a slot includes either all SBFD symbols or all non-SBFD symbols, including: Resource allocation in the frequency domain when different available frequency resources are used in different slots during SBFD and non-SBFD symbol transmit / receive - CSI reports of related CSI-RS instances occurring in both SBFD and non-SBFD symbols in different slots - SRS, PUCCH and PUSCH configuration in SBFD and non-SBFD symbols (resources, frequency hopping parameters, UL power control parameters and / or beam / spatial relationships, etc.) - Collision handling between DL receive in the DL subband and UL transmit in the UL subband in SBFD symbols (6) Based on TR 38.858 (Non-Patent Literature 5), the following is assumed: - SBFD on the gNB side - Half-duplex operation on the UE side Operation) ・FR1 and FR2-1 ・SBFD operation option 4 (for example, the time and frequency positions of the subband for SBFD operation are known to the SBFD-enabled UE) ・Coexistence of non-SBFD-enabled UEs (including legacy UEs) and SBFD-enabled UEs in a cell where SBFD is being operated on the gNB side ・SBFD scheme in a single configuration DL and UL BWP pair with aligned center frequencies ・One UL subband for SBFD operation in SBFD symbols (excluding legacy UL symbols / slots) within a TDD carrier ・The mechanism for SBFD operation must also consider the coexistence of adjacent channels between the two operators

[0085] <Transmission / reception spanning SBFD and non-SBFD symbols> Section 6.1.2 of Non-Patent Document 5 examines whether or not to support transmission / reception spanning SBFD and non-SBFD symbols.

[0086] For UL transmit / DL receive operations spanning SBFD and non-SBFD symbols in different slots (where each transmit / receive within a slot is either all SBFD or all non-SBFD symbols), the following options should be considered for SBFD-enabled UEs: Option 1: Transmit / receive is restricted to either SBFD symbols only or non-SBFD symbols only. Option 2: Transmit / receive can be performed using both SBFD and non-SBFD symbols.

[0087] UL transmission / DL reception spanning SBFD and non-SBFD symbols includes the following information: • PDSCH / PUSCH / PUCCH repetition • SPS (Semi-Persistent Scheduling) PDSCH / CG PUSCH (Configured Grant PUSCH) • TBoMS (Transport Block processing over Multiple Slots) • Multiple PUSCH / PDSCH scheduled by a single DCI • Periodic / semi-persistent SRS / CSI-RS / PUCCH • PDCCH

[0088] Option 1 can be achieved by configuring or scheduling the gNB so that all transmit / receive occasions are limited to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional instructions or rules to determine whether a transmit / receive occasion is valid within one symbol type and invalid within another. Frequency resources, power control, and beam / spatial relationships for all transmit / receive occasions may be the same in Option 1, but may be different in Option 2. If they are different, additional specification work may be required. Option 1 may increase or not increase transmit / receive latency if transmit / receive is delayed in other symbol types, and may degrade performance if transmit / receive is dropped in other symbol types. Option 2 may or may not reduce transmit / receive latency and improve coverage.

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

[0090] 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 tdd-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.

[0091] The parameters for configuring the resources of the Sounding Reference Signal (SRS) may include an SRS Config. The SRS Config is a parameter that defines a list of SRS-ResourceSets and a list of SRS-Resources. The SRS-ResourceSets included in the list may include an identifier for the SRS-ResourceSet (srs-ResourceSetId), a list of identifiers for the SRS-Resource (srs-ResourceIdList), etc. The SRS-Resources included in the list include an identifier for the SRS-Resource (srs-ResourceId), the SRS resource in the frequency domain (e.g., resourceMapping), etc. resourceMapping includes the start position (startPosition), the number of symbols (nrofSymbols), the repetition factor, etc. The SRS Config may also be a parameter defined in §6.3.2 “Radio resource control information elements” of Non-Patent Literature 4.

[0092] <Agreement Item 1> At the 3GPP RAN1#116 meeting, the term "DL / UL usable PRB (Physical Resource Block)" was agreed upon.

[0093] The UL subband frequency resources within an active UL BWP are called UL usable PRBs, and the DL subband frequency resources within an active DL BWP are called DL usable PRBs (see Figure 15).

[0094] To determine the available PRBs in UL / DL, the following options are considered: Option 1: In UL, the available PRBs are determined as the intersection of the cell-specific UL subband and the active UL BWP within the SBFD symbol. In DL, the available PRBs are determined as the intersection of the cell-specific DL subband and the active DL BWP within the SBFD symbol. Option 2: In UL / DL, the available PRBs are explicitly set within the active UL / DL BWP of the SBFD symbol.

[0095] As shown in Figure 15, the DL subband portion and the pure DL symbol portion within the SBFD symbol become PRBs usable in the downlink. Similarly, the UL subband portion and the pure UL symbol portion within the SBFD symbol become PRBs usable in the uplink.

[0096] <Agreement Item 2> The following items were agreed upon at the 3GPP RAN#116bis meeting:

[0097] In the case of PUSCH repetition Type A, where each repetition has either all SBFD symbols or all non-SBFD symbols and spans SBFD and non-SBFD symbols in different slots; in the case of multi-PUSCH scheduled by a single DCI, where each PUSCH in a slot has either all SBFD symbols or all non-SBFD symbols and spans SBFD and non-SBFD symbols; and in the case of TBoMS, where each transmission in a slot has either all SBFD symbols or all non-SBFD symbols and spans SBFD and non-SBFD symbols in different slots, discuss and determine which of the following options is supported.

[0098] Option 1: Separate FDRA settings / instructions / interpretations for SBFD symbols and non-SBFD symbols. Option 2: A single FDRA setting / instruction for one symbol type (SBFD or non-SBFD symbol) and RB offset settings / instructions / determinations for determining resources for other symbol types. Option 3: PUSCH in a slot that overlaps with an RB outside of a UL-available PRB within an SBFD symbol is invalid (e.g., PUSCH in a slot is dropped / delayed). Option 4: Only PUSCH for one symbol type is valid, and PUSCH for other symbol types is invalid. Option 5: In the case of a PUSCH in a slot that overlaps with an RB outside of a UL-available PRB within an SBFD symbol, only the allocated PRB within the UL-available PRB is considered valid. Option 6: gNB does not schedule PUSCH in an SBFD symbol in a slot to overlap with a PRB other than a UL-available PRB. Other options are not excluded. Applicable conditions are yet to be determined.

[0099] <Agreement Item 3> At the 3GPP RAN1#117 meeting, it was agreed that whether transmission / reception in different slots is limited to one symbol type or possible with two symbol types would be determined on a configuration basis, as follows:

[0100] For SBFD-enabled UEs, when performing UL transmission and DL reception that span SBFD and non-SBFD symbols within different slots (each transmission / reception within a slot contains either all SBFD symbols or all non-SBFD symbols), the SBFD-enabled UE is provided with one of the following configurations: Configuration 1: Transmission / reception is restricted to using either SBFD symbols only or non-SBFD symbols only (see Figure 16A). Configuration 2: Transmission / reception can be performed using both SBFD and non-SBFD symbols (see Figure 16B).

[0101] The granularity of the settings (e.g., per UE, per channel / signal, etc.) is yet to be determined. Furthermore, it is also undecided whether support for setting 2 depends on the terminal's capabilities (UE capability).

[0102] In UL transmission / DL reception for a single slot, SBFD and non-SBFD symbols will never coexist in a single occasion; each transmission / reception within a slot will always use one of the symbol types. However, in UL transmission / DL reception where resources are allocated periodically, such as in repetitions spanning multiple slots, it is possible that some slots will transmit / receive using SBFD symbol types, while others will transmit / receive using non-SBFD symbols. In such cases, two options are supported: one for enabling only one symbol type for the entire series of transmissions / receptions spanning multiple slots (Configuration 1), and another for allowing a mix of both symbol types (Configuration 2). One of these configurations is set for the terminal.

[0103] For example, if configuration 1 is set on a terminal, and the repetition is set to SBFD symbols, then on that terminal, that repetition will only be valid for SBFD symbols. If the repetition is set to non-SBFD symbols, then on that terminal, that repetition will only be valid for non-SBFD symbols. If configuration 2 is set on the terminal, then it becomes possible to use both SBFD and non-SBFD symbols for a given repetition.

[0104] <PDSCH / PUSCH without repetition scheduled by DCI> The following points have been agreed upon regarding PDSCH / PUSCH without repetition scheduled by DCI:

[0105] In USS, for frequency domain resource allocation Type 1 for a single-slot PDSCH scheduled at least in DCI format, PRG is determined as one of the values ​​{2, 4}.

[0106] Option 1-1: Only assigned PRBs within the DL usable PRB are considered valid for PDSCH. Assigned PRBs outside the DL usable PRB range are considered invalid and are not used for PDSCH resource mapping. Note that with this option, existing RB indexes and VRB-to-PRB mappings are reused. Also, with this option, the number of PRBs for TBS determination may be based only on assigned PRBs within the DL usable PRB.

[0107] For frequency resource allocation type 0 of a single-slot PDSCH or PUSCH with DCI-based scheduling (without repetition or TBoMS), if the allocated RBG overlaps with a subband boundary, the number of PRBs for TBS determination may be based on the allocated PRBs within only the PRBs available in DL for PDSCH, and on the allocated PRBs within only the PRBs available in UL for PUSCH.

[0108] <Agreement Item 4> At the 3GPP RAN1#118 meeting, the following was agreed upon regarding the establishment / direction of a single resource for non-SBFD symbols and the establishment / direction / determination of RB offsets for determining frequency resources for SBFD symbols:

[0109] Specifically, for SPS PDSCH, PDSCH repetitions, and multi-PDSCH scheduled by a single DCI, the following working assumptions exist for Configuration 2 when the PDSCH occasion spans both SBFD and non-SBFD symbols.

[0110] (Working Assumption) For an SPS PDSCH configuration without repetitions, if the receive occasion spans both SBFD and non-SBFD symbols, and each receive occasion is either all SBFD symbols or all non-SBFD symbols (i.e., Configuration 2), if there is a PDSCH repetition spanning both SBFD and non-SBFD symbols in different slots, and each repetition is either all SBFD symbols or all non-SBFD symbols (i.e., Configuration 2), and if there is a multi-PDSCH scheduled by a single DCI spanning both SBFD and non-SBFD symbols, and each PDSCH in the slot is either all SBFD symbols or all non-SBFD symbols (i.e., Configuration 2), then: Option 5: Only the allocated PRBs in the DL-enabled PRBs within the SBFD symbols are considered valid. - In the case of SPS PDSCH, it is undecided whether the number of PRBs for determining the TBS (transport block size) is based on the allocated PRBs or only on the allocated PRBs within the PRBs available in the DL. - In the case of PDSCH repetitions, it is undecided whether the number of PRBs for determining the TBS is based on the allocated PRBs, only on the allocated PRBs within the PRBs available in the DL, or on the allocated PRBs within the PRBs available in the DL for the first repetition. - In the case of multi-PDSCH scheduled by a single DCI, it is undecided whether the number of PRBs for determining the TBS is based on the allocated PRBs or only on the allocated PRBs within the PRBs available in the DL.

[0111] Specifically, for CG PUSCH, PUSCH repetition Type A, multi-PUSCH scheduled by a single DCI, and PUSCH TBoMS, the following agreement exists for Configuration 2 regarding cases where the PUSCH occasion spans both SBFD and non-SBFD symbols:

[0112] (RAN1#118 Agreement) (1) In the case of a CG PUSCH configuration without repetition, where the transmission occasion spans both SBFD and non-SBFD symbols, and each transmission occasion has either all SBFD symbols or all non-SBFD symbols (i.e., Configuration 2), (2) PUSCH repetition Type where each repetition has either all SBFD symbols or all non-SBFD symbols (i.e., Configuration 2), and spans between SBFD and non-SBFD symbols in different slots. In case A, and (3) in the case of a multi-PUSCH scheduled by a single DCI spanning SBFD and non-SBFD symbols, where each PUSCH in a slot has either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2), and (4) in the case of a TBoMS spanning SBFD and non-SBFD symbols in different slots, where each transmit in a slot has either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2) - Option 2: Single resource setting / instruction for non-SBFD symbols and RB offset setting / instruction / determination to determine frequency resources for SBFD symbols - The number of PRBs is the same for PUSCH transmits with SBFD symbols and PUSCH transmits with non-SBFD symbols.

[0113] <Prerequisites> It may be assumed that a single FDRA setting / instruction is made for a certain symbol type (e.g., either an SBFD symbol or a non-SBFD symbol), and that an RB offset setting / instruction / determination is made for determining the frequency resources of a symbol type different from that symbol type (e.g., the other of either an SBFD symbol or a non-SBFD symbol).

[0114] For example, a single FDRA setting / indication for a non-SBFD symbol and a setting / indication / determination of an RB offset for determining the frequency resources of an SBFD symbol may be assumed. In this case, the indicated FDRA may be applied to determine the PUSCH frequency resources of the non-SBFD symbol. Alternatively, in this case, the UE may determine the PUSCH frequency resources of the SBFD symbol based on the indicated FDRA and RB offset.

[0115] For example, a single FDRA setting / indication for an SBFD symbol and a setting / indication / determination of an RB offset for determining the frequency resources of a non-SBFD symbol may be assumed. In this case, the indicated FDRA may be applied to determine the PUSCH frequency resources of the SBFD symbol. Alternatively, the UE may determine the PUSCH frequency resources of a non-SBFD symbol based on the indicated FDRA and RB offset.

[0116] <Points to Consider> According to the RAN1 agreement, discussions / agreements regarding FDRA have been made for the following cases: - Single TX / RX occasion - Multiple TX / RX occasions

[0117] For a single transmit / receive occasion, a repetition-free FDRA type 1 / 0 PDSCH scheduled by DCI in the SBFD symbol is being considered. Alternatively, for a single transmit / receive occasion, a repetition-free FDRA type 0 PUSCH scheduled by DCI in the SBFD symbol is being considered. Note that no extension is required for the case of a repetition-free FDRA type 1 PUSCH scheduled by DCI.

[0118] For multiple transmit / receive occasions, Configuration 2 is being considered for cases where the PDSCH / PUSCH occasion spans both SBFD and non-SBFD symbols.

[0119] However, in cases where multiple transmit / receive occasions occur, there is room for consideration regarding the behavior depending on the type of symbol in which the occasion occurs. For example, configuration 1, where the PDSCH / PUSCH occasion occurs only within the SBFD symbol in multiple transmit / receive occasions, is worth considering. Also, configuration 2, where the PDSCH / PUSCH occasion occurs only within the SBFD symbol in multiple transmit / receive occasions, is worth considering.

[0120] In cases where multiple transmission / reception occasions occur, it is desirable that the handling of FDRA and / or TBS determination be clearly defined according to the type of symbol involved in the occasion.

[0121] Therefore, in this embodiment, we will describe the operation according to the type of symbol in which the occasion occurs, in cases where multiple transmission / reception occasions occur.

[0122] <Proposal 1> Proposal 1 describes the case where PDSCH occasions in different slots are only within the SBFD symbol. Proposal 1 illustrates the cases of SPS PDSCH, PDSCH repetition, and multi-PDSCH scheduled by a single DCI when PDSCH occasions in different slots are only within the SBFD symbol.

[0123] (FDRA in Proposal 1) Only the assigned PRBs within the DL usable PRBs in the SBFD symbol are considered valid. In this case, for example, the UE may determine which PRB to use for reception by assuming that the assigned PRBs within the DL usable PRBs in the SBFD symbol are valid PRBs.

[0124] If frequency resource allocation type 0 is applied as a variation of the FDRA in Proposal 1, the UE does not expect to be allocated RBs that are completely out of range with respect to the PRBs available in the DL. Here, the RBs that are completely out of range with respect to the PRBs available in the DL may be RBs that do not overlap with the PRBs available in the DL.

[0125] (TBS determination in Proposal 1) In the case of SPS PDSCH, the number of PRBs for TBS determination may be based on at least one of the following: ・Alt (alternative) 1-1a: Allocated PRBs ・Alt 1-1b: Allocated PRBs within the PRBs available in DL only

[0126] In the case of PDSCH repetition, the number of PRBs for TBS determination may be based on at least one of the following: • Alt 1-2a: Allocated PRBs • Alt 1-2b: Only allocated PRBs within the PRBs available in DL

[0127] For multi-PDSCH scheduled by a single DCI, the number of PRBs for TBS determination may be based on at least one of the following: • Alt 1-3a: All allocated PRBs • Alt 1-3b: Only allocated PRBs within the PRBs available in DL

[0128] <Variations of Proposal 1> Proposal 1 above may be applicable only to configuration 1. Alternatively, Proposal 1 above may be applicable only to configuration 2. Alternatively, Proposal 1 above may be applicable to both configuration 1 and configuration 2.

[0129] Different alternatives may be applied to Configuration 1 and Configuration 2.

[0130] Different options / alternatives may apply to SPS PDSCH, PDSCH repetitions, and multi-PDSCH scheduled by a single DCI.

[0131] In summary, Proposal 1 clarifies how the FDRA (Field Data Analysis) and / or TBS (Time-Based System) determination are handled for each PDSCH occasion in DL (Data Distribution) when PDSCH occasions in different slots exist only within SBFD symbols. This allows the UE (User Engineer), for example, to determine resources and TBS based on the FDRA, enabling it to appropriately perform actions according to the type of symbol in which the occasion occurs in cases where multiple receive occasions arise.

[0132] <Proposal 2> Proposal 2 describes the case where the PUSCH occasion in different slots is only within the SBFD symbol. Proposal 2 illustrates the cases of CG PUSCH, PUSCH repetition, multi-PUSCH scheduled by a single DCI, and PUSCH TBoMS when the PUSCH occasion in different slots is only within the SBFD symbol.

[0133] (FDRA in Proposal 2) In Proposal 2, at least one of the following options applies to the FDRA.

[0134] (Option 2-1 for FDRA in Proposal 2) The information in the FDRA field (e.g., bits) indicates the FDRA within the SBFD symbol.

[0135] As a variation of Option 2-1, when frequency resource allocation type 0 is applied, overlap of FDRA with PRBs outside the range of PRBs available in the UL is permitted. Here, only PRBs within the range of PRBs available in the UL are valid for the PUSCH occasion. Furthermore, the UE does not expect RBGs that are completely outside the range of PRBs available in the UL to be indicated by the FDRA.

[0136] (Option 2-2 for FDRA in Proposal 2) The information in the FDRA field (e.g., bits) indicates the FDRA within a non-SBFD symbol. The UE then applies the RB offset to determine the FDRA within the SBFD symbol.

[0137] In the FDRA of Proposal 2 described above, the UE determines which frequency resource to use for transmission, assuming that the information in the FDRA field (e.g., information regarding frequency resource allocation) indicates an FDRA within an SBFD symbol or an FDRA within a non-SBFD symbol.

[0138] (TBS determination in Proposal 2) This section describes the TBS determination when an FDRA overlapping with a PRB outside of the available PRB is permitted under UL.

[0139] In the case of CG PUSCH, the number of PRBs for TBS determination may be based on at least one of the following: • Alt 2-1a: Allocated PRBs • Alt 2-1b: Only allocated PRBs within UL-available PRBs

[0140] In the case of PUSCH repetition, the number of PRBs for TBS determination may be based on at least one of the following: • Alt 2-2a: Allocated PRBs • Alt 2-2b: Only allocated PRBs within the PRBs available in UL

[0141] For multi-PUSCH scheduled by a single DCI, the number of PRBs for TBS determination may be based on at least one of the following: • Alt 2-3a: Allocated PRBs • Alt 2-3b: Only allocated PRBs within the PRBs available in UL

[0142] In the case of PUSCH TBoMS, the number of PRBs for TBS determination is based on at least one of the following: • Alt 2-4a: Allocated PRBs • Alt 2-4b: Only allocated PRBs within the PRBs available in UL

[0143] <Variations of Proposal 2> Proposal 2 above may be applicable only to configuration 1. Alternatively, Proposal 2 above may be applicable only to configuration 2. Alternatively, Proposal 1 above may be applicable to both configuration 1 and configuration 2.

[0144] Different alternatives may be applied to Configuration 1 and Configuration 2.

[0145] Different options / alternatives may apply to CG PUSCH, PUSCH repetition, multi-PUSCH scheduled by a single DCI, and PUSCH TBoMS.

[0146] In summary, Proposal 2 clarifies how the FDRA (Functional Data Analysis) and / or TBS (Time-Based Switch) determination are handled for each PUSCH occasion in a UL (Unit-Likely Unit) when PUSCH occasions in different slots exist only within SBFD symbols. This allows the UE (Unit-Effective Encoder) to determine resources and TBS based on the FDRA, enabling it to appropriately perform actions according to the type of symbol in which the occasion occurs, in cases where multiple transmission occasions arise.

[0147] (Combination with Options) In Proposals 1 and 2 of this Disclosure, which proposal applies, or which option or alternative is used, may be determined by: - ​​Setting by higher-level parameters - Determining by relevant higher-level parameters - Indicated in MAC CE or DCI - Determining based on UE capabilities - Stated in the specification - Determining based on conditions stated in the specification - Determining by the higher-level parameters / MAC CE / DCI configuration and reported UE capabilities (combination of the above determinations)

[0148] In each proposal of this disclosure, multiple options and alternatives may be combined into a single option / alternative. Throughout the proposals, the measured RS (reference signal) will be the QCL source RS in the active TCI state / indicated TCI state.

[0149] (Signals from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW). Throughout the proposal, the network (NW) may also be referred to as a gNB. • Information via upper-layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) • MAC CE subheader with a new LCID extending the existing MAC CE (e.g., introducing a new octet) • DCI DCI field: Existing DCI field or newly introduced DCI field RNTI: Existing RNTI or DCI with a scrambled CRC by the newly introduced RNTI DCI format: Existing DCI format or newly introduced DCI format • Combinations of the above information

[0150] In this disclosure, the UE may receive information from the network (NW) in the following periodic forms: Option 1: Receive information periodically; Option 2: Receive information semi-persistently (triggered by instructions from the UE or gNB); Option 3: Receive information aperiodically (triggered by instructions from the UE or gNB).

[0151] In this disclosure, the UE may receive information from the network (NW) as the following QCL rules: • QCL Type A • QCL Type B • QCL Type C • QCL Type D

[0152] In this disclosure, the QCL resource RS for each QCL type may be configured as follows: • SSB (SS / PBCH Block) • CSI-RS with / without repetition • TRS (tracking reference signal) • PDCCH / PDSCH DMRS

[0153] In this disclosure, information from the network (NW) is set / presented as follows: • Common to UE / Dedicated to UE • Cell-specific / Common to cell • Per UE / CC / BWP / Bandwidth / Cell / CG

[0154] (Signals from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW). Throughout the proposal, the network (NW) may also be referred to as gNB. - Information via upper layer signaling (e.g., RRC messages / LPP messages) - MAC CE subheader with a new LCID, extending an existing MAC CE (e.g., introduction of a new octet) - UCI on PUCCH or PUSCH - Combinations of the above information

[0155] In this disclosure, the UE may report information to the network (NW) in the following periodic forms: Option 1: Send information periodically Option 2: Send information semi-persistently (triggered by instructions from the UE or gNB) Option 3: Send information aperiodically (triggered by instructions from the UE or gNB)

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

[0157] The capabilities of the UE described above and the configuration of this proposal are closely related, and if the functionality of each option in each 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.

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

[0159] <Base Station Configuration> Figure 17 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 18).

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

[0161] The DL signal may include, for example, downlink data signals 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 grants). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include reference signals.

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

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

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

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

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

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

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

[0169] <Terminal Configuration> Figure 18 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.

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

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

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

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

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

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

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

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

[0178] For example, if the downlink receive occasions in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, the control unit 203 of the UE200 determines the frequency resource to be used for reception, assuming that the frequency resource allocated within the frequency resources available for downlinks within the SBFD symbol is the valid frequency resource. The communication unit uses the frequency resource determined by the control unit 203 to receive the downlink receive occasions.

[0179] Here, for example, if the uplink transmit occasions in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, the control unit 203 of the UE200 determines the frequency resource to be used for transmission, assuming that the frequency resource allocation information (e.g., FDRA information) indicates either a frequency resource allocation within an SBFD symbol or a frequency resource allocation within a non-SBFD symbol. The communication unit uses the frequency resource determined by the control unit 203 to transmit the uplink transmit occasions.

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

[0181] Functions include, but are not limited to, judgment, decision, determination, 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.

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

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

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

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

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

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

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

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

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

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

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

[0193] (Supplement to Embodiments) While embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. Software operated by a processor in a base station according to embodiments of this disclosure, and software operated by a processor in a terminal according to embodiments of this disclosure, may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disks (HDDs), removable disks, CD-ROMs, databases, servers, or any other suitable storage medium.

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

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

[0196] <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 there is no contradiction. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0218] Figure 20 shows an example of the configuration of vehicle 2001. As shown in Figure 20, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0246] 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 greater than or equal to 1 ms.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0260] 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 determines the frequency resource to be used for reception when the reception occasions for the downlink in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, assuming that the frequency resource allocated within the frequency resources available for the downlink within the SBFD symbol is the valid frequency resource; and a communication unit that receives the reception occasions for the downlink using the frequency resource determined by the control unit.

2. The terminal according to claim 1, wherein the control unit determines the size of the information block to be received based on the number of allocated frequency resources or the number of frequency resources available for the downlink.

3. A terminal comprising: a control unit that determines the frequency resources to be used for transmission, assuming that, when the transmission occasions for uplinks in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, the information regarding frequency resource allocation indicates either a frequency resource allocation within the SBFD symbol or a frequency resource allocation within a symbol other than the SBFD symbol; and a communication unit that transmits the transmission occasions for the uplink using the frequency resources determined by the control unit.

4. The terminal according to claim 3, wherein the control unit determines the size of the information block to be transmitted based on the number of allocated frequency resources or the number of frequency resources available for the uplink.

5. A communication method in which, when a terminal has a receive occasion for a downlink in a different slot within a Subband non-overlapping Full Duplex (SBFD) symbol, the terminal determines which frequency resource to use for reception, assuming that the frequency resource allocated within the frequency resources available for the downlink within the SBFD symbol is a valid frequency resource, and uses the determined frequency resource to receive the receive occasion for the downlink.

6. A communication method comprising: when a terminal has uplink transmission occasions in different slots within a Subband non-overlapping Full Duplex (SBFD) symbol, determining which frequency resources to use for transmission based on information regarding frequency resource allocation indicating either a frequency resource allocation within the SBFD symbol or a frequency resource allocation within a symbol other than the SBFD symbol; and transmitting the uplink transmission occasion using the determined frequency resources.

Images