Terminal and communication method
The terminal and communication method effectively measures and manages cross-link interference using both SBFD and non-SBFD symbols, enhancing communication efficiency and accuracy in SBFD operations.
Patent Information
- Application Number
- PCT/JP2026/015436
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-16
- Publication Date
- 2026-11-12
AI Technical Summary
The challenge of cross-link interference (CLI) negatively impacting PUSCH performance and measurement accuracy in subband non-overlapping full duplex (SBFD) scenarios, particularly during UL transmission and DL reception, remains unresolved, with unclear support for CLI measurement on non-SBFD symbols.
A terminal and communication method that measures the received power of reference signals using both SBFD and non-SBFD symbols to detect cross-link interference, employing a control unit to manage CLI through predetermined conditions.
Enhances CLI detection and management across various symbol types, improving communication efficiency and accuracy in SBFD operations by addressing interference issues.
Smart Images

Figure JP2026015436_12112026_PF_FP_ABST
Abstract
Description
Terminal and Communication Method
[0001] The present disclosure relates to a terminal and a communication method.
[0002] 3GPP (registered trademark) has specified the 5th generation mobile communication system (also referred to as 5G, New Radio (NR) or Next Generation (NG)), and is further advancing the specification of next-generation mobile communication systems called Beyond 5G, 5G Evolution, or 6G.
[0003] In Release 18, a duplex scheme that enables simultaneous use of downlink (DL) and uplink (UL) by utilizing multiple subbands constituting a Time Division Duplex (TDD) band is under discussion. Such a duplex scheme is called subband non-overlapping full duplex (SBFD). Note that symbols to which SBFD is applied may be referred to as SBFD symbols. Further, in SBFD symbols, subbands used for DL may be referred to as DL subbands, and subbands used for UL may be referred to as UL subbands.
[0004] Furthermore, for Release 19, enhancements related to UL transmission and DL reception using SBFD symbols and non-SBFD symbols are being studied, and technical requirements for clarifying the operation of SBFD are being discussed (Non-Patent Document 1).
[0005] RP-241614, 3GPP TSG RAN Meeting #104, 3GPP, June 17-20, 20243GPP TS 38.214 V18.3.0 (2024-06) (2024-06) 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP TR 38.858 V18.1.0 (2024-03) 3GPP TR 38.213 V18.3.0 (2024-06) 3GPP TR 38.215 V18.4.0 (2024-12)
[0006] Non-Patent Document 5 outlines the technical requirements for SBFD operation and summarizes points that need to be considered for the implementation of Release-19. In the updated WID (Non-Patent Document 1), one of the challenges in the operation of dynamic TDD or flexible TDD is that the effects of cross-link interference (CLI) negatively impact PUSCH (Physical Uplink Shared Channel) performance and measurement accuracy. CLI is interference that occurs between different cells, base stations, or terminals, for example, when one base station or terminal is transmitting and another base station or terminal is receiving on the same frequency band.
[0007] The cross-link interference described above can occur during UL transmission and DL reception using SBFD symbols. On the other hand, in a quasi-static SBFD scenario, there is no terminal-to-terminal CLI on non-SBFD symbols. However, cross-link interference can occur during UL transmission and DL reception using non-SBFD symbols with dynamic TDD. Therefore, whether or not to support CLI measurement on non-SBFD symbols remains an unresolved issue and requires further investigation.
[0008] One aspect of this disclosure relates to a terminal and communication method for measuring the received power of a reference signal received at the physical layer using a symbol of a symbol type of a predetermined condition, in order to detect crosslink interference (CLI) caused by transmissions from other user devices.
[0009] A terminal according to one aspect of the present disclosure includes a communication unit that transmits and receives signals whose transmitted and / or received 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 at the physical layer in order to detect cross-link interference (CLI) caused by transmissions by other user devices, wherein the control unit measures the received power of the reference signal using symbols of a symbol type under predetermined conditions.
[0010] This is a schematic diagram of the overall configuration of a wireless communication system. This is a diagram showing the frequency range used in the wireless communication system. This is a diagram showing an example of the configuration of wireless frames, subframes, slots, and symbols used in the wireless communication system. This is a diagram showing an example of the TDD settings specified up to Rel-16. This is a diagram showing an example of the SBFD configuration. This is a diagram showing an example of SBFD operation. This is a diagram showing an example of an existing TDD setting. This is a diagram showing an example of TDD including the SBFD setting. This is a diagram showing the agreements (excerpts) from the RAN1#118bis and RAN1#119 meetings. This is a diagram showing the proposals for discussion (excerpts) from the RAN1#120bis meeting. This is a flowchart showing an example of terminal operation in Option 2-1 or Option 2-2. This is a flowchart showing an example of terminal operation in Option 2-3. This is a block diagram showing an example of the base station configuration. This is a block diagram showing an example of the terminal configuration. This is a diagram showing an example of the hardware configuration of the base station and terminal.
[0011] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.
[0012] <Configuration of the Wireless Communication System> The wireless communication system 10 shown in Figure 1 is a wireless communication system that conforms to a method called 5G. On the other hand, the wireless communication system 10 may also be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.
[0013] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates a more directional beam by controlling the radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication with two base stations. In this specification, "and / or" may be simply written as " / ".
[0014] As shown in Figure 1, the wireless communication system 10 includes a base station 100 (hereinafter also referred to as gNodeB (gNB) 100) that constitutes the Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as user equipment (UE) 200) that communicates wirelessly with the gNB 100. The NG-RAN 20 is connected to a core network (CN) which is not shown. The CN is composed of multiple network functions (NFs). Examples of NFs include the Access and Mobility Management Function (AMF) and the Network Data Analytics Function (NWDAF). The AMF performs, for example, the registration of the UE 200. The NWDAF performs, for example, the optimization of the CN. Note that the specific configuration of the wireless communication system 10, such as the number of gNB 100s and UE 200s, is not limited to the example shown in Figure 1. Also, the NG-RAN 20 and CN may simply be referred to as the "network".
[0015] gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration, having a Distributed Unit (DU) with the function of connecting to UE200 and a Central Unit (CU) with the function of connecting to the network. In this case, gNB100 may be interpreted as DU, as CU, or as DU and CU. When gNB100 is interpreted as DU, it may be called gNB-DU. When gNB100 is interpreted as CU, it may be called gNB-CU. When gNB100 is interpreted as DU and CU, the DU portion may be called gNB-DU and the CU portion may be called gNB-CU.
[0016] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FRs). That is, as shown in Figure 2, it may support the following FRs: • FR1: 410 MHz to 7.125 GHz • FR2-1: 24.25 GHz to 52.6 GHz • FR2-2: Over 52.6 GHz to 71 GHz
[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. 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 also be interpreted as numerology. Numerology is defined in §5.1 of Non-Patent Document 3, etc., and corresponds to a single subcarrier interval in the frequency domain.
[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] Figure 3 shows an example of the configuration of wireless frames (system frames), subframes, and slots used in the wireless communication system 10. As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.
[0021] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it could be 28 or 56 symbols, etc.). In addition, the number of slots per subframe may differ depending on the SCS.
[0022] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).
[0023] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of the cell (or physical channel) formed by the gNB100. Coverage enhancement may provide mechanisms to improve the reception success rate of various physical channels, such as repetition of PRACH (physical random access channel).
[0024] For example, the UE200 receives information related to random access procedures from the gNB100 as a downlink signal (DL: Downlink) (e.g., SIB1 (System Information Block Type 1)).
[0025] Furthermore, for example, UE200 transmits PRACH to gNB100 using a RACH occasion, or RACH (transmit) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble as a UL signal. For example, UE200 replicates PRACH to gNB100 as a UL signal.
[0026] The UL signal may include, for example, UL data signals and control information. For example, the UL signal may include information about the processing capabilities of the UE200 (e.g., UE capability). The UL signal may also include reference signals.
[0027] The channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, the UE200 transmits control information using PUCCH and transmits UL data signals using PUSCH. Note that PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. Shared channels may also be called data channels.
[0028] The reference signals included in the UL signal may include, for example, at least one of the following: DMRS (Demodulation Reference Signal), PTRS (Phase Tracking Reference Signal), CSI-RS (Channel State Information - Reference Signal), SRS (Sounding Reference Signal), and PRS (Positioning Reference Signal) for position information. For example, reference signals such as DMRS and PTRS are used to demodulate the UL data signal and are transmitted using PUSCH.
[0029] Meanwhile, the gNB100, in response to the operation of the UE200, transmits information related to the RACH procedure to the UE200 as a DL signal (e.g., SIB1, etc.).
[0030] For example, gNB100 receives PRACH from UE200 as a UL signal. For example, gNB100 receives PRACH from UE200 as a repetition signal.
[0031] The channels used to transmit DL signals include, for example, a data channel and a control channel. For example, the data channel may include a Physical Downlink Shared Channel (PDSCH), and the control channel may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using the PDCCH and transmits DL data signals using the PDSCH. Note that PDSCH is an example of a Downlink Shared Channel, and PDCCH is an example of a Downlink Control Channel. Note that PDCCH may be interpreted as Downlink Control Information (DCI), control information, etc., transmitted in the PDCCH.
[0032] The reference signals included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, RS, and PRS for location information. For example, reference signals such as DMRS and PTRS are used to demodulate the DL data signal and are transmitted using PDSCH.
[0033] Next, we will discuss SBFD, CG (Configured Grant), Codebook-based uplink transmission, non-codebook-based uplink transmission, and mTRP.
[0034] <SBFD Operation> Considering the transmission / reception time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel-16, there may be cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE200 may not be able to transmit UL signals / channels frequently, raising concerns about transmission delays for important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, in TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques such as repetition transmission.
[0035] In future wireless communication systems (e.g., Rel-18 and beyond), the introduction of a time-frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is being considered.
[0036] Examples of such time-frequency division duplexing methods include XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) of the TDD band (allowing simultaneous use of DL and UL).
[0037] Figure 4A shows an example of a TDD configuration as defined up to Rel-16. In the example shown in Figure 4A, a TDD slot or symbol is set in the UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).
[0038] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. With such conventional TDD slot or symbol settings, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and reduced coverage performance.
[0039] Figure 4B shows an example of an SBFD configuration. In the example shown in Figure 4B, within a single component carrier (CC), the resources used for receiving DL and the resources used for transmitting UL overlap in time. This resource configuration allows for the allocation of more UL resources, thereby improving resource utilization efficiency.
[0040] For example, as shown in the example in Figure 4B, the ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This can help avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources.
[0041] In consideration of the processing complexity of self-interference, it is conceivable that only the gNB 100 uses DL resources and UL resources simultaneously. That is, in radio resources where DL and UL temporally overlap, one UE 200 may use the DL resource, and another UE 200 may use the UL resource.
[0042] FIG. 5 is a diagram illustrating an example of SBFD operation. In the example shown in FIG. 5, a part of DL resources of a TDD band is configured as UL resources, and the DL and the UL are configured to partially overlap in the time domain.
[0043] In the example shown in FIG. 5, in a DL-only period, each of a plurality of UEs 200 (UE 1 and UE 2 in FIG. 5) receives a DL channel / signal.
[0044] Also, in a period where DL and UL temporally overlap, one UE 200 (UE 1 in the example of FIG. 5) receives a DL channel / signal, and another UE 200 (UE 2 in the example of FIG. 5) transmits a UL channel / signal. In this period, the gNB 100 performs simultaneous transmission and reception of DL and UL.
[0045] Furthermore, in a UL-only period, each of a plurality of UEs 200 (UE 1 and UE 2 in FIG. 5) transmits a UL channel / signal.
[0046] In existing NR (e.g., specified up to Rel-15 / 16 / 17), a DL frequency resource and a UL frequency resource in a carrier for a UE are configured as a DL BWP and a UL BWP, respectively. In order to switch a DL / UL frequency resource to another DL / UL frequency resource, configuration of a plurality of BWPs and a BWP adaptation mechanism are required.
[0047] FIG. 6A is a diagram illustrating an example of an existing TDD configuration. In FIG. 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 drawings as well.
[0048] In existing NR, as shown in FIG. 6A, time resources (time units such as symbols and slots) on the TDD carrier for UE200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.
[0049] FIG. 6B is a diagram illustrating an example of TDD including SBFD configuration. In FIG. 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 drawings as well.
[0050] As shown in FIG. 6B, the SBFD symbol may be a symbol that is notified or configured as UL (or DL) on a certain frequency resource (subband), or notified or configured for UL transmission (or DL reception), while being notified or configured as DL (or UL) on another frequency resource (subband), or notified or configured for DL reception (or UL transmission). Alternatively, the SBFD symbol may be a symbol that is notified or configured as UL (or DL) in a part of frequency resources, or notified or configured for UL transmission (or DL reception). Alternatively, the SBFD symbol may be a symbol that is notified or configured as DL (or UL) in a part of frequency resources, or notified or configured for DL reception (or UL transmission).
[0051] Here, the time unit may be at the symbol level, the slot / subslot level, or a group of symbols / slots / subslots. That is, an SBFD time unit may be an SBFD symbol, a slot / subslot containing or overlapping an SBFD symbol, or a group of symbols / slots / subslots containing or overlapping an SBFD symbol.
[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 / subslot that does not contain or overlap SBFD symbols, or a group of symbols / slots / subslots that do not contain or overlap SBFD symbols, and may also be called a non-SBFD time unit.
[0053] As mentioned above, SBFD may be applied to each slot / symbol. In addition, each slot / symbol may be set to DL, UL, or Flexible (FL) which can be used as DL or UL, and then SBFD may be applied.
[0054] SBFD is a type of (full-duplex) duplexing system based on time-division duplexing (TDD), enabling the simultaneous use of multiple subbands that make up the TDD band. SBFD can also be described as a duplexing system where multiple subbands are defined within the TDD band, or a duplexing system where UL and DL are allocated non-overlapping in the frequency direction within the TDD time unit, or simply as full-duplex communication on subbands.
[0055] Symbols to which SBFD applies are also called SBFD symbols. "SBFD applies" may be interpreted as SBFD being applied in at least part of the scheduling. That is, "symbols to which SBFD applies" may be interpreted as symbols to which SBFD applies in scheduling where SBFD is applied (SBFD symbols). Also, "time units to which SBFD does not apply" may be interpreted as symbols to which SBFD does not apply in scheduling where SBFD is applied (non-SBFD symbols).
[0056] Furthermore, UEs that support SBFD operation (SBFD-aware UEs) are described as SBFD-aware UEs or SBFD-capable UEs, while UEs that do not support SBFD operation are described as Legacy UEs. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol, but a Legacy UE will recognize this SBFD symbol as a regular DL symbol.
[0057] <Cross-Link Interference> Cross-link interference (CLI) is interference that occurs between uplink (UL) communication and downlink (DL) communication. In SBFD operation, DL and UL partially overlap in the time domain, so solutions are needed to manage cross-link interference between base stations and between UEs. Similarly, solutions are needed for CLI within subbands and between subbands.
[0058] Sounding Reference Signal Received Power (SRS-RSRP) is defined as the linear average of the power components (in watts) in the resource element carrying the sounding reference signal (SRS). SRS-RSRP is measured against a set resource element within a measurement frequency bandwidth during a set measurement time occasion (see §5.1.19 of Non-Patent Document 7). For example, SRS-RSRP can be used to measure interference power from a specific UE.
[0059] The SRS-ResourceConfigCLI settings include information elements (IE) such as the subcarrier interval (srs-SCS), the index of the reference service cell to which the refBWP belongs (refServCellindex), and the ID of the DL BWP used to derive the reference point of the SRS resource (refBWP) (see §6.3.2 of Non-Patent Literature 4).
[0060] The CLI-RSSI (Cross-Link Interference Received Signal Strength Indicator) is defined as the linear average of all received power (in watts) observed within a set measurement time resource, a set OFDM symbol, and a set measurement bandwidth. This power includes all signal sources, such as signals from service and non-service cells within the same channel, adjacent channel interference, and thermal noise (see §5.1.20 of Non-Patent Document 7). For example, CLI-RSSI can be used to measure interference power in the total received power in a given band.
[0061] The RSSI-ResourceConfigCLI settings include information elements (IE) such as the reference subcarrier interval for CLI-RSSI measurement (rssi-SCS), the starting 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 range in which the UE measures RSSI from startPosition to startPosition+nrofSymbols-1 within the slot set for CLI-RSSI measurement (nrofSymbols), the period and slot offset of the CLI-RSSI resource (rssi-PeriodicityAndOffset), and the index of the reference service cell (refServCellIndex) (see §6.3.2 of Non-Patent Document 4).
[0062] <CSI-Report> Section 5.2 of Non-Patent Document 4 outlines how a UE can report channel status information (CSI) to a gNB. To enable the UE to correctly report channel status to the gNB, the reference signal resource to be measured, the report content, the timing of reporting, and the reporting destination are defined using CSI-ResourceConfig and CSI-ReportConfig. The UE is configured using the following parameters: • Reporting settings (CSI-ReportConfig) • Resource settings for measurement (CSI-ResourceConfig) • Trigger conditions using DCI (TriggerStateList)
[0063] CSI-ReportConfig is used to configure periodic or semi-persistent reports transmitted on PUCCH in cells containing CSI-ReportConfig, as well as semi-static or aperiodic reports triggered by DCI received in cells containing CSI-ReportConfig and transmitted on PUCCH. In this case, the cell from which the report is transmitted is determined by the received DCI. Resource configuration using CSI-ResourceConfig specifies the reference signal resource used by CSI-ResourceConfig, the timing of the resource (aperiodic / periodic / semi-persistent), etc.
[0064] <Objective of the Work Item (WID) on the Advancement of NR Duplexing in Rel-19> In Rel-18, studies were conducted to enable the simultaneous existence of downlink and uplink (full-duplex, more specifically subband non-overlapping full-duplex) on the gNB side within the conventional TDD band. Regarding SBFD, the impact on specifications, performance evaluation results, implementability, impact on radio frequency (RF) requirements, and the impact on specifications and performance evaluation results regarding dynamic / flexible TDD expansion are summarized in TR 38.858. According to the conclusions of TR 38.858, it is desirable in Rel-19 to specify SBFD operation on the gNB side within the TDD carrier, CLI processing methods between gNBs, CLI processing methods between UEs, and RF requirements corresponding to SBFD operation in gNBs.
[0065] Non-patent document 1 describes the update of the 3GPP Work Item (WID) concerning the evolution of NR duplex operation. The objectives of the review toward Rel-19 are, for example, as follows:
[0066] - Specifies extensions for CLI (Cross Link Interference) processing [RAN1, RAN2, RAN3, RAN4] - Includes content regarding UL resource muting for PUSCH [RAN1, RAN2, RAN4]: - Instruction / determination based on semi-persistent setting of UL resource muting for PUSCH when up to 2 symbols in the time domain based on comb-2 (comb mapping pattern) for both DFT-S-OFDM and CP-OFDM in each assigned PRB - PUSCH resource mapping around muted REs (resource elements), i.e., rate matching - Determination of UCI resources in symbols containing muted REs - Includes L1 level (physical layer) UE-to-UE CLI measurement and reporting based on the existing CSI framework [RAN1, RAN2, RAN4]: - Setting / determining 'typeD' QCL assumptions for periodic, quasi-static, or aperiodic measurement resources (sets), i.e., SRS-RSRP resources or CLI-RSSI resources, and CLI measurement resources. - At least aperiodic reporting. - New reporting quantities, e.g., L1-SRS-RSRP, L1-CLI-RSSI, and / or measurement resource indices. - Generation of UCI bits. - Prioritization rules for multiple CSI reports. - Accuracy requirements for CLI measurements. Note: Dedicated optimization for dynamic / flexible TDD is not assumed.
[0067] In this embodiment, interference occurring between the downlink (DL) communication of one UE and the 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 the basis, and changes to the priority rules of multiple CSI reports are considered.
[0068] <Agreements> 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 Figure 7).
[0069] Agreement (3GPP RAN1#118bis) The previous agreement is updated as follows: Agreement The CSI-ResourceConfig will be extended to include two CLI measurement resource set lists for L3-based SRS-RSRP and CLI-RSSI measurements, based on the SRS-ResourceConfigCLI and rssi-ResourceConfigCLI defined in Rel-16. - The resourceType in these two new CLI measurement resource set lists will be configurable to periodic, semi-persistent, or aperiodic. - As with the current specification, the number of periodic / semi-static CLI measurement resource sets included in a single CSI-ResourceConfig will be limited to one. Note: It is not necessary to define new uses for SRS resource sets.
[0070] Agreement (3GPP RAN1#119) Define a new information element (IE) SRS-RSRP-MeasurementResourceSet that includes a set of SRS-RSRP measurement resources (SRS-RSRP-MeasurementResource) for L1-based SRS-RSRP measurement. - Setting a slot offset between the slot containing the DCI that triggers the set of aperiodic SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured (already agreed upon in RAN1#118bis) - FFS: Other settings The SRS-RSRP-MeasurementResource will include the following parameters: - Conventional SRS resource information elements - FFS: Other parameters
[0071] Agreement (3GPP RAN1#119) Define a new information element (IE) CLI-RSSI-MeasurementResourceSet that includes a set of CLI-RSSI measurement resources (CLI-RSSI-MeasurementResource) for L1-based CLI-RSSI measurements. - Setting a slot offset between the slot containing the DCI that triggers the set of non-periodic CLI-RSSI resources and the slot in which the CLI-RSSI resource set is measured (already agreed upon in RAN1#118bis) The CLI-RSSI-MeasurementResource will include the following parameters: - CLI-RSSI measurement resource ID - PRB start index - Number of PRBs - Start symbol of the CLI-RSSI resource in the slot - Number of symbols of the CLI-RSSI resource in the slot - Period and slot offset of the CLI-RSSI resource - FFS: Other parameters
[0072] As mentioned above, CLI measurement resources can be broadly divided into SRS-RSRP and CLI-RSSI measurement resources. SRS-RSRP is used to measure interference power from a specific UE, while CLI-RSSI is used to measure interference power based on the total received power in a particular band over a given time.
[0073] <Discussion at the Meeting> At the 3GPP RAN1#120bis meeting, the question of whether or not to support L1 CLI measurement in non-SBFD symbols was discussed. The proposal that formed the basis of the discussion is as follows (see Figure 8).
[0074] [Proposals that formed the basis of the discussion] (Alt.1) The valid symbol types for CSI derivation set in CSI-ReportConfig do not apply to L1 inter-UE CLI measurement and reporting. UEs must perform L1 inter-UE CLI measurement only with SBFD symbols. (Alt.2) The valid symbol types for CSI derivation set in CSI-ReportConfig apply to L1 inter-UE CLI measurement and reporting. UEs must perform L1 inter-UE CLI measurement based on the valid symbol types set in CSI-ReportConfig. Note: L1 CLI measurement is supported by both SBFD and non-SBFD symbol types.
[0075] The original proposal (Alt.1) on which this discussion is based does not support CLI measurement using non-SBFD symbols. Furthermore, the valid symbol type for CSI derivation set in CSI-ReportConfig, whether SBFD or non-SBFD, does not apply to CLI measurement. This (Alt.1) only supports CLI measurement using SBFD symbols.
[0076] Furthermore, 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 set in CSI-ReportConfig are also applied to CLI measurements.
[0077] <Problem Analysis> At the aforementioned meeting, the question of whether or not to support / perform L1 CLI measurement in non-SBFD symbols was discussed. Based on this discussion, there are two viewpoints: one that L1 CLI measurement should be supported / performed in non-SBFD symbols, and another that it should not be supported / performed.
[0078] (Motivation for not supporting / performing L1 CLI measurement on non-SBFD symbols) In a quasi-static SBFD scenario, there is no UE-to-CLI on non-SBFD symbols, therefore L1 CLI measurement on non-SBFD symbols is unnecessary. Furthermore, this measurement resource may cause overhead. For this reason, in a quasi-static SBFD scenario, it is preferable not to support / perform L1 CLI measurement on non-SBFD symbols. This point is based on the motivation for (Alt.1) of the proposal on which the above discussion was based.
[0079] (Motivation for supporting / performing L1 CLI measurement on non-SBFD symbols) In the case of dynamic TDD, CLIs exist between UEs, so it is desirable not to limit L1 CLI measurement and reporting capabilities to SBFD scenarios only. Therefore, it is appropriate to support L1 CLI measurement on non-SBFD symbols as well. This point is based on the motivation (Alt.2) of the proposal that formed the basis of the above discussion.
[0080] Therefore, in this embodiment, we will consider a proposal for determining whether or not the UE performs L1 CLI measurement using non-SBFD symbols.
[0081] <Summary of the Proposal> The summary of the proposal is as follows (details will be provided later).
[0082] (Option 1) The UE performs L1 interUE CLI measurements only with SBFD symbols.
[0083] Option 1 is the same as Alt.1 of the [Proposal that formed the basis of the discussion] at the RAN1#120bis meeting.
[0084] (Option 2) The UE performs L1 CLI measurements using both SBFD and non-SBFD symbol types.
[0085] (Option 2-1) The UE performs L1 interUE CLI measurement and reporting using symbol types valid for CSI derivation as configured in CSI-ReportConfig.
[0086] Option 2-1 is the same as Alt.2 of the [Proposal that formed the basis of the discussion] at the RAN1#120bis meeting.
[0087] (Option 2-2) The UE performs L1 interUE CLI measurement and reporting regardless of the symbol type valid for CSI derivation set in CSI-ReportConfig.
[0088] (Option 2-3) The UE decides whether to apply the valid symbol types for the CSI derivation set in CSI-ReportConfig, depending on whether it is configured to monitor the SFI.
[0089] (Option 3) The UE performs L1 CLI measurements using both SBFD symbols and non-SBFD flexible symbols.
[0090] (Option 3-1) The UE performs L1 interUE CLI measurement and reporting using symbol types valid for CSI derivation as configured in CSI-ReportConfig.
[0091] (Option 3-2) The UE performs L1 interUE CLI measurement and reporting regardless of the symbol type valid for CSI derivation set in CSI-ReportConfig.
[0092] (Option 3-3) The UE decides whether to apply the valid symbol types of the CSI derivation set in CSI-ReportConfig, depending on whether it is configured to monitor the SFI.
[0093] <Proposal> As a proposal in this embodiment, the following options 1 to 3 will be described in order.
[0094] (Option 1) The UE performs L1 interUE CLI measurements only with SBFD symbols.
[0095] Option 1 is the same as (Alt.1) of the [Proposal on which the discussion was based] at the RAN1#120bis meeting. In other words, the valid symbol type for CSI derivation set in CSI-ReportConfig, whether SBFD or non-SBFD, does not apply to CLI measurements. In Option 1, the UE performs L1 interUE CLI measurements only with SBFD symbols.
[0096] (Option 2) The UE performs L1 CLI measurements using both SBFD and non-SBFD symbol types.
[0097] In Option 2, the UE performs L1 CLI measurements and reporting using both SBFD and non-SBFD symbols, according to Options 2-1 to 2-3 below.
[0098] (Option 2-1) The UE performs L1 interUE CLI measurement and reporting using symbol types valid for CSI derivation as configured in CSI-ReportConfig.
[0099] Option 2-1 is the same as Alt.2 of the [Proposal on which the discussion was based] at the RAN1#120bis meeting. In other words, the UE performs L1 interUE CLI measurement and reporting using valid symbol types for CSI derivation set in CSI-ReportConfig.
[0100] (Option 2-2) The UE performs L1 interUE CLI measurements and reporting regardless of the valid symbol type set in CSI-ReportConfig.
[0101] In this Option 2-2, the UE further performs L1 CLI derivation using symbol types as shown in Options 2-2A to 2-2B.
[0102] (Option 2-2A) The UE determines one symbol type to use 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 set in the cell, and then determines the symbol type of the L1 measurement 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 set at the SBFD subband position, perform the L1 CLI derivation using L1 measurements of SBFD symbols only.
[0105] (Alt-1-1 variation) The UE performs L1 CLI measurement only with SBFD symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with SBFD symbols.
[0106] (Alt-1-2) If the UE is not set at the SBFD subband position, perform the L1 CLI derivation using L1 measurements with only non-SBFD symbols.
[0107] (Alt-1-2 variation) The UE performs L1 CLI measurements only with non-SBFD symbols. That is, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with non-SBFD symbols.
[0108] (Alt-2) The UE determines the symbol type to use for L1 CLI derivation based on whether the cell is configured to monitor the SFI (Slot Format Indicator), and then determines the symbol type of the L1 measurement to use for L1 CLI derivation based on Alt-2-1 to Alt-2-2 below.
[0109] SFI is an indicator used to indicate the transmit / receive direction (U: Uplink (UL) / D: Downlink (DL) / F: Flexible) in a symbol within 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 will perform L1 CLI derivation using L1 measurements with only SBFD symbols.
[0111] (Alt-2-1 variation) The UE performs L1 CLI measurements only with SBFD symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with SBFD symbols.
[0112] (Alt-2-2) If the UE is configured to monitor SFI in DCI format 2_0, it will perform L1 CLI derivation using L1 measurements with only non-SBFD symbols.
[0113] In this Alt-2-2, the UE is configured to monitor the SFI only when dynamic TDD is used. When dynamic TDD is used, inter-UE CLIs can occur even with 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 with non-SBFD symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with non-SBFD symbols.
[0115] (Option 2-2B) The UE may perform L1 CLI derivation using both SBFD symbols and non-SBFD symbols. The UE may perform L1 CLI measurement using either SBFD symbols or non-SBFD symbols.
[0116] (Option 2-3) The UE decides whether to apply the valid symbol types for the CSI derivation set 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 will perform L1 CLI measurements and reporting using a valid symbol type configured in CSI-ReportConfig.
[0118] If the UE is not configured to monitor SFI, dynamic TDD is not being used, so option 2-1 may be applied to perform L1 UE-to-UE CLI measurement and reporting.
[0119] (Option 2-3-2) Except for option 2-3-1 described above, the UE performs L1 CLI measurement and reporting without using a valid symbol type set in CSI-ReportConfig. In the case of option 2-3-2, the UE may perform L1 interUE CLI measurement and reporting by applying option 2-2 described above.
[0120] (Variations 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 set: - 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 set per DL BWP / serving cell.
[0121] (Example of Option 2) Figure 9 is a flowchart showing an example of the operation of the UE in Option 2-1 or Option 2-2. To make the relationships between each option easier to understand, decisions for each option are shown, but only the necessary parts of the decisions for each option may be performed. The UE performs L1 CLI measurement or derivation according to the process shown in the flowchart in Figure 9.
[0122] In S1 (Step 1), the receiving unit of the UE receives values related to CSI-ReportConfig and DCI from the network (NW) or base station (gNB).
[0123] In S2, the UE's control unit determines, based on the received configuration information or pre-configured information, whether or not to perform an L1 UE-to-CLI measurement using a valid symbol type for CSI derivation set in CSI-ReportConfig. If the control unit determines in S2 to perform an L1 UE-to-CLI measurement using a valid symbol type for CSI derivation set in CSI-ReportConfig (S2: Yes), the flow proceeds to S3. On the other hand, if the control unit determines in S2 to perform an L1 UE-to-CLI measurement without using a valid symbol type for CSI derivation set in CSI-ReportConfig (S2: No), the flow proceeds to S4.
[0124] In S3, the UE's control unit performs L1 UE-to-CLI measurement and reporting using the symbol type valid for CSI derivation set in CSI-ReportConfig (Option 2-1).
[0125] In S4, the UE's control unit determines whether to perform L1-CLI derivation using a single 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 a single 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 using a symbol type other than a single symbol type (S4: No), the flow proceeds to S5.
[0126] In S5, the UE's control unit performs L1 CLI measurement and reporting using either an SBFD symbol or a non-SBFD symbol (option 2-2B).
[0127] In S6, the UE's control unit determines, based on the received configuration information or pre-configured information, whether to determine the symbol type of the L1 measurement used for L1-CLI derivation based on whether SBFD is set in the cell. If the control unit determines in S6 to determine the symbol type of the L1 measurement used for L1-CLI derivation based on whether SBFD is set in the cell (S6: Yes), the flow proceeds to S7. On the other hand, if the control unit determines in S6 to determine the symbol type of the L1 measurement used for L1-CLI derivation regardless of whether SBFD is set 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 location. If the control unit determines in S7 that the UE is configured at the SBFD subband location (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 location (S7: No), the flow proceeds to S10.
[0129] In S8, the control unit of the UE determines in the cell whether the UE is configured to monitor the SFI. 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] In S9, the UE's control unit performs L1 CLI derivation using L1 measurements of SBFD symbols only.
[0131] In S10, the control unit of the UE performs L1 CLI derivation using L1 measurements of non-SBFD symbols only.
[0132] In S11, the UE control unit performs L1 CLI derivation using L1 measurement of SBFD symbols only.
[0133] In S12, the control unit of the UE performs L1 CLI derivation using L1 measurements of non-SBFD symbols only.
[0134] Figure 10 is a flowchart showing an example of UE operation in option 2-3. The UE performs L1 CLI derivation through the process shown in the flowchart in Figure 10.
[0135] Note that the processes in S1, S4, S5, S6, S7, S9, S10, and S12 in Figure 9 are the same as the processes in S21, S24, S25, S26, S27, S28, S29, and S30 in Figure 10, respectively, so their explanations are omitted.
[0136] In S22, the control unit of the UE determines whether the received DCI is configured to monitor the SFI in DCI format 2_0. 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 UE control unit performs L1 UE-to-CLI measurement and reporting using the symbol type valid for CSI derivation set in CSI-ReportConfig (Option 2-3-1).
[0138] (Option 3) The UE performs L1 CLI measurements using both SBFD symbols and non-SBFD flexible symbols.
[0139] Option 3 is a variation of Option 2, differing in that the "non-SBFD symbols" in Option 2 have been changed to "non-SBFD flexible symbols." In Option 3, the UE further performs L1 CLI measurement and reporting using both SBFD symbols and non-SBFD flexible symbols according to Options 3-1 to 3-3.
[0140] (Option 3-1) The UE performs L1 interUE CLI measurement and reporting using symbol types valid for CSI derivation as configured in CSI-ReportConfig.
[0141] If the valid symbol type for CSI derivation set in CSI-ReportConfig is "SBFD", the reported L1 CLI measurement results are derived from L1 CLI measurement resources on SBFD symbols.
[0142] If the valid symbol type for CSI derivation set 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 interUE CLI measurement and reporting regardless of the symbol type valid for CSI derivation set in CSI-ReportConfig.
[0144] In this option 3-2, the UE further performs L1 CLI derivation using symbol types as shown in the following options 3-2A to 3-2B.
[0145] (Option 3-2A) The UE determines one symbol type to use 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 set in the cell, and then determines the symbol type of the L1 measurement 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 set at the SBFD subband position, perform the L1 CLI derivation using L1 measurements of SBFD symbols only.
[0148] (Alt-1-1 variation) The UE performs L1 CLI measurement only with SBFD symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with SBFD symbols.
[0149] (Alt-1-2) If the UE is not set at the SBFD subband position, perform the L1 CLI derivation using L1 measurements of non-SBFD flexible symbols only.
[0150] (Alt-1-2 variation) The UE performs L1 CLI measurements only with non-SBFD flexible symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with non-SBFD flexible symbols.
[0151] (Alt-2) The UE determines the symbol type to use for L1 CLI derivation based on whether the cell is configured to monitor the SFI (Slot Format Indicator), and then determines the symbol type of the L1 measurement to use 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 will perform L1 CLI derivation using L1 measurements with only SBFD symbols.
[0153] (Alt-2-1 variation) The UE performs L1 CLI measurements only with SBFD symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with SBFD symbols.
[0154] (Alt-2-2) If the UE is configured to monitor SFI in DCI format 2_0, it will perform L1 CLI derivation using L1 measurements with only non-SBFD flexible symbols.
[0155] In this Alt-2-2, the UE is configured to monitor the SFI only when dynamic TDD is used. When dynamic TDD is used, inter-UE CLI can 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 with non-SBFD flexible symbols. In other words, the UE assumes that not only L1 CLI derivation but also the L1 CLI measurement itself is performed only with non-SBFD flexible symbols.
[0157] (Option 3-2B) The UE may perform L1 CLI derivation using both SBFD symbols and non-SBFD symbols. The UE may perform L1 CLI measurement using either SBFD symbols or non-SBFD flexible symbols.
[0158] (Option 3-3) The UE decides whether to apply the valid symbol types of the CSI derivation set 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 will perform L1 CLI measurements and reporting using a valid symbol type configured in CSI-ReportConfig.
[0160] If the UE is not configured to monitor SFI, dynamic TDD is not being used, so option 3-1 may be applied to perform L1 UE-to-CLI measurements and reporting.
[0161] (Option 3-3-2) Except for option 3-3-1 described above, the UE performs L1 CLI measurements and reporting without using the valid symbol types set in CSI-ReportConfig. In the case of option 3-3-2, the UE may perform L1 interUE CLI measurements and reporting by applying option 3-2 described above.
[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 set: - 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 and may be an SBFD symbol or a non-SBFD flexible symbol set per DL BWP / serving cell.
[0163] (Example of Option 3) The example of Option 3 is equivalent to the example of Option 2 described above, with the "non-SBFD symbols" in Figures 9 and 10 replaced with "non-SBFD flexible symbols".
[0164] (Effects) As explained above, according to this proposal, by appropriately selecting the symbol type of the reference signal for detecting crosslink interference (CLI) caused by transmissions from other UEs, taking into account the transmission and reception conditions and the interference that may occur, the UE can perform L1 CLI measurement (or reference) with a reference signal of the appropriate symbol type.
[0165] <Variations of the Proposal> (Combinations with Options) In the proposals of this disclosure, the choice of which option or Alt (Alternation) to use may be determined by: - Setting by higher-level parameters - Determining by relevant higher-level parameters - Indicated in MAC CE or DCI - Determining based on the capabilities of the UE - Stated in the specification - Determining based on conditions stated in the specification - Determining by the configuration of higher-level parameters / MAC CE / DCI and reported UE capabilities (combinations of the above determinations)
[0166] In the proposals presented in this disclosure, multiple options and alternatives may be combined into a single option / alternative.
[0167] Furthermore, throughout the entire proposal, the measured RS (reference signal) will be the QCL source RS of the active TCI state / indicated TCI state.
[0168] (Signals from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW). Throughout the proposal, the network (NW) may also be referred to as a gNB. • Information via upper-layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) • MAC CE subheader with a new LCID extending the existing MAC CE (e.g., introducing a new octet) • DCI DCI field: Existing DCI field or newly introduced DCI field RNTI: Existing RNTI or DCI with a scrambled CRC by the newly introduced RNTI DCI format: Existing DCI format or newly introduced DCI format • Combinations of the above information
[0169] In this disclosure, the UE may receive information from the network (NW) in the following periodic forms: Option 1: Receive information periodically; Option 2: Receive information quasi-statically (triggered by instructions from the UE or gNB); Option 3: Receive information aperiodically (triggered by instructions from the UE or gNB).
[0170] In this disclosure, the UE may receive information from the network (NW) as the following QCL rules: • QCL Type A • QCL Type B • QCL Type C • QCL Type D
[0171] In this disclosure, the QCL resource 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 this disclosure, information from the network (NW) is set / presented as follows: • Common to UE / Dedicated to UE • Cell-specific / Common to cell • Per UE / CC / BWP / Bandwidth / Cell / CG
[0173] (Signals from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW). Throughout the proposal, the network (NW) may also be referred to as gNB. - Information via upper layer signaling (e.g., RRC messages / LPP messages) - MAC CE subheader with a new LCID, extending an existing MAC CE (e.g., introduction of a new octet) - UCI on PUCCH or PUSCH - Combinations of the above information
[0174] In this disclosure, the UE may report information to the network (NW) in the following periodic forms: Option 1: Send information periodically Option 2: Send information quasi-statically (triggered by instructions from the UE or gNB) Option 3: Send information aperiodically (triggered by instructions from the UE or gNB)
[0175] <UE capability> The UE capability, which indicates the capabilities of a terminal, may include the following information indicating the capabilities of the terminal. For example, the following new UE capability and report signaling (and RRC settings) may be defined. Note that the information indicating the capabilities of a terminal may correspond to the information defining the capabilities of the terminal. The UE may report the following information indicating the capabilities of the terminal to the gNB: - The capabilities of the terminal for each proposal - The capabilities of each option in each proposal, or each combination of options - The capabilities of each alternative in each proposal, or each combination of alternatives The UE may report the above information indicating the capabilities of the terminal for each frequency to the gNB: - Capabilities for each UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC, etc. The UE may report the above information indicating the capabilities of the terminal for each cell to the gNB: - Capabilities for each UE / cell / TDD / FDD, etc.
[0176] The capabilities of the UE described above and the configuration of this proposal are closely related, and if the functionality of each option in each proposal depends on the capabilities of the UE, the gNB may select or permit the functionality of each option based on the capabilities reported by the UE.
[0177] Next, the configurations of gNB100 and UE200 will be described. Note that the configurations of gNB100 and UE200 described below are examples of functions related to this embodiment. gNB100 and UE200 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited, as long as the function performs the operations related to this embodiment.
[0178] <Base Station Configuration> Figure 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 transmitting unit 101, a receiving unit 102, and a control unit 103. The gNB 100 communicates wirelessly with the UE 200 (see Figure 12).
[0179] The transmitter 101 transmits downlink (DL) signals to the UE200. For example, the transmitter 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, acknowledgment, etc., as described above) under the control of the control unit 103.
[0180] The DL signal may include, for example, downlink data signals and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission for the UE200 (e.g., UL grants). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include reference signals.
[0181] The channels used to transmit DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, gNB100 transmits downlink control information to UE200 using the PDCCH and transmits downlink data signals using the PDSCH.
[0182] The reference signals included in the DL signal may include, for example, at least one of the following: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS). For example, reference signals such as DMRS and PTRS are used for demodulating the downlink data signal and are transmitted using PDSCH.
[0183] The receiving unit 102 receives uplink (UL) signals transmitted from the UE200. For example, the receiving unit 102 receives UL signals (e.g., the requests and notifications mentioned above) under the control of the control unit 103.
[0184] The transmitting unit 101 and the receiving unit 102 may together be referred to as the communication unit.
[0185] The control unit 103 controls the communication operation of the gNB100, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102.
[0186] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the reception unit 102 to the upper layer.
[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 signals received from the UE200 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to the UE200.
[0188] <Terminal Configuration> Figure 12 is a block diagram showing an example of the configuration of the UE200 according to this embodiment. The UE200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The UE200 communicates with, for example, the gNB100 wirelessly.
[0189] The transmitting unit 202 transmits the UL signal to the gNB100. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.
[0190] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of the UE200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.
[0191] The channels used to transmit UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes PUCCH (Physical Uplink Control Channel). For example, UE200 transmits uplink control information to gNB100 using PUCCH and transmits uplink data signals using PUSCH.
[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, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).
[0193] For example, the receiving unit 201 may receive physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper 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 gNB 100.
[0194] For example, the receiving unit 201 may receive values related to SRS-ResourceConfigCLI, RSSI-ResourceConfigCLI, CSI-ReportConfig, and CSI-ResourceConfig from the NW or gNB100 as RRC (Radio Resource Control) signaling.
[0195] For example, the receiving unit 201 may monitor and decode the target DCI based on information indicating the search space associated with the DCI and information indicating the control resource set (CORESET) in response to a command from the control unit 203.
[0196] The receiving unit 201 and the transmitting unit 202 may together be referred to as the communication unit.
[0197] The control unit 203 controls the communication operation of the UE200, including the receiving process in the receiving unit 201 and the transmitting process in the transmitting unit 202.
[0198] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.
[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 candidate physical downlink control channels (PDCCHs) based on information indicating the search space associated with the DCI and information indicating the control resource set (CORESET), and issue a command to the receiving unit 201 to decode the target DCI.
[0201] For example, the control unit 203 may perform CLI measurements, perform CLI derivation, and perform CLI reporting based on values related to SRS-ResourceConfigCLI, RSSI-ResourceConfigCLI, CSI-ReportConfig, and CSI-ResourceConfig, as well as the SBFD or non-SBFD symbol type, the valid symbol type for CSI (Channel State Information) derivation, the non-SBFD symbol type on the dynamic TDD slot, and the symbol type determined by whether or not there is a setting to monitor SFI.
[0202] <Applicable Systems> Each aspect / embodiment described in this disclosure is applicable to LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-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 decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access, registered trademark), GSM (Global System for Mobile communications, registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), and IEEE (Institute of Electrical and Electronics Engineers). 802.11, IEEE802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi4, x=ac is Wi-Fi5, x=ax is Wi-Fi6 or Wi-Fi6E, x=be is Wi-Fi7, x=bn is Wi-Fi8, etc. Note that Wi-Fi is a registered trademark.)This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (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 this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology in question, but also systems that utilize extensions or modifications of the technology in question.
[0203] <Base Station> In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base 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", "Ground 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 contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the 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 this 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] The terminal may be called 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 appropriate term.
[0206] <Mobile Devices> Base stations and terminals may each consist of one or more devices. Devices constituting at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Devices constituting at least a part of each base station and terminal may be, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, IoT (Internet of Things) devices (e.g., smart meters, sensors), etc., or include, but are not limited to, objects themselves, such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0207] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the UE200 may have at least some of the functions of the gNB100 described above. Also, terms such as "uplink" and "downlink" may be interpreted 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 interpreted as a sidelink channel.
[0208] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).
[0209] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the gNB100 may be configured to have the same functions as the UE200 described above.
[0210] <Hardware Configuration, etc.> The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.
[0211] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 13 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The gNB100 and UE200 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0212] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configurations of gNB100 and UE200 may include one or more of the devices shown in the figures, or may be configured to omit some of the devices.
[0213] Each function in the gNB100 and UE200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.
[0214] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 described above may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.
[0215] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the UE200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.
[0216] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (e.g., a processor 1001).
[0217] Memory 1002 is a computer-readable recording medium and may consist of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or a combination of at least two of these. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of this disclosure.
[0218] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., a card, stick, key drive), a floppy® disk, a magnetic strip, or at least a combination of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.
[0219] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, the above-mentioned transmit / receive antenna, amplifier section, transmit / receive section, or transmission path interface may be implemented by the communication device 1004. The transmit / receive section may be implemented in a physically or logically separated manner, consisting of a transmit section and a receive section.
[0220] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0221] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.
[0222] Furthermore, gNB100 and UE200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.
[0223] <Notification of Information, Signaling> Notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions may be considered as the notification of the information in question.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between lower or upper layers of gNB100 and UE200), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within gNB100 or UE200). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.
[0224] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged in order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.
[0225] <Base Station Operation> The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in the RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. Network nodes are, for example, nodes located in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provide one or more network functions (NFs).
[0226] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."
[0227] <Variations of Embodiments, etc.> Each embodiment / part described in this disclosure may be used individually, in combination, or switched between as needed during implementation.
[0228] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.
[0229] <"First", "Second"> Any reference to elements using the designations "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.
[0230] <Definition of Wireless Resources> Wireless resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.
[0231] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, but are not limited to, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof. Furthermore, these time units may be fixed-length time units independent of numerology, variable-length time units dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.
[0232] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.
[0233] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such 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 designation of frequency units is not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB may consist 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 the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For a UE200, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.
[0234] Furthermore, resources in both the time domain and the frequency domain may be defined in one or more time / frequency units, for example, consisting of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) 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, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.
[0236] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.
[0237] <Articles> In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may also include the fact that the noun following these articles is plural.
[0238] <Means> The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0239] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2025-78239, filed on 8 May 2025, are incorporated herein by reference.
[0240] One aspect of this disclosure is useful for terminals and communication methods.
[0241] 10 Wireless communication system 20 NG-RAN 100 Base station (gNB) 200 Terminal (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit
Claims
1. A terminal comprising: a communication unit that transmits and receives signals whose transmitted and / or received 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 at the physical layer in order to detect cross-link interference (CLI) caused by transmissions by other user devices, wherein the control unit measures the received power of the reference signal using symbols of a symbol type under predetermined conditions.
2. The terminal according to claim 1, wherein the symbol type of the predetermined conditions is the SBFD symbol type.
3. The terminal according to claim 1, wherein the symbol type of the predetermined conditions is a valid symbol type for CSI (Channel State Information) derivation.
4. The terminal according to claim 1, wherein the symbol type of the predetermined conditions is a non-SBFD symbol type on a dynamic TDD (dynamic Time Division Multiple Access) slot.
5. The terminal according to claim 1, wherein the control unit determines the symbol type for the predetermined conditions to the non-SBFD symbol type when the cell is set to monitor the SFI (Slot Format Indicator), and determines the symbol type for the predetermined conditions to the SBFD symbol type when the control unit is not set to monitor the SFI.
6. A communication method in which a terminal transmits and / or receives signals whose transmitted and / or received symbol type is either a subband non-overlapping full duplex (SBFD) symbol type or a non-SBFD symbol type, and measures the received power of a reference signal received at the physical layer using a symbol of a predetermined symbol type in order to detect cross-link interference (CLI) caused by transmissions by other user equipment.
