Terminal and communication method
The proposed terminal and communication method addresses CLI issues in SBFD by restricting frequency resources for CLI measurements in both downlink and uplink subbands, ensuring accurate CLI measurements and reduced interference in 5G and Beyond 5G systems.
Patent Information
- Application Number
- JP2024201190
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-11-18
- Publication Date
- 2025-10-15
AI Technical Summary
The expansion of duplexing methods in 5G communication systems, such as subband non-overlapping full duplex (SBFD), has led to cross-link interference (CLI) issues, necessitating improved CLI measurements, particularly with the anticipated support for Method #3 (RSSI measurement within the UL subband), which current technologies have not adequately addressed.
A terminal and communication method that includes a transceiver unit for transmitting and receiving signals in time units with restricted frequency resource settings, allowing for proper CLI measurements in both downlink and uplink subbands, and a control unit for performing cross-link interference measurements in the physical layer, with specific restrictions on frequency resource configurations for Method #3.
Enables accurate CLI measurements when Method #3 is supported, enhancing communication efficiency and reducing interference in future 5G and Beyond 5G systems.
Smart Images

Figure 2025157100000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a terminal and a communication method. [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation 10 (NNG)), and is also developing specifications for the next generation mobile communication system known as Beyond 5G, 5G Evolution, or 6G.
[0003] Release 18 discusses an extension of the duplexing scheme that allows simultaneous use of the downlink (DL) and uplink (UL) by utilizing multiple subbands that make up the time division duplexing (TDD) band. This extended duplexing scheme is called subband non-overlapping full duplex (SBFD).
[0004] The introduction of SBFD and dynamic / flexible TDD has made it possible to simultaneously transmit DL / UL from a base station (hereinafter also referred to as gNodeB (gNB)) / terminal (hereinafter also referred to as user equipment (UE)).
[0005] On the other hand, the expansion of duplexing methods has led to the occurrence of cross-link interference (CLI).
[0006] To counter this CLI, the terminal performs CLI measurements and reports the results of L1 (Layer 1)-based CLI measurements to the base station.
[0007] Regarding CLI measurement, support for Method #1 (RSSI measurement within DL subband) has been agreed upon, but support for Method #3 (RSSI measurement within UL subband) is currently under consideration. [Prior art documents] [Non-patent literature]
[0008] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 [Non-patent document 2] TS38.212 V18.3.0 (2024-06) Section 6.2.7 [Non-patent document 3] TS38.331 V18.3.0 (2024-07) Section 6.3 Summary of the Invention
[0009] In preparation for the future decision to support Method #3, it is necessary to consider the anticipated issues.
[0010] One aspect of the present disclosure provides a terminal and a communication method that can properly perform CLI measurements when Method #3 is supported.
[0011] A terminal according to one aspect of the present disclosure includes a transceiver unit that transmits uplink signals and receives downlink signals in a time unit in which multiple subbands constituting a time division duplex band are available, and a control unit that performs measurements for crosslink interference in the physical layer in each of the downlink subbands and the uplink subbands in the time unit, and the frequency resources set for measurements in the uplink subbands are restricted in relation to the frequency resources set for measurements in the downlink subbands. [Brief explanation of the drawings]
[0012] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] This is a diagram showing an example of TDD settings specified up to Release 16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7A] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7B] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7C] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7D] FIG. 1 illustrates pure time units and SBFD time units. [Figure 7E] FIG. 1 illustrates pure time units and SBFD time units. [Figure 8]FIG. 1 is a diagram illustrating an overview of the CSI report framework (Report setting). [Figure 9] FIG. 1 is a diagram illustrating an overview of resource setting. [Figure 10] 1A and 1B are diagrams showing Method #1, Method #2, Method #3, and Method #1+#3, respectively. [Figure 11] 1A to 1C are diagrams showing examples 1, 2, and 3 of option 2 of proposal 2-1. [Figure 12] FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 13] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 14] FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 15] FIG. 1 is a diagram illustrating an example of a configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION
[0013] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.
[0014] (1) Wireless communication system configuration 1 is a wireless communication system conforming to a scheme called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.
[0015] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) as a bundle, and Dual Connectivity (DC), which communicates simultaneously with two base stations.
[0016] As shown in FIG. 1, a wireless communication system 10 includes a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) constituting a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as a user equipment (UE) 200) that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) (not shown). The CN is composed of multiple network functions (NFs). The NFs are, for example, an access and mobility management function (AMF) and a network data analytics function (NWDAF). The AMF performs, for example, registration of the UE 200. The NWDAF performs, for example, optimization of the CN. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1. The NG-RAN 20 and the CN may be simply referred to as a "network."
[0017] The gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration having a distributed unit (DU) having a function for connecting to the UE200 and a central unit (CU) having a function for connecting to the network. In this case, the gNB100 may be read as a DU, a CU, or a DU and a CU. When read as a DU, the gNB100 may be called a gNB-DU. When read as a CU, the gNB100 may be called a gNB-CU. When read as a DU and a CU, the DU portion may be called a gNB-DU and the CU portion may be called a gNB-CU.
[0018] Furthermore, the wireless communication system 10 may support a plurality of frequency ranges (FRs). That is, as shown in FIG. 2, the wireless communication system 10 may support the following FRs: FR1: 410MHz~7.125GHz FR2-1: 24.25GHz~52.6GHz ·FR2-2: More than 52.6GHz~71GHz
[0019] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used, and in FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.
[0020] Note that the SCS may be interpreted as a numerology, which is defined in 3GPP TS 38.300 and corresponds to one subcarrier spacing in the frequency domain.
[0021] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.
[0022] Fig. 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in Fig. 3, one slot is made up of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.
[0023] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it may be 28 or 56 symbols, etc.) Furthermore, the number of slots per subframe may differ depending on the SCS.
[0024] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.
[0025] The wireless communication system 10 may support coverage enhancement (CE) that expands the coverage of a cell (or a physical channel) formed by the gNB 100. In coverage enhancement, a mechanism for increasing the success rate of reception of various physical channels, such as repeated transmission (repetition) of a physical random access channel (PRACH), may be provided.
[0026] For example, UE200 receives information related to the random access procedure from gNB100 as a downlink (DL) signal (e.g., SIB1 (System Information Block Type 1) etc.).
[0027] Furthermore, for example, the UE 200 transmits a PRACH as an UL signal to the gNB 100 using a RACH occasion (RO), which is a resource for transmitting a random access preamble. For example, the UE 200 repeatedly transmits the PRACH as an UL signal to the gNB 100.
[0028] The UL signal may include, for example, a UL data signal and control information. For example, the UL signal may include information related to the processing capability of the UE 200 (e.g., UE capability). The UL signal may also include a reference signal.
[0029] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels may include a Physical Uplink Shared Channel (PUSCH), and the control channels may include a Physical Uplink Control Channel (PUCCH). For example, the UE 200 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel, and the PUCCH is an example of an uplink control channel. The shared channels may also be called data channels.
[0030] The reference signal included in the UL signal may include at least one of a DMRS (Demodulation Reference Signal), a PTRS (Phase Tracking Reference Signal), a CSI-RS (Channel State Information - Reference Signal), an SRS (Sounding Reference Signal), and a PRS (Positioning Reference Signal) for positioning information. For example, reference signals such as the DMRS and PTRS are used to demodulate the UL data signal and are transmitted using the PUSCH.
[0031] Meanwhile, in response to the operation of UE200, gNB100 transmits information related to the RACH procedure to UE200 as a DL signal (e.g., SIB1, etc.).
[0032] Furthermore, for example, the gNB 100 receives, as an UL signal, a PRACH from the UE 200. For example, the gNB 100 repeatedly receives, as an UL signal, a PRACH from the UE 200.
[0033] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the gNB 100 transmits control information to the UE 200 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel, and the PDCCH is an example of a downlink control channel. Note that the PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.
[0034] The reference signal included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRSRS, and PRS for location information. For example, the reference signal such as DMRS or PTRS is used for demodulating the DL data signal and is transmitted using the PDSCH.
[0035] Here, the UE 200 performs measurements related to reception quality in the physical layer. The measurements related to reception quality in the physical layer may be referred to as L1 measurements. The reception quality in the physical layer may include L1-SRS-RSRP (Reference Signal Received Power) and L1-CLI-RSSI (Received Signal Strength Indicator).
[0036] Furthermore, the UE 200 reports measurement results regarding reception quality in the physical layer to the gNB 100. This report may be referred to as L1 reporting. Furthermore, the reception quality in the physical layer may include L1-SRS-RSRP and L1-CLI-RSSI.
[0037] The L1-SRS-RSRP may be a linear average of the power ([W]) of the resource elements carrying the SRS. The measurement time resource of the linear average may be configured by a higher 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 configured by higher layers (RRC messages).
[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 definitions of SRS-RSRP / CLI-RSSI, or may be updated definitions of the existing SRS-RSRP / CLI-RSSI. The existing SRS-RSRP / CLI-RSSI may be defined in TR38.215 §5.1.19 / §5.1.20.
[0040] (SBFD operation) Considering the time ratio of transmission and reception (e.g., DL:UL = 4:1) using Time Division Duplex (TDD) up to Release 16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL signals / channels. In such cases, UE 200 cannot transmit UL signals / channels frequently, which raises concerns about transmission delays of important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, with TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques, such as repetition transmission.
[0041] In future wireless communication systems (for example, Release 18 and later), the introduction of a time-frequency division duplexing method that combines TDD and frequency division duplexing (FDD) for both UL and DL is being considered.
[0042] Examples of the time-frequency division duplexing method include XDD (Cross Division Duplex) and Subband-non-overlapping Full Duplex (SBFD). XDD or SBFD may refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) in the TDD band (allowing DL and UL to be used simultaneously).
[0043] Fig. 4A is a diagram showing an example of TDD configuration defined up to Release 16. In the example shown in Fig. 4A, TDD slots or symbols are configured for a UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).
[0044] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. This conventional TDD slot or symbol configuration does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.
[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), resources used for DL reception and resources used for UL transmission overlap in time. With this resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.
[0046] For example, as shown in the example of Figure 4B, both ends of the frequency domain may be set as DL resources, and these DL resources may sandwich UL resources. This may prevent or mitigate cross link interference (CLI) with neighboring carriers. Also, a guard region may be set at the boundary between the DL resources and the UL resources.
[0047] Considering the complexity of handling self-interference, it may be considered that only the base station 100 uses the DL resource and the UL resource simultaneously. That is, in radio resources where the DL and UL overlap in time, one UE 200 may use the DL resource and another UE 200 may use the UL resource.
[0048] Fig. 5 is a diagram showing an example of SBFD operation. In the example shown in Fig. 5, part of the DL resources of the TDD band is set as the UL resources, and the DL and UL are configured to partially overlap in the time domain.
[0049] In the example shown in FIG. 5, during the DL-only period, each of the multiple UEs 200 (UE#1 and UE#2 in FIG. 5) receives the DL channel / signal.
[0050] Furthermore, during a period in which DL and UL overlap in time, 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. During this period, base station 100 performs simultaneous transmission and reception of DL and UL.
[0051] Furthermore, during the UL-only period, each of the multiple UEs 200 (UE#1 and UE#2 in FIG. 5) transmits a UL channel / signal.
[0052] In existing NR (e.g., those specified by Release 15 / 16 / 17), the DL frequency resource and UL frequency resource of a UE carrier are configured as DL BWP and UL BWP, respectively. To switch a DL / UL frequency resource to another DL / UL frequency resource, multiple BWP configurations and a BWP adaptation mechanism are required.
[0053] Figure 6A is a diagram showing an example of an existing TDD configuration. In Figure 6A, slots / symbols marked with "D" are DL slots / symbols, slots / symbols marked with "U" are UL slots / symbols, and slots / symbols marked with "F" are flexible (hereinafter also referred to as FL) slots / symbols. Note that similar notations may be used in the following figures.
[0054] In the existing NR, as shown in FIG. 6A, time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.
[0055] Figure 6B is a diagram showing an example of an existing TDD configuration. In Figure 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Note that similar notations may be used in the following figures.
[0056] As shown in FIG. 6B , the SBFD symbol may be signaled or configured as UL (or DL) on some frequency resources (subbands) or signaled or configured for UL transmission (or DL reception), while being signaled or configured as DL (or UL) on other frequency resources (subbands) or signaled or configured for DL reception (or UL transmission). Alternatively, the SBFD symbol may be signaled or configured as UL (or DL) on a portion of the frequency resources or signaled or configured for UL transmission (or DL reception). Alternatively, the SBFD symbol may be signaled or configured as DL (or UL) on a portion of the frequency resources or signaled or configured for DL reception (or UL transmission).
[0057] Here, the time unit may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots, i.e., the SBFD time unit may be an SBFD symbol, a slot / subslot containing or overlapping an SBFD symbol, or a group of symbols / slots / subslots containing or overlapping an SBFD symbol.
[0058] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol, also referred to as a non-SBFD symbol), a slot / subslot that does not contain or overlap an SBFD symbol, or a group of symbols / slots / subslots that do not contain or overlap an SBFD symbol, and may also be referred to as a non-SBFD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DL on frequency resources as shown in Figure 7A, or as a time unit consisting only of UL on frequency resources as shown in Figure 7B.
[0059] Furthermore, for an SBFD time unit, DL resources and UL resources may have various allocation patterns in the frequency domain. For example, an SBFD time unit of frequency domain pattern #1 may have an allocation pattern as shown in FIG. 7C. An SBFD time unit of frequency domain pattern #2 may have an allocation pattern as shown in FIG. 7D. An SBFD time unit of frequency domain pattern #3 may have an allocation pattern as shown in FIG. 7E. These allocation patterns are merely exemplary, and other allocation patterns may also be used. The frequency domain pattern of an SBFD time unit may refer to a resource repetition pattern in the frequency domain for the SBFD time unit.
[0060] As described above, SBFD may be applied to each slot / symbol. Note that each slot / symbol may be set to DL, UL, or Flexible (FL) that can be used as DL or UL, and then SBFD may be applied.
[0061] SBFD is a type of (full-duplex) duplexing scheme based on time division duplexing (TDD), enabling simultaneous use of multiple sub-bands that make up the TDD band. SBFD can be described as a duplexing scheme in which multiple sub-bands are specified within the TDD band, a duplexing scheme in which UL and DL are allocated non-overlapping in the frequency direction within the TDD time unit, or full-duplex duplexing of sub-bands.
[0062] A symbol to which SBFD is applied is also called an SBFD symbol. "SBFD is applied" may be interpreted as SBFD being applied to at least a part of scheduling. In other words, "a symbol to which SBFD is applied" may be interpreted as a symbol to which SBFD is applied (SBFD symbol) in scheduling to which SBFD is applied. Also, "a time unit to which non-SBFD is applied" may be interpreted as a symbol to which SBFD is not applied (non-SBFD symbol) in scheduling to which SBFD is applied.
[0063] The following describes the terms related to SBFD. · SBFD DL symbol: A symbol indicated for DL by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, and on which the SBFD sub-band is configured · SBFD FL symbol: A symbol indicated for FL by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, and on which the SBFD sub-band is configured · SBFD SSB symbol: A symbol configured for SSB reception, and on which the SBFD sub-band is configured · Non-SBFD symbol: A symbol on which the SBFD sub-band is not configured, and / or a symbol on which SBFD operation is not performed on the gNB side
[0064] <Enhancement of CLI Handling> At the RAN#104 meeting, the enhancement of CLI Handling was updated as follows. · Specific enhancement functions for CLI Handling [RAN1, RAN2, RAN3, RAN4] · Muting of UL resources of PUSCH including [RAN1, RAN2, RAN4] · Indication / decision of muting of UL resources of PUSCH based on a quasi-static setting, assuming comb-2 for both DFT-S-OFDM and CP-OFDM of each allocated PRB and assuming a maximum of 2 symbols in the time domain · PUSCH resource mapping, i.e., rate matching around the muted REs · Decision of UCI resources in the symbol having the muted RE L1-based UE-to-UE CLI measurement and reporting based on the existing CSI (Channel State Information) framework, including [RAN1, RAN2, RAN4] ·Setting / determining "type D" QCL assumptions for CLI measurement resources At least occasional reporting New reporting quantities, e.g., L1-SRS-RSRP, L1-CLI-RSSI and / or measurement resource index UCI bit generation Priority rules for multiple CSI (Channel State Information) reporting CLI measurement accuracy requirements *Note: There will be no dedicated optimizations for dynamic / flexible TDD.
[0065] <Agreement> At the RAN#118 meeting, the following agreements were reached:
[0066] (Agreement details 1) Regarding UE-to-UE CLI measurement and reporting, CLI measurement is performed within the active DL BWP and the following is supported: Method #1: The UE measures the RSSI in the DL subband. Method #2: The UE measures the RSRP of the aggressor UE in the UL subband. Method #3: The UE measures RSSI in the UL subband. However, Method #3 is undefined.
[0067] FIG. 10 is a diagram showing Method #1, Method #2, Method #3, and Method #1+#3, respectively.
[0068] (Agreement details 2) For frequency resource allocation, the following are supported: Measurement resource type #1: One CLI-RSSI measurement resource is configured in the DL subband. Measurement resource type #2: One CLI-RSSI measurement resource is configured across two DL subbands.
[0069] The number of configurable resources and the UE behavior for measurements have not yet been determined.
[0070] (Agreement details 3) For UE-to-UE CLI measurement and reporting, two additional report quantities {'cli-RSSI', 'cli-SRS-RSRP'} are supported in the higher layer parameter reportQuantity.
[0071] The number of CLI resources reported by reportConfig and the reporting criteria have yet to be determined.
[0072] (Agreement details 4) Regarding UE-to-UE CLI measurement and reporting, the following is supported: Wideband CLI-RSRP reporting Wideband CLI-RSSI reporting Sub-band CLI-RSSI reporting has not yet been determined.
[0073] (Agreement details 5) For Method #1 (RSSI measurement within DL subbands), the frequency resource for CLI-RSSI measurement resource type #2 (one CLI-RSSI measurement resource configured across two DL subbands) is derived by excluding the frequency resource outside the DL available PRB.
[0074] In this case, the UE supports a single wideband RSSI measurement report.
[0075] The two CLI-RSSI measurement reports per DL subband, including a wideband report for each DL subband, are yet to be determined.
[0076] (RRC information elements) 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 reporting CSI feedback. Multiple CSI report configs can be set. The CSI-ReportConfigId in the CSI report config is an identifier indicating the resources used when performing measurements.
[0078] The CSI resource config is a configuration for calling the CSI report configId in the CSI report config and configuring the CSI resource. The CSI-ResourceConfigId in the CSI resource config is an identifier indicating a resource such as nzp-CSI-RS-SSB as a CSI-RS (Reference Signal) resource set.
[0079] R16 CLI measurement resource config is a configuration related to L3 (Layer 3) reporting by measurement report. SRS resource, RSSI resource, etc. are set by CLI resource config called in measurement object.
[0080] The AP CSI report triggering is a configuration for calling the CSI-ReportConfigId in order to trigger a specific state selected from the trigger states previously configured by the RRC when a CSI report is triggered aperiodically by the DCI.
[0081] The SP CSI report triggering is a configuration for calling the CSI-ReportConfigId in order to trigger a specific state selected from among the trigger states configured in advance by the RRC when semi-statically triggering a CSI report.
[0082] (CSI reporting framework in NR) As shown in Figure 8, the UE configures a CSI report using information including the Resource setting for Channel Measurement and reports it to the gNB. The Report setting in Figure 8 is an image of the CSI report configuration. The Resource setting is information indicating the CSI-RS resource used for CSI measurement. As shown in Fig. 9, each resource setting #i (i is an integer equal to or greater than 0) includes a CSI-RE resource set #j (j is an integer equal to or greater than 0). The resource setting in Fig. 9 is an image of a CSI resource config.
[0083] (CLI-RSSI setting for Rel-16) Only multiples of 4 are allowed for the measurement bandwidth size. The minimum configurable value is 4 plus the minimum of the 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] That is, 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] Also, as explained in Agreement 5 above, for Method #1, it was agreed that the frequency resource of CLI-RSSI measurement resource type #2 (one CLI-RSSI measurement resource configured across two DL subbands) will be derived by excluding the frequency resource outside the DL available PRB.
[0087] In preparation for the decision to support Method #3 in the future, it is necessary to consider the following issues.
[0088] [Task 1] Method #3 frequency resource configuration needs to be considered.
[0089] [Task 2] The operation of Method #1 and Method #3 needs to be clarified.
[0090] If the CLI-RSSI of the DL subband and the CLI-RSSI of the UL subband are measured by separate CLI-RSSI measurement resources, it is easy to configure and report the DL CLI-RSSI and the UL CLI-RSSI separately.
[0091] When the CLI-RSSI of the DL subband and the CLI-RSSI of the UL subband are measured in a single CLI-RSSI measurement resource (e.g., a CLI-RSSI measurement resource spanning the DL subband and the UL subband), there are several problems, such as the following. How do I determine whether the UE's behavior is based on Method #1, Method #3, or Method #1+#3? For Method #1+#3, how should CLI-RSSI be reported in DL / UL?
[0092] <Proposal Summary> In this application, the following proposals are made to address the above-mentioned problems.
[0093] [Proposal 1] In Proposal 1, we propose the possibility of limiting the frequency resource configuration for Method #3 in response to Issue 1.
[0094] [Proposal 2] Proposal 2 addresses issue 2 by proposing support for a combination of Method #1 and Method #3 using a single CLI-RSSI measurement resource.
[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 in the case of Method #1+#3.
[0097] The items described in the following proposals may be combined as appropriate as long as 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 frequency resource configuration for Method #3.
[0100] (Limit 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) Regarding whether or not to allow CLI-RSSI measurement resources to be configured across SBFD subband boundaries, any of the following alternatives (hereinafter referred to as "Alt") may be applied.
[0102] (Alt.1) In the case of CLI-RSSI measurement in the UL subband, the UE may allow CLI-RSSI measurement resources to be configured across the SBFD subband boundary.
[0103] In this case, the UE may support partial CLI-RSSI subbands up to the SBFD subband boundary.
[0104] If the configured CLI-RSSI measurement resource spans RBs outside the UL available PRBs, the RBs outside the UL available PRBs are excluded from the CLI-RSSI measurement. The UE performs CLI-RSSI measurement in RBs within the UL available PRBs.
[0105] The UE does not assume that there are more than X PRBs outside the UL usable PRBs around one SBFD subband boundary, where X may be defined in the specification or configured by the RRC.
[0106] (Alt.2) The UE does not assume that a CLI-RSSI measurement resource that crosses an SBFD subband boundary is configured.
[0107] (Restriction 3) Restrictions may be placed on the relationship between the DL CLI-RSSI measurement resource (ie, Method #1) and the UL CLI-RSSI measurement resource (ie, 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 is greater than X, where X may be defined in the specification or configured by the RRC.
[0109] In this case, if the first CLI-RSSI measurement resource is configured for Method #1 (i.e., CLI-RSSI measurement in the DL subband) and the second CLI-RSSI measurement resource is configured for Method #3 (i.e., CLI-RSSI measurement in the UL subband), the UE assumes that the gap between the first and second CLI-RSSI measurement resources is greater than (or not less than) X.
[0110] (Effects of Proposal 1) According to Proposal 1, if Method #3 is supported, CLI measurements can be performed properly.
[0111] <Proposal 2> Proposal 2 proposes supporting a 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 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).
[0113] (Option 1) If reportQuantity is set to "cli-RSSI", whether the UE measures CLI-RSSI on DL subbands and / or UL subbands may be explicitly indicated / configured by the gNB.
[0114] Examples of parameters for explicit instruction / configuration by the gNB include: (Example 1) Explicit parameters in CSI-ReportConfig (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type) (Example 2) Explicit parameters in the L1 CLI measurement resource(set) configuration (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type) (Example 3) Explicit parameters in the trigger state (e.g., a new parameter "cli-rssi-dl-ul" indicating the method type)
[0115] (Option 1 Variation 1) The explicit parameter may be set only if the CLI-RSSI measurement resource is configured across both subbands.
[0116] (Option 1 Variation 2) If the parameter is not set, the following option 2 may be applied, and a default method (e.g., Method #1, Method #3, or Method #1+#3) may be applied.
[0117] (Option 2) When reportQuantity is set to "cli-RSSI", whether the UE measures CLI-RSSI in the DL subband and / or the UL subband may be implicitly determined by the frequency resource set to the CLI-RSSI measurement resource. Note that Figure 11 shows examples 1, 2, and 3 below.
[0118] (Example 1) Method #3 may be applied if the number of PRBs within the DL usable PRBs (or within one / each / two DL subbands) of the CLI-RSSI measurement resource (or the number of PRBs outside the UL usable PRBs) is less than (or not greater than) X. The value of X may be defined by the specification (e.g., X=0 / 4 / 8) or may be set by RRC. Note that a value of X of "0" means that there is no overlap between the CLI-RSSI measurement resource and the DL subbands.
[0119] (Example 2) Method #1 may be applied if the number of PRBs within the UL available PRBs (or the number of PRBs outside the DL available PRBs) of the CLI-RSSI measurement resource is smaller (or not larger) than Y. The value of Y may be defined by the specification (e.g., Y=0 / 4) or may be set by RRC. Note that a value of Y of "0" means that there is no overlap between the CLI-RSSI measurement resource and the UL subband.
[0120] (Example 3) Method #1+#3 may be applied if the number of PRBs in the DL usable PRB (or in one / each / two DL subbands) is greater than (or not less than) the number of UL usable PRBs of the CLI-RSSI measurement resource X and the number of PRBs in the UL usable PRBs of the CLI-RSSI measurement resource Y. The value of X / Y may be defined by a specification or configured by RRC.
[0121] When there is one CLI-RSSI measurement resource, the number of PRBs within the PRBs available in the UL for the CLI-RSSI measurement resource is determined by including the PRBs of the CLI-RSSI measurement resource within the PRBs available in the UL. When the CLI-RSSI measurement resource spans two DL subbands, the number of PRBs within the PRBs available in the UL for the CLI-RSSI measurement resource is equal to the size of the PRBs available in the UL. When the CLI-RSSI measurement resource overlaps with the SBFD subband boundary, the number of PRBs that overlap with the PRBs available in the 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) The UE may report the CLI-RSSI value for the DL subband and the CLI-RSSI value for the UL subband separately.
[0124] In this case, the "CLI-RSSI value in the DL subband" may be either the CLI-RSSI value of 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" may be 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 of one UL subband.
[0127] Also, differential reporting may be supported for the CLI-RSSI value in the DL subband and the CLI-RSSI value in the UL subband. For example, the UE may report an offset value of the CLI-RSSI in the DL (or UL) subband based on the CLI-RSSI in the UL (or DL) subband.
[0128] (Alt.2) The UE may report the value of CLI-RSSI in one wideband across the DL subband and the UL subband.
[0129] (Alt.3) The UE may report either the CLI-RSSI on the DL subband or the CLI-RSSI on 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, the UE may report the CLI-RSSI of the DL subband if the CLI-RSSI of the UL / DL subband (or the wideband CLI-RSSI) exceeds a certain threshold (or vice versa), and may report the CLI-RSSI of the UL subband (or the wideband CLI-RSSI) otherwise. Note that the threshold may be defined by a specification or may be set by the gNB.
[0132] For example, the 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 vice versa), and may report the CLI-RSSI of the DL subband (or wideband CLI-RSSI) otherwise. Note that the threshold may be defined by a specification or set by the gNB.
[0133] Among the above Alts, the Alt that is actually applied may be defined by the specification or may be set by the gNB.
[0134] (Effects of Proposal 2) According to Proposal 2, if Method #3 is supported, CLI measurements can be performed properly.
[0135] <UE capability> The UE capability indicating the capability of the terminal may include the following information indicating the capability of the terminal. For example, the following new UE capability and report signaling (and RRC configuration) may be defined. Note that the information indicating the capability of the terminal may correspond to information defining the capability of the terminal. The UE may report the following information indicating the capabilities of the terminal to the gNB: ·Device capabilities for each proposal ·Ability to implement each option or combination of options in each proposal · Capabilities for each alternative or combination of alternatives in each proposal The UE may report information indicating the above-mentioned terminal capabilities for each frequency to the gNB. · Capabilities for UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC etc. The UE may report information indicating the above terminal capabilities for each cell to the gNB. Capabilities for each UE / cell / TDD / FDD, etc.
[0136] The above UE capabilities and the configuration of this proposal are closely related, and if the functions related to each option in each proposal depend on the UE capabilities, the gNB may select or enable the functions related to each option based on the capabilities reported by the UE.
[0137] Next, the configurations of base station 100 and terminal 200 will be described. Note that the configurations of base station 100 and terminal 200 described below are examples of functions related to the present embodiment. Base station 100 and terminal 200 may have functions not shown. Furthermore, the functional divisions and / or names of functional units are not limited as long as the functions perform operations related to the present embodiment.
[0138] <Base station configuration> 12 is a block diagram showing an example of the configuration of base station 100 according to this embodiment. Base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 100 communicates with terminal 200 (see FIG. 13) by radio.
[0139] Transmitter 101 transmits a downlink (DL) signal to terminal 200. For example, transmitter 101 transmits a DL signal (for example, the above-mentioned RRC, SIB, MAC CE, DCI, notification, confirmation, etc.) under the control of controller 103.
[0140] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of terminal 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.
[0141] Channels used for transmitting DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, base station 100 transmits downlink control information to terminal 200 using the PDCCH and transmits downlink data signals using the PDSCH.
[0142] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.
[0143] The receiver 102 receives an uplink (UL) signal transmitted from the terminal 200. For example, under the control of the controller 103, the receiver 102 receives an UL signal (for example, the above-mentioned request, notification, etc.).
[0144] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.
[0145] The control unit 103 controls the communication operations of the base station 100, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit .
[0146] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.
[0147] For example, 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 (e.g., data and control information, etc.) received from terminal 200 and / or data and control information, etc. acquired from a higher layer. Information related to the allocated resources may be included in control information transmitted to terminal 200.
[0148] <Device configuration> 13 is a block diagram showing an example of the configuration of terminal 200 according to the present embodiment. Terminal 200 includes, for example, receiving section 201, transmitting section 202, and control section 203. Terminal 200 communicates with base station 100, for example, wirelessly.
[0149] The transmitter 202 transmits an UL signal to the base station 100. For example, the transmitter 202 transmits the UL signal under the control of the controller 203. For example, the transmitter 202 may transmit an MsgA PRACH in a valid MsgA RO determined by the controller 203, and may transmit an MsgA PUSCH in a valid MsgA PO determined by the controller 203.
[0150] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of terminal 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.
[0151] Channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, terminal 200 transmits uplink control information to base station 100 using the PUCCH and transmits uplink data signals using the 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, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).
[0153] The receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.
[0154] The control unit 203 controls the communication operations of the terminal 200 , including the reception processing in the reception unit 201 and the transmission processing in the transmission unit 202 .
[0155] For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the higher layer.
[0156] For example, the control unit 203 controls 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, 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 UCI.
[0157] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.
[0158] <Hardware configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.
[0159] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0160] For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 14 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 100 and terminal 200 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0161] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of base station 100 and terminal 200 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0162] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0163] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.
[0164] Furthermore, the processor 1001 reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.
[0165] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.
[0166] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.
[0167] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.
[0168] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0169] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0170] Furthermore, base station 100 and terminal 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
[0171] (Supplementary explanation of the embodiment) Although the 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, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; features described in two or more items may be used in combination as needed, and features described in one item may apply to features described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagrams do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, base stations and terminals have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of a base station in accordance with an embodiment of the present disclosure, and the software operated by the processor of a terminal in accordance with an embodiment of the present 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] <Information notification, signaling> The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0173] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), 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, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.
[0174] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0175] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. 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 may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.
[0176] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.
[0177] <Handling of input and output information> Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.
[0178] <Judgment method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0179] <Variations of form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0180] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0181] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0182] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0183] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0184] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0185] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0186] <Parameter, channel name> Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0187] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0188] <Base station> In this disclosure, terms such as "base station (BS)," "radio 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. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.
[0190] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
[0191] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.
[0193] <Base station / mobile station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal may be configured to have the functions of the base station described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0195] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.
[0196] Fig. 15 shows an example configuration of a vehicle 2001. As shown in Fig. 15, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0197] The drive unit 2002 is configured, for example, by 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 operated by the user.
[0198] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0199] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0200] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.
[0201] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0202] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0203] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029, which are 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.
[0205] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0206] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, and the like provided in the vehicle 2001.
[0207] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0208] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0209] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0210] <The meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0211] <"First", "Second"> As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0212] <Means> In the configuration of each of the above devices, the "means" may be replaced with "section", "circuit", "device", etc.
[0213] <Open format> In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.
[0214] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be composed 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 be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.
[0215] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.
[0216] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.
[0217] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0218] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.
[0221] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0222] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0223] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0224] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0225] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0226] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0227] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.
[0228] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0229] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0230] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0231] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0232] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0233] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0234] <Article> In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0235] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Industrial Applicability]
[0236] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]
[0237] 10. Wireless communication systems 20 NG-RAN 100 base stations (gNB) 200 User Equipment (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit
Claims
1. a transceiver unit that transmits an uplink signal and receives a downlink signal in a time unit in which a plurality of subbands constituting a time division duplex band are available; a control unit that performs measurements for crosslink interference in a physical layer in each of a downlink subband and an uplink subband during the time unit; Equipped with The frequency resources configured for measurements in the uplink subband are restricted in relation to the frequency resources configured for measurements in the downlink subband. Terminal.
2. The number of resource blocks for measurement in the uplink subband is a multiple of X, where X is defined by a specification. The terminal according to claim 1 .
3. The control unit does not assume that measurement resources are configured across a boundary between the uplink subband and the downlink subband. The terminal according to claim 1 .
4. The control unit assumes that a frequency gap between the uplink subband and the downlink subband is larger than X; X is defined by the specification, The terminal according to claim 1 .
5. The device is Transmitting an uplink signal and receiving a downlink signal in a time unit in which a plurality of sub-bands constituting a time division duplex band are available; performing physical layer crosslink interference measurements in each of the downlink subbands and the uplink subbands during the time unit; The frequency resources configured for measurements in the uplink subband are restricted in relation to the frequency resources configured for measurements in the downlink subband. Communication method.