Terminal and communication method

Abstract

To provide a terminal and a communication method for measuring the received power of a reference signal which is received in a physical layer using symbols of a symbol type under predetermined conditions in order to detect crosslink interference (CLI) caused by transmissions by other user devices.SOLUTION: A terminal includes a communication unit that transmits and receives signals whose transmission and / or reception symbol type is either a subband non-overlapping full duplex (SBFD) symbol type or a non-SBFD symbol type, and a control unit that measures the received power of a reference signal which is received in a physical layer in order to detect crosslink interference (CLI) caused by transmissions by other user devices, and the control unit measures the received power of the reference signal using symbols of a symbol type under predetermined conditions.SELECTED DRAWING: Figure 9

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 multiple access (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 to UL transmission and DL reception using SBFD symbols and non-SBFD symbols are being considered, and technical requirements for clarifying SBFD operation are being examined (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] “Revised WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-241614, 3GPP TSG RAN Meeting #104, 3GPP, June 17-20, 2024 [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) [Non-patent document 6] 3GPP TR 38.213 V18.3.0 (2024-06) [Non-Patent Document 7] 3GPP TR 38.215 V18.4.0 (2024-12) Summary of the Invention

[0006] Non-Patent Document 5 summarizes the technical requirements for SBFD operation and summarizes the points that need to be considered for the implementation of Release-19. The updated WID (Non-Patent Document 1) lists as one of the issues that dynamic TDD or flexible TDD operation faces the adverse effect of cross-link interference (CLI) on PUSCH (Physical Uplink Shared Channel) performance and measurement accuracy. CLI is interference that occurs between different cells, base stations, or terminals, and occurs, for example, when one base station or terminal is transmitting while another base station or terminal is receiving in the same frequency band.

[0007] The crosslink interference described above can occur in UL transmission and DL reception using SBFD symbols. On the other hand, in a quasi-static SBFD scenario, there is no end-to-end CLI on non-SBFD symbols. However, crosslink interference can occur in UL transmission and DL reception using non-SBFD symbols using dynamic TDD. Therefore, whether to support CLI measurement on non-SBFD symbols remains an open issue and requires further study.

[0008] One aspect of the present disclosure provides a terminal and a communication method for measuring the received power of a reference signal received at a physical layer using symbols of a symbol type under predetermined conditions in order to detect crosslink interference (CLI) caused by transmissions by other user equipment.

[0009] A terminal according to one embodiment of the present disclosure includes a communication unit that transmits and receives signals whose transmission and / or reception symbol type is either a subband non-overlapping full duplex (SBFD) symbol type or a non-SBFD symbol type, and a control unit that measures the received power of a reference signal received in a physical layer in order to detect cross link interference (CLI) caused by transmission by other user equipment, and the control unit measures the received power of the reference signal using symbols of a symbol type that satisfies a predetermined condition. [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 shows excerpts of the agreements reached at the RAN1#118bis and RAN1#119 meetings. [Figure 8] FIG. 1 shows a discussion proposal (excerpt) from the RAN1#120bis meeting. [Figure 9] FIG. 10 is a flowchart showing an example of the operation of a terminal in option 2-1 or option 2-2. [Figure 10] FIG. 10 is a flowchart showing an example of the operation of the terminal in option 2-3. [Figure 11] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 12] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 13] 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 becomes 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, some of the DL resources of the TDD band are configured as 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 in the TDD time unit, or a duplexing scheme in which all two sub-bands are overlapped.

[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] <Crosslink Interference> Cross-Link Interference (CLI) is interference that occurs between uplink (UL) and downlink (DL) communications. In SBFD operation, DL and UL partially overlap in the time domain, so solutions are required to manage cross-link interference between base stations and between UEs. Solutions are also required for intra-subband CLI and inter-subband CLI.

[0058] The SRS-RSRP (Sounding Reference Signal Received Power) is defined as the linear average of the power components (unit: W) in the resource elements carrying the sounding reference signal (SRS). The SRS-RSRP is measured for a set of resource elements within the measurement frequency bandwidth at a set measurement time occasion (see §5.1.19 of Non-Patent Document 7). For example, the SRS-RSRP can be used to measure the interference power from a specific UE.

[0059] The SRS-ResourceConfigCLI configuration configures information elements (IEs) such as the subcarrier spacing (srs-SCS), the index of the reference serving cell to which the refBWP belongs (refServCellindex), and the ID of the DL BWP (refBWP) used to derive the reference point of the SRS resource (see §6.3.2 of 3GPP TS 36.3.2).

[0060] The Cross-Link Interference Received Signal Strength Indicator (CLI-RSSI) is defined as the linear average of the total received power (unit: [W]) observed within the configured measurement bandwidth, the configured OFDM symbols, and the configured measurement time resource. This power includes all signal sources, such as signals from co-channel serving and non-serving cells, adjacent channel interference, and thermal noise (see §5.1.20 of Non-Patent Document 7). For example, CLI-RSSI can be used to measure the interference power in the total received power in a certain band.

[0061] The RSSI-ResourceConfigCLI configuration configures information elements (IEs) such as the reference subcarrier spacing for CLI-RSSI measurement (rssi-SCS), the start PRB index of the measurement bandwidth (startPRB), the allowable size of the measurement bandwidth (nrofPRBs), the OFDM symbol position of the CLI-RSSI resource within the slot (startPosition), the RSSI that the UE measures within the slot configured for CLI-RSSI measurement in the range from startPosition to startPosition+nrofSymbols-1 (nrofSymbols), the periodicity and slot offset of the CLI-RSSI resource (rssi-PeriodicityAndOffset), and the index of the reference serving cell (refServCellIndex) (see §6.3.2 of Non-Patent Document 4).

[0062] <csi-report> §5.2 of Non-Patent Document 4 describes an overview of how a UE reports channel state information (CSI) to a gNB. To enable the UE to correctly report the channel state to the gNB, CSI-ResourceConfig and CSI-ReportConfig are used to define the reference signal resources to be measured, as well as the reporting content, reporting timing, and reporting destination. The UE is configured using the following parameters. · Settings for reporting (CSI-ReportConfig) · Settings for resources used for measurement (CSI-ResourceConfig) · Settings for trigger conditions by DCI (TriggerStateList)

[0063] CSI-ReportConfig is used to configure periodic or semi-persistent reports transmitted on PUCCH in the cell containing CSI-ReportConfig, and also to configure semi-persistent or aperiodic reports transmitted on PUSCH triggered by DCI received in the same cell containing CSI-ReportConfig. In this case, the cell where the report is transmitted is determined by the received DCI. Also, in the resource configuration by CSI-ResourceConfig, the reference signal resources used in CSI-ResourceConfig, the timing of the resources (aperiodic / periodic / semi-persistent), etc. are specified.

[0064] <Objective of the Work Item (WID) on the Evolution of NR Duplex Modes in Rel-19> In Rel-18, studies were conducted to enable simultaneous downlink and uplink (full duplex, more specifically, subband non-overlapping full duplex) on the gNB side within the conventional TDD band. Regarding SBFD, TR 38.858 summarizes the impact on specifications, performance evaluation results, implementability, impact on radio frequency (RF) requirements, and impact on specifications regarding dynamic / flexible TDD extensions, performance evaluation results, etc. According to the conclusions of TR 38.858, it is desirable to specify in Rel-19 SBFD operation on the gNB side within TDD carriers, CLI processing methods between gNBs, CLI processing methods between UEs, and RF requirements for SBFD operation at the gNB.

[0065] In Non-Patent Document 1, the 3GPP work item (WID) on the evolution of NR duplex operation has been updated. The objectives of the study for Rel-19 are, for example, as follows:

[0066] -Specify extensions for CLI (Cross Link Interference) processing [RAN1, RAN2, RAN3, RAN4] Includes content regarding UL resource muting for PUSCH [RAN1, RAN2, RAN4]: Semi-persistent indication / decision of UL resource muting for PUSCH for up to 2 symbols in the time domain based on comb-2 (comb-like mapping pattern) for both DFT-S-OFDM and CP-OFDM in each allocated PRB PUSCH resource mapping around muted REs (resource elements), i.e., rate matching Determining UCI resources on symbols containing muted REs Includes UE-to-UE CLI measurements and reporting at L1 level (physical layer) based on the existing CSI framework [RAN1, RAN2, RAN4]: Setting / determining periodic, quasi-static or aperiodic measurement resources (sets), i.e. SRS-RSRP resources or CLI-RSSI resources, as well as 'type D' QCL assumptions for CLI measurement resources At least non-periodic reporting New reporting quantities, e.g., L1-SRS-RSRP, L1-CLI-RSSI, and / or measurement resource index -UCI bit generation Priority rules for multiple CSI reports Accuracy requirements for CLI measurement Note: No special optimizations for dynamic / flexible TDD are assumed.

[0067] In this embodiment, interference occurring between a downlink (DL) communication of a UE and an uplink (UL) communication of another UE is measured by UE-to-UE CLI measurement. In this UE-to-UE CLI measurement, the CSI framework is used as a base, and changes to the priority rules for multiple CSI reports are considered.

[0068] <Agreement> At the 3GPP RAN1#118bis and #119 meetings, it was agreed to define the SRS-RSRP measurement resource set and the CLI-RSSI measurement resource set as follows (see FIG. 7).

[0069] Agreement (3GPP RAN1#118bis) The previous agreement is updated as follows: Agreement Extend CSI-ResourceConfig to include two CLI measurement resource set lists for L3-based SRS-RSRP measurements and CLI-RSSI measurements, based on SRS-ResourceConfigCLI and rssi-ResourceConfigCLI defined in Rel-16. The resourceType in these two new CLI measurement resource set lists can be set to periodic, semi-persistent, or aperiodic. As in the current specification, the number of periodic / quasi-static CLI measurement resource sets included in one CSI-ResourceConfig is limited to 1. NOTE: There is no need to define new uses for SRS resource sets.

[0070] Agreement (3GPP RAN1#119) We define a new information element (IE) SRS-RSRP-MeasurementResourceSet that contains a set of SRS-RSRP measurement resources (SRS-RSRP-MeasurementResource) for L1-based SRS-RSRP measurements. - Configuration of slot offset between the slot containing the DCI that triggers the aperiodic SRS-RSRP resource set and the slot where the SRS-RSRP resource set is measured (already agreed in RAN1#118bis) -Topics for Further Study (FFS): Other Settings SRS-RSRP-MeasurementResource contains the following parameters: - Traditional SRS resource information elements -Topics for further study (FFS): Other parameters

[0071] Agreement (3GPP RAN1#119) Define a new information element (IE) CLI-RSSI-MeasurementResourceSet that contains a set of CLI-RSSI measurement resources (CLI-RSSI-MeasurementResource) for L1-based CLI-RSSI measurements. - Configuration of slot offset between the slot containing the DCI that triggers the set of aperiodic CLI-RSSI resources and the slot in which the CLI-RSSI resource set is measured (already agreed in RAN1#118bis) CLI-RSSI-MeasurementResource contains the following parameters: -CLI-RSSI Measurement Resource ID - PRB start index -Number of PRBs -Start symbol of CLI-RSSI resource within slot -Number of CLI-RSSI resource symbols in a slot -CLI-RSSI resource period and slot offset -Topics for further study (FFS): Other parameters

[0072] As mentioned above, CLI measurement resources are roughly divided into SRS-RSRP and CLI-RSSI measurement resources. SRS-RSRP is used to measure interference power from a specific UE, and CLI-RSSI is used to measure interference power in terms of the total amount of received power in a certain band at a certain time.

[0073] <Discussion at the meeting> At the 3GPP RAN1#120bis meeting, there was a discussion about whether to support L1 CLI measurements on non-SBFD symbols. The proposal that was the basis for the discussion was as follows (see Figure 8):

[0074] [Proposals that served as the basis for discussion] (Alt.1) The valid symbol types for CSI derivation configured in CSI-ReportConfig do not apply to L1 UE-to-UE CLI measurements and reports. · The UE shall perform L1 Inter-UE CLI measurements only on SBFD symbols. (Alt.2) The valid symbol types for CSI derivation configured in CSI-ReportConfig apply to L1 UE-to-UE CLI measurements and reporting. · The UE shall perform L1 UE-to-UE CLI measurements based on the valid symbol types configured in CSI-ReportConfig. · Note: L1 CLI measurements are supported by both symbol types: SBFD and non-SBFD symbols.

[0075] The proposal (Alt.1) on which this discussion is based does not support CLI measurements on non-SBFD symbols. Also, the valid symbol types for CSI derivation configured in CSI-ReportConfig do not apply to CLI measurements, whether they are SBFD symbols or non-SBFD symbols. This (Alt.1) supports CLI measurements on SBFD symbols only.

[0076] In addition, the proposal (Alt.2) on which the discussion was based supports CLI measurements using non-SBFD symbols, and the valid symbol types for CSI derivation configured in CSI-ReportConfig also apply to CLI measurements.

[0077] <Problem analysis> At the meeting mentioned above, there was a discussion on whether to support / perform L1 CLI measurements on non-SBFD symbols. Based on this discussion, there are opinions that L1 CLI measurements should be supported / performed on non-SBFD symbols, and opinions that they should not be supported / performed.

[0078] (Motivation for not supporting / performing L1 CLI measurements on non-SBFD symbols) In a quasi-static SBFD scenario, there is no UE-to-UE CLI on non-SBFD symbols, so L1 CLI measurements on non-SBFD symbols are not necessary. Furthermore, this measurement resource may cause overhead. Therefore, in a quasi-static SBFD scenario, it is preferable not to support / perform L1 CLI measurements on non-SBFD symbols. This is the motivation for (Alt. 1) of the proposal that forms the basis of the above discussion.

[0079] Motivation for supporting / performing L1 CLI measurements on non-SBFD symbols In dynamic TDD scenarios, since CLI exists between UEs, it is desirable that the L1 CLI measurement and reporting function should not be limited to SBFD scenarios only. Therefore, it is appropriate to support L1 CLI measurement on non-SBFD symbols as well. This point is the motivation for (Alt.2) of the proposal that is the basis of the above discussion.

[0080] Therefore, in this embodiment, a proposal for a UE to decide whether to perform L1 CLI measurements using non-SBFD symbols is considered.

[0081] <Proposal Summary> The outline of the proposal is as follows (details will be given later):

[0082] (Option 1) The UE performs L1 UE-to-UE CLI measurements only on SBFD symbols.

[0083] This option 1 is the same as Alt. 1 of the proposal that served as the basis for discussion at the RAN1#120bis meeting.

[0084] (Option 2) The UE shall perform L1 CLI measurements with both symbol types, SBFD and non-SBFD symbols.

[0085] (Option 2-1) The UE performs L1 UE-to-UE CLI measurement and reporting with valid symbol types for CSI derivation configured in CSI-ReportConfig.

[0086] This option 2-1 is the same as Alt.2 of the proposal that served as the basis for discussion at the RAN1#120bis meeting.

[0087] (Option 2-2) The UE performs L1 UE-to-UE CLI measurements and reporting regardless of the symbol types available for CSI derivation configured in CSI-ReportConfig.

[0088] (Option 2-3) The UE determines whether to apply the valid symbol type for CSI derivation configured in CSI-ReportConfig depending on whether it is configured to monitor the SFI.

[0089] (Option 3) The UE shall perform L1 CLI measurements with both symbol types: SBFD symbols and non-SBFD flexible symbols.

[0090] (Option 3-1) The UE performs L1 UE-to-UE CLI measurement and reporting with valid symbol types for CSI derivation configured in CSI-ReportConfig.

[0091] (Option 3-2) The UE performs L1 UE-to-UE CLI measurements and reporting regardless of the symbol types available for CSI derivation configured in CSI-ReportConfig.

[0092] (Option 3-3) The UE determines whether to apply the valid symbol type for CSI derivation configured in CSI-ReportConfig depending on whether it is configured to monitor the SFI.

[0093] <Proposal> As proposals in this embodiment, the following options 1 to 3 will be explained in order.

[0094] (Option 1) The UE performs L1 UE-to-UE CLI measurements only on SBFD symbols.

[0095] This option 1 is the same as (Alt.1) in the proposal that was the basis for discussion at the RAN1#120bis meeting. That is, whether the valid symbol type for CSI derivation configured in CSI-ReportConfig is SBFD symbols or non-SBFD symbols, it does not apply to CLI measurements. In option 1, UEs perform L1 UE-UE CLI measurements only on SBFD symbols.

[0096] (Option 2) The UE shall perform L1 CLI measurements with both symbol types, SBFD and non-SBFD symbols.

[0097] In Option 2, the UE performs L1 CLI measurement and reporting using both SBFD symbols and non-SBFD symbols according to the following Option 2-1 to Option 2-3.

[0098] (Option 2-1) The UE performs L1 UE-to-UE CLI measurement and reporting with valid symbol types for CSI derivation configured in CSI-ReportConfig.

[0099] This option 2-1 is the same as Alt. 2 of the proposal that served as the basis for discussion at the RAN1#120bis meeting, i.e., the UE performs L1 UE-to-UE CLI measurements and reporting using the valid symbol types for CSI derivation configured in CSI-ReportConfig.

[0100] (Option 2-2) The UE performs L1 UE-to-UE CLI measurements and reporting regardless of the valid symbol types configured in CSI-ReportConfig.

[0101] In this option 2-2, the UE further performs L1 CLI derivation according to the symbol type as shown in the following options 2-2A to 2-2B.

[0102] (Option 2-2A) The UE determines one symbol type to be used for L1 CLI derivation based on the following Alt-1 to Alt-2.

[0103] (Alt-1) The UE determines the symbol type to be used for L1 CLI derivation based on whether SBFD is configured in the cell, and determines the symbol type of L1 measurements to be used for L1 CLI derivation based on the following Alt-1-1 to Alt-1-2.

[0104] (Alt-1-1) If the UE is configured with SBFD subband locations, it shall perform L1 CLI derivation using L1 measurements on SBFD symbols only.

[0105] (Alt-1-1 variation) The UE performs L1 CLI measurements only on SBFD symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on SBFD symbols.

[0106] (Alt-1-2) If the UE is not configured with SBFD subband locations, it performs L1 CLI derivation using L1 measurements on non-SBFD symbols only.

[0107] (Alt-1-2 variation) The UE performs L1 CLI measurements only on non-SBFD symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurements themselves are performed only on non-SBFD symbols.

[0108] (Alt-2) The UE determines the symbol type to be used for L1 CLI derivation based on whether the cell is configured to monitor the SFI (Slot Format Indicator), and determines the L1 measurement symbol type to be used for L1 CLI derivation based on the following Alt-2-1 to Alt-2-2.

[0109] The SFI is an indicator for indicating the transmission / reception direction (U: uplink (UL) / D: downlink (DL) / F: flexible) of a symbol in a slot, and is set in dynamic TDD (see, for example, Figure 6A). Flexible symbols can be dynamically changed between uplink (UL) and downlink (DL) and can include a guard period for DL / UL switching.

[0110] (Alt-2-1) If the UE is not configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI derivation using L1 measurements of only SBFD symbols.

[0111] (Alt-2-1 variation) The UE performs L1 CLI measurements only on SBFD symbols, i.e. the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on SBFD symbols.

[0112] (Alt-2-2) If the UE is configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI derivation using L1 measurements of non-SBFD symbols only.

[0113] In this Alt-2-2, the UE is configured to monitor the SFI when dynamic TDD is used. When dynamic TDD is used, inter-UE CLI may occur even in non-SBFD symbols. Therefore, the UE performs L1 CLI derivation using non-SBFD symbols.

[0114] (Alt-2-2 variation) The UE performs L1 CLI measurements only on non-SBFD symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on non-SBFD symbols.

[0115] (Option 2-2B) The UE may perform L1 CLI derivation using both symbol types, SBFD symbols or non-SBFD symbols. The UE may perform L1 CLI measurements using SBFD symbols or non-SBFD symbols.

[0116] (Option 2-3) The UE determines whether to apply the valid symbol type for CSI derivation configured in CSI-ReportConfig depending on whether it is configured to monitor the SFI.

[0117] (Option 2-3-1) If the UE is not configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI measurements and reporting using valid symbol types configured in CSI-ReportConfig.

[0118] If the UE is not configured to monitor the SFI, then it may apply option 2-1 to perform L1 UE-to-UE CLI measurements and reporting since dynamic TDD is not being used.

[0119] (Option 2-3-2) In cases other than the above-mentioned option 2-3-1, the UE performs L1 CLI measurements and reporting without using a valid symbol type configured in CSI-ReportConfig. In this option 2-3-2, the UE may perform L1 UE-UE CLI measurements and reporting by applying the above-mentioned option 2-2.

[0120] (Variation of Option 2) If the UE decides to apply a valid symbol type (e.g., option 2-1 / option 2-3) and CSI-ReportConfig is not configured: Option 2-2A or Option 2-2B may be applied. In addition to Option 2-2A or Option 2-2B, the UE may use a "default symbol type" for L1 CLI derivation. This default symbol type may be defined in the specification and may be an SBFD symbol or a non-SBFD symbol configured per DL BWP / serving cell.

[0121] (Example of Option 2) 9 is a flowchart showing an example of UE operation in Option 2-1 or Option 2-2. To facilitate understanding of the relationship between the options, a determination for each option is described, but only the necessary parts of the determination for each option may be performed. The UE performs L1 CLI measurement or derivation by processing the flowchart shown in FIG. 9.

[0122] In S1 (step 1), the receiver of the UE receives values ​​related to CSI-ReportConfig and DCI from the network (NW) or the base station (gNB).

[0123] In S2, the control unit of the UE determines "whether to perform L1 inter-UE CLI measurement using a valid symbol type for CSI derivation configured in CSI-ReportConfig" based on the received configuration information or pre-configured information. If the control unit determines in S2 to perform L1 inter-UE CLI measurement using a valid symbol type for CSI derivation configured in CSI-ReportConfig (S2: Yes), the flow proceeds to S3. On the other hand, if the control unit determines in S2 to perform L1 inter-UE CLI measurement without using a valid symbol type for CSI derivation configured in CSI-ReportConfig (S2: No), the flow proceeds to S4.

[0124] In S3, the UE control unit performs L1 inter-UE CLI measurement and reporting using the symbol type valid for CSI derivation configured in CSI-ReportConfig (option 2-1).

[0125] In S4, the control unit of the UE determines "whether to perform L1-CLI derivation using one symbol type" based on the received configuration information or pre-configured information. If the control unit determines in S4 to perform L1-CLI derivation using one symbol type (S4: Yes), the flow proceeds to S6. On the other hand, if the control unit determines in S4 to perform L1-CLI derivation regardless of one symbol type (S4: No), the flow proceeds to S5.

[0126] In S5, the UE control unit performs L1 CLI measurement and reporting using (either) symbol type of SBFD symbol or non-SBFD symbol (option 2-2B).

[0127] In S6, the control unit of the UE determines "whether to determine the symbol type of the L1 measurements used for L1-CLI derivation based on whether SBFD is configured in the cell" based on the received configuration information or pre-configured information. If the control unit determines in S6 that the symbol type of the L1 measurements used for L1-CLI derivation should be determined based on whether SBFD is configured in the cell (S6: Yes), the flow proceeds to S7. On the other hand, if the control unit determines in S6 that the symbol type of the L1 measurements used for L1-CLI derivation should be determined regardless of whether SBFD is configured in the cell (S6: No), the flow proceeds to S8.

[0128] In S7, the control unit of the UE determines whether the UE is configured at the SBFD subband position. If the control unit determines in S7 that the UE is configured at the SBFD subband position (S7: Yes), the flow proceeds to S9. On the other hand, if the control unit determines in S7 that the UE is not configured at the SBFD subband position (S7: No), the flow proceeds to S10.

[0129] In S8, the control unit of the UE determines whether the UE is configured to monitor the SFI in the cell. If the control unit determines in S8 that the UE is configured to monitor the SFI (S8: Yes), the flow proceeds to S12. On the other hand, if the control unit determines in S8 that the UE is not configured to monitor the SFI (S8: No), the flow proceeds to S11.

[0130] At S9, the UE controller performs L1 CLI derivation using L1 measurements of only SBFD symbols.

[0131] At S10, the UE controller performs L1 CLI derivation using L1 measurements of only non-SBFD symbols.

[0132] At S11, the UE controller performs L1 CLI derivation using L1 measurements of only SBFD symbols.

[0133] At S12, the UE controller performs L1 CLI derivation using L1 measurements of only non-SBFD symbols.

[0134] 10 is a flowchart showing an example of the operation of the UE in option 2-3. The UE performs L1 CLI derivation through the processing of the flowchart shown in FIG.

[0135] Note that the processes at S1, S4, S5, S6, S7, S9, S10, and S12 in FIG. 9 are the same as the processes at S21, S24, S25, S26, S27, S28, S29, and S30 in FIG. 10, respectively, and therefore will not be described.

[0136] In S22, the control unit of the UE determines "whether the UE is configured to monitor the SFI in DCI format 2_0" of the received DCI. If the control unit determines in S22 that the UE is configured to monitor the SFI in DCI format 2_0 (S22: Yes), the flow proceeds to S24. On the other hand, if the control unit determines in S22 that the UE is not configured to monitor the SFI in DCI format 2_0 (S22: No), the flow proceeds to S23.

[0137] In S23, the control unit of the UE performs L1 inter-UE CLI measurement and reporting using the symbol type valid for CSI derivation configured in CSI-ReportConfig (option 2-3-1).

[0138] (Option 3) The UE shall perform L1 CLI measurements with both symbol types: SBFD symbols and non-SBFD flexible symbols.

[0139] This option 3 is a variation of option 2, and differs in that "non-SBFD symbols" in option 2 is changed to "non-SBFD flexible symbols." In option 3, the UE performs L1 CLI measurements and reporting using both SBFD symbols and non-SBFD flexible symbols according to the following options 3-1 to 3-3.

[0140] (Option 3-1) The UE performs L1 UE-to-UE CLI measurement and reporting with valid symbol types for CSI derivation configured in CSI-ReportConfig.

[0141] If the valid symbol type for CSI derivation configured in CSI-ReportConfig is "SBFD", the reported L1 CLI measurement results are derived by L1 CLI measurement resources on SBFD symbols.

[0142] If the valid symbol type for CSI derivation configured in CSI-ReportConfig is "non-SBFD", the reported L1 CLI measurement results are derived by L1 CLI measurement resources on non-SBFD flexible symbols.

[0143] (Option 3-2) The UE performs L1 UE-to-UE CLI measurements and reporting regardless of the symbol types available for CSI derivation configured in CSI-ReportConfig.

[0144] In this option 3-2, the UE further performs L1 CLI derivation according to the symbol type as shown in the following options 3-2A to 3-2B.

[0145] (Option 3-2A) The UE determines one symbol type to be used for L1 CLI derivation based on the following Alt-1 to Alt-2.

[0146] (Alt-1) The UE determines the symbol type to be used for L1 CLI derivation based on whether SBFD is configured in the cell, and determines the symbol type of L1 measurements to be used for L1 CLI derivation based on the following Alt-1-1 to Alt-1-2.

[0147] (Alt-1-1) If the UE is configured with SBFD subband locations, it shall perform L1 CLI derivation using L1 measurements on SBFD symbols only.

[0148] (Alt-1-1 variation) The UE performs L1 CLI measurements only on SBFD symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on SBFD symbols.

[0149] (Alt-1-2) If the UE is not configured with SBFD subband locations, it shall perform L1 CLI derivation using L1 measurements of only non-SBFD flexible symbols.

[0150] (Alt-1-2 variation) The UE performs L1 CLI measurements only on non-SBFD flexible symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurements themselves are performed only on non-SBFD flexible symbols.

[0151] (Alt-2) The UE determines the symbol type to be used for L1 CLI derivation based on whether the cell is configured to monitor the SFI (Slot Format Indicator), and determines the L1 measurement symbol type to be used for L1 CLI derivation based on the following Alt-2-1 to Alt-2-2.

[0152] (Alt-2-1) If the UE is not configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI derivation using L1 measurements of only SBFD symbols.

[0153] (Alt-2-1 variation) The UE performs L1 CLI measurements only on SBFD symbols, i.e. the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on SBFD symbols.

[0154] (Alt-2-2) If the UE is configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI derivation using L1 measurements of non-SBFD flexible symbols only.

[0155] In Alt-2-2, the UE is configured to monitor SFI when dynamic TDD is used. When dynamic TDD is used, inter-UE CLI may occur even with non-SBFD flexible symbols. Therefore, the UE performs L1 CLI derivation using non-SBFD flexible symbols.

[0156] (Alt-2-2 variation) The UE performs L1 CLI measurements only on non-SBFD flexible symbols, i.e., the UE assumes that not only the L1 CLI derivation but also the L1 CLI measurement itself is performed only on non-SBFD flexible symbols.

[0157] (Option 3-2B) The UE may perform L1 CLI derivation using both symbol types, SBFD symbols or non-SBFD symbols. The UE may perform L1 CLI measurements using SBFD symbols or non-SBFD flexible symbols.

[0158] (Option 3-3) The UE determines whether to apply the valid symbol type for CSI derivation configured in CSI-ReportConfig depending on whether it is configured to monitor the SFI.

[0159] (Option 3-3-1) If the UE is not configured to monitor SFI in DCI format 2_0, it shall perform L1 CLI measurements and reporting using valid symbol types configured in CSI-ReportConfig.

[0160] If the UE is not configured to monitor SFI, it may apply option 3-1 to perform L1 UE-to-UE CLI measurements and reporting since dynamic TDD is not used.

[0161] (Option 3-3-2) In cases other than the above-mentioned option 3-3-1, the UE performs L1 CLI measurements and reporting without using a valid symbol type configured in CSI-ReportConfig. In this option 3-3-2, the UE may perform L1 UE-UE CLI measurements and reporting by applying the above-mentioned option 3-2.

[0162] (Variation of Option 3-3-2) If the UE decides to apply a valid symbol type (e.g., option 3-1 / option 3-3) and CSI-ReportConfig is not configured: Option 3-2A or Option 3-2B may be applied. In addition to Option 3-2A or Option 3-2B, the UE may use a "default symbol type" for L1 CLI derivation. This default symbol type may be defined in the specification or may be an SBFD symbol or a non-SBFD flexible symbol configured per DL BWP / serving cell.

[0163] (Example of Option 3) The embodiment of Option 3 is the same as the embodiment of Option 2 described above, except that "non-SBFD symbol" in Figures 9 and 10 is replaced with "non-SBFD flexible symbol."

[0164] (effect) As described above, according to this proposal, the symbol type of the reference signal for detecting crosslink interference (CLI) caused by transmissions by other UEs is appropriately selected taking into account the transmission and reception conditions and possible interference, allowing the UE to perform L1 CLI measurement (or reference) using a reference signal of the appropriate symbol type.

[0165] <Variations of proposals> (Combined with options) In the present disclosure, which option or Alt (Alternation) is 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)

[0166] In the proposals of this disclosure, multiple options and alternatives may be combined into one option / alternative.

[0167] Also, throughout the proposal, the reference signal (RS) to be measured will be the QCL source RS in the active / indicated TCI state.

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

[0169] 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-static reception of information (triggered by UE or gNB instructions) Option 3: Aperiodically receive information (triggered by UE or gNB instructions)

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

[0171] In the present disclosure, the QCL resources RS for each QCL type may be set as follows: SSB (SS / PBCH Block) CSI-RS with / without repetition ·TRS(tracking reference signal) PDCCH / PDSCH DMRS

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

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

[0174] 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: Transmit information semi-statically (triggered by UE or gNB instructions) Option 3: Send information aperiodically (triggered by UE or gNB instruction)

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

[0176] The above UE capabilities and the configurations 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.

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

[0178] <Base station configuration> Fig. 11 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. 12) by radio.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0201] For example, the control unit 203 may perform CLI measurement, CLI derivation, and CLI reporting based on values ​​related to SRS-ResourceConfigCLI, RSSI-ResourceConfigCLI, CSI-ReportConfig, and CSI-ResourceConfig, as well as SBFD or non-SBFD symbol type, valid symbol type for CSI (Channel State Information) derivation, non-SBFD symbol type on dynamic TDD slot, and symbol type determined by whether or not there is a setting to monitor SFI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0235] Furthermore, resources in the spatial domain may be defined, for example, in terms of 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.

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

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

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

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

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

Claims

1. A communication unit that transmits and receives signals whose transmission and / or reception symbol type is either a subband non-overlapping full duplex (SBFD) symbol type or a non-SBFD symbol type; a control unit configured to measure the received power of a reference signal received at a physical layer in order to detect cross link interference (CLI) caused by transmissions by other user equipments; Equipped with The control unit measures the received power of the reference signal using a symbol of a symbol type that satisfies a predetermined condition. Terminal.

2. The symbol type of the predetermined condition is the SBFD symbol type. The terminal of claim 1.

3. The predetermined condition symbol type is a valid symbol type for CSI (Channel State Information) derivation. The terminal of claim 1.

4. The predetermined condition symbol type is a non-SBFD symbol type on a dynamic TDD (dynamic Time Division Multiple Access) slot. The terminal of claim 1.

5. When the control unit is set to monitor an SFI (Slot Format Indicator) in a cell, the control unit determines the symbol type of the predetermined condition to be the non-SBFD symbol type, and when the control unit is not set to monitor an SFI, the control unit determines the symbol type of the predetermined condition to be the SBFD symbol type. The terminal of claim 1.

6. The device is Transmitting and receiving signals in which the transmit and / or receive symbol type is either a Subband non-overlapping Full Duplex (SBFD) symbol type or a non-SBFD symbol type; measuring the received power of a reference signal received at a physical layer using symbols of a symbol type under a predetermined condition in order to detect cross link interference (CLI) caused by transmissions by other user equipments; Communication method.

Images