Terminal, base station, and communication method

Abstract

In the present invention, interference among terminals is appropriately reported. This terminal comprises: a control circuit that determines whether or not there is detection of a signal for measurement of cross-link interference between terminals; and a transmission circuit that, if the signal for measurement is not detected, transmits information indicating the inability to detect the signal for measurement, such transmission performed by using at least one of a first field for reporting an absolute value of a measurement value and a second field for reporting the differential of the measurement value with respect to the absolute value, the first field and the second field constituting control information for reporting a plurality of measurement values of cross-link interference.

Description

Terminals, base stations, and communication methods

[0001] This disclosure relates to terminals, base stations, and communication methods.

[0002] The 3rd Generation Partnership Project (3GPP) has completed the specification of the physical layer for Release 17 NR (New Radio access technology) as an enhancement to the functionality of 5th Generation mobile communication systems (5G). NR supports enhanced Mobile Broadband (eMBB) and Ultra Reliable and Low Latency Communication (URLLC) to meet requirements such as high speed and large capacity (see, for example, Non-Patent Documents 1-7).

[0003] 3GPP TS 38.133 V18.8.0, "Requirements for support of radio resource management (Release 18) ", Jan. 2025 3GPP TS 38.211 V18.5.0, "Physical channels and modulation (Release 18) ", Jan. 2025 3GPP TS 38.212 V18.5.0, "Multiplexing and channel coding (Release 18)", Jan. 2025 3GPP TS 38.213 V18.5.0, "Physical layer procedures for control (Release 18)", Jan. 2025 3GPP TS 38.214 V18.5.0, "Physical layer procedures for data (Release 18)", Jan. 2025 3GPP TS 38.215 V18.4.0, "Physical layer measurements (Release 18)", Jan. 2025 3GPP TS �8.331 V18.4.0, "Radio Resource Control (RRC) protocol specification (Release 18)", Dec. 2024

[0004] However, there is room for consideration regarding the method of reporting interference between terminals.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately report interference between terminals.

[0006] A terminal according to an embodiment of the present disclosure includes a control circuit that determines whether a signal for measuring cross-link interference between terminals is detected, and when the measurement signal is not detected, using at least one of a first field that reports an absolute value of the measurement value and a second field that reports a difference value of the measurement value with respect to the absolute value, which constitute control information for reporting a plurality of measurement values of the cross-link interference, and a transmission circuit that transmits information indicating that the measurement signal cannot be detected.

[0007] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0008] According to one embodiment of this disclosure, interference between terminals can be appropriately reported.

[0009] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features.

[0010] Figure 3: Example of subband non-overlapping full duplex (SBFD) operation Figure 4: Example of Dynamic / flexible time division duplex (TDD) operation Figure 5: Example of cross-link interference (CLI) between terminals in SBFD operation Figure 6: Example of Channel State Indicator (CSI) field for CLI report Figure 7: Example of Sounding Reference Signal (SRS) - Reference Signal Received Power (RSRP) quantization mapping table Figure 8: Example of partial base station configuration Block diagrams, example terminal configuration Block diagrams, example base station configuration Block diagrams, example terminal configuration Block diagrams, example base station and terminal operation Sequence diagrams, example SRS-RSRP quantization mapping table Figure 9: Example of CSI field for CLI report Figure 10: Example CSI field for CLI report Figure 11: Example SRS-RSRP quantization mapping table Figure 12: Example CSI field for CLI report Figure 23: Example of GPP NR system architecture Figure 34: Example functional partitioning in G O-RAN

[0011] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0012] [Regarding subband non-overlapping full duplex (SBFD) and Dynamic / flexible time division duplex (TDD)] Subband non-overlapping full duplex (SBFD) and Dynamic / flexible TDD are discussed in Release 18 and Release 19. Figure 1 shows an example of SBFD, and Figure 2 shows an example of Dynamic / flexible TDD.

[0013] Figure 1(a) shows an example of the operation of a base station (also called a gNB) and terminals (also called UE: User Equipment) (e.g., UE#1 and UE#2) within the same cell in SBFD operation. In SBFD operation, the base station performs SBFD operation, and the terminals perform Half duplex operation.

[0014] Figure 1(b) shows an example of SBFD operation. In Figure 1(b), the vertical axis represents frequency and the horizontal axis represents time. Also in Figure 1(b), "UL" represents uplink transmission and "DL" represents downlink transmission. Additionally, unused resources in each device (e.g., gNB, UE#1, and UE#2) are indicated by dotted lines.

[0015] As shown in Figure 1(b), in SBFD, the frequency resource (frequency band) is divided into multiple subbands (also called bands, RB sets, subbands, or sub-BWPs (Bandwidth parts)), and transmission in different directions is supported on a subband basis. As shown in Figure 1(b), the base station can transmit and receive simultaneously on both the uplink and downlink (e.g., SBFD operation), and the terminal can transmit and receive on either the uplink or downlink in a given time resource (e.g., Half-duplex operation). For example, in the example in Figure 1(b), in the same time resource (e.g., slot or symbol), UE#1 communicates with the base station on the uplink, and UE#2 communicates with the base station on the downlink.

[0016] Figure 2 shows an example of operation for different base stations (e.g., gNB1 and gNB2) and terminals (e.g., UE#1 and UE#2) in Dynamic / flexible TDD operation. In Dynamic / flexible TDD operation, base stations and terminals operate in half-duplex mode, and the transmission direction may differ between different base stations.

[0017] In the example in Figure 2, gNB1 sends a DL to UE#1 and gNB2 receives an UL from UE#2 within the same time resource (for example, the same time slot or symbol).

[0018] [Inter-terminal interference in Dynamic / flexible TDD operations] In Dynamic / flexible TDD operations, various types of interference can occur. For example, cross-link interference (CLI) between terminals (UE-to-UE) and between base stations (gNB-to-gNB) can occur. Inter-terminal and inter-base station CLI significantly degrade reception characteristics, so countermeasures are required.

[0019] In the following, regarding CLI communication between terminals, the terminal that causes interference will be referred to as the "aggressor UE," and the terminal that is affected by the interference will be referred to as the "victim UE."

[0020] For example, in Dynamic / flexible TDD operation, as shown in Figure 2, different terminals may communicate in different directions at the same time. In this case, the terminal receiving DL (UE#1 in Figure 2) may receive CLI from the terminal transmitting UL (UE#2 in Figure 2), which may degrade the DL reception characteristics of UE#1.

[0021] One way to avoid such interference is for the victim UE to measure the CLI between terminals, report the measurement results to the base station, and for the base station to avoid the CLI between terminals by scheduling or other means based on the measurement results. For example, the base station may assign the victim UE's DL reception to a time resource different from the time resource to which the aggressor UE's UL transmission is allocated.

[0022] [Inter-terminal interference in SBFD operations] In SBFD operations, CLI (UE-to-UE CLI) can occur between terminals within the same cell.

[0023] Figure 3 shows an example of inter-terminal CLI in SBFD operation. In Figure 3, gNB1 performs SBFD operation, simultaneously receiving UL from terminal (UE#1) and transmitting DL to terminal (UE#2). As shown in Figure 3, UE#2, which receives DL from gNB1, may receive CLI from UE#1, which transmits UL to gNB1, potentially degrading the DL reception characteristics.

[0024] One way to avoid such CLIs between terminals is for the victim UE to measure the CLI between terminals, report the measurement results to the base station, and for the base station to avoid CLIs between terminals by scheduling or other means based on the measurement results. For example, the base station may assign the victim UE's DL reception to a time resource different from the time resource to which the aggressor UE's UL transmission is allocated.

[0025] [Regarding CLI measurement methods between devices] This section explains how to measure CLI usage between devices.

[0026] For example, the aggressor UE transmits a reference signal (e.g., SRS (Sounding Reference Signal)) or UL channel for CLI measurement, and the victim UE receives the reference signal or UL channel transmitted by the aggressor UE and performs CLI measurement. In this case, in order for the victim UE to know (or receive) the settings (configuration) of the reference signal or UL channel for measurement of the aggressor UE, information regarding the reference signal or UL channel for measurement may be shared between the terminals in advance.

[0027] Examples of CLI measurements include SRS-RSRP (RSRP: Reference Signal Received Power) or CLI-RSSI (RSSI: Received Signal Strength Indicator). SRS-RSRP is a measurement of the power of SRS signals received by a terminal from another terminal. CLI-RSSI is a measurement of the linear average of the total received power of the resources configured for measurement by the terminal. Note that CLI measurements are not limited to SRS-RSRP and CLI-RSSI; other values ​​may also be used.

[0028] For example, an aggressor UE may transmit an SRS, and a victim UE may receive the SRS transmitted from the aggressor UE and measure the SRS-RSRP. The victim UE may, for example, report multiple SRS-RSRPs to the base station.

[0029] Release 16 supports Layer 3-based inter-terminal CLI measurement and reporting. In Layer 3-based inter-terminal CLI measurement and reporting, terminals average (filter) multiple CLI measurements before reporting. As a result, the reporting cycle for measurement values ​​in Layer 3-based inter-terminal CLI measurement and reporting is on the order of several hundred milliseconds. In SBFD operations, inter-terminal CLI measurement values ​​are expected to be reflected in the scheduling, but in Layer 3-based inter-terminal CLI measurement and reporting, the reporting cycle of measurement values ​​is longer than the cycle expected in the scheduling, making it difficult to reflect them in the scheduling of SBFD operations.

[0030] In response to this, Release 19 is considering supporting Layer 1-based inter-terminal CLI measurement and reporting. In Layer 1-based inter-terminal CLI measurement and reporting, terminals report the measured values ​​to the base station using UCI (Uplink Control Information) without averaging the CLI measurements. This shortens the reporting cycle compared to Layer 3-based inter-terminal CLI measurement and reporting, making it possible to reflect inter-terminal CLI measurements in the scheduling of SBFD operations.

[0031] [CSI Report-Based Layer 1 Inter-Terminal CLI Measurement and Reporting] Layer 1 inter-terminal CLI measurement and reporting is being considered, for example, based on the framework of existing Layer 1-based CSI (Channel State Information) reports.

[0032] In a CSI report, for example, a terminal uses at least one of the CSI-RS (Reference Signal) and SSB (Synchronization Signal Block) transmitted from the base station to the terminal to measure values ​​such as channel quality information (e.g., CQI (Channel Quality Indicator)), transmission rank, and L1-RSRP (L1: Layer 1), and reports a report containing the measured values ​​to the base station.

[0033] The report quantity in a CSI report is defined as, for example, L1-RSRP, L1-SINR, or CQI. In a CSI report, the base station configures the terminal being measured, including the operation in the reporting time domain (e.g., periodic, quasi-periodic, or aperiodic reporting), the report configuration that sets the values ​​to be reported, and the resource configuration that includes information on the resources being measured.

[0034] The terminal, for example, quantizes the measured values ​​and configures (or stores / places) them in a CSI field. Each report number, which identifies multiple reports to be reported, is associated with a CSI field. For example, the Uplink Control Information (UCI) bit sequence corresponds to one of the multiple report numbers reported by the terminal.

[0035] Release 19 is considering adding SRS-RSRP and CLI-RSSI for CLI reports to the report quantity of CSI reports. Therefore, SRS-RSRP and CLI-RSSI for CLI reports may be linked to UCI bit sequences using the CSI field.

[0036] Figure 4 shows an example of the configuration of a CSI field for CLI reporting. The CSI field can report up to four CLI measurement resources (e.g., an index number that identifies the CLI measurement resource) and CLI measurement values ​​measured using the CLI measurement resource. As shown in Figure 4, the first row of the CSI field, the CLI resource index (e.g., SRS resource index or CLI RSSI resource index #1), reports the CLI resource on which the CLI was measured, and the fifth row of the CSI field reports the CLI measurement value (e.g., SRS-RSRP or CLI-RSSI #1) measured using the CLI resource corresponding to the first row. The same applies to the other rows of the CSI field.

[0037] Furthermore, in the CSI field, CLI measurement values ​​may be reported (arranged) in descending order from largest to smallest. For example, in the example in Figure 4, the largest CLI measurement value (absolute value) among the CLI measurement values ​​measured by the terminal is set in "SRS-RSRP or CLI-RSSI #1". Hereafter, reporting the largest CLI measurement value will be referred to as "absolute value reporting".

[0038] Furthermore, other CLI measurements (for example, SRS-RSRP or CLI-RSSI #2 to #4 shown in Figure 4) are set in descending order among the CLI measurements measured by the terminal, excluding the largest CLI measurement. At this time, the terminal calculates the difference between the absolute value report and other CLI measurements that differ from the absolute value report, and sets the difference value. Hereinafter, the reporting of the difference value will be referred to as the "differential value report".

[0039] The above describes Layer 1-based inter-terminal CLI measurement and reporting based on CSI reports.

[0040] In Layer 1-based inter-terminal CLI (e.g., SRS-RSRP) measurement and reporting, there may be cases where a terminal cannot receive (or detect) one or more SRSs for CLI measurement. How the terminal reports the measurement in such cases has not been sufficiently considered. Furthermore, since differential reporting may be supported in Layer 1-based inter-terminal CLI measurement and reporting, there is room to consider how the terminal calculates the differential report when it cannot receive an SRS for CLI measurement.

[0041] Non-limiting embodiments of this disclosure describe a method for appropriately performing Layer 1-based inter-terminal CLI measurement and reporting even when a terminal cannot receive one or more SRSs for CLI measurement.

[0042] [Measurement Range, Resolution, and Bit Width in Layer 1-Based Inter-Terminal CLI Measurement and Reporting] Release 19 discusses the measurement range, resolution for quantization, and reporting bit width (bit size) for absolute and differential value reporting in Layer 1-based inter-terminal CLI measurement and reporting.

[0043] For example, the measurement range and resolution used for quantization in Layer 1-based inter-terminal CLI measurements and reports can be reused from the measurement range and resolution of the CLI report in Release 16 (L3-based).

[0044] For example, the measurement value range in the case of CLI-RSSI is from -100 dBm to -25 dBm, and the measurement value range in the case of SRS-RSRP is from -140 dBm to -44 dBm, which can be reused for layer 1-based CLI measurement and reporting between terminals.

[0045] Also, 1 dBm can be reused for the resolution in quantization for layer 1-based CLI measurement and reporting between terminals.

[0046] Also, regarding the bit width of layer 1-based CLI measurement and reporting between terminals, the reporting bit width of L1-RSRP in the existing CSI report can be reused. For example, a 7-bit width for absolute value reporting and a 4-bit width for differential value reporting can be reused for the bit width of layer 1-based CLI measurement and reporting between terminals.

[0047] [Blocking Problem in Release 16 SRS-RSRP] In the CLI measurement between terminals by SRS-RSRP measurement, a blocking problem may occur. The blocking problem is described below.

[0048] As described above, the aggressor UE transmits SRS for CLI measurement, and the victim UE receives SRS for CLI measurement. Here, it is difficult for the base station to grasp the detailed positions of the victim UE and the aggressor UE. For example, when the victim UE and the aggressor UE are in a very close proximity, the transmission power of the SRS from the aggressor UE is extremely high (too strong), and there is a possibility that the receiver of the victim UE (e.g., RF or analog circuit) may saturate. This is called the "blocking problem".

[0049] When the blocking problem occurs, the victim UE cannot detect the SRS, and thus cannot calculate (measure) the CLI measurement value (e.g., SRS-RSRP).

[0050] Release 16 of SRS-RSRP enables CLI reporting that takes blocking issues into account. Figure 5 shows an example of a quantization mapping table in the Release 16 SRS-RSRP report. As shown in Figure 5, the terminal that measures SRS-RSRP quantizes the measured value (e.g., measured quantity value) to the reported value. For example, if the measured value is -45.5 dBm, the quantized measured value (reported value) will be 'SRS-RSRP_95'.

[0051] As shown in Figure 5, if a terminal cannot detect the SRS due to a blocking problem, the terminal reports 'SRS-RSRP_98' to the base station, which corresponds to 'Infinity' indicating that the SRS cannot be detected.

[0052] [Overview of the Communication System] A communication system according to one aspect of this disclosure may include, for example, a base station 100 (e.g., gNB) shown in Figures 6 and 8, and a terminal 200 (e.g., UE) shown in Figures 7 and 9. Multiple base stations 100 and terminals 200 may exist in the communication system.

[0053] Figure 6 is a block diagram showing a partial configuration example of a base station 100 according to one aspect of the present disclosure. In the base station 100 shown in Figure 6, the receiving unit (corresponding to, for example, a receiving circuit) receives information indicating that the crosslink interference measurement signal (e.g., SRS) is undetectable, using at least one of a first field (absolute value reporting field) that reports the absolute value of the measured value and a second field (difference value reporting field) that reports the difference value of the measured value relative to the absolute value, which constitute control information (e.g., CLI measurement report or UCI) that reports multiple measured values ​​of crosslink interference between terminals. The control unit (corresponding to, for example, a control circuit) schedules the terminal 200 based on the information indicating undetectable interference.

[0054] Figure 7 is a block diagram showing a partial configuration example of a terminal 200 according to one aspect of the present disclosure. In the terminal 200 shown in Figure 7, the control unit (for example, corresponding to a control circuit) determines whether or not a measurement signal (e.g., SRS) for crosslink interference between terminals is detected. If the measurement signal is not detected, the transmitting unit (for example, corresponding to a transmitting circuit) transmits information indicating that the measurement signal cannot be detected, using at least one of the following: a first field (absolute value reporting field) that reports the absolute value of the measurement, and a second field (difference value reporting field) that reports the difference value of the measurement relative to the absolute value, which constitute control information (e.g., CLI measurement report or UCI) that reports multiple measurement values ​​of crosslink interference.

[0055] [Base Station Configuration] Figure 8 is a block diagram showing an example configuration of a base station 100 according to one aspect of the present disclosure. In Figure 8, the base station 100 includes a receiving unit 101, a demodulation / decoding unit 102, an inter-terminal CLI determination unit 103, a scheduling unit 104, a control information holding unit 105, a data / control information generation unit 106, an encoding / modulation unit 107, and a transmission unit 108.

[0056] For example, at least one of the demodulation / decoding unit 102, the terminal-to-terminal CLI determination unit 103, the scheduling unit 104, the control information holding unit 105, the data / control information generation unit 106, and the encoding / modulation unit 107 may be included in the control unit shown in Figure 6, and the receiving unit 101 may be included in the receiving unit shown in Figure 6.

[0057] The receiving unit 101 performs reception processing on the received signal received via the antenna, for example, such as down-conversion or A / D conversion, and outputs the processed received signal to the demodulation / decoding unit 102.

[0058] The demodulation / decoding unit 102 demodulates and decodes the received signal input from the receiving unit 101, for example, and outputs the decoding result to the scheduling unit 104. Furthermore, if the decoding result includes a CLI measurement report (for example, SRS-RSRP report information), the demodulation / decoding unit 102 outputs the CLI measurement report to the inter-terminal CLI determination unit 103.

[0059] The terminal-to-terminal CLI determination unit 103 determines the combination of terminals 200 according to the terminal-to-terminal CLI based on, for example, the CLI measurement report (e.g., SRS-RSRP report information) input from the demodulation / decoding unit 102 and the control information input from the control information holding unit 105, and outputs the determination result (e.g., terminal 200 combination information) to the scheduling unit 104. For example, the terminal-to-terminal CLI determination unit 103 may determine a combination of terminals 200 with a strong terminal-to-terminal CLI or a combination of terminals 200 with a weak terminal-to-terminal CLI. The determination of whether terminals 200 have a strong or weak terminal-to-terminal CLI may be made, for example, based on a comparison of the terminal-to-terminal CLI with a threshold.

[0060] The scheduling unit 104 may, for example, perform scheduling for the terminals 200. Based on, for example, the decoding result input from the demodulation / decoding unit 102, the combination information of the terminals 200 input from the terminal-to-terminal CLI determination unit 103, and the control information input from the control information holding unit 105, the scheduling unit 104 schedules the transmission and reception of each terminal 200 and issues a data / control information generation instruction to the data / control information generation unit 106 to generate at least one of the data and control information. The scheduling unit 104 also outputs the scheduling information to the control information holding unit 105.

[0061] The control information holding unit 105 holds control information input from, for example, the scheduling unit 104. The control information may include, for example, the configuration of the SRS, which includes information about the SRS assigned to the terminal 200, the configuration of the SRS-RSRP report, or SRS-RSRP information measured in the past. The control information holding unit 105 may, for example, output the held information to each component of the base station 100 (for example, the terminal-to-terminal CLI determination unit 103 and the scheduling unit 104) as needed.

[0062] The data and control information generation unit 106 generates at least one of data and control information according to instructions from, for example, the scheduling unit 104, and outputs a signal containing the generated data or control information to the encoding and modulation unit 107. The generated data and control information may include, for example, at least one of upper-layer signaling information and downlink control information.

[0063] The encoding and modulation unit 107 encodes and modulates the signal input from, for example, the data and control information generation unit 106, and outputs the modulated signal to the transmission unit 108.

[0064] The transmitting unit 108 performs transmission processing such as D / A conversion, upconversion, or amplification on the signal input from the encoding / modulation unit 107, and transmits the resulting wireless signal from the antenna to the terminal 200.

[0065] [Terminal Configuration] Figure 9 is a block diagram showing an example configuration of a terminal 200 according to one aspect of the present disclosure. In Figure 9, the terminal 200 includes a receiving unit 201, a demodulation / decoding unit 202, an SRS receiving unit 203, a control information holding unit 204, an inter-terminal report setting unit 205, a transmission control unit 206, an SRS generation unit 207, a data / control information generation unit 208, an encoding / modulation unit 209, and a transmission unit 210.

[0066] For example, at least one of the demodulation / decoding unit 202, SRS receiving unit 203, control information holding unit 204, inter-terminal report setting unit 205, transmission control unit 206, SRS generation unit 207, data / control information generation unit 208, and encoding / modulation unit 209 may be included in the control unit shown in Figure 7, and the transmission unit 210 may be included in the transmission unit shown in Figure 7.

[0067] The receiving unit 201 performs reception processing, such as down-conversion or A / D conversion, on the received signal received via the antenna, and outputs the processed received signal to the demodulation / decoding unit 202. Furthermore, if the power of the received signal is too strong and reception processing cannot be performed (for example, if a blocking problem occurs), the receiving unit 201 outputs information regarding power saturation to the terminal report setting unit 205.

[0068] The demodulation / decoding unit 202 demodulates and decodes the received signal input from the receiving unit 201, for example, and outputs the decoded result to the transmission control unit 206. Furthermore, if the received signal contains SRS information to be measured, the demodulation / decoding unit 202 outputs the SRS information to the SRS receiving unit 203.

[0069] The SRS receiving unit 203 extracts an SRS received signal from the SRS information input from the demodulation / decoding unit 202, based on the SRS setting information input from the control information holding unit 204, for example. The SRS receiving unit 203 measures the SRS based on information such as the resource configuration and report configuration of the SRS-RSRP report input from the control information holding unit 204, and the extracted SRS received signal, and outputs the measurement result to the terminal-to-terminal report setting unit 205.

[0070] The control information holding unit 204 holds control information, including, for example, signaling information such as resource configuration information, report configuration information, and setting information related to SRS transmission for SRS-RSRP reports, which is input from the transmission control unit 206, and outputs the held information to each component (for example, the SRS receiving unit 203, the inter-terminal report setting unit 205, and the transmission control unit 206) as needed.

[0071] The inter-terminal report setting unit 205 configures CSI fields for inter-terminal CLI reports (for example, fields for absolute value reporting and fields for differential value reporting) based on, for example, the SRS measurement values ​​input from the SRS receiving unit 203 and the settings for inter-terminal CLI measurement reports input from the control information holding unit 204, and outputs them to the transmission control unit 206.

[0072] Furthermore, the inter-terminal report setting unit 205 determines whether SRS-RSRP measurement is possible based on, for example, the SRS settings input from the control information holding unit 204 (e.g., SRS time allocation) and the power saturation information input from the receiving unit 201. If the inter-terminal report setting unit 205 determines that SRS-RSRP measurement is not possible, it may set a report value to be used when SRS cannot be received (or detected) (e.g., a dedicated report value; for example, a value corresponding to 'Infinity' or 'Invalid' described later). Based on the measured value input from the SRS receiving unit 203, the settings related to the inter-terminal CLI measurement report input from the control information holding unit, and the report value to be used when SRS cannot be received, the inter-terminal report setting unit 205 configures a CSI field for the inter-terminal CLI report and outputs it to the transmission control unit 206.

[0073] The transmission control unit 206 outputs signaling information (for example, resource configuration information, report configuration information, and settings related to SRS transmission for the SRS-RSRP report) included in the decoding result input from the demodulation / decoding unit 202 to the control information holding unit 204. The transmission control unit 206 may also instruct the data / control information generation unit 208 to generate at least one of data and control information based on, for example, control information input from the control information holding unit 204 or the decoding result input from the demodulation / decoding unit 202 (for example, downlink control information). The transmission control unit 206 may also instruct the SRS generation unit 207 to generate SRS and output signaling information related to SRS transmission based on the control information input from the control information holding unit 204 and the downlink control information input from the demodulation / decoding unit 202. The transmission control unit 206 also outputs measured values ​​(reported values) to the data / control information generation unit 208 based on information input from the inter-terminal report setting unit 205.

[0074] The SRS generation unit 207 generates a code sequence for SRS based on signaling information related to SRS transmission input from, for example, the transmission control unit 206. The SRS generation unit 207 outputs the generated code sequence as SRS to the encoding and modulation unit 209.

[0075] The data / control information generation unit 208 generates data or control information, for example, according to instructions from the transmission control unit 206. The data / control information generation unit 208 outputs a signal containing the generated data or control information to the encoding / modulation unit 209.

[0076] The encoding and modulation unit 209 encodes and modulates, for example, the signal input from the data and control information generation unit 208 and the SRS input from the SRS generation unit 207, and outputs the modulated transmission signal to the transmission unit 210.

[0077] The transmitting unit 210 performs transmission processing such as D / A conversion, upconversion, or amplification on the signal input from the encoding / modulation unit 209, and transmits the resulting radio signal from the antenna to the base station 100.

[0078] [Operation of Base Station 100 and Terminal 200] An example of operation of the base station 100 and terminal 200 having the above configuration will be described below.

[0079] Figure 10 is a sequence diagram showing an example of the operation of the base station 100 and terminal 200. In the example in Figure 10, for example, terminal 200a is an aggressor UE and terminal 200b is a victim UE. Note that terminal 200 may be configured to perform both the operations of terminal 200a and terminal 200b shown in Figure 10.

[0080] In Figure 10, the base station 100 determines the settings (configuration) for SRS transmission (S101) and transmits signaling information including the determined configuration to the terminal 200a (S102). The terminal 200a configures the SRS transmission settings based on the configuration included in the received signaling information (S103).

[0081] The base station 100 determines the settings (configuration) for SRS measurement (S104) and transmits signaling information including the determined configuration to the terminal 200b (S105). Based on the configuration included in the received signaling information, the terminal 200b configures, for example, the resources and report settings for the SRS-RSRP report (S106).

[0082] Terminal 200a transmits an SRS to base station 100 based on the SRS transmission settings (S107). At this time, terminal 200b determines whether or not it was able to receive (or detect) the SRS transmitted by terminal 200a (S108).

[0083] If SRS is received (detected) (S108: Yes), terminal 200b performs a measurement using the detected SRS (S109) and sets the CSI field using the measurement result (S110). On the other hand, if SRS cannot be received (detected) (S108: No), terminal 200b sets the CSI field using, for example, information indicating that SRS could not be detected (S110).

[0084] Terminal 200b transmits a UCI containing the configured CSI field to base station 100 based on the report settings of the SRS-RSRP report (S111).

[0085] [Method for setting CSI fields in inter-terminal CLI reports] Next, an example of a method for setting CSI fields in inter-terminal CLI reports according to a non-limiting embodiment of this disclosure will be described.

[0086] For example, the method for setting the CSI field in the base station 100 (e.g., the inter-terminal CLI determination unit 103, the scheduling unit 104) and the terminal 200 (e.g., the SRS receiving unit 203, the inter-terminal report setting unit 205, the transmission control unit 206) will be described.

[0087] The following describes, for example, a method for reporting information indicating that terminal 200 cannot detect SRS for inter-terminal CLI measurement (CSI field setting method 1), and a method for reporting information indicating that terminal 200 cannot detect SRS and the remaining measured SRS-RSRP (CSI field setting method 2).

[0088] [CSI Field Setting Method 1] In setting method 1, terminal 200 sets information indicating that SRS cannot be detected (SRS undetectable) (hereinafter referred to as "SRS undetectable information") in the CSI field, and does not set other information (for example, measured values ​​based on other detected SRS) in the CSI field.

[0089] For example, if terminal 200 cannot detect an SRS for inter-terminal CLI measurement, terminal 200 sets the CSI field with the index number of the undetectable SRS resource and a quantized measurement value (quantized value) indicating that the SRS could not be detected.

[0090] Quantized values ​​indicating that SRS cannot be detected (SRS undetectable information) may be defined, for example, in a quantization table for a Layer 1-based SRS-RSRP. Figure 11 shows an example of a quantization table for a Layer 1-based SRS-RSRP.

[0091] Figure 11(a) shows an example of a quantization table in absolute value reporting. In the quantization table shown in Figure 11(a), the bit size of the absolute value report is 7 bits (e.g., 128 values ​​from RSRP_0 to RSRP_127), the resolution of the absolute value report is 1 bit (e.g., 1 dBm), and the measurement range of the absolute value report is from -44 dBm to -140 dBm. In Figure 11(a), measurements (RSRP) lower than -140 dBm are quantized to RSRP_16, and measurements (RSRP) above -44 dBm are quantized to RSRP_113.

[0092] Furthermore, RSRP_127, one of the quantized values ​​(Reported values) shown in Figure 11(a), is set to 'Infinity'. 'Infinity' for RSRP_127 means that the signal power is too strong for terminal 200 to detect the SRS (i.e., SRS is undetectable, or a blocking problem occurs).

[0093] Figure 11(b) shows an example of a quantization table in differential value reporting. In the quantization table shown in Figure 11(b), the bit size of the differential value report is 4 bits (e.g., 16 values ​​from DIFFRSRP_0 to DIFFRSRP_15), the resolution of the differential value report is 2 bits (e.g., 2 dB), and the range of the differential value report is from 0 dB to -28 dB. In Figure 11(b), differential value reports below -28 dB are quantized to DIFFRSRP_14.

[0094] Furthermore, DIFFRSRP_15, one of the quantized values ​​(Reported values) shown in Figure 11(b), is set to 'Invalid'. 'Invalid' for DIFFRSRP_15 means, for example, that the UE cannot calculate the difference value report if the absolute value report is set to 'Infinity' (e.g., RSRP_127).

[0095] Furthermore, for example, if terminal 200 cannot detect multiple SRSs, terminal 200 may report SRS undetectable information using both absolute value reporting and differential value reporting. In this case, terminal 200 may use 'Invalid' (DIFFRSRP_15) as the differential value report, for example. Terminal 200 may also use 'Invalid' (DIFFRSRP_15) when reporting that it could not detect the SRS corresponding to the differential value report.

[0096] In the CSI field setting method 1 using the Layer 1-based quantization table for SRS-RSRP described above, examples include reporting with an immutable UCI payload size (setting method 1-1 below) and reporting with a variable UCI payload size (setting method 1-2 below).

[0097] <Setting Method 1-1> In Setting Method 1-1, the terminal 200 sets the SRS undetectable information while maintaining the UCI payload size, and does not set any other information (for example, measurement information). According to Setting Method 1-1, the base station 100 can receive a UCI with an unchanging payload size regardless of whether the terminal 200 was able to detect the SRS, and therefore can accurately decode the UCI.

[0098] The quantization table used in setting method 1-1 may be, for example, the layer 1-based SRS-RSRP quantization table defined in setting method 1 described above (see, for example, Figure 11).

[0099] For example, if terminal 200 cannot detect SRS, the CSI field may be set to "Infinity" (RSRP_127) for absolute value reporting and to "Invalid" (DIFFRSRP_15) for differential value reporting, and the inter-terminal CLI may be reported.

[0100] Furthermore, if terminal 200 cannot detect SRS, no report will be made in unused fields in the CSI field, and such fields may be filled with 0 or 1, or specific values ​​may be set.

[0101] Thus, if terminal 200 cannot detect SRS, it transmits SRS undetectable information using the absolute value reporting field and the difference value reporting field of the CSI field, and does not need to transmit other SRS measurements (for example, measurements of SRS that were detected).

[0102] Figure 12 shows an example of setting the CSI field according to setting method 1-1.

[0103] In the CSI report #n shown in Figure 12, the CSI fields used for the CLI report (for example, CSI fields specifically for the CLI report) are configured.

[0104] For example, base station 100 sets seven configurations, SRS resources #1 to #7, for CLI measurement on terminal 200 to be measured. In this case, the number of bits N used in the CLI resource index report (e.g., SRS resource index) is 3 bits.

[0105] In the example shown in Figure 12, the base station 100 instructs the terminal 200 to be measured to report four measurement values ​​(for example, one absolute value report and three difference value reports).

[0106] Figure 12 illustrates, as an example, a case where the terminal 200 under measurement cannot detect the signals corresponding to SRS resources (e.g., SRS) because the received power of SRS resource #1 and SRS resource #4 is too strong (a blocking problem occurs in SRS resource #1 and SRS resource #4).

[0107] In this case, as shown in Figure 12, terminal 200 sets the index numbers of SRS resource #1 and SRS resource #4, and SRS undetectable information (e.g., Infinity (RSRP_127) and Invalid (DIFFRSRP_15)) in the CSI field. In Figure 12, terminal 200 sets '001' (index number of SRS resource #1) in the first row of the CSI field (3 bits) and '010' (index number of SRS resource #4) in the second row of the CSI field (3 bits). Also in Figure 12, terminal 200 sets '1111111' (RSRP_127), corresponding to 'Infinity', as the reported value corresponding to the set resource in the fifth row of the CSI field (7 bits) as the absolute value report, and sets '1111' (DIFFRSRP_15), corresponding to 'Invalid', as the first difference value report in the sixth row of the CSI field (4 bits).

[0108] Furthermore, terminal 200 does not set measurement values ​​for SRS resources other than those for which it cannot detect the aforementioned SRS in the CSI field. As shown in Figure 12, unused CSI fields may be filled with 0.

[0109] Based on the inter-terminal CLI report shown in Figure 12, the base station 100 can determine (identify) the possibility that a terminal 200 that transmitted SRS using SRS resource #1 and SRS resource #4 (e.g., an aggressor UE) and a terminal 200 that measured SRS (e.g., a victim UE) are in close proximity, and determine that the impact of inter-terminal CLI is significant. Based on this information, the base station 100 can adjust the scheduling for these terminals 200 to avoid (or reduce) inter-terminal CLI.

[0110] According to setting method 1-1, terminal 200 prioritizes reporting information indicating that it cannot detect SRS. This allows base station 100 to identify terminals 200 with high inter-terminal CLI, and thus prioritize CLI reduction processing for those terminals 200 with high inter-terminal CLI.

[0111] <Setting Method 1-2> In Setting Method 1-2, the terminal 200 sets the UCI payload size to be variable, sets the SRS undetectable information, and does not set other information (e.g., measurement information). For example, the terminal 200 may determine the UCI payload size according to the number of resources (SRS resources) for which SRS is not detected.

[0112] In configuration method 1-2, if terminal 200 changes the UCI payload size, base station 100 may not be able to decode the UCI because the configured UCI payload size and the UCI payload size reported by terminal 200 do not match. Therefore, when the UCI payload size is changed, terminal 200 is expected to notify base station 100 of the changed UCI payload size.

[0113] For example, terminal 200 may report an inter-terminal CLI report using CSI report part 1 and part 2.

[0114] CSI report parts 1 and 2 may be reported using the same PUSCH format, for example (e.g., a non-periodic or quasi-periodic CSI report). On the other hand, if CSI report part 1 is reported but CSI report part 2 is not, CSI report part 1 may be reported using PUCCH format, for example (e.g., a periodic or quasi-periodic CSI report).

[0115] Furthermore, CSI report parts 1 and 2 may be encoded separately, with CSI report part 2 being transmitted after CSI report part 1. Therefore, base station 100 can determine the payload size of CSI report part 2 based on CSI report part 1. For example, even if the data size of CSI report part 2 is variable, terminal 200 can still notify the payload size of CSI report part 2 via CSI report part 1.

[0116] Therefore, in setting method 1-2, for example, CSI report part 1 may contain information regarding the number of SRS resources reported in CSI report part 2 (or the payload size of CSI report part 2). In addition, CSI report part 2 may contain the SRS resources to be reported (e.g., SRS resource index) and the measured values ​​corresponding to the resources to be reported (e.g., absolute value report and differential value report). As a result, the base station 100 can identify the number of resources reported from the terminal 200 as an inter-terminal CLI report based on CSI report part 1, and identify the measured values ​​for each resource based on CSI report part 2.

[0117] Another way to make the UCI payload size variable is for base station 100 to perform blind detection on the number of reported resources.

[0118] In a blind detection method for the reported number of resources, the base station 100 assumes, for example, multiple UCI payload size patterns and decodes the UCI based on multiple (e.g., all) patterns. If the base station 100 successfully decodes the UCI based on a certain pattern, it identifies (confirms) that the terminal 200 used the payload size of the UCI of that pattern.

[0119] For example, Pattern 1 may be a pattern with one piece of information (SRS resource) that SRS cannot detect, Pattern 2 may be a pattern with two pieces of information (SRS resource) that SRS cannot detect, Pattern 3 may be a pattern with three pieces of information (SRS resource) that SRS cannot detect, and Pattern 4 may be a case with four pieces of information (SRS resource) that SRS cannot detect. The base station 100 decodes the UCI for each of the patterns defined in this way. The quantization table used may also be a Layer 1-based quantization table for SRS-RSRP defined in the CSI field setting method 1 (see, for example, Figure 11).

[0120] In configuration method 1-2, the UCI payload size is set to be variable, allowing terminal 200 to reduce the overhead of inter-terminal CLI reporting (e.g., number of reported bits) depending on the number of resources that cannot detect the SRS.

[0121] The above explains the CSI field setting methods 1-1 and 1-2.

[0122] Thus, in setting method 1, terminal 200 transmits SRS undetectable information using the CSI field (field for absolute value reporting or field for differential value reporting) and does not transmit SRS measurement values.

[0123] As a result, even if a blocking problem occurs, terminal 200 (e.g., victim UE) can report to base station 100 in Layer 1-based inter-terminal CLI measurement and reporting that there is another terminal (e.g., aggressor UE) nearby that is giving a large CLI to terminal 200. Furthermore, base station 100 can reduce inter-terminal CLI by scheduling for terminal 200 based on the reported information.

[0124] [Method 2 for setting the CSI field] In method 2, the terminal 200 sets information indicating that SRS cannot be detected (SRS undetectable information) and the measured value of the detected SRS in the CSI field.

[0125] For example, if terminal 200 cannot detect an SRS for inter-terminal CLI measurement, terminal 200 sets the CSI field with the index number of the undetectable SRS resource and a quantized measurement value (quantized value) indicating that the SRS could not be detected.

[0126] Furthermore, terminal 200 sets the index number of the detected SRS resource and the quantized measurement value of the detected SRS in the remaining CSI fields, which are different from the CSI fields used for the SRS undetectable information.

[0127] Here, when reporting both undetectable SRS information and detected SRS measurements in a single CSI report, there is room to consider how to calculate the difference value report. For example, in existing methods, the difference value report is calculated based on the absolute value report. However, if 'Infinity' is set for the absolute value report, the terminal 200 does not calculate the measurement for the absolute value report, making it difficult to calculate the difference value report based on the absolute value report.

[0128] The following describes an example of how to calculate the difference value report in setting method 2.

[0129] For example, in setting method 2, there are two methods: one in which the difference value report is calculated as the difference value from a predetermined reference value (setting method 2-1 below), and another in which the difference value report is calculated within the measured values ​​measured by terminal 200 (setting method 2-2 below).

[0130] <Setting Method 2-1> In Setting Method 2-1, if terminal 200 cannot detect SRS for inter-terminal CLI measurement, it sets SRS undetectable information and the measured value of the detected SRS in the CSI field. For example, terminal 200 sets SRS undetectable information in the absolute value report and difference value report fields of the CSI field, and sets the measured value (difference value) in the difference value report field.

[0131] At this time, terminal 200 calculates a difference value report as the difference between the measured value and a specified reference value, using the detected SRS measurement value as the measurement value. The reference value may be defined in a specification (standard), for example, or it may be notified to terminal 200 by RRC signaling, MAC CE, or DCI.

[0132] The quantization table used in setting method 2-1 may be, for example, the layer 1-based SRS-RSRP quantization table defined in setting method 1 of the CSI field (see, for example, Figure 11).

[0133] For example, SRS undetectable information may be reported using "Infinity" (RSRP_127) in absolute value reports and "Invalid" (DIFFRSRP_15) in differential value reports.

[0134] Furthermore, other CSI fields not used for SRS undetectable information may be set to the SRS-RSRP measured by terminal 200. For example, when terminal 200 sets SRS-RSRP in the CSI field for difference value reporting, it calculates the difference between the reference value and the measured value of SRS-RSRP.

[0135] In this manner, if terminal 200 cannot detect SRS, it transmits SRS undetectable information and other SRS measurement values ​​(for example, measurement values ​​of SRS that were detected) using the absolute value reporting field and the difference value reporting field of the CSI field.

[0136] Figure 13 shows an example of setting the CSI field according to setting method 2-1.

[0137] In the CSI report #n shown in Figure 13, the CSI fields used for the CLI report (for example, CSI fields specifically for the CLI report) are configured.

[0138] For example, base station 100 sets seven configurations, SRS resources #1 to #7, for CLI measurement on terminal 200 to be measured. In this case, the number of bits N used in the CLI resource index report (e.g., SRS resource index) is 3 bits.

[0139] In addition, in the example shown in Figure 13, the base station 100 instructs the terminal 200 to be measured to report four measurement values ​​(for example, one absolute value report and three difference value reports).

[0140] Additionally, -43 dBm is set as the reference value for reporting the difference value on terminal 200. Note that the reference value is not limited to -43 dBm; other values ​​may also be used.

[0141] Figure 13 illustrates, as an example, a case where the terminal 200 under measurement cannot detect the signals corresponding to SRS resources (e.g., SRS) because the received power of SRS resource #1 and SRS resource #4 is too strong (a blocking problem occurs in SRS resource #1 and SRS resource #4).

[0142] In this case, as shown in Figure 13, terminal 200 sets the index numbers of SRS resource #1 and SRS resource #4, and SRS undetectable information (e.g., Infinity (RSRP_127) and Invalid (DIFFRSRP_15)) in the CSI field. In Figure 13, terminal 200 sets '001' (index number of SRS resource #1) in the first row of the CSI field (3 bits) and '100' (index number of SRS resource #4) in the second row of the CSI field (3 bits). Also in Figure 13, terminal 200 sets '1111111' (RSRP_127), corresponding to 'Infinity', as the reported value corresponding to the set resource in the fifth row of the CSI field (7 bits) as the absolute value report, and sets '1111' (DIFFRSRP_15), corresponding to 'Invalid', as the first difference value report in the sixth row of the CSI field (4 bits).

[0143] Furthermore, as shown in Figure 13, terminal 200 sets the measured values ​​of the remaining SRS resources in descending order to the remaining CSI fields (for example, the CSI fields for difference value reporting).

[0144] At this time, terminal 200 may calculate the difference value using the set reference value (e.g., -43 dBm). For example, consider the case where, among the SRS resources measured by terminal 200, the measured value of SRS resource #3 (e.g., -65 dBm) is the largest, and the measured value of SRS resource #2 (e.g., -68 dBm) is the second largest. In this case, as shown in Figure 13, terminal 200 sets the index numbers of SRS resource #3 and SRS resource #2, and the information of DIFFRSRP_11, which is the difference value report for SRS resource #3 (e.g., difference value using the reference value: -22 dB), and DIFFRSRP_12, which is the difference value report for SRS resource #2 (e.g., difference value using the reference value: -25 dB), in the CSI field.

[0145] Therefore, in Figure 13, terminal 200 sets '011' (index number of SRS resource #3) in the 3rd row CSI field (3 bits) and '010' (index number of SRS resource #2) in the 4th row CSI field (3 bits). Also in Figure 13, terminal 200 sets '1011' (DIFFRSRP_11) as the second difference value report in the 7th row CSI field (4 bits) as the report value corresponding to the set resource, and sets '1100' (DIFFRSRP_12) as the third difference value report in the 8th row CSI field (4 bits).

[0146] According to setting method 2-1, by using a reference value in the calculation of the difference value report, the SRS measurement value measured by terminal 200 is reported as a difference value report. This allows base station 100 to identify the remaining measurement values ​​measured by terminal 200, in addition to information indicating that SRS cannot be detected. For example, if the remaining measurement values ​​include large interference values, base station 100 can perform interference reduction processing based on those measurement values.

[0147] <Setting Method 2-2> In Setting Method 2-2, if terminal 200 cannot detect SRS for inter-terminal CLI measurement, it sets SRS undetectable information and the measured value of the detected SRS in the CSI field. For example, terminal 200 sets SRS undetectable information in the difference value report field of the CSI field, and sets the measured value (absolute value and difference value) in the absolute value report and difference value report fields.

[0148] At this time, terminal 200 sets information indicating that SRS cannot be detected (SRS undetectable information) in order from the fields after the CSI field. For example, terminal 200 sets the SRS undetectable information in the CSI field prioritizing the differential value reporting field over the absolute value reporting field.

[0149] Furthermore, terminal 200 sets the detected SRS measurements into absolute value reporting and difference value reporting in descending order of measurement values. For example, terminal 200 sets the largest measurement value (absolute value) among the detected SRS measurements into the absolute value reporting field, and sets the difference between the largest measurement value and the other detected SRS measurements into the difference value reporting field.

[0150] The quantization table used in setting method 2-2 may be a layer 1-based quantization table for SRS-RSRP defined in setting method 1 of the CSI field (see, for example, Figure 11).

[0151] In this way, if terminal 200 cannot detect SRS, it transmits SRS undetectable information using the difference value reporting field of the CSI field, transmits the maximum value of other SRS measurements (for example, SRS measurements that were detected) using the absolute value reporting field, and transmits the difference between the remaining SRS measurements and the maximum value using the difference value reporting field.

[0152] Figure 14 shows an example of setting the CSI field according to setting method 2-2.

[0153] In the CSI report #n shown in Figure 14, the CSI fields used for CLI reports (for example, CSI fields specifically for CLI reports) are configured.

[0154] For example, base station 100 sets seven configurations, SRS resources #1 to #7, for CLI measurement on terminal 200 to be measured. In this case, the number of bits N used in the CLI resource index (e.g., SRS resource index) report is 3 bits.

[0155] In the example shown in Figure 14, the base station 100 instructs the terminal 200 to be measured to report four measurement values ​​(for example, one absolute value report and three differential value reports).

[0156] Figure 14 illustrates, as an example, a case where the terminal 200 being measured cannot detect the signals corresponding to SRS resources (e.g., SRS) because the received power of SRS resource #1 and SRS resource #4 is too strong (a blocking problem occurs in SRS resource #1 and SRS resource #4).

[0157] In this case, as shown in Figure 14, terminal 200 sets the index numbers of SRS resource #1 and SRS resource #4, and SRS undetectable information (e.g., Invalid (DIFFRSRP_15)) in the later fields within the CSI field (e.g., the fields for the third and second difference value reports). In Figure 14, terminal 200 sets '001' (index number of SRS resource #1) in the 4th row CSI field (3 bits) and '100' (index number of SRS resource #4) in the 3rd row CSI field (3 bits). Also in Figure 14, terminal 200 sets '1111' (DIFFRSRP_15), corresponding to 'Invalid', as the report value corresponding to the set resource in the 8th row CSI field (4 bits) as the third difference value report, and sets '1111' (DIFFRSRP_15), corresponding to 'Invalid', as the second difference value report in the 7th row CSI field (4 bits).

[0158] Furthermore, as shown in Figure 14, terminal 200 sets the measured values ​​of the remaining SRS resources in descending order to the remaining CSI fields (e.g., absolute value reporting and difference value reporting fields). For example, terminal 200 sets the largest measured value among the remaining SRS resources to the absolute value reporting field and the second largest measured value to the first difference value reporting field. If there are three or more measured values ​​for the remaining SRS resources, they may be set in descending order to the largest measured values ​​in the CSI fields. In this case, terminal 200 calculates the difference value set in the first difference value reporting as the difference from the absolute value set in the absolute value reporting.

[0159] For example, consider the case in Figure 14 where, among the SRS resources measured by terminal 200, the measured value of SRS resource #3 (e.g., -65 dBm) is the largest, and the measured value of SRS resource #2 (e.g., -68 dBm) is the second largest. In this case, as shown in Figure 14, terminal 200 sets the index numbers of SRS resource #3 and SRS resource #2, RSRP_92 (quantized absolute value of the measured value of SRS resource #3), which is the absolute value report for SRS resource #3, and DIFFRSRP_01 (e.g., difference value from the measured value of SRS resource #3: -3 dB), which is the difference value report for SRS resource #2, in the CSI field.

[0160] Therefore, in Figure 14, terminal 200 sets '011' (index number of SRS resource #3) in the first row's CSI field (3 bits) and '010' (index number of SRS resource #2) in the second row's CSI field (3 bits). Also in Figure 14, terminal 200 sets '1011100' (RSRP_92) as the absolute value report in the fifth row's CSI field (7 bits) as the report value corresponding to the set resource, and sets '0001' (DIFFRSRP_1) as the first difference value report in the sixth row's CSI field (4 bits).

[0161] According to setting method 2-2, the SRS measurement values ​​detected by terminal 200 can be reported by absolute value reporting, making it possible to report measurement values ​​using a high-resolution quantization table.

[0162] The above explains the CSI field setting methods 2-1 and 2-2.

[0163] Thus, in setting method 2, terminal 200 transmits SRS undetectable information and SRS measurement values ​​using the CSI field (field for absolute value reporting and field for differential value reporting).

[0164] As a result, terminal 200 (e.g., victim UE) reports to base station 100, in Layer 1-based inter-terminal CLI measurement and reporting, that there is another terminal (e.g., aggressor UE) nearby that is giving a large CLI to the SRS resource where the blocking problem occurs. This allows base station 100 to reduce inter-terminal CLI by scheduling for terminal 200 based on the reported information.

[0165] Furthermore, terminal 200 (e.g., victim UE) reports measurements for SRS resources where blocking issues are not occurring. This allows base station 100 to adjust the scheduling of terminal 200 on resources with high inter-terminal CLI based on the reported information, thereby reducing inter-terminal CLI.

[0166] <Modification of Setting Method 2-2> In the modification of Setting Method 2-2, terminal 200 sets SRS undetectable information and the measured value of the detected SRS in the CSI field when it cannot detect the SRS for inter-terminal CLI measurement. For example, terminal 200 sets SRS undetectable information in the absolute value reporting field of the CSI field and sets the measured value (absolute value and difference value) in the difference value reporting field.

[0167] At this time, terminal 200 sets the SRS undetectable information in order, starting with the absolute value report of the CSI field.

[0168] Furthermore, terminal 200 sets the detected SRS measurement value in a remaining CSI field (a field for reporting the difference value) that is different from the CSI field in which the SRS undetectable information is set. For example, if terminal 200 sets the largest measurement value among the detected SRS measurement values ​​in the field for reporting the difference value, it may set a quantized value using a 4-bit absolute value reporting quantization table. Also, terminal 200 calculates the remaining measurement values ​​among the detected SRS measurement values, excluding the maximum value, as difference values ​​using the maximum value, and quantizes them.

[0169] Figure 15 shows an example of a quantization table for Layer 1-based SRS-RSRP related to a modified example of setting example 2-2. Figures 15(a) and (c) are the quantization tables for 7-bit absolute value reporting and 4-bit difference value reporting of the quantization table for Layer 1-based SRS-RSRP defined in CSI field setting method 1 (for example, Figures 11(a) and (b)). Figure 15(b) is an example of a quantization table for 4-bit absolute value reporting.

[0170] Figure 16 shows an example of setting the CSI field according to a modified version of setting method 2-2.

[0171] In the CSI report #n shown in Figure 16, the CSI fields used for the CLI report (for example, CSI fields specifically for the CLI report) are configured.

[0172] For example, base station 100 sets seven configurations, SRS resources #1 to #7, for CLI measurement on terminal 200 to be measured. In this case, the number of bits N used in the CLI resource index (e.g., SRS resource index) report is 3 bits.

[0173] In the example shown in Figure 16, the base station 100 instructs the terminal 200 to be measured to report four measurement values ​​(for example, one absolute value report and three differential value reports).

[0174] Figure 16 illustrates, as an example, a case where the terminal 200 under measurement cannot detect the signals corresponding to SRS resources (e.g., SRS) because the received power of SRS resource #1 and SRS resource #4 is too strong (a blocking problem occurs in SRS resource #1 and SRS resource #4).

[0175] In this case, as shown in Figure 16, terminal 200 sets the index numbers of SRS resource #1 and SRS resource #4, and SRS undetectable information (e.g., Infinity (RSRP_127 in Figure 15(a)), Invalid (DIFFRSRP_15 in Figure 15(c))) in the CSI fields (e.g., the fields for absolute value reporting and the first difference value reporting). In Figure 16, terminal 200 sets the first row of the CSI field (3 bits) to '001' (index number of SRS resource #1) and the second row of the CSI field (3 bits) to '100' (index number of SRS resource #4). Furthermore, in Figure 16, terminal 200 sets the absolute value report in the 7-bit CSI field on the 5th row, which corresponds to 'Infinity', to '111111' (RSRP_127), and sets the first differential value report in the 4-bit CSI field on the 6th row, which corresponds to 'Invalid', to '1111' (DIFFRSRP_15).

[0176] Furthermore, as shown in Figure 16, terminal 200 sets the measured values ​​of the remaining SRS resources in descending order to the remaining CSI fields (e.g., the difference value reporting fields). For example, terminal 200 sets the second difference value reporting field to a quantized value using a 4-bit absolute value reporting quantization table (e.g., the quantization table in Figure 15(b)). Terminal 200 also calculates the difference value using the absolute value (actual measured value) set in the second difference value reporting and sets the third difference value reporting field to a quantized value using a 4-bit difference value reporting quantization table (e.g., Figure 15(c)).

[0177] For example, in Figure 16, let's consider the case where, among the SRS resources measured by terminal 200, the measured value of SRS resource #3 (e.g., -65 dBm) is the largest, and the measured value of SRS resource #2 (e.g., -68 dBm) is the second largest. In this case, as shown in Figure 16, terminal 200 sets the index numbers of SRS resource #3 and SRS resource #2, RSRP_11 (the absolute value report for SRS resource #3, which is the value obtained by quantizing the measured value of SRS resource #3 using the 4-bit absolute value report quantization table shown in Figure 15(b)), and DIFFRSRP_01 (the difference value for SRS resource #2, which is the difference value (-3 dB) from the measured value of SRS resource #3, which is obtained by quantizing the 4-bit difference value report quantization table shown in Figure 15(c)) in the CSI field.

[0178] Therefore, in Figure 16, terminal 200 sets '011' (index number of SRS resource #3) in the 3rd row CSI field (3 bits) and '010' (index number of SRS resource #2) in the 4th row CSI field (3 bits). Also in Figure 16, terminal 200 sets '1011' (RSRP_11) as the second difference value report in the 7th row CSI field (4 bits) as the report value corresponding to the set resource, and sets '0001' (DIFFRSRP_1) as the third difference value report in the 8th row CSI field (4 bits).

[0179] According to the modified version of setting method 2-2, terminal 200 sets the SRS undetectable information and the detected SRS measurement values ​​in the CSI field in descending order. This allows terminal 200 to report a CSI field with a simple structure without performing complex processing.

[0180] The above explains an example of how to configure the CSI field in inter-terminal CLI reports.

[0181] Thus, in this embodiment, terminal 200 transmits SRS undetectable information in CSI report-based Layer 1-based inter-terminal CLI measurement and reporting using at least one of the absolute value reporting field and the difference value reporting field that constitute the CLI report (e.g., CSI field). Furthermore, base station 100 performs scheduling of terminal 200, for example, based on the SRS undetectable information reported by terminal 200 in CSI report-based Layer 1-based inter-terminal CLI measurement and reporting.

[0182] As a result, even with CSI report-based Layer 1-based inter-terminal CLI measurement and reporting, terminal 200 (e.g., victim UE) can appropriately report information to base station 100 indicating that a blocking problem has occurred (SRS is undetectable). Therefore, according to this embodiment, terminal 200 can appropriately report inter-terminal interference.

[0183] The embodiments of this disclosure have been described above.

[0184] (Other embodiments) [Calculation method for difference value reporting] In Layer 1-based inter-terminal CLI measurement and reporting, the following two methods for calculating the difference value are possible.

[0185] <Alt.1: Calculate the difference value using the actual maximum measurement> After calculating the difference value between the measured actual value and the maximum measured value, terminal 200 may quantize the difference value using a quantization table for reporting the difference value.

[0186] For example, if the first SRS-RSRP is -45.5 dBm and the second SRS-RSRP is -65.5 dBm, the difference value is -20 dB. Terminal 200 sets the quantized absolute value report to "RSRP_111" using a quantization table for absolute value reporting (e.g., Figure 11(a)), and sets the quantized difference value report to "DIFFRSRP_10" using a quantization table for difference value reporting.

[0187] <Alt.2: Calculate the difference value using the largest quantized measurement> Terminal 200 may quantize the measured actual value and the largest measured value using a quantization table for absolute value reporting, and then calculate the difference value as the difference between the quantized actual value and the largest quantized actual value.

[0188] For example, if the first SRS-RSRP is -45.5 dBm and the second SRS-RSRP is -65.5 dBm, the first measured value quantized using the quantization table for absolute value reporting will be "RSRP_111", and the second measured value quantized will be "RSRP_91". Therefore, the quantized absolute value will be "RSRP_111", and the quantized difference value will be "DIFFRSRP_10", since the difference between RSRP_91 and RSRP_111 is -20 dB, using the quantization table for difference value reporting.

[0189] Other embodiments have been described above.

[0190] In the above embodiment, as an example, a case was described in which the number of SRS resources for CLI measurement set on terminal 200 is set to 7, and the number of measurement values ​​that can be reported by CLI report is set to 4. However, the number of SRS resources set on terminal 200 and the number of measurement values ​​that can be reported by CSI field may be other numbers. Also, in the above embodiment, a case was described in which the number of SRS resources that terminal 200 cannot detect is 2 (for example, SRS resources #1 and #4). However, it is not limited to this, and the number of SRS resources that terminal 200 cannot detect may be 1, 3, or 4.

[0191] Furthermore, the parameter values ​​used in the above embodiment, such as the number of SRS resources, the measured value of the SRS, the quantization table (e.g., the measured value range, the resolution for quantization), and the number of bits in the CSI field (e.g., the bit width for the resource index, absolute value reporting, and differential value reporting), are merely examples and may be other values.

[0192] (Supplement) Information indicating whether or not the terminal 200 supports the functions, operations, or processes described in the above-described embodiment may be transmitted (or notified) from the terminal 200 to the base station 100 as, for example, capability information or capability parameters of the terminal 200.

[0193] The capability information may include an information element (IE) that individually indicates whether the terminal 200 supports at least one of the functions, operations, or processes shown in the embodiments described above. Alternatively, the capability information may include an information element that indicates whether the terminal 200 supports any two or more combinations of the functions, operations, or processes shown in the embodiments described above.

[0194] The base station 100 may, for example, determine (or decide or assume) which functions, operations, or processes the source terminal 200 supports (or does not support) based on capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls in accordance with the determination result based on the capability information. For example, the base station 100 may control the measurement and reporting settings of inter-terminal CLI based on capability information received from the terminal 200.

[0195] Furthermore, the fact that the terminal 200 does not support some of the functions, operations, or processes shown in the embodiments described above may be interpreted as the terminal 200 having restrictions on such some functions, operations, or processes. For example, information or requests regarding such restrictions may be notified to the base station 100.

[0196] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or it may be implicitly communicated to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0197] (Control Signals) In this disclosure, the downlink control signals (or downlink control information) relating to one embodiment of this disclosure may be, for example, signals (or information) transmitted in a Physical Downlink Control Channel (PDCCH) at the physical layer, or signals (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) at a higher layer. Furthermore, the signals (or information) are not limited to being notified by downlink control signals, but may be predetermined in a specification (or standard), or may be pre-configured in base stations and terminals.

[0198] In this disclosure, the uplink control signal (or uplink control information) related to one embodiment of this disclosure may be, for example, a signal (or information) transmitted in the physical layer PUCCH, or a signal (or information) transmitted in the upper layer MAC CE or RRC. Furthermore, the signal (or information) is not limited to being notified by the uplink control signal, but may be predetermined in the specification (or standard), or may be pre-configured in the base station and terminal. In addition, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0199] (Base Station) In one embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), master unit, gateway, etc. Also, in side-link communication, the terminal may assume the role of a base station. Alternatively, instead of a base station, there may be a relay device that relays communication between the upper node and the terminal. There may also be a roadside unit.

[0200] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, an uplink, a downlink, or a sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) of an uplink, a Physical Downlink Shared Channel (PDSCH), PDCCH, Physical Broadcast Channel (PBCH) of a downlink, or a Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Broadcast Channel (PSBCH) of a sidelink.

[0201] PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channels, downlink data channels, uplink data channels, and uplink control channels, respectively. PSCCH and PSSCH are examples of sidelink control channels and sidelink data channels. PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0202] (Data Channel / Control Channel) One embodiment of the present disclosure may be applied to either a data channel or a control channel, for example. For example, the channel in one embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, PSBCH.

[0203] (Reference Signal) In one embodiment of the present disclosure, the reference signal is, for example, a signal known to both the base station and the mobile station, and may be called a Reference Signal (RS) or pilot signal. The reference signal may be any of the following: Demodulation Reference Signal (DMRS), Channel State Information - Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-specific Reference Signal (CRS), or Sounding Reference Signal (SRS).

[0204] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be a time resource unit such as a frame, superframe, subframe, slot, time slot, subslot, minislot, or symbol, Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier - Frequency Division Multiplexing Access (SC-FDMA) symbol, or any other time resource unit. Furthermore, the number of symbols contained in one slot is not limited to the number of symbols exemplified in the above embodiment, but may be any other number of symbols.

[0205] (Frequency Band) One embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.

[0206] (Communication) One embodiment of the present disclosure may be applied to communication between a base station and a terminal (Uu-link communication), communication between terminals (Sidelink communication), or Vehicle to Everything (V2X) communication. For example, the channel in one embodiment of the present disclosure may be replaced with any of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.

[0207] Furthermore, one embodiment of this disclosure may be applied to any of the following: a terrestrial network, a satellite, or a non-terrestrial network (NTN) using a high-altitude pseudo-satellite (HAPS). Also, one embodiment of this disclosure may be applied to terrestrial networks with large cell sizes, ultra-wideband transmission networks, and other networks where transmission delay is large relative to symbol length or slot length.

[0208] (SBFD) In ​​one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may also be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband non-overlapping full duplex, Subband full duplex) operation or control is performed. In an SBFD symbol, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., also called subbands, RB sets, subbands, or sub-BWPs (Bandwidth parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) on a subband basis. In an SBFD symbol, a terminal may transmit and receive in either the uplink or downlink direction only, and not in the other direction. On the other hand, a base station may be able to transmit and receive both uplink and downlink simultaneously. An SBFD symbol may have a smaller frequency domain available for downlink transmission compared to a symbol that transmits and receives only downlink. Similarly, an SBFD symbol may have a smaller frequency domain available for uplink transmission compared to a symbol that transmits and receives only uplink.

[0209] Furthermore, in the SBFD symbol, a terminal may transmit and receive both uplink and downlink simultaneously. In this case, the frequency domain from which the terminal transmits and the frequency domain from which it receives may not be adjacent, and a frequency gap (also called a frequency interval) may be maintained between them.

[0210] Furthermore, sidelink transmission and reception may be included as different transmission and reception directions for each subband unit, which is a divided region.

[0211] (XDD: cross division duplex) In one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) on which full duplex operation or control is performed. In full duplex symbols, both the terminal and the base station can transmit and receive uplink and downlink simultaneously. In full duplex symbols, the terminal and base station may transmit and receive simultaneously in the available frequency domain (or frequency resource, frequency band), or they may transmit and receive simultaneously in some frequency domains (i.e., they may transmit or receive in other frequency domains). In this case, the frequency domain on which the base station or terminal transmits and the frequency domain on which it receives may not be adjacent, and a frequency gap (also called a frequency gap) may be maintained between them. Alternatively, for example, to reduce interference, either the terminal or the base station may transmit and receive simultaneously (i.e., the other may transmit or receive).

[0212] Furthermore, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks. Also, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

[0213] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna composed of multiple antennas. For example, the number of physical antennas that make up an antenna port is not specified, and it may be defined as the smallest unit on which a terminal station can transmit a reference signal. An antenna port may also be defined as the smallest unit on which the weighting of a precoding vector is multiplied.

[0214] <5G NR System Architecture and Protocol Stack> The 5G NR system architecture, as a whole, assumes an NG-RAN (Next Generation - Radio Access Network) with gNBs. The gNBs provide the UE-side termination for the user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols of NG radio access. The gNBs are connected to each other by Xn interfaces. Furthermore, the gNBs are connected to the NGC (Next Generation Core) by Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity performing the AMF) by NG-C interfaces, and to the UPF (User Plane Function) (e.g., a specific core entity performing the UPF) by NG-U interfaces. The NG-RAN architecture is shown in Figure 17 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0215] <RRC Connection Setup and Reconfiguration Procedure> This describes the communication between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS section (see TS 38.300 v15.6.0).

[0216] RRC is a higher-layer signaling (protocol) used for configuring the UE and gNB. The AMF prepares the UE context data (which includes, for example, the PDU session context, security key, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding to the gNB with a SecurityModeComplete message. Subsequently, the gNB sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures itself to set up the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the SRB2 and DRB are not set up, so the RRCReconfiguration step is omitted. Finally, the gNB notifies the AMF that the setup procedure is complete with an Initial Context Setup Response.

[0217] Accordingly, this disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) comprising a control circuit that establishes a Next Generation (NG) connection with gNodeB during operation, and a transmission unit that sends an initial context setup message to gNodeB via the NG connection during operation so that a signaling radio bearer between gNodeB and User Equipment (UE) is set up. Specifically, gNodeB transmits Radio Resource Control (RRC) signaling, including a Resource Allocation Setting Information Element (IE), to the UE via the signaling radio bearer. The UE then transmits on the uplink or receives on the downlink based on the resource allocation setting.

[0218] <QoS Control> The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows where a guaranteed flow bit rate is required (GBR: Guaranteed Bit Rate QoS flows) and QoS flows where a guaranteed flow bit rate is not required (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS within a PDU session. QoS flows are identified within a PDU session by a QoS Flow ID (QFI: QoS Flow ID) carried in the encapsulation header via the NG-U interface.

[0219] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes, for example, at least one Data Radio Bearers (DRB) in accordance with the PDU session. Additional DRBs for the QoS flow of that PDU session can be configured later (when this is done is up to the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0220] (Open-RAN) The base station described in each embodiment (for example, a 5G NR base station called a gNB) may consist of three functional modules: a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0221] CU may be referred to as, for example, a central node, aggregation node, central station, aggregation station, or central unit. DU may be referred to as, for example, an O-DU (O-RAN Distributed Unit), a distributed node, a distributed station, or a distributed unit. RU may be referred to as, for example, an O-RU (O-RAN Radio Unit), a radio device, a radio node, a radio station, an antenna unit, or a radio unit.

[0222] The functional division configuration (or functional division point) between CU, DU, and RU has multiple division options defined. The term "functional division point" is sometimes referred to as "split," "option," or "split option."

[0223] Examples of "splitting options" include the following splitting options 1 to 8. The functions of the base station described in each embodiment may be split into CU, DU, and RU functions according to any of the following splitting options 1 to 8. For example, CU, DU, and RU may be functionally split individually, or functional split may occur only between CU and DU, or only between DU and RU. (1) Splitting option 1: Between RRC (radio resource control) and PDCP (2) Splitting option 2: Between PDCP and RLC (High-RLC) (3) Splitting option 3: Between High-RLC and Low-RLC (4) Splitting option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Splitting option 5: Between High-MAC and Low-MAC (6) Splitting option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Splitting option 7: Between High-PHY and Low-PHY (8) Splitting option 8: Between PHY (Low-PHY) and RF

[0224] The functional division point between the CU and O-DU may be Split Option 2. The section between the CU and O-DU is called the midhaul, and the F1 interface is defined by 3GPP. The section between the O-DU and O-RU is called the fronthaul, and its functional division point may be Split Option 7-2x, which has been adopted as the O-RAN fronthaul specification.

[0225] Figure 18 shows an example of splitting the base station functions of a gNB into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0226] The CU may, for example, include RRC (radio resource control) functionality, SDAP (service data adaptation protocol) functionality, and PDCP (packet data convergence protocol) functionality.

[0227] The O-DU may include, for example, RLC (radio link control) functionality, MAC functionality, and high-level physical layer (HIGH-PHY) functionality. The HIGH-PHY functionality may also include encoding functionality, scrambling functionality, modulation functionality, layer mapping functionality, precoding functionality, and RE (resource element) mapping functionality for downlink (DL) transmission. The HIGH-PHY functionality may also include decoding functionality, descrambling functionality, demodulation functionality, layer demapping functionality, and RE (resource element) demapping functionality for uplink (UL) reception.

[0228] The O-RU may, for example, be equipped with a LOW-PHY function and an RF function. The LOW-PHY function may also be equipped with a beamforming function, an IFFT (Inverse First Fourier Transform) + CP (Cyclic Prefix) application function, and a D / A (Digital to Analog) conversion function for downlink transmission. The LOW-PHY function may also be equipped with an A / D (Analog to Digital) conversion function, a CP removal + FFT (First Fourier Transform) function, and a beamforming function for uplink reception.

[0229] If the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0230] The O-RU may also be equipped with LBT (listen before talk) functionality. In Split Option 7-2x, eCPRI (Evolved Common Public Radio Interface) is specified as the communication method between the O-DU and O-RU. In Split Option 7-2x, eCPRI transmits and receives not only the sampling sequence of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, but also information used for beamforming in the antenna and time synchronization signals.

[0231] The information transmitted by the signals described in each embodiment (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) may be transmitted between the O-DU and O-RU via the eCPRI's User Plane (U-Plan) or Control Plane (C-Plane).

[0232] If the functions described in each embodiment are executed in the O-RU by functional partitioning, the O-DU may control the O-RU by transmitting information for controlling the functions via a control signal (e.g., eCPRI) between the O-DU and the O-RU.

[0233] If the functions described in each embodiment are executed in the O-DU by functional partitioning, the O-RU may receive the result of the execution of the function in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received result.

[0234] The CU, O-DU, and O-RU may be deployed in physically different devices connected by optical fibers or the like, or some or all of their functions may be deployed in the same physical device.

[0235] CU and O-DU may be logical entities implemented as software running on a server such as a cloud, as a virtualized RAN (virtual Radio Access Network: vRAN). Furthermore, some or all of the functions of CU and O-DU may be provided as a service of virtualized network functions (NFV).

[0236] The transceiver does not have to be a wireless transceiver; for example, it may be a network transceiver, an optical transceiver, etc. The wireless resources allocated by the O-DU may be resources for wireless communication between the O-RU and the UE.

[0237] This disclosure can be implemented using software, hardware, or software integrated with hardware.

[0238] Each functional block used in the description of the above embodiments may be implemented partially or entirely as an integrated circuit (LSI), and each process described in the above embodiments may be controlled partially or entirely by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may also be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0239] The integrated circuit implementation method is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a Field Programmable Gate Array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that allows for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0240] Furthermore, if advancements in semiconductor technology or related technologies lead to the emergence of integrated circuit technologies that can replace LSIs, then naturally, these technologies can be used to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0241] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0242] Communication devices are not limited to portable or movable devices, but also include all kinds of non-portable or fixed devices, devices, and systems, such as smart home devices (appliances, lighting fixtures, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0243] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0244] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0245] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0246] A terminal according to one embodiment of the present disclosure comprises a control circuit that determines whether or not a measurement signal for crosslink interference between terminals is detected, and a transmission circuit that, if the measurement signal is not detected, transmits information indicating that the measurement signal cannot be detected, using at least one of a first field that reports the absolute value of the measurement and a second field that reports the difference value of the measurement with respect to the absolute value, which constitute control information that reports a plurality of measurement values ​​of the crosslink interference.

[0247] In one embodiment of the present disclosure, the transmitting circuit transmits information indicating the inability to detect using the first field and the second field, and does not transmit the measured value.

[0248] In one embodiment of the present disclosure, the control circuit determines the payload size of the control information according to the number of resources for which the measurement signal is not detected.

[0249] In one embodiment of the present disclosure, the control information includes one first field and a plurality of second fields, and the transmission circuit uses the first field and the second field to transmit information indicating undetectable for resources where the measurement signal is not detected, and the measured value for resources where the measurement signal is detected.

[0250] In one embodiment of the present disclosure, the transmitting circuit transmits information indicating undetectable using the first field or the second field, and transmits the difference between the measured value and a specified reference value using the second field.

[0251] In one embodiment of the present disclosure, the transmitting circuit transmits information indicating undetectable using the second field, transmits the largest measurement value among the plurality of measurements using the first field, and transmits the difference between the remaining measurements among the plurality of measurements and the largest measurement value using the second field.

[0252] A base station according to one embodiment of the present disclosure includes a receiving circuit that receives information indicating the inability to detect the crosslink interference measurement signal, using at least one of a first field that reports the absolute value of the measured value and a second field that reports the difference value of the measured value with respect to the absolute value, which constitute control information that reports a plurality of measured values ​​of crosslink interference between terminals; and a control circuit that schedules the terminals based on the information indicating the inability to detect.

[0253] In a communication method according to one embodiment of the present disclosure, a terminal determines whether or not a measurement signal for crosslink interference between terminals is detected, and if the measurement signal is not detected, it transmits information indicating that the measurement signal is undetectable using at least one of a first field that reports the absolute value of the measurement and a second field that reports the difference value of the measurement with respect to the absolute value, which constitute control information for reporting multiple measurements of the crosslink interference.

[0254] In a communication method according to one embodiment of the present disclosure, the base station receives information indicating that the crosslink interference measurement signal is undetectable, using at least one of a first field that reports the absolute value of the measured value and a second field that reports the difference value of the measured value with respect to the absolute value, which constitute control information that reports a plurality of measured values ​​of crosslink interference between terminals, and schedules the terminals based on the information indicating undetectable.

[0255] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2025-017717, filed on February 5, 2025, are incorporated herein by reference.

[0256] One embodiment of this disclosure is useful for wireless communication systems.

[0257] 100 Base station 101, 201 Receiving unit 102, 202 Demodulation / decoding unit 103 Inter-terminal CLI determination unit 104 Scheduling unit 105, 204 Control information holding unit 106, 208 Data / control information generation unit 107, 209 Encoding / modulation unit 108, 210 Transmitting unit 200 Terminal 203 SRS receiving unit 205 Inter-terminal report setting unit 206 Transmission control unit 207 SRS generation unit

Claims

1. A terminal comprising: a control circuit that determines whether or not a measurement signal for crosslink interference between terminals is detected; and a transmission circuit that, if the measurement signal is not detected, transmits information indicating that the measurement signal cannot be detected, using at least one of a first field that reports the absolute value of the measurement and a second field that reports the difference value of the measurement with respect to the absolute value, which constitute control information for reporting multiple measurements of the crosslink interference.

2. The terminal according to claim 1, wherein the transmitting circuit transmits information indicating undetectable using the first field and the second field, and does not transmit the measured value.

3. The terminal according to claim 2, wherein the control circuit determines the payload size of the control information according to the number of resources for which the measurement signal is not detected.

4. The terminal according to claim 1, wherein the control information includes one first field and multiple second fields, and the transmission circuit uses the first field and the second field to transmit information indicating undetectable for resources where the measurement signal is not detected, and the measured value for resources where the measurement signal is detected.

5. The terminal according to claim 4, wherein the transmitting circuit transmits information indicating undetectable using the first field or the second field, and transmits the difference between the measured value and a specified reference value using the second field.

6. The terminal according to claim 4, wherein the transmitting circuit transmits information indicating undetectable using the second field, transmits the largest measurement value among the plurality of measurements using the first field, and transmits the difference between the remaining measurement values ​​among the plurality of measurements and the largest measurement value using the second field.

7. A base station comprising: a receiving circuit that receives information indicating the inability to detect the crosslink interference measurement signal, using at least one of a first field that reports the absolute value of the measurement and a second field that reports the difference value of the measurement with respect to the absolute value, which constitute control information that reports multiple measurements of crosslink interference between terminals; and a control circuit that schedules the terminals based on the information indicating the inability to detect.

8. A communication method comprising: a terminal determining whether or not a measurement signal for crosslink interference between terminals is detected; and, if the measurement signal is not detected, transmitting information indicating that the measurement signal is undetectable, using at least one of a first field reporting the absolute value of the measurement and a second field reporting the difference value of the measurement relative to the absolute value, which constitute control information for reporting multiple measurements of the crosslink interference.

9. A communication method comprising: a base station receiving information indicating the inability to detect the crosslink interference measurement signal, using at least one of a first field reporting the absolute value of the measured value and a second field reporting the difference value of the measured value relative to the absolute value, which constitute control information reporting multiple measured values ​​of crosslink interference between terminals; and scheduling the terminals based on the information indicating the inability to detect.

Images