terminal

Abstract

To provide a terminal that can operate properly for upstream reference signals.SOLUTION: A terminal includes a communication unit that transmits and / or receives signals of either a subband non-overlapping full duplex (SBFD) symbol or a non-SBFD symbol, and a control unit that determines the symbol type of a resource set of a reference signal used to assume an uplink channel state on the basis of a specific rule when the symbol type is not specified in the resource set.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] The present disclosure relates to a terminal. [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, in preparation for Release 19, extensions regarding UL transmission and DL reception using SBFD symbols and non-SBFD symbols 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] A terminal periodically transmits a reference signal (SRS: Sounding Reference Signal) via uplink, which is received by the base station. The base station analyzes the SRS received from the terminal and collects information on the quality of the uplink wireless channel to perform management such as appropriate resource allocation, beamforming management, and interference mitigation.

[0007] However, the terminal operation in SRS has not been sufficiently studied, and further study is required.

[0008] One aspect of the present disclosure is to provide a terminal that can operate appropriately with respect to an uplink reference signal. [Means for solving the problem]

[0009] A terminal according to one embodiment of the present disclosure includes a communication unit that transmits and / or receives signals of either a subband non-overlapping full duplex (SBFD) symbol or a non-SBFD symbol symbol, and a control unit that determines the symbol type of a resource set of a reference signal used to estimate an uplink channel state based on a specific rule when the symbol type is not specified in the resource set.

[0010] A terminal according to one embodiment of the present disclosure includes a communication unit that transmits and / or receives signals of either a subband non-overlapping full duplex (SBFD) symbol or a non-SBFD symbol symbol, and a control unit that, when one resource set of reference signals used for estimating an uplink channel state is provided, determines that the symbol type is not specified in the resource set.

[0011] A terminal according to one embodiment of the present disclosure includes a communication unit that transmits and / or receives signals of either a subband non-overlapping full duplex (SBFD) symbol or a non-SBFD symbol symbol, and a control unit that, when one resource set of reference signals used for estimating an uplink channel state is provided, applies an indicator that identifies resources within the resource set to the one provided resource set regardless of the symbol type of the uplink channel. [Brief explanation of the drawings]

[0012] [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. [Figure 4B] FIG. 1 is a diagram illustrating an example of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 is a diagram illustrating an example of a TDD configuration. [Figure 6B] A diagram showing an example of a TDD configuration including SBFD. [Figure 7] FIG. 1 is a diagram illustrating a Codebook-based SRS. [Figure 8] FIG. 1 is a diagram illustrating a non-Codebook-based SRS. [Figure 9] FIG. 10 is a diagram illustrating multi-TRP PUSCH repetition. [Figure 10] A figure showing an example of resources for DL ​​subbands and UL subbands when SBFD is applied. [Figure 11] FIG. 1 is a diagram illustrating Configuration 1. [Figure 12] FIG. 10 is a diagram illustrating configuration 2. [Figure 13] FIG. 1 shows the draft CR of TS 38.214. [Figure 14] FIG. 1 shows the draft CR of TS 38.214. [Figure 15] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 16] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 17] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present disclosure is applied is not limited to the following embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] Examples of the time-frequency division duplexing method include XDD (Cross Division Duplex) 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).

[0038] 4A is a diagram illustrating an example of TDD. In the example shown in FIG. 4A, TDD slots or symbols are configured to 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).

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

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

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

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

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

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

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

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

[0047] In 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.

[0048] Figure 6A is a diagram showing an example of 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.

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

[0050] Figure 6B is a diagram showing an example of a TDD configuration including SBFD. 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.

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

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

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

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

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

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

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

[0058] <CG PUSCH> There are two types of CG PUSCH: Type 1 CG PUSCH and Type 2 CG PUSCH. Type 1 CG PUSCH is configured by RRC only (i.e., it does not rely on DCI), and transmission parameters are provided by configuredGrantConfig, pusch-Config, and rrc-ConfiguredUplinkGrant.

[0059] On the other hand, Type 2 CG PUSCH involves RRC configuration and DCI activation / deactivation, where one DCI can activate only one CG PUSCH configuration and one DCI can deactivate multiple CG PUSCH configurations, and transmission parameters are provided by configuredGrantConfig, pusch-Config, and activation DCI. The configuredGrantConfig, pusch-Config, and activation DCI may also be referred to as periodic or semi-persistent signals or information on channels, etc. Type 1 CG PUSCH may also be referred to as Type 1 PUSCH transmission with CG. Type 2 CG PUSCH may also be referred to as Type 2 PUSCH transmission with CG.

[0060] <ul codebook based transmission (strp)> Codebook-based uplink transmission (in the case of a single TRP (Transmit / Receive Point)) will be described. As shown in FIG. 7, a UE transmits SRSs (Sounding Reference Signals) precoded with different precoders using SRS resource #0 and SRS resource #1 configured in advance by RRC. The gNB uses an SRS Resource Indicator (SRI) in a UL grant to feed back to the UE which of the two different precoded SRSs had a better reception state. For example, the gNB feeds back to the UE, using the SRI, that the reception state of the SRS precoded using SRS resource #0 was good. The UE determines a precoder for PUSCH transmission based on the fed-back SRI.

[0061] The gNB, via a UL grant, indicates SRS resources as SRI, the weighting of each port as TPMI (Transmitted Precoding Matrix Indicator), the rank as TRI (Transmitted Rank Indicator), and the modulation scheme and coding rate as MCS (Modulation and Coding Scheme). A codebook is a set of pre-defined candidates for the pre-coding weight matrix.

[0062] If an SRS resource set has multiple SRS resources, the SRS resource set includes multiple resources (e.g., SRS resource #0, SRS resource #1). The SRS resource indicator (SRI) indicates the SRS resource in the SRS resource set. For example, if SRS resource #0 is indicated by the SRI, the SRS port of SRS resource #0 is used.

[0063] Note that §6.1.1.1 of Non-Patent Document 2 describes how resources and parameters for codebook-based UL transmission are handled. Also, §6.1.2.3 of Non-Patent Document 2 describes how resources are allocated in uplink transmission according to a set grant.

[0064] <ul non-codebook based transmission (strp)> Next, we will explain non-codebook-based uplink transmission (for a single TRP). As shown in Figure 8, CSI-RS is transmitted from the gNB. Multiple SRS resources (up to the maximum rank) are configured for the UE, and each resource has one port. The UE determines the precoder for the SRS resource using the reciprocity property (path duality), which means that the uplink and downlink propagation path conditions are essentially the same, and transmits SRSs (Sounding Reference Signals) precoded with different precoders. The gNB uses the SRI in the UL grant to feed back to the UE which SRS had the best reception condition among the multiple different precoded SRSs (one SRS resource is selected per port). The UE determines the SRS resource for PUSCH transmission based on the fed-back SRI.

[0065] Note that §6.1.1.2 of Non-Patent Document 2 describes the handling of resources and parameters for non-codebook-based UL transmission. Also, §6.1.2.3 of Non-Patent Document 2 describes the allocation of resources in uplink transmission according to a configured grant.

[0066] <mtrp> This section describes a multi-TRP scenario in which signals are transmitted and received using two transmission and reception points (TRPs) at different locations. Starting with Rel. 17, TDM M-TRP PUSCH repetition Type A / Type B is supported to improve reliability. Cyclic and sequential mapping between two beams (SRI / TPMI) / power control parameter sets (p0, alpha, PL-RS, closed-loop index) and repetition are supported. For example, as shown in Figure 9, gNB / UE switches TRPs by time division. Antenna switching between Rep#1 / Rep#2 and Rep#3 / Rep#4 can improve reliability and stability. When configuring mTRP, two resource sets can be configured using RRC or DCI.

[0067] Starting with Rel. 18, simultaneous UL transmission with multiple panels (STxMP) is supported. Two UE panels are used for UL transmission on overlapping time resources, and each of the two transmit panels transmits signals simultaneously using a different uplink transmit beam. In an ideal backhaul environment, two TRPs can coordinate to schedule PUSCH or PUCCH for a UE. Therefore, one TRP transmits one DCI to schedule PUSCH / PUCCH for the two TRPs. On the other hand, in a non-ideal backhaul environment, two TRPs cannot coordinate to schedule PUSCH for a UE due to backhaul delay. Therefore, each TRP independently schedules PUSCH using multiple DCIs transmitted by each TRP.

[0068] <Rel-19 duplex WID objectives> As mentioned above, Rel-18 has been studying ways to enable simultaneous 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 of specifications, performance evaluation results, implementability, and impact on RF requirements are summarized in Non-Patent Document 5.

[0069] Non-Patent Document 1 focuses on the extension of Subband Non-Overlapping Full Duplex (SBFD) operation on the gNB side within a TDD carrier. The objectives of the study for Rel-19 are as follows: (1) Study on the specification of semi-static indication of the time position of SBFD subbands to UE in 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 (for example, both the time and frequency positions of the subbands for SBFD are known to the SBFD-capable UE) · Coexistence of non-SBFD-capable UEs (including legacy UEs) and SBFD-capable UEs within a cell where SBFD is being operated on the gNB side · SBFD mode within a single configured DL and UL BWP pair with aligned center frequencies · One UL subband for SBFD operation in SBFD symbols (excluding legacy UL symbols / slots) within a TDD carrier · The mechanism of SBFD operation needs to consider adjacent channel coexistence between two operators

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

[0071] The UL subband frequency resources within the active UL BWP are called UL usable PRB, and the DL subband frequency resources within the active DL BWP are called DL usable PRB (see Figure 10).

[0072] The following options are considered to determine the UL / DL usable PRB. Option 1: The PRBs available for UL are determined as the intersection of the cell-specific UL subband and the active UL BWP within the SBFD symbol. The PRBs available for DL are determined as the intersection of the cell-specific DL subband and the active DL BWP within the SBFD symbol. Option 2: The PRBs available for UL / DL are explicitly configured within the active UL / DL BWP of the SBFD symbol.

[0073] As shown in Figure 10, the DL subband part within the SBFD symbol and the pure DL symbol part become the PRBs available for downlink. Similarly, the UL subband part within the SBFD symbol and the pure UL symbol part become the PRBs available for uplink.

[0074] <RAN1#117 Agreement> In the 3GPP RAN1#117 meeting, it was agreed that whether transmission / reception in different slots is restricted to one symbol type or enabled by two symbol types is determined based on the following configuration.

[0075] For SBFD-capable UEs, when performing UL transmission and DL reception that span SBFD symbols and non-SBFD symbols in different slots (each transmission / reception within a slot has either all SBFD symbols or all non-SBFD symbols), one of the following configurations is provided to the SBFD-capable UE. Configuration 1: Transmission / reception is restricted to either only SBFD symbols or only non-SBFD symbols (see Figure 1). Configuration 2: Transmission / reception is possible with both SBFD symbols and non-SBFD symbols (see Figure 2).

[0076] Note that the granularity of the configuration (e.g., per UE, per channel / signal, etc.) is undetermined. Also, it is undetermined whether the support for Configuration 2 depends on the capabilities of the terminal (UE capability).

[0077] 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 spanning multiple slots, events such as being transmitted / received with SBFD symbol type in some slots and being transmitted / received with non-SBFD symbols in other slots can occur. In such a case, two options are supported: an option (Configuration 1) where the entire transmission / reception spanning a series of multiple slots is valid only for one of the symbol types, and an option (Configuration 2) where both symbol types may coexist, and one of the configurations is set for the terminal.

[0078] 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. In other words, in Configuration 1, one of the SBFD symbols and non-SBFD symbols can be the valid symbol type. On the other hand, if Configuration 2 is set for the terminal, it is possible to use both SBFD symbols and non-SBFD symbols in a certain repetition.

[0079] In the latest draft CR (Change Request) of TS 38.214, a new clause 6.1.1.3 is added to TS 38.214. In the draft CR, UL transmission for SBFD is proposed, and specifications regarding the SRS resource set (SRS resource) are included. The specifications regarding the SRS resource set are proposed as follows.

[0080] The relevant SRS resource is identified by the SRI value within the SRS resource set corresponding to the symbol type of the PUSCH. · When Configuration 1 is applied to the UE, the SRI value is only applied to the SRS resource set corresponding to the active symbol type of the PUSCH. · When Configuration 2 is applied to the UE, the SRI value can be applied to the SRS resource set for SBFD or non - SBFD according to the symbol type of the PUSCH.

[0081] For details, please refer to Figure 13.

[0082] <UE Sounding Procedure for SBFD> In the latest draft CR of TS 38.214, a new clause 6.2.1.5 is added to TS 38.214. In the draft CR, the UE sounding procedure for SBFD is proposed, and specifications regarding the SRS resource set (SRS resource) are included. The specifications regarding the SRS resource set are proposed as follows.

[0083] · The SRS resource set is for the SBFD symbol type or the non - SBFD symbol type. The number of SRS resources in an SRS resource set whose symbol type is set to "SBFD" is the same as the number of SRS resources in an SRS resource set whose symbol type is set to "non-SBFD". An SRS (or an SRS resource set or an SRS resource) may be configured with a usage such as "codebook", "non-codebook", or "beam management", and the above conditions apply to the same usage "codebook", "non-codebook", or "beam management".

[0084] For details, see Figure 14.

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

[0086] The SRS Config is an RRC parameter (information element) used to configure the transmission of the SRS. In other words, the SRS Config is a parameter that configures the resources of the SRS.

[0087] 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. SRS Config includes parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 that provide an SRS resource set.

[0088] <Consideration> Study 1: UL transmission for SBFD (Clause 6.1.1.3 newly added to TS 38.214) The agreements reached up to the RAN1#120bis meeting and the draft CR only cover the case where a symbol type is specified for the SRS resource set, and the UE behavior when no symbol type is specified is not clear. As a result, the UE may not operate properly in SRS-related operations.

[0089] Study 2: UE sounding procedures for SBFD (Clause 6.2.1.5 newly added to TS 38.214) The previous agreements and draft CRs up to the RAN1#120bis meeting only address the case where two SRS resource sets are configured with usage set to "codebook" or "non-codebook" for SBFD and non-SBFD. The UL transmission behavior for the case where only one SRS resource set is configured with usage set to "codebook" or "non-codebook" is not clear. As a result, the UE may not operate properly in SRS-related operations.

[0090] It is still under discussion whether support for separate SRS resource sets for SBFD and non-SBFD should be part of the basic Feature Group (FG) for SBFD or a separate FG. If it is a separate FG, there may be UEs that support the basic FG for SBFD operation but do not support separate SRS resource sets for SBFD and non-SBFD.

[0091] Furthermore, even if support for separate SRS resource sets for SBFD and non-SBFD is part of the basic FG for SBFD, it may be up to the gNB implementation whether the gNB should configure two SRS resource sets for SBFD and non-SBFD with usage set to "codebook" or "non-codebook".

[0092] <Proposal 1> Proposal 1 provides a technique for the case where symbolType, such as SBFD symbol and non-SBFD symbol, is not provided in SRS-ResourceSet. Proposal 1 provides the following options 1 to 3.

[0093] <Proposal 1: Option 1> If symbolType is not provided in the SRS-ResourceSet, the UE assumes that the default value of symbolType is "non-sbfd" (or "sbfd").

[0094] The default value of symbolType is determined, for example, in the specification. In option 1, signaling can be reduced since symbolType is the default value and is not provided in the SRS-ResourceSet.

[0095] <Proposal 1: Option 2> If the symbolType is not provided in the SRS-ResourceSet, the UE behavior depends on the number of SRS resource sets for the same application. In other words, the symbolType of an SRS resource set is determined by the number of SRS resource sets.

[0096] <Proposal 1: Option 2: Example 1> For SRS resource sets with the same usage set to "Codebook" or "Non-Codebook" or "Beam Management", If M>1 SRS resource sets with the same usage set to "codebook" or "non-codebook" or "beam management" are provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2, The UE assumes that the first X SRS resource sets with the same usage are configured as symbolType "non-sbfd" (or "sbfd"), and the remaining Y SRS resource sets are configured as symbolType "sbfd" (or "non-sbfd").

[0097] X and Y may be represented by the following formulas (1) and (2).

number

number

[0098] <Proposal 1: Option 2: Example 2> For SRS resource sets with the same usage set to "Codebook" or "Non-Codebook" or "Beam Management", If only one SRS resource set with the same usage set to "Codebook" or "Non-Codebook" or "Beam Management" is provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2, The SRS resource set is configured as symbolType "non-sbfd" (or "sbfd").

[0099] The symbolType may be determined by the specification.

[0100] <Proposal 1: Option 2: Example 3> For SRS resource sets with the same usage set to "Codebook" or "Non-Codebook" or "Beam Management", If M>1 SRS resource sets with the same usage set to "codebook" or "non-codebook" or "beam management" are provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2, The UE assumes that even-numbered (or odd-numbered) SRS resource sets with the same usage are configured as symbolType "non-sbfd" (or "sbfd"), and odd-numbered (or even-numbered) SRS resource sets are configured as symbolType "sbfd" (or "non-sbfd").

[0101] Whether it is an even number or an odd number may be determined by specifications.

[0102] <Proposal 1: Option 3> The symbol type of an SRS resource set is implicitly determined based on other configuration parameters, such as the frequency resource configuration of the SRS resources within the resource set.

[0103] For example, if all SRS resources in an SRS resource set are within a UL enabled PRB, the symbol type of the SRS resource set is "sbfd".

[0104] For example, if at least one SRS resource in an SRS resource set overlaps (extends) with an RB outside the PRBs available in the UL, the symbol type of the SRS resource set is "non-sbfd".

[0105] <Proposal 1: Variation> If SBFD subband locations are configured for a serving cell, the symbol type is always present in the SRS-ResourceSet of that cell (if multiple SRS resource sets with the same usage are provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2).

[0106] <Proposal 1: Summary> According to Proposal 1, the UE can operate properly with respect to SRS.

[0107] <Proposal 2> Proposal 2 provides a technique where only one SRS resource set with the same usage set to "codebook" or "non-codebook" is provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2. Proposal 2 provides the following options 1 and 2.

[0108] <Proposal 2: Option 1> If only one SRS resource set with the same purpose set to "codebook" or "non-codebook" is provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2, the UE expects that the symbolType is not provided (not provided as "sbfd") in the SRS resource set with the purpose set to "codebook" or "non-codebook".

[0109] <Proposal 2: Option 2> If only one SRS resource set with the same usage set to "codebook" or "non-codebook" is provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2, the SRI value applies to the only SRS resource set with usage set to "codebook" or "non-codebook", regardless of the symbol type of the PUSCH transmission.

[0110] <Proposal 2: Option 2: Example 1> Regardless of whether Configuration 1 or Configuration 2, for Type 1 CG PUSCH transmissions in SBFD or non-SBFD symbols, the srs-ResourceIndicator is associated with the most recent transmission on the SRS resource identified by the SRI in the SRS-ResourceSet, regardless of the symbolType.

[0111] If txConfig is set to "codebook", then precodingAndNumberOfLayers corresponds to the SRS resource identified by SRI in the SRS-ResourceSet, regardless of symbolType.

[0112] <Proposal 2: Option 2: Example 2> Regardless of whether Configuration 1 or Configuration 2, for Type 2 CG PUSCH transmissions on SBFD or non-SBFD symbols, or PUSCH transmission opportunities on SBFD or non-SBFD symbols scheduled by DCI Format 0_1 / 0_2 / 0_3, the srs-ResourceIndicator is associated with the most recent transmission of the SRS resource identified by the SRI in the SRS-ResourceSet, regardless of symbolType, where the SRS resource precedes the PDCCH carrying the SRI.

[0113] If txConfig is set to "codebook", then precodingAndNumberOfLayers corresponds to the SRS resource identified by the SRI in SRS-ResourceSet, regardless of symbolType, where the SRS resource precedes the PDCCH carrying the SRI.

[0114] <Proposal 2: Variation> The above describes the case where only one SRS resource set with the same usage is provided, which is set as a "codebook" or a "non-codebook." In a variation, a technique is provided for the case where there is more than one SRS resource set set as a "codebook" or a "non-codebook."

[0115] <Proposal 2: Option 2: Variation 1> If SBFD subband locations are configured for the serving cell, the UE expects either zero or two SRS resource sets with usage set to "codebook" to be provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 (with "symbolType" of "non-sbfd" and "sbfd", respectively).

[0116] <Proposal 2: Option 2: Variation 2> If SBFD subband locations are configured for the serving cell, the UE expects either zero or two SRS resource sets with usage set to "non-codebook" to be provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 (with "symbolType" of "non-sbfd" and "sbfd", respectively).

[0117] <Proposal 2: Summary> According to Proposal 2, the UE can operate appropriately with respect to SRS.

[0118] <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 Whether the UE supports transmission of CG PUSCH occasions with one CG configuration in SBFD symbols and non-SBFD symbols Whether the UE supports reception of SPS PDSCH occasions with one SPS configuration in SBFD symbols and non-SBFD symbols 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.

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

[0120] <Notes> (Combined with options) In the proposals of the present disclosure, which proposals are applied or which options or alternatives are used may be determined by the following: - 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)

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

[0122] (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

[0123] 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: Receiving information aperiodically (triggered by UE or gNB instructions)

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

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

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

[0127] (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

[0128] 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 instruction)

[0129] <Base station configuration> Fig. 15 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. 16) by radio.

[0130] The configurations of the gNB 100 and the UE 200 described below are examples of functions related to the present embodiment. The gNB 100 and the UE 200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to the present embodiment.

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

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

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

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

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

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

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

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

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

[0140] The communication unit may transmit and / or receive signals of any symbol type, including SBFD symbols and non-SBFD symbols.

[0141] The control unit 103 does not need to specify a symbol type in a resource set of a reference signal used for estimating an uplink channel state. The reference signal may be an SRS. The resource set may be an SRS resource set.

[0142] The control unit 103 may determine to provide one resource set of reference signals used for estimating uplink channel conditions, and the control unit 103 may not specify a symbol type in the one resource set to be provided.

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

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

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

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

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

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

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

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

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

[0152] The communication unit may transmit and / or receive signals of any symbol type, including SBFD symbols and non-SBFD symbols.

[0153] When a symbol type is not specified in a resource set of a reference signal used for estimating an uplink channel state, the control unit 203 may determine the symbol type of the resource set based on a specific rule. The reference signal may be an SRS. The resource set may be an SRS resource set.

[0154] The specific rule may be determined by the specification. The control unit 203 may determine the symbol type of the resource set to be the symbol type determined by the specification.

[0155] The specific rule may be the number of resource sets for the same application. The control unit 203 may determine the symbol type of the resource set based on the number of resource sets.

[0156] The specific rule may be based on other configuration parameters, such as the frequency resource configuration of the resources in the resource set, etc. The control unit 203 may (implicitly) determine the symbol type of the resource set based on the other configuration parameters.

[0157] When one resource set of reference signals used for estimating uplink channel conditions is provided, the control unit 203 may determine that the symbol type is not specified in the resource set.

[0158] When one resource set of reference signals used for estimating uplink channel conditions is provided, the control unit 203 may apply the indicator identifying the resources in the resource set to the provided one resource set regardless of the symbol type of the uplink channel. The uplink channel may be a PUSCH.

[0159] The indicator may be associated with the most recent transmission of the resource (resource set or resource of the most recent transmission) identified by the indicator.

[0160] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

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

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

[0163] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of base station 100 and terminal 200 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0164] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the reading, writing, or both reading and writing of data in the memory 1002 and storage 1003.

[0165] 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 baseband signal processing unit 104, call processing unit 105, etc. may be realized by the processor 1001. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0166] The processor 1001 also reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with the programs. 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 401 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via the communication device 1004, for example.

[0167] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

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

[0169] Storage 1003 is a computer-readable recording medium, and may be, 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, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.

[0170] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, 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, or a combination of at least two of these. For example, the above-mentioned transmission / reception antenna 101, amplifier unit 102, transmission / reception unit 103, transmission path interface 106, etc. may be realized by the communication device 1004. The transmission / reception unit 103 may be implemented as a transmission unit 103a and a reception unit 103b that are physically or logically separated.

[0171] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

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

[0174] <Information notification, signaling> The notification of information is not limited to the aspects / 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) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. Furthermore, the RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Furthermore, notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices. Regarding any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically stated in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0175] <Applicable systems> Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA, registered trademark), Global System for Mobile communications (GSM, registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), and Institute of Electrical and Electronics Engineers (IEEE). 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Furthermore, "based on" naturally refers not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

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

[0177] <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 or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0178] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, the operation of "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" and the operation of "a terminal configures a predetermined operation based on the configuration information."

[0179] <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 and output via multiple network nodes.

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

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

[0182] <Variations in form, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0183] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

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

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

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

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

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

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

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

[0191] <Base station> In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0192] 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., an indoor small base station (RRH)). 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 that coverage.

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

[0194] <terminal> In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module" and "Terminal" may be used interchangeably.

[0195] A terminal may be referred to 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0196] <Base station / terminal> The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0197] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the aspects / 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)) or communication of a non-terrestrial network (NTN). In this case, the terminal 20 may be configured to have at least some of the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

[0198] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

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

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

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

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

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

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

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

[0206] <Open format> In the present disclosure, when terms such as "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.

[0207] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio resource can be defined by a combination of units of resources in one or more regions such as, for example, a time region, a frequency region, a spatial region, a code region, and a power region.

[0208] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in the present disclosure may be read as another time unit.

[0209] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0210] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0211] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0212] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of MIMO (Multi-Input Multi-Output), an antenna port, or a combination of at least two of these.

[0213] Furthermore, the resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

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

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

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

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

[0218] 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< / mtrp> < / sbfd>

Claims

1. A communication unit that transmits and / or receives signals of any symbol type of subband non-overlapping full duplex (SBFD) symbols and non-SBFD symbols; a control unit that, when the symbol type is not specified in a resource set of a reference signal used for estimating an uplink channel state, determines the symbol type of the resource set based on a specific rule; A terminal having:

2. The specific rules are determined by a specification, The control unit determines the symbol type of the resource set to a symbol type determined by the specification. The terminal according to claim 1 .

3. The specific rule is the number of resource sets for the same use, The control unit determines the symbol type of the resource set based on the number of the resource sets. The terminal according to claim 1 .

4. A communication unit that transmits and / or receives signals of any symbol type of subband non-overlapping full duplex (SBFD) symbols and non-SBFD symbols; a control unit that determines, when one resource set of reference signals used for estimating an uplink channel state is provided, that the symbol type is not specified in the resource set; A terminal having:

5. A communication unit that transmits and / or receives signals of any symbol type of subband non-overlapping full duplex (SBFD) symbols and non-SBFD symbols; a control unit that applies an indicator that identifies a resource in a resource set to the one provided resource set of reference signals used for estimating an uplink channel state, regardless of the symbol type of the uplink channel; A terminal having:

6. the indicator is associated with a most recent transmission of the resource identified by the indicator; The terminal according to claim 5.

Images