Terminal and communication method

Abstract

To provide a terminal and a communication method for handling CSI-RS resources, assuming that the CSI-RS symbol type for calculating a precoder matches the symbol type of an aperiodic SRS resource set, in non-codebook-based aperiodic SRS transmission when multiple subbands constituting a time division duplex band are available.SOLUTION: A terminal receives the aperiodic CSI-RS and DCI, calculates a precoder for the SRS on the basis of the aperiodic CSI-RS, applies the calculated precoder, and controls the transmission of the SRS aperiodically on the basis of the DCI. When an aperiodic SRS resource set with usage set to nonCodebook is associated with the aperiodic CSI-RS and the symbol type of the aperiodic SRS resource set is the SBFD symbol type, the terminal determines that the symbol type of the associated aperiodic CSI-RS resource is the SBFD symbol type.SELECTED DRAWING: Figure 13

Description

[Technical Field]

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

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

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

[0004] Furthermore, 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.6.0 (2025-03) [Non-patent document 3] 3GPP TS 38.300 V18.5.0 (2025-03) [Non-patent document 4] 3GPP TS 38.331 V18.5.1 (2025-03) [Non-Patent Document 5] 3GPP TR 38.858 V18.2.0 (2024-12) Summary of the Invention

[0006] In the case of a non-codebook-based transmission method, the UE calculates a precoder for the reference signal (SRS: Sounding Reference Signal) to be transmitted to the base station based on the reference signal for channel state information estimation (CSI-RS: Channel-State Information Reference Signal) received from the gNB (base station). The UE then transmits the SRS precoded using the calculated precoder via the uplink. The base station analyzes the SRS received from the UE and collects information on the quality of the uplink wireless channel to perform appropriate resource allocation, beamforming management, interference mitigation, and other management tasks.

[0007] When a UE calculates a precoder for an SRS based on CSI-RS, the channel measurement results may differ between SBFD symbols and non-SBFD symbols. Therefore, in the case of periodic or semi-persistent CSI-RS resources associated with an SRS resource set, such as in non-codebook-based SRS transmission, it has been agreed that the SRS precoder calculation should be based on periodic or semi-persistent CSI-RS occasions of the same symbol type in the SRS resource set. However, there are still open issues regarding aperiodic non-zero power (NZP) CSI-RS associated with aperiodic SRS, and further study is required.

[0008] One aspect of the present disclosure contributes to a terminal and a communication method that handle CSI-RS resources on the assumption that the symbol type of the CSI-RS for calculating a precoder matches the symbol type of the aperiodic SRS resource set in non-codebook-based aperiodic SRS transmission when multiple subbands constituting a time division duplex band are available.

[0009] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives an aperiodic Channel-state information reference signal (CSI-RS) and Downlink Control Information (DCI); and a control unit that calculates a precoder for a Sounding Reference Signal (SRS) based on the aperiodic CSI-RS, applies the calculated precoder, and controls transmission of the SRS aperiodically based on the DCI. When an aperiodic SRS resource set whose usage is set to nonCodebook is associated with the aperiodic CSI-RS and the symbol type of the aperiodic SRS resource set is a subband non-overlapping full duplex (SBFD) symbol type, the control unit determines that the symbol type of the associated aperiodic CSI-RS resource is the SBFD symbol type. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] FIG. 1 is a diagram illustrating an example of TDD settings defined up to Rel-16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7] FIG. 1 illustrates an example of non-Codebook-based uplink transmission. [Figure 8]FIG. 1 is a diagram depicting a description of resources and parameters for non-Codebook-based UL transmission. [Figure 9] FIG. 10 is a diagram illustrating parameters related to CSI-RS resources. [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. 10 is a diagram depicting aperiodic CSI-RS associated with an aperiodic SRS resource set. [Figure 14] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 15] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 16] FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] <CG PUSCH> CG PUSCHs include Type 1 CG PUSCHs and Type 2 CG PUSCHs. In Type 1 CG PUSCHs, only RRC configuration is performed (i.e., not relying on DCI), and transmission parameters are provided by configuredGrantConfig, pusch-Config, and rrc-ConfiguredUplinkGrant. On the other hand, in Type 2 CG PUSCHs, RRC configuration and DCI activation / deactivation are performed, and 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 information on periodic or semi-persistent signals or channels, etc.

[0058] <ul non-codebook based transmission (strp)> This section describes non-codebook-based uplink transmission (single TRP case). As shown in Figure 7, a gNB transmits CSI-RS. The UE is configured with multiple SRS resources (up to the maximum rank), each with one port. The UE calculates the precoder to be used for SRS transmission based on measurements of the associated non-zero power (NZP) CSI-RS resources. When the SRS-ResourceSet upper layer parameter is configured, the UE can configure only one non-zero power (NZP) CSI-RS resource per SRS resource set with usage set to "non-codebook." The UE determines the precoder for the SRS resource 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 status among the multiple different precoded SRSs (selecting one SRS resource per port). The UE determines the SRS resource for PUSCH transmission based on the fed back SRI.

[0059] §6.1.1.2 of Non-Patent Document 2 describes the handling of resources and parameters for non-codebook-based UL transmission (see Figure 8). In a specific configuration, the UE can calculate the precoder to be used for SRS transmission based on measurement of the NZP CSI-RS resource in non-codebook-based transmission, and this configuration is limited to one NZP CSI-RS resource per resource set. In addition, the UE does not update the SRS precoding information if the time interval between aperiodic NZP-CSI-RS and aperiodic SRS transmission is within a certain range. If an aperiodic SRS is configured to be associated with an aperiodic CSI-RS, the associated NZP CSI-RS is present / triggered. The slot of the associated NZP CSI-RS is in the same slot as the triggering DCI. Figure 9 shows an overview of parameters related to CSI-RS resources.

[0060] <mtrp> A multi-TRP scenario for transmitting and receiving signals using two transmission and reception points (TRPs) with different positions will be described. Since Rel.17, TDM M-TRP PUSCH repetition Type A / Type B has been supported to improve reliability. Circular mapping and sequential mapping between two beam (SRI / TPMI) / power control parameter sets (p0, alpha, PL-RS, closed-loop index), as well as repetition repetition, have been supported. The gNB / UE can achieve higher reliability and stability by switching TRPs through time division. In the mTRP configuration, two resource sets can be configured using RRC or DCI.

[0061] Since Rel.18, UL multi-panel simultaneous transmission (STxMP) has been supported. For UL transmission in overlapping time resources, two UE panels are used, and each of the two transmission panels uses a different uplink transmission beam to transmit signals simultaneously. In the case of an ideal backhaul environment, two TRPs can cooperate to schedule the UE's PUSCH or PUCCH. Therefore, using one DCI transmitted by one TRP, PUSCH / PUCCH for two TRPs is scheduled. On the other hand, in the case of a non-ideal backhaul environment, due to the delay of the backhaul, two TRPs cannot cooperate to schedule the UE's PUSCH. Therefore, each TRP schedules the PUSCH independently using multiple DCIs transmitted by each TRP.

[0062] <Study on Duplex Extension towards Rel-19> 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.

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

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

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

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

[0067] Option 1 can be achieved by gNB configuration or scheduling such that all transmit / receive occasions are restricted to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional instructions or rules to determine which transmit / receive occasions are valid within one symbol type and invalid within other symbol types. The frequency resources, power control, and beam / spatial relationships for all transmit / receive occasions may be identical in Option 1 but may be different in Option 2. If different, additional work on the specifications may be required. Option 1 may / may not increase transmit / receive latency if transmit / receive in other symbol types is postponed, and may degrade performance if transmit / receive in other symbol types is dropped. Option 2 may / may not reduce transmit / receive latency and improve coverage.

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

[0069] 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 TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated UL (or semi-static U) symbol: A symbol designated as UL by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated. Flexible (or semi-static F, or flexible) symbol: a symbol designated as flexible by TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated SBFD DL symbol: A symbol indicated as downlink (DL) by the TDD-UL-DL-Configuration Common and / or TDD-UL-DL-Configuration Dedicated, in which the SBFD subband is configured SBFD Flexible (FL) Symbol: A symbol indicated as flexible by the TDD-UL-DL-Configuration Common and / or TDD-UL-DL-Configuration Dedicated, in which SBFD sub-bands are configured.

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

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

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

[0073] To determine the available PRBs in UL / DL, the following options are considered: Option 1: The usable PRBs in the UL are determined as the intersection of the cell-specific UL subbands and the active UL BWPs in the SBFD symbol. The usable PRBs in the DL are determined as the intersection of the cell-specific DL subbands and the active DL BWPs in the SBFD symbol. Option 2: The available PRBs in UL / DL are explicitly configured within the active UL / DL BWP of the SBFD symbol.

[0074] As shown in Figure 10, the DL subband portion and the pure DL symbol portion in the SBFD symbol are PRBs available for use in the downlink. Similarly, the UL subband portion and the pure UL symbol portion in the SBFD symbol are PRBs available for use in the uplink.

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

[0076] For an SBFD-capable UE with UL transmissions and DL receptions spanning SBFD and non-SBFD symbols in different slots (each transmission / reception in a slot having either all SBFD symbols or all non-SBFD symbols), the SBFD-capable UE is provided with one of the following configurations: Configuration 1: Transmission / reception is restricted to either SBFD symbols only or non-SBFD symbols only (see Figure 11). Configuration 2: Transmission / reception can be performed using both SBFD and non-SBFD symbols (see Figure 12).

[0077] The granularity of the settings (for example, per UE, per channel / signal, etc.) has not yet been determined. It is also unclear whether support for setting 2 depends on the UE capability.

[0078] In UL transmission / DL reception for one slot, SBFD symbols and non-SBFD symbols are never mixed in one occasion, and one of the symbol types is always used for each transmission / reception within the slot. However, in UL transmission / DL reception where resources are periodically allocated, such as in repetition spanning multiple slots, an event may occur in which transmission / reception is performed using SBFD symbol types in some slots and non-SBFD symbols in other slots. In such cases, two options are supported: one option (Configuration 1) that enables only one of the symbol types for the entire transmission / reception spanning multiple slots, and another option (Configuration 2) that allows both symbol types to be mixed. Either configuration is set in the terminal.

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

[0080] <Agreement 3> At the 3GPP RAN1#118bis meeting, the following was agreed upon regarding the configuration of separate SRS resources for SBFD and non-SBFD:

[0081] Supports separate SRS configuration for SBFD and non-SBFD symbols. Select one of the following options: Option 1: Support separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols per usage. · The SRS-ResourceSet configured for the SBFD symbol applies only to SRS transmission occasions in the SBFD symbol. For periodic and semi-persistent SRS, SRS transmissions on non-SBFD symbols are dropped. For aperiodic SRS with available slot count, only SBFD symbols are available for SRS transmission. In case of aperiodic SRS where there is no slot count available, it is assumed that the UE is instructed to transmit SRS in the SBFD symbol. · The SRS-ResourceSet configured for non-SBFD symbols applies only to SRS transmission occasions in non-SBFD symbols. For periodic and semi-persistent SRS, SRS transmissions in SBFD symbols are dropped. For aperiodic SRS with available slot count, only non-SBFD symbols are available for SRS transmission. In the case of aperiodic SRS where there is no available slot count, it is assumed that the UE is instructed to transmit SRS in a non-SBFD symbol. · The application is yet to be determined. Option 2: Support separate configurations of SBFD and non-SBFD symbols within the same SRS-Resource. At least freqDomainPosition, freqDomainShift and freqHopping are set separately. -Individual settings for other parameters have not yet been determined. · The application is yet to be determined.

[0082] <Agreement 4> At the 3GPP RAN1#121 meeting, the following was agreed upon:

[0083] For each SRS resource set with usage set to "nonCodebook": If the associated CSI-RS is periodic or semi-persistent, only CSI-RS of the same symbol type as the SRS is used in the SRS precoder calculation.

[0084] However, for an aperiodic NZP CSI-RS associated with an aperiodic SRS, further consideration is required regarding UE behavior.

[0085] <Issues> It was agreed that separate SRS resource sets with usage set to "Codebook," "nonCodebook," or "beamSwitching" can be configured for SBFD and non-SBFD, respectively. As mentioned above, the 3GPP RAN1#121 meeting also agreed that for periodic or semi-persistent CSI-RS resources associated with an SRS resource set with usage set to "nonCodebook," the SRS precoder calculation is based on the periodic or semi-persistent CSI-RS occasion of the same symbol type as the SRS resource set. However, further study is required for UE behavior for aperiodic CSI-RS associated with aperiodic SRS. The underlined parts in Figure 13 were discussed at the 3GPP RAN1#121 meeting, and further study is required.

[0086] Therefore, in the <proposal> of this embodiment, further scalability of UE operation in aperiodic CSI-RS associated with an aperiodic SRS resource set is proposed.

[0087] <Proposal 1> If one aperiodic SRS resource set with usage set to "nonCodebook" is triggered by DCI for SBFD (or vice versa for non-SBFD) and if the aperiodic SRS resource set with usage set to "nonCodebook" is associated with an aperiodic NZP CSI-RS, the UE shall make the following assumptions as per Option 1 to Option 2.

[0088] (Option 1) The UE assumes that the symbols of the associated NZP CSI-RS are of the same symbol type as the aperiodic SRS resource set.

[0089] Note: The determination of the associated NZP CSI-RS is done as per legacy, i.e. in the same slot as the triggering DCI.

[0090] (Option 2) The associated NZP CSI-RS is in the first available slot that is not before the slot that triggers the DCI. A slot is an available slot if the symbol type of the CSI-RS in the slot is the same as the symbol type of the aperiodic SRS resource set. In this case, the UE makes the following assumptions as in Option 2-1 to Option 2-2.

[0091] (Option 2-1) The UE assumes that the last symbol of the associated CSI-RS is earlier (at least X symbols / slots) than the first symbol of the triggered aperiodic SRS resource.

[0092] (Option 2-2) The UE assumes that the determined slot of the associated CSI-RS is earlier (by at least Y slots) than the slot of the triggered aperiodic SRS resource.

[0093] where the X / Y values ​​may be set as follows: The value of X is 0 or a positive integer value (e.g. 1 / 2 / 4 / 8 / 16 / 24 / 32 / 42 / 48, etc.). The value of X may be defined in the specification or set by the RRC. · The value of X may depend on the SCS of the DL BWP.

[0094] (Effects of Proposal 1) As described above, according to Proposal 1, when one aperiodic SRS resource set with usage set to "nonCodebook" is triggered by a DCI and the aperiodic SRS resource set with usage set to "nonCodebook" is associated with an aperiodic NZP CSI-RS, the UE assumes that the symbol types of the aperiodic SRS and the NZP CSI-RS associated with the aperiodic SRS are the same. Therefore, the UE determines the CSI-RS symbol type for calculating the precoder by matching it with the symbol type of the SRS transmission. Therefore, the UE can appropriately determine the symbol type of the associated CSI-RS even in the case of aperiodic SRS. Furthermore, the UE assumes that the last symbol / determined slot of the associated CSI-RS is transmitted earlier than the first symbol / slot of the triggered aperiodic SRS resource. Therefore, the UE can appropriately detect the associated CSI-RS even in the case of aperiodic SRS.

[0095] <Proposal 2> If two aperiodic SRS resource sets with usage set to "nonCodebook" for SBFD and non-SBFD respectively are triggered simultaneously by the same DCI, and both of the two aperiodic SRS resource sets with usage set to "nonCodebook" are associated with an aperiodic NZP CSI-RS, the UE shall act as follows: Alt (alternative) 1 to Alt 2.

[0096] (Alt1) The NZP CSI-RS associated with the two SRS resource sets must be allocated to the same slot. In this case, the UE performs the following operations Alt1-1 to Alt1-2.

[0097] (Alt1-1) The UE determines the CSI-RS associated with each SRS resource set, as in the legacy case, and the UE expects that the symbol type of the determined and associated CSI-RS matches the corresponding SRS resource set. The UE determines the CSI-RS associated with the two SRS resource sets as in the legacy case (i.e., the two associated CSI-RS are placed in the same slot as the triggering DCI). The UE expects the aperiodic NZP CSI-RS associated with an aperiodic SRS resource set for SBFD to be in SBFD symbols and the aperiodic NZP CSI-RS associated with an aperiodic SRS resource set for non-SBFD to be in non-SBFD symbols. ·The principle of this Alt1-1 is the same as option 2.

[0098] (Alt1-2) The UE determines that the NZP CSI-RS associated with the two SRS resource sets is in the first available slot that is not earlier than the slot containing the triggering DCI, where a slot is available if the CSI-RS symbol associated with the SBFD SRS resource set in the slot is in an SBFD symbol and the CSI-RS symbol associated with the non-SBFD SRS resource set in the slot is in a non-SBFD symbol. Compared to option 2 of proposal 1, there are two conditions for available slots:

[0099] (Alt2) The CSI-RS associated with the two SRS resource sets may be located in the same slot or different slots.

[0100] For each SRS resource set, the UE may use Option 2 of Proposal 1 separately to determine the available slots for the corresponding associated CSI-RS.

[0101] (Alt1~Alt2 variations) Restrictions according to option 2-1 / option 2-2 can be applied to Alt1-2 and Alt2.

[0102] (Variation of Proposal 2) The UE shall not assume that two SRS resource sets, one SBFD and one non-SBFD with usage set to "nonCodebook", are triggered simultaneously by the same DCI.

[0103] (Effects of Proposal 2) As described above, according to Proposal 2, when two aperiodic SRS resource sets, each for SBFD and non-SBFD, with usage set to "nonCodebook," are simultaneously triggered by the same DCI and both aperiodic SRS resource sets with usage set to "nonCodebook" are associated with an aperiodic NZP CSI-RS, the UE determines the CSI-RS associated with the two SRS resource sets and expects the symbol type of the CSI-RS to match the corresponding SRS resource set. This allows the UE to make an appropriate decision on the symbol type of the CSI-RS even in the case of aperiodic SRS. Furthermore, the UE determines that the symbol of the associated NZP CSI-RS is in the first slot after the triggering DCI and determines that a slot with the symbol type of the CSI-RS associated with the SRS resource set matches can be used. This allows the UE to properly detect the associated CSI-RS even in the case of aperiodic SRS.

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

[0105] In Proposals 1-2 of this disclosure, multiple options and alternatives may be combined into a single option / alternative. Also, throughout the proposals, the RS (reference signal) being measured will be the QCL source RS in the active / indicated TCI state.

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

[0107] 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)

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

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

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

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

[0112] 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)

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

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

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

[0116] <Base station configuration> Fig. 14 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. 15) wirelessly.

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

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

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

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

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

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

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

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

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

[0126] <Device configuration> 15 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 by radio, for example.

[0127] The transmitter 202 transmits the UL signal to the gNB 100. For example, the transmitter 202 transmits the UL signal under the control of the controller 203.

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

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

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

[0131] For example, the receiving unit 201 may receive physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), and other signals from the NW or gNB100.

[0132] For example, the receiving unit 201 may receive values ​​related to SRS-ResourceConfigCLI, RSSI-ResourceConfigCLI, CSI-ReportConfig, and CSI-ResourceConfig as RRC (Radio Resource Control) signaling from the NW or gNB100.

[0133] For example, the receiver 201 may monitor and decode the target DCI based on information indicating a search space associated with the DCI and information indicating a control resource set (CORESET) in response to an instruction from the controller 203.

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

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

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

[0137] For example, the control unit 203 may perform control based on DCI and RRC signaling.

[0138] For example, the control unit 203 may monitor physical downlink control channel (PDCCH) candidates based on information indicating a search space associated with the DCI and information indicating a control resource set (CORESET), and may instruct the receiving unit 201 to decode the target DCI.

[0139] For example, the control unit 203 may perform CLI measurement and CLI reporting based on values ​​related to SRS-ResourceConfigCLI, RSSI-ResourceConfigCLI, CSI-ReportConfig, and CSI-ResourceConfig, and SBFD or non-SBFD symbol type, etc.

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

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

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

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

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

[0145] Furthermore, the 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 referred to as, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)) or communication of a non-terrestrial network (NTN). In this case, the UE 200 may be configured to have at least some of the functions of the gNB 100 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (e.g., "sidelink") or terms corresponding to NTN (e.g., feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

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

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

[0148] <Hardware configuration, etc.> 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.

[0149] 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. Figure 16 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 gNB 100 and UE 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0150] 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 the gNB100 and the UE200 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.

[0151] Each function in gNB100 and UE200 is realized by loading specified software (programs) onto hardware such as processor 1001, memory 1002, etc., so that processor 1001 performs calculations, controls communication by communication device 1004, and controls reading, writing, or both reading and writing of data in memory 1002 and storage 1003.

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

[0153] Furthermore, the processor 1001 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 UE 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via, for example, the communication device 1004.

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

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

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

[0157] The communication device 1004 is hardware (transmitting / receiving 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, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, or a transmission path interface may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.

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

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

[0160] Furthermore, the gNB 100 and the UE 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0161] <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 gNB100 and the UE200) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the gNB100 or the UE200). 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 relating to) the value of the any information may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

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

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

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

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

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

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

[0168] <Radio resource definition> The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

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

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

[0171] 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 in one carrier for the UE 200, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

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

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

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

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

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

[0177] One aspect of the present disclosure is useful for a terminal and a communication method. [Explanation of symbols]

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

Claims

1. a receiver for receiving a non-periodic Channel-state information reference signal (CSI-RS) and Downlink Control Information (DCI); a control unit that calculates a precoder for a Sounding Reference Signal (SRS) based on the aperiodic CSI-RS, applies the calculated precoder, and aperiodically controls transmission of the SRS based on the DCI; Equipped with the control unit determines, when an aperiodic SRS resource set whose usage is set to "nonCodebook" is associated with the aperiodic CSI-RS and the symbol type of the aperiodic SRS resource set is a subband non-overlapping full duplex (SBFD) symbol type, that the symbol type of the associated aperiodic CSI-RS resource is an SBFD symbol type. Terminal.

2. the controller determines that the symbol type of the associated aperiodic CSI-RS resource is a non-SBFD symbol type if the symbol type of the aperiodic SRS resource set is not a subband non-overlapping full duplex (non-SBFD) symbol type. The terminal of claim 1.

3. the control unit assumes that the last symbol of the associated aperiodic CSI-RS precedes in time the first symbol of the aperiodic SRS resource. The terminal of claim 1.

4. The control unit assumes that a slot in which the associated aperiodic CSI-RS is arranged precedes in time a slot in which the aperiodic SRS resource is arranged. The terminal of claim 1.

5. The device is receiving a non-periodic Channel-state information reference signal (CSI-RS) and Downlink Control Information (DCI); Calculating a precoder for a Sounding Reference Signal (SRS) based on the aperiodic CSI-RS, applying the calculated precoder, and aperiodic controlling transmission of the SRS based on the DCI; If an aperiodic SRS resource set with usage set to nonCodebook is associated with the aperiodic CSI-RS and the symbol type of the aperiodic SRS resource set is a subband non-overlapping full duplex (SBFD) symbol type, determine that the symbol type of the associated aperiodic CSI-RS resource is an SBFD symbol type. Communication method.

Images