Terminal and communication method

Abstract

According to the present invention, CLI measurement is appropriately performed when Method #3 is supported. This terminal comprises: a transmission / reception unit that performs transmission of an uplink signal and reception of a downlink signal in a time unit in which a plurality of subbands constituting a time division duplex band can be used; and a control unit that performs, in the time unit, measurement for cross-link interference in a physical layer in each of a downlink subband and an uplink subband. A frequency resource configured for the measurement in the uplink subband is restricted in relation to a frequency resource configured for the measurement in the downlink subband.

Description

Terminal and Communication Method

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

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) is standardizing the 5th generation mobile communication system (5G, New Radio (NR) or also called Next Generation (NNG). Further, the standardization of the next generation mobile communication system called Beyond 5G, 5G Evolution or 6G is also underway.

[0003] In Release 18, an extension of the multiplexing method that enables simultaneous use of the downlink (DL) and the uplink (UL) by using a plurality of subbands constituting the time division duplex (TDD) band has been discussed. Such an extended multiplexing method is called subband non - overlapping full duplex (SBFD).

[0004] With the introduction of SBFD and dynamic / flexible TDD, simultaneous DL / UL transmission from the base station (hereinafter also referred to as gNodeB (gNB)) / terminal (hereinafter also referred to as user equipment (UE)) has become possible.

[0005] On the other hand, due to the extension of the multiplexing method, cross - link interference (CLI) has occurred.

[0006] For countermeasures against this CLI, the terminal performs CLI measurement and reports the result of the L1 (Layer 1) - based CLI measurement to the base station.

[0007] Regarding CLI measurement, support for Method #1 (RSSI measurement within the DL subband) has been agreed, but support for Method #3 (RSSI measurement within the UL subband) is currently under consideration.

[0008] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023TS38.212 V18.3.0 (2024-06) Section 6.2.7TS38.331 V18.3.0 (2024-07) Section 6.3

[0009] In preparation for the possibility of Method #3 support being approved in the future, we need to consider the potential challenges.

[0010] One aspect of this disclosure provides a terminal and communication method that can properly perform CLI measurement when Method #3 is supported.

[0011] A terminal according to one aspect of the present disclosure comprises a transceiver unit that transmits uplink signals and receives downlink signals in time units in which a plurality of subbands constituting a time-division duplex band are available, and a control unit that performs measurements for crosslink interference at the physical layer in each of the downlink subband and the uplink subband in the said time unit, wherein the frequency resources set for measurement in the uplink subband are limited in relation to the frequency resources set for measurement in the downlink subband.

[0012] 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 Release 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 pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing the pure time unit and the SBFD time unit. This is a diagram showing an overview of the CSI report framework (Report setting). This is a diagram showing an overview of the Resource setting. This is a diagram showing Method #1, Method #2, Method #3, and Method #1+#3, respectively. This is a diagram showing Examples 1, 2, and 3 of Option 2 of Proposal 2-1, respectively. This is a block diagram showing an example of a base station configuration. This is a block diagram showing an example of a terminal configuration. This is a diagram showing an example of the hardware configuration of a base station and a terminal. This is a diagram showing an example of a vehicle configuration.

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

[0014] (1) The wireless communication system 10 shown in diagram 1 is a wireless communication system that follows a method called 5G. On the other hand, the wireless communication system 10 may also be a wireless communication system that follows a method called Beyond 5G, 5G Evolution, or 6G.

[0015] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates a more directional beam by controlling the wireless 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.

[0016] 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 a plurality of 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, for example, the number of gNB 100 and UE 200, 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".

[0017] 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 read as DU, or as CU, or as DU and CU. When gNB100 is read as DU, it may be called gNB-DU. When gNB100 is read as CU, it may be called gNB-CU. When gNB100 is read as DU and CU, the DU portion may be called gNB-DU and the CU portion may be called gNB-CU.

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

[0019] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used. In FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0020] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS 38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0021] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

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

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

[0024] 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, bandwidth part (BWP), or similar.

[0025] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of cells (or physical channels) formed by the gNB 100. Coverage enhancement may provide mechanisms to increase the success rate of receiving various physical channels, such as repeated transmission (repetition) of PRACH (physical random access channel).

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

[0027] Furthermore, for example, UE200 transmits PRACH to gNB100 as a UL signal using a resource such as RACH Occasion (RO), which is used to transmit a random access preamble. For example, UE200 repeatedly transmits PRACH to gNB100 as a UL signal.

[0028] The UL signal may include, for example, UL data signals and control information. For example, the UL signal may include information regarding the processing capability of the UE200 (e.g., UE capability). The UL signal may also include reference signals.

[0029] The channels used to transmit UL signals include, for example, a data channel and a control channel. 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, 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. The shared channel may also be called a data channel.

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

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

[0032] Furthermore, for example, gNB100 receives PRACH from UE200 as a UL signal. For example, gNB100 repeatedly receives PRACH from UE200 as a UL signal.

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

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

[0035] Here, the UE200 performs measurements related to the received quality at the physical layer. These measurements related to the received quality at the physical layer may also be referred to as L1 measurements. The received quality at the physical layer may include L1-SRS-RSRP (Reference Signal Received Power) or L1-CLI-RSSI (Received Signal Strength Indicator).

[0036] Furthermore, UE200 reports measurement results regarding reception quality at the physical layer to gNB100. This report may be referred to as L1 reporting. The reception quality at the physical layer may include L1-SRS-RSRP or L1-CLI-RSSI.

[0037] L1-SRS-RSRP may be a linear average of the power ([W]) of the resource element carrying the SRS. The measurement time resource for the linear average may be set by the upper layer (RRC message).

[0038] The L1-CLI-RSSI may be a linear average of the observed total received power ([W]). The measurement time resource for the linear average may be set by the upper layer (RRC message).

[0039] The definitions of L1-SRS-RSRP and L1-CLI-RSSI may be newly introduced. The definitions of L1-SRS-RSRP and L1-CLI-RSSI may be the same as the existing SRS-RSRP / CLI-RSSI definitions, or they may be updated definitions of the existing SRS-RSRP / CLI-RSSI definitions. The existing SRS-RSRP / CLI-RSSI may be those defined in TR38.215 §5.1.19 / §5.1.20.

[0040] (SBFD operation) Considering the transmission-to-transmission time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Release 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 restricts the application of UL coverage extension techniques such as repetition.

[0041] In future wireless communication systems (e.g., Release 18 and later), the introduction of a time-frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is being considered.

[0042] 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 DL and UL to be used simultaneously).

[0043] Figure 4A shows an example of TDD configuration as defined up to Release 16. In the example shown in Figure 4A, a TDD slot or symbol is set to UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).

[0044] In the example shown in FIG. 4A, the time ratio of the DL slot to the UL slot is 4:1. In such a conventional slot or symbol setting in TDD, sufficient UL time resources cannot be ensured, and there is a risk of occurrence of UL transmission delay and deterioration of coverage performance.

[0045] 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), the resources used for DL reception and the resources used for UL transmission overlap in time. According to such a resource configuration, more UL resources can be ensured, and the utilization efficiency of resources can be improved.

[0046] For example, as in the example shown in FIG. 4B, both ends of the frequency domain may be set as DL resources, and the UL resources may be sandwiched by these DL resources. Thereby, the occurrence of cross-link interference (Cross Link Interference (CLI)) with adjacent carriers can be avoided and mitigated. Also, a guard area may be set at the boundary between the DL resources and the UL resources.

[0047] Considering the complexity of self-interference processing, it is conceivable that only the base station 100 uses the DL resources and the UL resources simultaneously. That is, in the radio resources where DL and UL overlap in time, one UE 200 may use the DL resources, and another UE 200 may use the UL resources.

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

[0049] In the example shown in FIG. 5, during the period of only DL, each of a plurality of UEs 200 (UE#1 and UE#2 in FIG. 5) receives the DL channel / signal.

[0050] Furthermore, during periods when DL and UL overlap in time, one UE200 (UE#1 in the example in Figure 5) receives the DL channel / signal, and another UE200 (UE#2 in the example in Figure 5) transmits the UL channel / signal. During this period, the base station 100 performs simultaneous transmission and reception of DL and UL.

[0051] Furthermore, during UL-only periods, each of the multiple UE200 units (UE#1 and UE#2 in Figure 5) transmits a UL channel / signal.

[0052] In existing NRs (for example, those defined by Release 15 / 16 / 17), DL frequency resources and UL frequency resources in UE carriers are configured as DL BWP and UL BWP, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism.

[0053] Figure 6A shows 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. The same notation may be used in the following figures as well.

[0054] In existing NRs, as shown in Figure 6A, the time resources (time units such as symbols and slots) in the TDD carrier for UE200 are configured in the TDD settings as at least one of DL, UL, and Flexible (FL).

[0055] Figure 6B shows an example of an existing TDD setting. 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. Similar notation may be used in the following figures.

[0056] As shown in Figure 6B, an SBFD symbol may be a symbol that is notified or set as UL (or DL) on one frequency resource (subband), or notified or set for UL transmission (or DL ​​reception), while on another frequency resource (subband), it may be a symbol that is notified or set as DL (or UL), or notified or set for DL ​​reception (or UL transmission). Alternatively, an SBFD symbol may be a symbol that is notified or set as UL (or DL) on a portion of the frequency resource, or notified or set for UL transmission (or DL ​​reception). Alternatively, an SBFD symbol may be a symbol that is notified or set as DL (or UL) on a portion of the frequency resource, or notified or set for DL ​​reception (or UL transmission).

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

[0058] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an 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. For example, a pure time unit may be referred to as a time unit consisting only of DLs on a frequency resource, as shown in Figure 7A, or as a time unit consisting only of ULs on a frequency resource, as shown in Figure 7B.

[0059] Furthermore, with respect to the SBFD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the SBFD time unit of frequency domain pattern #1 may have the arrangement pattern shown in Figure 7C. The SBFD time unit of frequency domain pattern #2 may have the arrangement pattern shown in Figure 7D. The SBFD time unit of frequency domain pattern #3 may have the arrangement pattern shown in Figure 7E. These arrangement patterns are merely examples, and other arrangement patterns may be used. The frequency domain pattern of the SBFD time unit may mean a resource repetition pattern in the frequency domain for the SBFD time unit.

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

[0061] 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 as a full-duplexing system using subbands.

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

[0063] The following explains the terminology related to SBFD. • SBFD DL symbol: A symbol instructed to DL by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, which sets the SBFD subband. • SBFD FL symbol: A symbol instructed to FL by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, which sets the SBFD subband. • SBFD SSB symbol: A symbol set for SSB reception, which sets the SBFD subband. • Non-SBFD symbol: A symbol for which the SBFD subband is not set, and / or a symbol for which SBFD operation is not performed on the gNB side.

[0064] <CLI Handling Extensions> At the RAN#104 meeting, the CLI Handling extensions were updated as follows: - Specific extensions for CLI Handling [RAN1, RAN2, RAN3, RAN4] - Muting of PUSCH UL resources including [RAN1, RAN2, RAN4] - Instruction / determination of PUSCH UL resource muting based on quasi-static settings assuming comb-2 for both DFT-S-OFDM and CP-OFDM of each allocated PRB and a maximum of 2 symbols in the time domain - PUSCH resource mapping, i.e., rate matching around muted REs - Determination of UCI resources at symbols with muted REs - L1-based UE-to-UE CLI measurement and reporting based on existing CSI (Channel State Information) framework including [RAN1, RAN2, RAN4] - Setting / determination of "type D" QCL assumptions for CLI measurement resources - At least irregular reporting - New reporting volumes, e.g., L1-SRS-RSRP, L1-CLI-RSSI and / or measurement resource index - UCI bit generation - Multiple CSI (Channel State Information) Reporting priority rules, CLI measurement accuracy requirements, (Note) No specific optimizations are made for dynamic / flexible TDD.

[0065] <Agreements> The following agreements were reached at the RAN#118 meeting.

[0066] (Agreement 1) Regarding UE-to-UE CLI measurement and reporting, CLI measurement will be performed within the active DL BWP, and the following will be supported: ・Method #1: UE measures RSSI within the DL subband. ・Method #2: UE measures the RSRP of the aggressor UE within the UL subband. ・Method #3: UE measures RSSI within the UL subband. However, Method #3 is yet to be determined.

[0067] Figure 10 shows Method #1, Method #2, Method #3, and Method #1+#3, respectively.

[0068] (Agreement 2) The following will be supported for frequency resource allocation: ・Measurement resource type #1: One CLI-RSSI measurement resource will be set up within the DL subband. ・Measurement resource type #2: One CLI-RSSI measurement resource will be set up across two DL subbands.

[0069] The number of configurable resources and the UE behavior for measurement are yet to be determined.

[0070] (Agreement 3) Regarding UE-to-UE CLI measurement and reporting, the upper layer parameter reportQuantity will support two additional report quantities {'cli-RSSI', 'cli-SRS-RSRP'}.

[0071] The number of CLI resources reported by reportConfig, as well as the reporting criteria, are yet to be determined.

[0072] (Agreement Item 4) The following will be supported for UE-to-UE CLI measurement and reporting: • Wideband CLI-RSRP reporting • Wideband CLI-RSSI reporting Subband CLI-RSSI reporting is yet to be determined.

[0073] (Agreement Item 5) In the case of Method #1 (RSSI measurement within the DL subband), the frequency resource of CLI-RSSI measurement resource type #2 (one CLI-RSSI measurement resource set up across two DL subbands) is derived by excluding the frequency resource outside the DL-enabled PRB.

[0074] In this case, the UE supports a single wideband RSSI measurement report.

[0075] The two CLI-RSSI measurement reports for each DL subband, including the wideband report for each DL subband, are yet to be determined.

[0076] The configuration of RRC information elements such as CSI report config (CSI-ReportConfig), CSI resource config (CSI-ResourceConfig), R16 CLI measurement resource config (MeasObjectCLI-r16), AP CSI report triggering (CSI-AperiodicTriggerStateList), and SP CSI report triggering (CSI-SemiPersistentOnPUSCH-TriggerStateList) is disclosed in Non-Patent Document 3.

[0077] The CSI report config is a configuration related to the reporting of CSI feedback. Multiple CSI report configs can be configured. The CSI-ReportConfigId within the CSI report config is an identifier that indicates the resource used when performing the measurement.

[0078] The CSI resource config is a configuration that calls the CSI report configId found within the CSI report config to set up the CSI resource. The CSI-ResourceConfigId within the CSI resource config is an identifier that indicates a resource such as nzp-CSI-RS-SSB as a CSI-RS (Reference Signal) resource set.

[0079] The R16 CLI measurement resource config is a configuration for L3 (Layer 3) reporting by measurement reports. The CLI resource config called within the measurement object sets up resources such as the SRS resource and RSSI resource.

[0080] AP CSI report triggering is a configuration that calls CSI-ReportConfigId to trigger a specific state selected from the trigger states set in RRC beforehand in DCI when a CSI report is triggered aperiodically in DCI.

[0081] SP CSI report triggering is a configuration that calls CSI-ReportConfigId to trigger a specific state selected from the trigger states pre-configured in RRC when triggering a CSI report quasi-statically.

[0082] (CSI report framework in NR) As shown in Figure 8, the UE constructs a CSI report using a set of information including resource setting for channel measurement and reports it to the gNB. The Report setting in Figure 8 is an image of the CSI report config. Resource setting is information indicating the CSI-RS resource used for CSI measurement. As shown in Figure 9, each Resource setting #i (where i is a non-negative integer) contains a CSI-RE resource set #j (where j is a non-negative integer). The Resource setting in Figure 9 is an image of the CSI resource config.

[0083] (CLI-RSSI settings for Rel-16) The allowable size of the measurement bandwidth is limited to multiples of 4. The minimum configurable value is 4 plus the minimum width of the active DL BWP. If the configured value is greater than the width of the active DL BWP, the UE assumes that the actual CLI-RSSI resource bandwidth is within the active DL BWP.

[0084] In other words, in the conventional L3 CLI-RSSI measurement resource configuration, #PRB must be a multiple of 4.

[0085] <Analysis> As explained in Agreement 1 above, support for Method #1 (RSSI measurement within the DL subband) has been agreed upon, but support for Method #3 (RSSI measurement within the UL subband) is currently under consideration.

[0086] Furthermore, as explained in Agreement 5 above, for Method #1, it was agreed that the frequency resource for CLI-RSSI measurement resource type #2 (a single CLI-RSSI measurement resource set up across two DL subbands) would be derived by excluding the frequency resources outside the DL-enabled PRB.

[0087] In preparation for the event that support for Method #3 is decided upon in the future, the following issues need to be considered.

[0088] [Problem 1] The frequency resource configuration for Method #3 needs to be considered.

[0089] [Challenge 2] The operation methods for Method #1 and Method #3 need to be clarified.

[0090] If the CLI-RSSI for the DL subband and the CLI-RSSI for the UL subband are measured by separate CLI-RSSI measurement resources, it is easy to construct and report the CLI-RSSI for DL ​​and UL individually.

[0091] When CLI-RSSI for the DL subband and CLI-RSSI for the UL subband are measured in a single CLI-RSSI measurement resource (e.g., a CLI-RSSI measurement resource spanning both the DL and UL subbands), several issues arise, such as: • How can we determine whether the UE's behavior is based on Method #1, Method #3, or Method #1+#3? • If Method #1+#3 is used, how should CLI-RSSI be reported for DL / UL?

[0092] <Summary of Proposal> This application proposes the following to address the above-mentioned issues.

[0093] [Proposal 1] In Proposal 1, we propose the possibility of limiting the frequency resource configuration for Method #3 in response to Problem 1.

[0094] [Proposal 2] In Proposal 2, we propose supporting the combination of Method #1 and Method #3 using a single CLI-RSSI measurement resource to address Problem 2.

[0095] Proposal 2-1 proposes a method for determining whether to select Method #1 (CLI-RSSI measurement in the DL subband), Method #3 (CLI-RSSI measurement in the UL subband), or Method #1+#3 (CLI-RSSI measurement in both the DL and UL subbands).

[0096] Proposal 2-2 proposes reporting of CLI-RSSI in the DL subband and CLI-RSSI in the UL subband for Method #1+#3.

[0097] The matters described in the following proposals may be combined as appropriate, provided that no contradictions arise.

[0098] In this application, the notation " / " may mean "and / or" unless otherwise specified.

[0099] <Proposal 1> Proposal 1 proposes the possibility of limiting the frequency resource configuration for Method #3.

[0100] (Restriction 1) The number of PRBs for CLI-RSSI measurement in the UL subband is a multiple of X, where X may be defined by the specification (e.g., X = 2 / 4 / 6 / 8).

[0101] (Restriction 2) Any of the following alternatives (hereinafter referred to as "Alt") may be applied to whether or not to allow CLI-RSSI measurement resources to be set up across SBFD subband boundaries.

[0102] (Alt.1) In the case of CLI-RSSI measurement in the UL subband, the UE may allow the CLI-RSSI measurement resource to be set up across the SBFD subband boundary.

[0103] In this case, the UE may support a partial CLI-RSSI subband up to the SBFD subband boundary.

[0104] If the configured CLI-RSSI measurement resource spans RBs outside of the UL-enabled PRB, the RBs outside the UL-enabled PRB are excluded from the CLI-RSSI measurement. The UE performs the CLI-RSSI measurement on the RBs within the UL-enabled PRB.

[0105] The UE does not assume that there are PRBs exceeding X outside of UL-enabled PRBs near a single SBFD subband boundary. X may be defined in the specification or set by the RRC.

[0106] (Alt.2) The UE does not assume that CLI-RSSI measurement resources will be configured to span SBFD subband boundaries.

[0107] (Restriction 3) Restrictions may be imposed on the relationship between DL's CLI-RSSI measurement resource (i.e., Method #1) and UL's CLI-RSSI measurement resource (i.e., Method #3).

[0108] For example, a restriction may be imposed that the gap between the DL CLI-RSSI measurement resource and the UL CLI-RSSI measurement resource must be greater than X. X may be defined in the specification or set by the RRC.

[0109] In this case, if the first CLI-RSSI measurement resource is set up for Method #1 (i.e., CLI-RSSI measurement in the DL subband) and the second CLI-RSSI measurement resource is set up for Method #3 (i.e., CLI-RSSI measurement in the UL subband), the UE assumes that the gap between the first CLI-RSSI measurement resource and the second CLI-RSSI measurement resource is greater than (or not less than) X.

[0110] (Effects of Proposal 1) According to Proposal 1, CLI measurement can be performed properly if Method #3 is supported.

[0111] <Proposal 2> Proposal 2 proposes supporting the combination of Method #1 and Method #3 using a single CLI-RSSI measurement resource.

[0112] <Proposal 2-1> Proposal 2-1 proposes a method for deciding which of the following methods to choose: Method #1 (CLI-RSSI measurement in the DL subband), Method #3 (CLI-RSSI measurement in the UL subband), or Method #1+#3 (CLI-RSSI measurement in both the DL and UL subbands).

[0113] (Option 1) If reportQuantity is set to "cli-RSSI", whether the UE measures CLI-RSSI in the DL subband and / or UL subband may be explicitly indicated / set by the gNB.

[0114] Examples of parameters for explicit instruction / configuration by gNB include: • (Example 1) Explicit parameters within CSI-ReportConfig (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type) • (Example 2) Explicit parameters within L1 CLI measurement resource (set) configuration (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type) • (Example 3) Explicit parameters within trigger states (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type)

[0115] (Variation 1 of Option 1) Explicit parameters may only be set if CLI-RSSI measurement resources are configured across both subbands.

[0116] (Variation 2 of Option 1) If no parameters are set, the following Option 2 may be applied, and the default method (e.g., Method #1, Method #3, or Method #1+#3) may be applied.

[0117] (Option 2) If reportQuantity is set to "cli-RSSI", whether or not the UE performs CLI-RSSI measurements in the DL subband and / or UL subband may be implicitly determined by the frequency resource set in the CLI-RSSI measurement resource. Figure 11 shows examples 1, 2, and 3 below, respectively.

[0118] (Example 1) If the number of PRBs within the DL-enabled PRBs of the CLI-RSSI measurement resource (or within one / each / two DL subbands) (or the number of PRBs outside the UL-enabled PRBs) is less than (or not greater than) X, Method #3 may be applied. The value of X may be defined by the specification (e.g., X = 0 / 4 / 8) or set by the RRC. Note that a value of "0" for X means that there is no overlap between the CLI-RSSI measurement resource and the DL subbands.

[0119] (Example 2) If the number of PRBs within the UL-available PRBs of the CLI-RSSI measurement resource (or the number of PRBs outside the DL-available PRBs) is less than (or not greater than) Y, Method #1 may be applied. The value of Y may be defined by the specification (e.g., Y = 0 / 4) or set by the RRC. Note that a value of "0" for Y means that there is no overlap between the CLI-RSSI measurement resource and the UL subband.

[0120] (Example 3) If the number of PRBs within a DL-enabled PRB (or within one / each / two DL subbands) is greater than (or not less than) the number of UL-enabled PRBs in the CLI-RSSI measurement resource X, and the number of PRBs within the UL-enabled PRBs in the CLI-RSSI measurement resource is greater than (or not less than) Y, then Method #1+#3 may be applied. The values ​​of X / Y may be defined by the specification or set by the RRC.

[0121] If there is one CLI-RSSI measurement resource, the number of PRBs within the PRB available for UL for the CLI-RSSI measurement resource is determined by whether the CLI-RSSI measurement resource PRB is included within the PRB available for UL. If the CLI-RSSI measurement resource spans two DL subbands, the number of PRBs within the PRB available for UL for the CLI-RSSI measurement resource is equal to the size of the PRB available for UL. If the CLI-RSSI measurement resource overlaps with an SBFD subband boundary, the number of PRBs overlapping with the PRB available for UL must be less than four.

[0122] <Proposal 2-2> Proposal 2-2 proposes reporting of CLI-RSSI in the DL subband and CLI-RSSI in the UL subband in the case of Method #1+#3.

[0123] (Alt.1) UE may report the CLI-RSSI values ​​for the DL subband and the CLI-RSSI values ​​for the UL subband separately.

[0124] In this case, the "CLI-RSSI value in the DL subband" may be either the CLI-RSSI value for one DL subband or the CLI-RSSI value spanning two DL subbands.

[0125] Alternatively, as a variation, the "CLI-RSSI value in the DL subband" can be the two CLI-RSSI values ​​for each of the two DL subbands.

[0126] Furthermore, the "CLI-RSSI value in the UL subband" may be the CLI-RSSI value for a single UL subband.

[0127] Furthermore, differential reporting may be supported for the CLI-RSSI values ​​in the DL subband and the CLI-RSSI values ​​in the UL subband. For example, the UE may report the CLI-RSSI offset value for the DL (or UL) subband relative to the CLI-RSSI of the UL (or DL) subband.

[0128] (Alt.2) UE may report CLI-RSSI values ​​in one wideband spanning the DL subband and UL subband.

[0129] (Alt.3) UE may report either CLI-RSSI in the DL subband or CLI-RSSI in the UL subband.

[0130] Whether the reported value is the CLI-RSSI in the DL subband or the CLI-RSSI in the UL subband may be determined based on rules such as whether the CLI-RSSI in the UL subband (or DL ​​subband, or wideband CLI-RSSI) exceeds a threshold.

[0131] For example, a UE may report the CLI-RSSI of the DL subband if the CLI-RSSI of the UL / DL subband (or wideband CLI-RSSI) exceeds a certain threshold (or conversely, does not exceed it), and otherwise report the CLI-RSSI of the UL subband (or wideband CLI-RSSI). The threshold may be defined by the specification or set by the gNB.

[0132] For example, a UE may report the CLI-RSSI of the UL subband if the CLI-RSSI of the DL / UL subband (or wideband CLI-RSSI) exceeds a certain threshold (or conversely, does not exceed it), and otherwise report the CLI-RSSI of the DL subband (or wideband CLI-RSSI). The threshold may be defined by the specification or set by the gNB.

[0133] Note that among the above Alts, the Alt that is actually applied may be defined by the specification or set by gNB.

[0134] (Effects of Proposal 2) According to Proposal 2, CLI measurement can be performed properly if Method #3 is supported.

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

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

[0137] Next, the configuration of the base station 100 and terminal 200 will be described. Note that the configuration of the base station 100 and terminal 200 described below is an example of the functions related to this embodiment. The base station 100 and terminal 200 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 operation according to this embodiment.

[0138] <Base Station Configuration> Figure 12 is a block diagram showing an example of the configuration of a base station 100 according to this embodiment. The base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 100 communicates with a terminal 200 (see Figure 13) wirelessly.

[0139] The transmitting unit 101 transmits downlink (DL) signals to the terminal 200. For example, the transmitting unit 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, confirmation, etc. as described above) under the control of the control unit 103.

[0140] The DL signal may include, for example, data signals for the downlink and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission by terminal 200 (e.g., UL grant). 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 a reference signal.

[0141] 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, base station 100 transmits downlink control information to terminal 200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0142] 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 data signal of the downlink and are transmitted using PDSCH.

[0143] The receiving unit 102 receives uplink (UL) signals transmitted from the terminal 200. 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.

[0144] The transmitting unit 101 and the receiving unit 102 may together be referred to as the communication unit.

[0145] The control unit 103 controls the communication operations of the base station 100, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102.

[0146] 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 receiving unit 102 to the upper layer.

[0147] 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 terminal 200 (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 terminal 200.

[0148] <Terminal Configuration> Figure 13 is a block diagram showing an example of the configuration of a terminal 200 according to this embodiment. The terminal 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 200 communicates with, for example, a base station 100 wirelessly.

[0149] The transmitting unit 202 transmits the UL signal to the base station 100. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203. For example, the transmitting unit 202 may transmit MsgA PRACH in a valid MsgA RO determined by the control unit 203, or it may transmit MsgA PUSCH in a valid MsgA PO determined by the control unit 203.

[0150] 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 terminal 200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0151] 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, terminal 200 transmits uplink control information to base station 100 using PUCCH and transmits uplink data signals using PUSCH.

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

[0153] The receiving unit 201 and the transmitting unit 202 may together be referred to as the communication unit.

[0154] The control unit 203 controls the communication operation of the terminal 200, including the receiving process in the receiving unit 201 and the transmission process in the transmitting unit 202.

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

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

[0157] The channels used for transmitting DL signals and UL signals are not limited to the examples described above. For example, the channels used for transmitting DL signals and UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH may be used, for example, to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI).

[0158] <Hardware Configuration, etc.> The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. 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 or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0159] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0160] For example, a base station, terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 14 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 base station 100 and terminal 200 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.

[0161] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 100 and terminal 200 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0162] Each function in the base station 100 and terminal 200 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 at least one of data reading and writing in the memory 1002 and storage 1003.

[0163] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0164] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes 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 203 of the terminal 200 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 also be transmitted from the network via a telecommunications line.

[0165] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0166] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. 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 at least one of the memory 1002 and the storage 1003.

[0167] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be implemented by the communication device 1004.

[0168] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0170] Furthermore, the base station 100 and terminal 200 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), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0171] (Supplement to Embodiments) While embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. Software operated by a processor in a base station according to embodiments of this disclosure, and software operated by a processor in a terminal according to embodiments of this disclosure, may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0172] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described herein and may be carried out by other means. 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 combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0173] <Applicable Systems> The embodiments described in this disclosure include LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0174] <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 there is no contradiction. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0175] <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. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides the base station, but it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0176] <Direction of Input / Output> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes.

[0177] <Handling of Input / Output Information, etc.> Input and output information, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, etc. may be overwritten, updated, or appended to. Output information, etc. may be deleted. Input information, etc. may be transmitted to other devices.

[0178] <Determination Method> The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0179] <Variations of Embodiments, etc.> Each embodiment / appearance described in this disclosure may be used individually, in combination, or switched between during implementation. Furthermore, notification of predetermined information (for example, notification that "it is X") is not limited to explicit notification, but may also be implicit (for example, by not providing notification of the predetermined information).

[0180] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0181] <Software> Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0182] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0183] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

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

[0185] <Systems and Networks> The terms “systems” and “networks” as used in this disclosure are interchangeable.

[0186] <Parameters, Channel Names> Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0187] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0189] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0190] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0191] <Mobile Station> In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.

[0192] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0193] <Base Station / Mobile Station> At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of a base station and a mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes cases where the mobile body is stationary. The mobile body includes, but is not limited to, 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, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0194] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the embodiments of this disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0195] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the terminal described above.

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

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

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

[0199] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0200] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0201] The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to the outside (e.g., displays, speakers, LED lamps, touch panels, etc.).

[0202] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0204] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

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

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

[0207] <Meaning and Interpretation of Terms> As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" about some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0208] The terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0210] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on".

[0211] <"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 adopted, or that the first element must precede the second element in any way.

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

[0213] <Open Format> Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

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

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

[0216] A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology.

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

[0218] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0219] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0220] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0221] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0222] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0223] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0224] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0226] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0227] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0228] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0229] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0230] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0231] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0232] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0233] <Maximum Transmit Power> The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

[0235] <"Different"> In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0236] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2024-201190, filed on 18 November 2024, are incorporated herein by reference.

[0237] One aspect of this disclosure is useful for wireless communication systems.

[0238] 10 Wireless communication system 20 NG-RAN 100 Base station (gNB) 200 Terminal (UE) 101, 202 Transmitting unit 102, 201 Receiving unit 103, 203 Control unit

Claims

1. A terminal comprising: a transmitting / receiving unit that transmits uplink signals and receives downlink signals in time units in which multiple subbands constituting a time-division duplex band are available; and a control unit that performs measurements for crosslink interference at the physical layer in each of the downlink subband and the uplink subband in the said time unit, wherein the frequency resources set for measurements in the uplink subband are limited in relation to the frequency resources set for measurements in the downlink subband.

2. The terminal according to claim 1, wherein the number of resource blocks for measuring the subband of the uplink is a multiple of X, where X is defined by the specifications.

3. The terminal according to claim 1, wherein the control unit does not assume that measurement resources are set across the boundary between the subband of the uplink and the subband of the downlink.

4. The terminal according to claim 1, wherein the control unit assumes that the frequency gap between the subband of the uplink and the subband of the downlink is greater than X, where X is defined by the specifications.

5. A communication method comprising: a terminal transmitting uplink signals and receiving downlink signals in time units in which multiple subbands constituting a time-division duplex band are available; performing measurements for crosslink interference at the physical layer in each of the downlink subbands and uplink subbands in the said time unit; and the frequency resources set for measurements in the uplink subband being limited in relation to the frequency resources set for measurements in the downlink subband.

Images