Terminal and communication method

Abstract

To provide a terminal and a communication method that, in a case where a plurality of transmission / reception occasions occur, appropriately performs an operation according to the type of symbol for which the occasion occurs.SOLUTION: A terminal includes a control unit that, when downlink reception occasions in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, determines a frequency resource to be used for reception, assuming that a frequency resource allocated within the frequency resources available for downlink within the SBFD symbol is a valid frequency resource, and a communication unit that receives the downlink reception occasion using the frequency resource determined by the control unit.SELECTED DRAWING: Figure 18

Description

[Technical Field]

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

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

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

[0004] Furthermore, for Release 19, extensions regarding UL transmission and DL reception across SBFD and non-SBFD symbols in different slots are being considered (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Subband full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 [Non-patent document 2] 3GPP TS 38.214 V18.3.0 (2024-06) [Non-patent document 3] 3GPP TS 38.300 V18.2.0 (2024-06) [Non-patent document 4] 3GPP TS 38.331 V18.1.0 (2024-03) [Non-Patent Document 5] 3GPP TR 38.858 V18.1.0 (2024-03) Summary of the Invention

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

[0007] One aspect of the present disclosure contributes to providing a terminal that can appropriately operate according to the type of symbol in which the occasion occurs when multiple transmission / reception occasions occur.

[0008] A terminal according to one embodiment of the present disclosure includes a control unit that, when downlink reception occasions in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, 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 SBFD symbol is a valid frequency resource, and a communication unit that receives the downlink reception occasion using the frequency resource determined by the control unit. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] FIG. 1 is a diagram illustrating an example of TDD settings defined up to Rel-16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7A] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7B] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7C] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7D] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7E] FIG. 1 illustrates pure time units and SBFD time units. [Figure 8] FIG. 10 is a diagram illustrating the periodicity of CG PUSCH. [Figure 9] FIG. 10 illustrates the periodicity of SPS PDSCH. [Figure 10] FIG. 1 is a diagram illustrating multi-PUSCH scheduling using NR. [Figure 11A] FIG. 10 is a diagram illustrating counting of PUSCH repetitions based on physical slots. [Figure 11B] FIG. 10 is a diagram illustrating counting of PUSCH repetitions on an available slot basis. [Figure 12] FIG. 1 is a diagram illustrating TBoMS. [Figure 13] FIG. 1 is a diagram illustrating time domain resource allocation in TBoMS. [Figure 14] FIG. 1 is a diagram illustrating repetition of TBoMS. [Figure 15] A figure showing an example of resources for DL ​​subbands and UL subbands when SBFD is applied. [Figure 16A] FIG. 1 is a diagram illustrating Configuration 1. [Figure 16B] FIG. 10 is a diagram illustrating configuration 2. [Figure 17] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 18] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 19] FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 20] FIG. 1 is a diagram illustrating an example of a configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

[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, and in FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

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

[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] Fig. 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in Fig. 3, one slot is made up of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0033] <SBFD operation> Considering the time ratio of transmission and reception by time division duplex (TDD) up to Rel-16 (for example, DL:UL = 4:1), there may be cases where the transmission opportunities for UL signals / channels are fewer than the reception opportunities for DL signals / channels. In such cases, the UE200 may not be able to transmit UL signals / channels frequently, and there is concern that significant transmission delays may occur for important UL signals / channels. Also, since the UL transmission opportunities are fewer compared to the DL reception opportunities, congestion of signals / channels during UL transmission opportunities is also a concern. Furthermore, in TDD, since the time resources available for transmitting UL signals / channels are limited, for example, the application of UL coverage extension techniques such as repetition transmission is also limited.

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

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

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

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

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

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

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

[0041] Fig. 5 is a diagram showing an example of SBFD operation. In the example shown in Fig. 5, part of the DL resources of the TDD band is set as the 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 multiple UEs 200 (UE1 and UE2 in FIG. 5) receives the DL channel / signal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] <CG PUSCH> CG PUSCHs include Type 1 CG PUSCHs and Type 2 CG PUSCHs. Type 1 CG PUSCHs are configured by RRC only (i.e., do not rely on DCI), and transmission parameters are provided by configuredGrantConfig, pusch-Config, and rrc-ConfiguredUplinkGrant. On the other hand, Type 2 CG PUSCHs are configured by RRC and DCI activation / deactivation. One DCI can activate only one CG PUSCH configuration, and one DCI can deactivate multiple CG PUSCH configurations. Transmission parameters are provided by configuredGrantConfig, pusch-Config, and activation DCI. (See FIG. 8.) The configuredGrantConfig, pusch-Config, and activation DCI may be referred to as periodic or semi-persistent signal or channel-related information, etc.

[0058] <SPS PDSCH> In Rel-16, multiple SPS configurations are supported. SPS can be activated / deactivated by DCI. Transmission 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 periodic or semi-persistent signal or channel information.

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

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

[0061] <Coverage expansion> Rel-17 specifies several techniques for extending the coverage of uplink signals. For example, available slot counting (available slot basis) for PUSCH repetition and TB processing over multi-slot (TBoMS) are specified. Available slot basis and TBoMS are explained below.

[0062] <Coverage expansion: available slot basis> 11A is a diagram illustrating counting of PUSCH repetitions based on physical slots. The count for PUSCH repetitions in Rel-15 / 16 is based on physical slots. Therefore, as shown in FIG. 11A, when the number of PUSCH repetitions is 16, up to four actual PUSCH repetitions are configured for the TDD (Time Division Duplex) pattern "DDDDU."

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

[0064] 11B is a diagram illustrating counting of PUSCH repetitions on an available slot basis. On an available slot basis, PUSCH repetitions are determined based on the following two steps.

[0065] Step 1: The terminal determines available slots 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 determines whether to drop the PUSCH repetition according to a predetermined dropping rule, for example, a PUSCH dropping rule in Rel-15 / 16.

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

[0068] <Coverage expansion: TBoMS> TBoMS transmits one Transport Block (TB) over multiple slots, and the TB size determination is performed based on PUSCH resource elements over N slots.

[0069] TBoMS may have 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 -1TB can be allocated to multiple slots in the time domain, reducing the number of Resource Blocks (RBs) required to transmit a specific TB

[0070] Fig. 12 is a diagram for explaining TBoMS, showing an example in which one TB is transmitted over three slots.

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

[0072] The number of slots (N) allocated to one TB is indicated by numberOfSlotsTBoMS, which is notified by higher layer signaling such as RRC signaling.

[0073] Fig. 13 is a diagram illustrating time domain resource allocation for TBoMS. Fig. 13 shows an example where numberOfSlotsTBoMS = 4. The same symbols are allocated to each slot (PUSCH).

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

[0075] The RV (Redundancy Version) determination for each repetition is the same as for Rel-15 / 16. 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] Fig. 14 is a diagram for explaining the repetition of TBoMS, showing an example in which the number of slots of single TBoMS is 2, the number of repetitions is 3, and the RV sequence is [0, 2, 3, 1].

[0077] <PUSCH repetition Type A> PUSCH repetition Type A is a form in which a PUSCH allocated in a slot is transmitted repeatedly. 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のタイプ> The UE determines resource block allocation in the frequency domain using the resource allocation field detected in the PDCCH DCI. According to §6.1.2.2 of Non-Patent Document 2, Type 0, Type 1, etc. are supported as UL resource allocation schemes in the frequency domain.

[0079] 1.UL Resource Allocation Type 0 UL Resource Allocation in FDRA Type 0 The UL resource allocation information includes a bitmap indicating the resource block group (RBG) allocated to the scheduled UE. An RBG is a set of contiguous virtual resource blocks. Transform precoding is not available in this scheme.

number

[0080] The size of the bitmap is N RGB There are 1688888 bits, one bitmap bit per RBG, and each RBG is addressable. RBGs are indexed in increasing order of frequency in the bandwidth portion, starting with the lowest frequency. The RBG bitmap order is RBG 0 to RBG N. RGB -1 is mapped from the MSB to the LSB of the bitmap. If the corresponding bit value of the bitmap is 1, the RBG is assigned to the UE; otherwise, the RBG is not assigned to the UE.

[0081] 2. UL Resource Allocation Type 1 The information on the UL resource allocation of FDRA's UL resource allocation Type 1 is provided to the scheduled UE in the form of a set of non-interleaved virtual resource blocks that are continuously allocated within an active bandwidth part of size N BWF size PRBs.

[0082] The UL Type1 resource allocation field consists of a resource indication value (RIV) corresponding to the starting virtual resource block (RB start ) and the length (L RBs ) of the continuously allocated resource blocks. The resource indication value is defined by the following formula.

Equation

[0083] <Considerations on Duplex Extension for Rel-19> As described above, in Rel-18, studies have been conducted to enable the coexistence of downlink and uplink (full duplex, more specifically sub-band 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 RF requirements is summarized in Non-Patent Document 5.

[0084] In Non-Patent Document 1, studies have been centered around the extension of sub-band non-overlapping full duplex (SBFD) operation on the gNB side within the TDD carrier. The objectives of the studies for Rel-19 are as follows. (1) Examination of the specification for semi-static indication of the time position of the SBFD sub-band for the UE in the RRC_CONNECTED mode Indication of the time position of the SBFD subband in the SIB is not excluded (2) Study on the specification of semi-static indication of the frequency domain location of SBFD subbands to UE in RRC_CONNECTED mode Indication of the frequency domain location of SBFD subbands in the SIB is not excluded (3) Study on SBFD operation specifications to support random access of SBFD symbols by UE in RRC CONNECTED mode (4) Consider SBFD operation to support random access by UE in RRC_IDLE / INACTIVE mode and specify it if appropriate. ·Check whether standardization work will proceed in RAN#104 (5) Study on the specifications for the operation and procedures of SBFD-enabled UE (SBFD aware UE) transmission / reception and measurement of SBFD symbols and / or non-SBFD symbols. Transmit / receive operation in SBFD sub-bands configured for DL ​​and / or flexible symbols as indicated by TDD-UL-DL-ConfigCommon UL transmission only in the UL sub-band DL reception only within DL sub-band (excluding CLI measurements by UE outside DL sub-band) Note: When flexible symbols are used, it is not expected that legacy uplink symbols will be converted to downlink / SBFD symbols. Enhanced resource allocation in the frequency domain for the following SBFD symbols: Frequency domain resource allocation for PDSCH / CSI-RS across two DL subbands in an SBFD symbol Handling misalignment of boundaries between SBFD subbands and resource block groups (RBGs), CSI report subbands, CSI-RS resources, and precoding resource block groups (PRGs) Enhancements for physical channels / signals and procedures spanning SBFD and non-SBFD symbols in different slots, where each transmission / reception within a slot includes either all SBFD symbols or all non-SBFD symbols, including: Resource allocation in the frequency domain when transmitting / receiving SBFD and non-SBFD symbols using different available frequency resources in different slots CSI reports for related CSI-RS instances occurring in both SBFD and non-SBFD symbols in different slots SRS, PUCCH and PUSCH configurations in SBFD and non-SBFD symbols (e.g., resources, frequency hopping parameters, UL power control parameters and / or beam / spatial relationships) Collision handling between DL reception in DL sub-band and UL transmission in UL sub-band in SBFD symbols (6) Based on TR 38.858 (Non-Patent Document 5), the following is assumed: SBFD on the gNB side Half duplex operation on the UE side FR1 and FR2-1 SBFD operation option 4 (e.g., both the time and frequency location of the sub-bands for SBFD operation are known to the SBFD-capable UE) Coexistence of non-SBFD-capable UE (including legacy UE) and SBFD-capable UE in a cell where SBFD is operated on the gNB side SBFD method within a single 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 SBFD operation mechanism must also consider adjacent channel coexistence between the two operators.

[0085] <Transmission / Reception Spanning SBFD Symbols and Non-SBFD Symbols> In §6.1.2 of Non-Patent Document 5, it is being considered whether to support transmission / reception spanning SBFD symbols and non-SBFD symbols.

[0086] For UL transmission / DL reception spanning SBFD symbols and non-SBFD symbols in different slots (where each transmission / reception within the slot is either all SBFD or all non-SBFD symbols), the following options are considered for SBFD-capable UEs. Option 1: Transmission / reception is restricted to only SBFD symbols or only non-SBFD symbols Option 2: Transmission / reception can be performed with both SBFD symbols and non-SBFD symbols

[0087] UL transmission / DL reception spanning SBFD symbols and non-SBFD symbols includes the following information: · Repetition of PDSCH / PUSCH / PUCCH · 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 gNB configuration or scheduling such that all transmit / receive occasions are restricted to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional instructions or rules to determine which transmit / receive occasions are valid within one symbol type and invalid within other symbol types. The frequency resources, power control, and beam / spatial relationships for all transmit / receive occasions may be identical in Option 1 but may be different in Option 2. If different, additional work on the specifications may be required. Option 1 may / may not increase transmit / receive latency if transmit / receive in other symbol types is postponed, and may degrade performance if transmit / receive in other symbol types is dropped. Option 2 may / may not reduce transmit / receive latency and improve coverage.

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

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

[0091] Parameters for configuring SRS (Sounding Reference Signal) resources may include SRS Config. SRS Config is a parameter that defines a list of SRS-ResourceSets and a list of SRS-Resources. An SRS-ResourceSet included in the list may include an SRS-ResourceSet identifier (srs-ResourceSetId), a list of SRS-Resource identifiers (srs-ResourceIdList), etc. An SRS-Resource included in the list includes an SRS-Resource identifier (srs-ResourceId), SRS resources in the frequency domain (e.g., resourceMapping), etc. ResourceMapping includes a start position (startPosition), the number of symbols (nrofSymbols), the number of repetitions (repetitionFactor), etc. SRS Config may be a parameter specified in §6.3.2 "Radio resource control information elements" of Non-Patent Document 4.

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

[0093] The UL sub-band frequency resources in an active UL BWP are called UL usable PRBs, and the DL sub-band frequency resources in an active DL BWP are called DL usable PRBs (see FIG. 15).

[0094] To determine the available PRBs in UL / DL, the following options are considered: Option 1: The usable PRBs in the UL are determined as the intersection of the cell-specific UL subbands and the active UL BWPs in the SBFD symbol. The usable PRBs in the DL are determined as the intersection of the cell-specific DL subbands and the active DL BWPs in the SBFD symbol. Option 2: The available PRBs in UL / DL are explicitly configured 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 in the SBFD symbol are PRBs available for use in the downlink. Similarly, the UL subband portion and the pure UL symbol portion in the SBFD symbol are PRBs available for use in the uplink.

[0096] <Agreement 2> At the 3GPP RAN#116bis meeting, the following was agreed upon:

[0097] For 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, for 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 for 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 decide which of the following options are supported:

[0098] Option 1: Separate FDRA configuration / instructions / interpretations for SBFD and non-SBFD symbols. Option 2: Single FDRA setting / indication for one symbol type (SBFD or non-SBFD symbol) and RB offset setting / indication / decision to determine resources for other symbol types. Option 3: PUSCH in slots that overlap with RBs outside the UL enabled PRBs in the SBFD symbol are disabled (e.g., PUSCH in the slot is dropped / deferred). Option 4: Only PUSCH of one symbol type is enabled, and PUSCH of other symbol types is disabled. Option 5: For PUSCH in a slot that overlaps with RBs outside the UL available PRBs in the SBFD symbol, only assigned PRBs within the UL available PRBs are considered valid. Option 6: The gNB shall not schedule the PUSCH in the SBFD symbols in a slot to overlap with any PRB other than those available in the UL. Other options are not excluded. The applicable conditions have yet to be determined.

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

[0100] For an SBFD-capable UE with UL transmissions and DL receptions spanning SBFD and non-SBFD symbols in different slots (each transmission / reception in a slot having either all SBFD symbols or all non-SBFD symbols), the SBFD-capable UE is provided with one of the following configurations: Configuration 1: Transmission / reception is restricted to 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 (for example, per UE, per channel / signal, etc.) has not yet been determined. It is also unclear whether support for setting 2 depends on the UE capability.

[0102] For UL transmission / DL reception for one slot, in one occasion, SBFD symbols and non-SBFD symbols do not coexist, and for each transmission / reception within the slot, one of the symbol types must be used. However, in the case of UL transmission / DL reception where resources are periodically allocated in repetitions etc. that span multiple slots, events such as being transmitted / received using SBFD symbol type in some slots and being transmitted / received using non-SBFD symbols in other slots can occur. In such cases, options are supported for the entire transmission / reception that spans a series of multiple slots, where one option (Configuration 1) is to make only one of the symbol types valid, and another option (Configuration 2) is that both symbol types may coexist, and one of the configurations is set for the terminal.

[0103] For example, when Configuration 1 is set for a certain terminal, if a repetition is set to SBFD symbols, in that terminal, that repetition is valid only for SBFD symbols, and if the repetition is set to non-SBFD symbols, in that terminal, that repetition is valid only for non-SBFD symbols. If Configuration 2 is set for the terminal, it becomes possible to use both SBFD symbols and non-SBFD symbols in a certain repetition.

[0104] <PDSCH / PUSCH without repetition scheduled by DCI> Regarding PDSCH / PUSCH without (or) repetition scheduled by DCI, the following points are agreed upon.

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

[0106] Option 1-1: Only assigned PRBs within the DL usable PRBs 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 this option reuses the existing RB index and VRB to PRB mapping. Also, with this option, the number of PRBs for TBS determination may be based only on assigned PRBs within the DL usable PRBs.

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

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

[0109] Specifically, for SPS PDSCH, PDSCH repetition, and multi-PDSCH scheduled by a single DCI, for configuration 2, the following working assumptions exist for the case where a PDSCH occasion spans SBFD symbols and non-SBFD symbols:

[0110] (Working Assumption) For SPS PDSCH configurations without repetition, where receive occasions span SBFD and non-SBFD symbols and each receive occasion is either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2), PDSCH repetitions span 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 multi-PDSCH scheduled by a single DCI that spans SBFD and non-SBFD symbols and each PDSCH in a slot is either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2): · Option 5: Only allocated PRBs among the DL available PRBs in the SBFD symbol are considered valid. In the case of SPS PDSCH, it is not yet determined whether the number of PRBs for determining the transport block size (TBS) is based on the allocated PRBs or only on the allocated PRBs within the DL available PRBs. For PDSCH repetitions, it is not yet determined whether the number of PRBs for TBS determination is based on the allocated PRBs, only on the allocated PRBs among the PRBs available in DL, or on the allocated PRBs among the PRBs available in DL for the first repetition. In the case of multi-PDSCH scheduled by a single DCI, it is not yet determined whether the number of PRBs for TBS determination will be based on the allocated PRBs or only on the allocated PRBs among the available PRBs in DL.

[0111] Specifically, for CG PUSCH, PUSCH repetition Type A, multi-PUSCH scheduled by a single DCI, and PUSCH TBoMS, for configuration 2, there is the following agreement on when a PUSCH occasion spans SBFD symbols and non-SBFD symbols:

[0112] (RAN1#118 Agreed) (1) In the case of a CG PUSCH configuration without repetition, where transmission occasions span SBFD symbols and non-SBFD symbols, and each transmission occasion has either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2); (2) In the case of PUSCH repetition Type A, where each repetition has either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2) and spans SBFD symbols and non-SBFD symbols in different slots; (3) 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 (i.e., configuration 2) and spans SBFD symbols and non-SBFD symbols; and (4) In the case of TBoMS, where each transmission in a slot has either all SBFD symbols or all non-SBFD symbols (i.e., configuration 2) and spans SBFD symbols and non-SBFD symbols in different slots. Option 2: Single resource configuration / indication for non-SBFD symbols and RB offset configuration / indication / determination to determine frequency resource for SBFD symbols The number of PRBs for PUSCH transmission in SBFD symbols and PUSCH transmission in non-SBFD symbols is the same.

[0113] <Premise> The premise may be a single FDRA setting / instruction for a certain symbol type (e.g., one of SBFD symbols or non-SBFD symbols), and a setting / instruction / determination of an RB offset to determine frequency resources for a symbol type different from the symbol type (e.g., the other of SBFD symbols or non-SBFD symbols).

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

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

[0116] <Considerations> According to the RAN1 agreement, FDRA discussions / agreements are taking place in the following cases: Single TX / RX occasion Multiple TX / RX occasions

[0117] A single transmit / receive occasion is considered for an FDRA type 1 / 0 PDSCH without repetition scheduled by DCI in the SBFD symbol, or a single transmit / receive occasion is considered for an FDRA type 0 PUSCH without repetition scheduled by DCI in the SBFD symbol, where no extension is required for the case of an FDRA type 1 PUSCH without repetition scheduled by DCI.

[0118] For multiple transmit / receive occasions, configuration 2 is considered where PDSCH / PUSCH occasions span SBFD and non-SBFD symbols.

[0119] However, in cases where multiple transmit / receive occasions occur, there is room for consideration regarding the operation according to the type of symbol in which the occasion occurs. For example, there is room for consideration regarding Configuration 1 when there are multiple transmit / receive occasions and the PDSCH / PUSCH occasion is only within the SBFD symbol. There is also room for consideration regarding Configuration 2 when there are multiple transmit / receive occasions and the PDSCH / PUSCH occasion is only within the SBFD symbol.

[0120] In cases where multiple transmit / receive occasions occur, it is desirable to clarify the handling of FDRA and / or TBS determination as an operation depending on the type of symbol in which the occasion occurs.

[0121] Therefore, in this embodiment, in the case where a plurality of transmission / reception occasions occur, an operation according to the type of symbol in which the occasion occurs will be described.

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

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

[0124] As a variation of the FDRA of Proposal 1, when frequency resource allocation type 0 is applied, the UE does not expect to be assigned an RBG that is completely out of range of the PRBs available in the DL, where the RBG that is completely out of range of the PRBs available in the DL may be an RBG that does not overlap with the PRBs available in the DL.

[0125] (TBS decision on Proposal 1) For SPS PDSCH, the number of PRBs for TBS determination may be based on any one or more of the following: Alt (alternative) 1-1a: assigned PRB Alt 1-1b: Only assigned PRBs among those available in DL

[0126] In the case of PDSCH repetition, the number of PRBs for TBS determination may be based on any one or more of the following: Alt 1-2a: Assigned PRB Alt 1-2b: Only assigned PRBs among those available in DL

[0127] In the case of multiple PDSCHs scheduled by a single DCI, the number of PRBs for TBS determination may be based on any one or more of the following: Alt 1-3a: Assigned PRB Alt 1-3b: Only assigned PRBs among those available in DL

[0128] <Variation of Proposal 1> The above proposal 1 may be applicable only to configuration 1. Alternatively, the above proposal 1 may be applicable only to configuration 2. Alternatively, the above proposal 1 may be applicable to both configurations 1 and 2.

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

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

[0131] As described above, Proposal 1 clarifies the handling of FDRA and / or TBS determination for PDSCH occasions of each PDSCH in the DL when PDSCH occasions in different slots are only within the SBFD symbol. This allows, for example, a UE to determine resources and TBS based on FDRA, so that in cases where multiple reception occasions occur, it can appropriately operate according to the type of symbol in which the occasion occurs.

[0132] <Proposal 2> Proposal 2 describes the case where PUSCH occasions in different slots are only within SBFD symbols. Note that Proposal 2 exemplarily describes the cases of CG PUSCH, PUSCH repetition, multi-PUSCH scheduled by a single DCI, and PUSCH TBoMS, where PUSCH occasions in different slots are only within SBFD symbols.

[0133] (Prop. 2 FDRA) Proposal 2 would apply at least one of the following options to the FDRA:

[0134] (FDRA Option 2-1 of Proposal 2) The information (eg, bits) in the FDRA field 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 the FDRA with PRBs outside the range of PRBs available in the UL is allowed, where only PRBs within the range of PRBs available in the UL are valid for PUSCH occasions, and the UE does not expect the FDRA to indicate RBGs that are completely outside the range of PRBs available in the UL.

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

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

[0138] (TBS decision on Proposal 2) Here, we will explain how to determine the TBS when an FDRA that overlaps with an RB outside the PRB available in the UL is allowed.

[0139] For CG PUSCH, the number of PRBs for TBS determination may be based on any one or more of the following: Alt 2-1a: Assigned PRB Alt 2-1b: Only assigned PRBs among UL available PRBs

[0140] In the case of PUSCH repetition, the number of PRBs for TBS determination may be based on any one or more of the following: Alt 2-2a: Assigned PRB Alt 2-2b: Only assigned PRBs among those available in UL

[0141] In the case of multi-PUSCH scheduled by a single DCI, the number of PRBs for TBS determination may be based on any one or more of the following: Alt 2-3a: Assigned PRB Alt 2-3b: Only assigned PRBs among those available in UL

[0142] For PUSCH TBoMS, the number of PRBs for TBS determination is based on at least one of the following: Alt 2-4a: Assigned PRB Alt 2-4b: Only assigned PRBs among those available in UL

[0143] <Variation of Proposal 2> The above-mentioned proposal 2 may be applicable only to configuration 1. Alternatively, the above-mentioned proposal 2 may be applicable only to configuration 2. Alternatively, the above-mentioned proposal 1 may be applicable to both configurations 1 and 2.

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

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

[0146] As described above, Proposal 2 clarifies the handling of FDRA and / or TBS determination for PUSCH occasions of each PUSCH in the UL when PUSCH occasions in different slots are only within the SBFD symbol. This allows, for example, a UE to determine resources or TBS based on FDRA, so that in cases where multiple transmission occasions occur, it can appropriately operate according to the type of symbol in which the occasion occurs.

[0147] (Combined with options) In Proposals 1 to 3 of the present disclosure, which proposal is applied or which option or alternative is used may be determined as follows. - Set by upper layer parameters Determined by related higher level parameters Indicated in MAC CE or DCI Determined based on UE capabilities - Listed in the specifications - Determined based on the conditions stated in the specifications Determined by higher layer parameters / MAC CE / DCI configuration and reported UE capabilities (combination of the above decisions)

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

[0149] (Signal from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) DCI DCI Field: Existing DCI field or newly introduced DCI field RNTI: DCI with CRC scrambled by the existing RNTI or the newly introduced RNTI DCI Format: Existing DCI format or newly introduced DCI format Combination of the above information

[0150] In the present disclosure, the UE may receive information from the network (NW) in the following periodic format: Option 1: Receive periodic updates Option 2: Semi-persistent reception of information (triggered by UE or gNB instructions) Option 3: Aperiodic information reception (triggered by UE or gNB instructions)

[0151] In the present 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 the present disclosure, information from the network (NW) is set / indicated as follows: ·UE common / UE only Cell specific / Cell common Per UE / CC / BWP / band / cell / CG

[0154] (Signal from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g. RRC message / LPP message) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) UCI UCI on PUCCH or PUSCH Combination of the above information

[0155] In the present disclosure, the UE may report information to the network (NW) in a periodic manner as follows: Option 1: Send information periodically Option 2: Semi-persistent information transmission (triggered by UE or gNB instruction) Option 3: Aperiodic information transmission (triggered by UE or gNB instructions)

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

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

[0158] Next, the configurations of the gNB100 and the UE200 will be described. Note that the configurations of the gNB100 and the UE200 described below are examples of functions related to the present embodiment. The gNB100 and the UE200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to the present embodiment.

[0159] <Base station configuration> Fig. 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 transmitter 101, a receiver 102, and a controller 103. The gNB 100 communicates with a UE 200 (see Fig. 18) wirelessly.

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

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

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

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

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

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

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

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

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

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

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

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

[0172] The channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, the UE 200 transmits uplink control information to the gNB 100 using the PUCCH and transmits an uplink data signal using the PUSCH.

[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, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).

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

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

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

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

[0178] Here, for example, when downlink reception occasions in different slots are within a Subband Non-Overlapping Full Duplex (SBFD) symbol, the control unit 203 of the UE 200 determines the frequency resource to be used for reception by determining that the frequency resource allocated within the frequency resource available for downlink in the SBFD symbol is the valid frequency resource. The communication unit receives the downlink reception occasion using the frequency resource determined by the control unit 203.

[0179] Here, for example, when uplink transmission occasions in different slots are within Subband non-overlapping Full Duplex (SBFD) symbols, the control unit 203 of the UE 200 determines the frequency resource to be used for transmission, assuming that the information on frequency resource allocation (e.g., information on FDRA) indicates frequency resource allocation within the SBFD symbol or frequency resource allocation within a symbol that is not an SBFD symbol (non-SBFD symbol).The communication unit transmits the uplink transmission occasion using the frequency resource determined by the control unit 203.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

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

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

[0198] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

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

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

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

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

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

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

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

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

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

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

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

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

[0211] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

[0213] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. When downlink reception occasions in different slots are within a Subband Non-Overlapping Full Duplex (SBFD) symbol, a control unit determines a frequency resource to be used for reception by determining that a frequency resource allocated within the frequency resource available for the downlink within the SBFD symbol is a valid frequency resource; a communication unit that receives the downlink receiving occasion using the frequency resource determined by the control unit; A terminal comprising:

2. The control unit determines a 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. The terminal according to claim 1 .

3. a control unit for determining a frequency resource to be used for transmission when an uplink transmission occasion in a different slot is within a Subband non-overlapping Full Duplex (SBFD) symbol, based on the information on frequency resource allocation indicating a frequency resource allocation within the SBFD symbol or a frequency resource allocation within a symbol other than the SBFD symbol; a communication unit configured to transmit the uplink transmission occasion using the frequency resource determined by the control unit; A terminal comprising:

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

5. The device is When the downlink reception occasions in different slots are within a Subband Non-Overlapping Full Duplex (SBFD) symbol, determining a frequency resource to be used for reception by determining that a frequency resource allocated within the frequency resource available for the downlink in the SBFD symbol is a valid frequency resource; receiving the downlink receiving occasion using the determined frequency resource; Communication method.

6. The device is When the uplink transmission occasions in different slots are within a Subband non-overlapping Full Duplex (SBFD) symbol, determining a frequency resource to be used for transmission, assuming that the information on frequency resource allocation indicates a frequency resource allocation within the SBFD symbol or a frequency resource allocation within a symbol other than the SBFD symbol; transmitting the uplink transmission occasion using the determined frequency resource; Communication method.

Images