WO2024166380A1 - Terminal, base station, wireless communication system, and wireless communication method - Google Patents

Abstract

This terminal comprises a control unit that controls measurement of inter-link interferences and a transmission unit that transmits a report of inter-link interferences, the transmission unit transmitting the report of inter-link interferences on the basis of a specific event that is defined by a downlink signal reception state.

Description

Terminal, base station, wireless communication system, and wireless communication method

This disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support reporting of CLI (Cross Link Interference).

The 3rd Generation Partnership Project (3GPP) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)) and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution or 6G.

For example, 3GPP Release 18 is considering the extension of duplexing methods (Non-Patent Document 1). Specifically, XDD (Cross Division Duplex) is proposed as a new duplexing method that enables simultaneous use of the downlink (DL) and uplink (UL) within a carrier in the time division duplex (TDD) band.

In order to expand such duplexing methods, interference countermeasure technologies, such as Cross Link Interference (CLI), are important. Measurement and reporting of CLI by terminals (User Equipment, UE) is specified in 3GPP Release 16 and other documents (Non-Patent Document 2).

"New SI: Study on evolution of NR duplex operation", RP-213591, 3GPP TSG RAN#94-e, 3GPP, December 2021 3GPP TS 38.331 V17.3.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16), 3GPP, December 2022

By the way, CLI reporting is triggered by an event (e.g., Event I1) defined by a CLI measurement result (e.g., a filtered layer 3 CLI measurement result) derived based on the Reference Signal Received Power (RSRP) of the Sounding Reference Signal (SRS) or the Received Signal Strength Indicator (RSSI) of the CLI.

Against this background, the inventors, after careful consideration, have found that in cases where CLI monitoring and measurement is not frequently performed by the UE, large CLI may not be appropriately reflected in the CLI report based on the above-mentioned Event I1.

The present disclosure has been made to solve the above-mentioned problems, and aims to provide a terminal, a base station, a wireless communication system, and a wireless communication method that can properly report CLI.

One aspect of the disclosure is a terminal that includes a control unit that controls measurement of inter-link interference and a transmission unit that transmits a report of the inter-link interference, and the transmission unit transmits the report of the inter-link interference based on a specific event defined by the reception status of a downlink signal.

One aspect of the disclosure is a base station that includes a receiver that receives a report of link interference and a controller that assumes receipt of the report of link interference, and the controller assumes that a terminal transmits the report of link interference based on a specific event that is defined by the reception status of a downlink signal.

One aspect of the disclosure is a wireless communication system that includes a terminal and a base station, the terminal includes a control unit that controls measurement of link interference, and a transmission unit that transmits a report of the link interference, and the transmission unit transmits the report of the link interference based on a specific event defined by the reception status of a downlink signal.

One aspect of the disclosure is a wireless communication method comprising step A of controlling measurement of inter-link interference and step B of transmitting a report of the inter-link interference, the step B including a step of transmitting the report of the inter-link interference based on a specific event defined by a reception status of a downlink signal.

FIG. 1 is a schematic diagram showing the overall configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating the frequency ranges used in the wireless communication system 10. FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. FIG. 4 is a functional block diagram of the UE 200. Figure 5 is a functional block diagram of gNB100. FIG. 6 is a diagram for explaining the problem. FIG. 7 is a diagram for explaining an operation example. FIG. 8 is a diagram for explaining an operation example. FIG. 9 is a diagram for explaining an operation example. FIG. 10 is a diagram for explaining an operation example. FIG. 11 is a diagram for explaining an operation example. FIG. 12 is a diagram for explaining an operation example. FIG. 13 is a diagram for explaining an operation example. FIG. 14 is a diagram for explaining an operation example. FIG. 15 is a diagram for explaining an operation example. FIG. 16 is a diagram showing an example of the hardware configuration of gNB100 and UE200. FIG. 17 is a diagram showing an example of the configuration of a vehicle 2001.

The following describes the embodiments with reference to the drawings. Note that identical or similar symbols are used for identical functions and configurations, and descriptions thereof will be omitted as appropriate.

[Embodiment]
(1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

In addition, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

NG-RAN 20 includes a base station 100 (hereinafter, gNB 100). Note that the specific configuration of the wireless communication system 10, including the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1.

NG-RAN20 actually includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN20 and 5GC may also be simply referred to as a "network."

The gNB100 is a 5G-compliant radio base station, and performs 5G-compliant radio communication with the UE200. The gNB100 and UE200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CC) by bundling them together, and Dual Connectivity (DC), which communicates simultaneously on two or more transport blocks between the UE and each of two NG-RAN Nodes.

Furthermore, the wireless communication system 10 supports multiple frequency ranges (FR). Figure 2 shows the frequency ranges used in the wireless communication system 10.

As shown in FIG. 2, the wireless communication system 10 corresponds to FR1, FR2-1, and FR2-2. The frequency bands of each FR are as follows:

・FR1: 410 MHz to 7.125 GHz
・FR2-1: 24.25 GHz to 52.6 GHz
・FR2-2: 52.6 GHz to 71 GHz
FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30 or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2-1 may be higher in frequency than FR1, use an SCS of 60 or 120 kHz (may include 240 kHz) and use a bandwidth (BW) of 50 to 400 MHz. FR2-2 may be higher in frequency than FR2-1, use an SCS of 120, 480 kHz or 960 kHz and use a bandwidth (BW) of 400 to 2000 MHz.

Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

Furthermore, the wireless communication system 10 also supports higher frequency bands than the FR2-2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

To solve the problem of phase noise becoming more significant at higher frequencies, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied when using bands above 52.6 GHz.

FIG. 3 shows an example of the configuration of a radio frame, subframe, and slot used in the wireless communication system 10.

As shown in Figure 3, one slot is made up of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used.

Also, the number of symbols that make up one slot does not necessarily have to be 14 symbols (e.g., 28 symbols, 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

Note that the time direction (t) shown in FIG. 3 may be called the time domain, symbol period, or symbol time. The frequency direction may be called the frequency domain, resource block, subcarrier, bandwidth part (BWP), etc.

DMRS is a type of reference signal and is prepared for various channels. Unless otherwise specified, the term may refer to a downlink data channel, specifically, a DMRS for a PDSCH (Physical Downlink Shared Channel). However, a DMRS for an uplink data channel, specifically, a PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as a DMRS for a PDSCH.

DMRS may be used for channel estimation in a device, e.g., UE 200, as part of coherent demodulation. DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.

The DMRS may have multiple mapping types. Specifically, the DMRS has mapping type A and mapping type B. In mapping type A, the first DMRS is placed in the second or third symbol of a slot. In mapping type A, the DMRS may be mapped relative to the slot boundary, regardless of where in the slot the actual data transmission starts. The reason for placing the first DMRS in the second or third symbol of a slot may be interpreted as being to place the first DMRS after the control resource sets (CORESET).

In mapping type B, the first DMRS may be placed in the first symbol of the data allocation, i.e., the position of the DMRS may be given relative to where the data is placed, rather than relative to a slot boundary.

DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in mapping in the frequency domain and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, and Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

(2) Functional Block Configuration of the Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described.

First, we will explain the functional block configuration of UE200.

FIG. 4 is a functional block diagram of UE 200. As shown in FIG. 4, UE 200 includes a radio signal transmitting/receiving unit 210, an amplifier unit 220, a modulation/demodulation unit 230, a control signal/reference signal processing unit 240, an encoding/decoding unit 250, a data transmitting/receiving unit 260, and a control unit 270.

The radio signal transmission/reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission/reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and each of two NG-RAN nodes.

The amplifier section 220 is composed of a PA (Power Amplifier)/LNA (Low Noise Amplifier) etc. The amplifier section 220 amplifies the signal output from the modem section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission/reception section 210.

The modem unit 230 performs data modulation/demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100 or other gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

The control signal/reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE 200, and processing related to various reference signals transmitted and received by the UE 200.

Specifically, the control signal/reference signal processor 240 receives various control signals, such as radio resource control layer (RRC) control signals, transmitted from the gNB 100 via a predetermined control channel. The control signal/reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

The control signal/reference signal processing unit 240 performs processing using reference signals (RS) such as the Demodulation Reference Signal (DMRS) and the Phase Tracking Reference Signal (PTRS).

DMRS is a known reference signal (pilot signal) between the base station and the terminal for each terminal, used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

In addition to DMRS and PTRS, reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

Channels also include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH).

In addition, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via a data channel. A data channel may also be read as a shared channel.

Here, the control signal/reference signal processing unit 240 may receive downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and the information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and the information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and the default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is specified by the value stored in the MCS and the MCS table. The MCS table may be specified by an RRC message or may be specified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which the DCI is applied. The value stored in the NDI is an information element that specifies whether the data to which the DCI is applied is initial transmission data or not. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

In an embodiment, the control signal/reference signal processing unit 240 constitutes a transmission unit that transmits a report of cross link interference (hereinafter, CLI; Cross Link Interference). CLI may mean that the UL signal of a UE 200 served by a first cell interferes with the DL signal of a UE 200 served by a second cell adjacent to the first cell. In such a case, the UE 200 served by the second cell (the UE 200 that is subject to interference) measures the CLI and transmits a CLI report.

The encoding/decoding unit 250 performs data division/concatenation and channel coding/decoding for each predetermined communication destination (gNB100 or other gNB).

Specifically, the encoding/decoding unit 250 divides the data output from the data transmission/reception unit 260 into pieces of a predetermined size, and performs channel coding on the divided data. The encoding/decoding unit 250 also decodes the data output from the modem unit 230, and concatenates the decoded data.

The data transmission/reception unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission/reception unit 260 performs assembly/disassembly of PDUs/SDUs in multiple layers (such as the Medium Access Control layer (MAC), Radio Link Control layer (RLC), and Packet Data Convergence Protocol layer (PDCP)). The data transmission/reception unit 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).

The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 constitutes a control unit that controls measurement of link interference (CLI).

Here, examples of CLI reporting configurations include periodic reporting configurations (e.g., PeriodicalReportConfig) and event-triggered configurations (EventTriggerConfig). Examples of CLI reporting events include events (e.g., Event I1) defined by the CLI measurement results (e.g., filtered layer 3 CLI measurement result) derived based on the Sounding Reference Signal (SRS) Reference Signal Received Power (RSRP) or the CLI RSSI (Received Signal Strength Indicator) (TS38.331 V17.3.0 §6.3.2 Radio resource control information).

Under this background, the control unit 270 instructs the control signal/reference signal processing unit 240 to transmit a CLI report based on a specific event defined separately from Event 1. The specific event is an event defined by the reception status of the downlink signal. In other words, the control signal/reference signal processing unit 240 transmits a CLI report based on a specific event defined by the reception status of the downlink signal. Details of the specific event will be described later.

Secondly, we will explain the functional block configuration of the gNB100.

FIG. 5 is a functional block diagram of the gNB100. As shown in FIG. 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

The receiver 110 receives various signals from the UE 200. The receiver 110 may receive a UL signal via a PUCCH or a PUSCH. In an embodiment, the receiver 110 constitutes a receiver that receives reports of link interference (CLI).

The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit DL signals via the PDCCH or PDSCH.

The control unit 130 controls the gNB 100. In the embodiment, the control unit 130 configures a control unit that assumes receipt of a report of link interference (CLI). The control unit 130 assumes that the terminal (UE 200) transmits a report of link interference (CLI) based on a specific event defined by the reception status of the downlink signal.

(3) Issues First, we will explain resource allocation for gNB100.

As shown in the upper part of Figure 6, in Release 15/16/17, gNB100 sets or designates "DL", "F (Flexible)" or "UL" for each symbol. On the other hand, as shown in the lower part of Figure 6, in Release 18, gNB100 sets or designates "DL" for symbols of one frequency resource (e.g., sub-band(s)) and sets or designates "UL" for symbols of other frequency resources (e.g., sub-band(s)). Such a method may be referred to as SBFD (Sub-Band non-overlapping Full Duplex).

By adopting SBFD, CLI may occur in which the UL signal of UE200 served by a first cell interferes with the DL signal of UE200 served by a second cell adjacent to the first cell. In such a case, UE200 served by the second cell (UE200 that is subject to interference) measures the CLI and transmits a CLI report.

Second, we discuss the challenges associated with implementing CLI measurement/reporting.

Configurations related to CLI reporting include periodic reporting configurations (e.g., PeriodicalReportConfig) and event-triggered configurations (EventTriggerConfig). Events related to CLI reporting may be events (e.g., Event I1) defined by CLI measurement results (e.g., filtered layer 3 CLI measurement result) derived based on the Sounding Reference Signal (SRS) Reference Signal Received Power (RSRP) or the CLI Received Signal Strength Indicator (RSSI) (TS38.331 V17.3.0 §6.3.2 Radio resource control information).

Against this background, the inventors, after careful consideration, have found that in cases where UE200 does not frequently monitor and measure CLI, large CLI may not be properly reflected in the CLI report based on the above-mentioned Event I1.

(4) Operation Example In order to solve the above-mentioned problem, the following operation example may be specified. Specifically, a specific event defined separately from Event I1 may be specified. UE 200 may transmit a CLI report when Event I1 is satisfied, or may transmit a CLI report when a trigger condition of the specific event is satisfied. The specific event is an event defined by the reception status of a downlink signal (PDSCH, PDCCH, BFD (Beam Failure Detection)-RS, Periodic/Semi-persistent/Aperiodic CSI-RS, SSB, etc.).

(4.1) Operation example 1
In the first operation example, the specific event may be defined by a failure to receive the PDSCH and/or the PDCCH. For example, the specific event may be an event in which the number of failures to receive the PDSCH and/or the PDCCH is greater than (or equal to) a threshold N (N≧1). The threshold N may be predefined in the wireless communication system 10 or may be set by the RRC (hereinafter the same).

In such cases, the following options are possible for specific events:

In option 1-1, the specific event may be an event in which the number of consecutive failed receptions of the PDSCH and/or PDCCH is greater than (or equal to) a threshold N (N≧1). In option 1-1, a counter may be provided that counts the number of consecutive failed receptions of the PDSCH and/or PDCCH. The counter may be initially set to 0.

For example, as shown in FIG. 7, UE 200 may increase the counter value by 1 in response to detection of failure to receive PDSCH and/or PDCCH. UE 200 may reset the counter to an initial value in response to detection of successful reception of PDSCH and/or PDCCH. UE 200 may transmit a CLI report and reset the counter to the initial value when the counter value reaches threshold N.

In option 1-2, the specific event may be an event in which the number of times of failure to receive the PDSCH and/or PDCCH within a specific time is greater than (or equal to or greater than) a threshold N (N≧1). In option 1-2, a counter that counts the number of times of failure to receive the PDSCH and/or PDCCH and a timer that is activated by a failure to receive the PDSCH and/or PDCCH may be provided. The timer is a timer for measuring the specific time described above. The counter may be set to an initial value of 0, and the timer may be set to an initial value of the specific time. The specific time may be predefined in the wireless communication system 10, or may be set by the RRC (same below).

For example, as shown in the left column of FIG. 8, UE200 may increase the counter value by 1 in response to detection of failure to receive PDSCH and/or PDCCH, and may start the timer if it is not running. If the counter value reaches threshold N before the timer expires, UE200 may transmit a CLI report and reset the counter and timer to their initial values. As shown in the right column of FIG. 8, UE200 may reset the counter to its initial value if the timer expires without the counter value reaching threshold N.

In options 1-3, the specific event may be an event in which the number of failed receptions of the PDSCH and/or PDCCH is greater than (or equal to) a threshold N (N≧1) before the number of receptions of the PDSCH and/or PDCCH reaches X times. In options 1-3, a first counter for counting the number of receptions of the PDSCH and/or PDCCH and a second counter for counting the number of failed receptions of the PDSCH and/or PDCCH may be provided. X may be set as the initial value of the first counter, and 0 may be set as the initial value of the second counter. The value of X may be predefined in the wireless communication system 10, or may be set by the RRC (similar below).

For example, as shown in the left column of FIG. 9, UE200 may decrease the value of the first counter by 1 and increase the value of the second counter by 1 in response to detection of failure to receive the PDSCH and/or PDCCH. When the value of the first counter is greater than 0 and the value of the second counter reaches threshold N, UE200 transmits a CLI report and resets the first counter and the second counter to their initial values. As shown in the right column of FIG. 9, UE200 may decrease the value of the first counter by 1 in response to detection of successful reception of the PDSCH and/or PDCCH and maintain the value of the second counter. When the value of the second counter becomes 0 without reaching threshold N, UE200 resets the first counter and the second counter to their initial values.

In option 1-4, the specific event may be an event in which the number of failed receptions of the PDSCH and/or PDCCH within a specific time is greater than (or equal to) a threshold N (N≧1). In option 1-4, a counter that counts the number of failed receptions of the PDSCH and/or PDCCH and a timer that is started by a failed reception of the PDSCH and/or PDCCH may be provided. The timer is a timer for measuring the specific time described above. The difference with option 1-2 is that the counter is reset to an initial value by successful reception of the PDSCH and/or PDCCH, and the timer is stopped by successful reception of the PDSCH and/or PDCCH. The initial value of the counter may be set to 0, and the initial value of the timer may be set to a specific time.

For example, as shown in the left column of FIG. 10, UE200 may increase the counter value by 1 and start the timer in response to detection of failure to receive PDSCH and/or PDCCH when the timer is not started. If the counter value reaches threshold N before the timer expires, UE200 may transmit a CLI report and reset the counter and timer to their initial values. As shown in the middle column of FIG. 10, UE200 may stop the timer and reset the counter to their initial values in response to detection of successful reception of PDSCH and/or PDCCH. As shown in the right column of FIG. 10, UE200 may stop the timer and reset the counter to their initial values in response to expiration of the timer.

In option 1-5, the specific event may be an event in which the number of failed receptions of the PDSCH and/or PDCCH within a specific time period is greater than (or equal to) a threshold N (N≧1). In option 1-5, a counter that counts the number of failed receptions of the PDSCH and/or PDCCH and a timer that is activated by a failed reception of the PDSCH and/or PDCCH may be provided. The timer is a timer for measuring the specific time period mentioned above. The difference from option 1-2 is that the timer is restarted in response to a failed reception of the PDSCH and/or PDCCH. The counter may be set to an initial value of 0, and the timer may be set to an initial value of a specific time.

For example, as shown in the left column of FIG. 11, UE200 may increase the counter value by 1 and start or restart the timer (i.e., reset the timer value to the initial value) in response to detection of failure to receive the PDSCH and/or PDCCH. UE200 may maintain the counter value in response to detection of successful reception of the PDSCH and/or PDCCH. UE200 may transmit a CLI report and reset the counter and timer to their initial values when the counter value reaches threshold N before the timer expires. As shown in the right column of FIG. 11, UE200 may reset the counter and timer to their initial values when the timer expires.

In option 1-6, the specific event may be an event in which the number of failed receptions of the PDSCH and/or PDCCH is greater than (or equal to) a threshold N (N≧1) before the number of receptions of the PDSCH and/or PDCCH reaches X times. In option 1-3, a first counter that counts the number of receptions of the PDSCH and/or PDCCH and a second counter that counts the number of failed receptions of the PDSCH and/or PDCCH may be provided. The difference from option 1-3 is that the first counter is reset to an initial value in response to a failure to receive the PDSCH and/or PDCCH. X may be set as the initial value of the first counter, and 0 may be set as the initial value of the second counter.

For example, as shown in the left column of FIG. 12, UE 200 may reset the value of the first counter to an initial value and increase the value of the second counter by 1 in response to detection of failure to receive PDSCH and/or PDCCH. When the value of the first counter is greater than 0 and the value of the second counter reaches threshold N, UE 200 transmits a CLI report and resets the first counter and the second counter to their initial values. As shown in the right column of FIG. 12, UE 200 may decrease the value of the first counter by 1 in response to detection of successful reception of PDSCH and/or PDCCH and maintain the value of the second counter. When the value of the second counter becomes 0 without reaching threshold N, UE 200 resets the first counter and the second counter to their initial values.

In option 1-7, the specific event may be an event in which the number of failed receptions of the PDSCH and/or PDCCH within a specific time period is greater than (or equal to) a threshold N (N≧1). In option 1-7, a counter that counts the number of failed receptions of the PDSCH and/or PDCCH and a timer that is activated by a failed reception of the PDSCH and/or PDCCH may be provided. The timer is a timer for measuring the specific time period described above. The difference from option 1-2 is that the timer is restarted in response to a failed reception of the PDSCH and/or PDCCH. The counter may be set to an initial value of 0, and the timer may be set to an initial value of a specific time.

For example, as shown in the left column of FIG. 13, UE200 may increase the counter value by 1 and start or restart the timer (i.e., reset the timer value to the initial value) in response to detection of failure to receive the PDSCH and/or PDCCH. UE200 may transmit a CLI report and reset the counter and timer to their initial values if the counter value reaches threshold N before the timer expires. As shown in the middle column of FIG. 13, UE200 may stop the timer and reset the counter to its initial value in response to detection of successful reception of the PDSCH and/or PDCCH. As shown in the right column of FIG. 13, UE200 may stop the timer and reset the counter to its initial value in response to expiration of the timer.

(4.2) Operation example 2
In the second example operation, the specific event may be defined by an instance of poor measurement quality of the BFD-RS. For example, the specific event may be an event in which the number of times the measurement quality of the BFD-RS is less than a threshold is greater (or equal to or greater than) a threshold N (N≧1). An instance of poor measurement quality of the BFD-RS is an example of a poor quality measurement of the DL signal.

In operation example 2, the above-mentioned option 1-1 may be adopted as option 2-1. The above-mentioned option 1-2 may be adopted as option 2-2. The above-mentioned option 1-3 may be adopted as option 2-3. The above-mentioned option 1-4 may be adopted as option 2-4. The above-mentioned option 1-5 may be adopted as option 2-5. The above-mentioned option 1-6 may be adopted as option 2-6. The above-mentioned option 1-7 may be adopted as option 2-7.

In such cases, failure to receive PDSCH and/or PDCCH may be interpreted as an instance of poor measured quality of BFD-RS.

Here, we consider BFR (Beam Failure Report) based on BFD-RS monitoring. The conditions for triggering a CLI report based on BFD-RS measurement quality may be more relaxed than the conditions for triggering a BFR.

For example, in Example 2A, the beam quality threshold used in the condition to trigger a CLI report may be higher than the beam quality threshold used in the condition to trigger a BFR. In Example 2B, the number of beam instances with poor measurement quality used in the condition to trigger a CLI report may be lower than the beamFailureInstanceMaxCount used in the condition to trigger a BFR. In Example 2C, the interval between two beams with poor measurement quality when used in the condition to trigger a CLI report may be longer than the time applied in the condition to trigger a BFR.

(4.3) Operation example 3
In the operation example 3, the specific event may be defined by a CSI report with poor measurement quality. For example, the specific event may be an event in which the number of CSI reports with any/maximum/minimum L1-SINR lower than a threshold is greater than (or equal to) a threshold N (N≧1) (Option 3A). The specific event may be an event in which the number of CSI reports with any/maximum/minimum CQI (wideband or subband) lower than a threshold is greater than (or equal to) a threshold N (N≧1) (Option 3B). Option 3A and Option 3B may be combined. A CSI report with poor measurement quality is an example of poor quality measurement of a DL signal.

In operation example 3, the above-mentioned option 1-1 may be adopted as option 3-1. The above-mentioned option 1-2 may be adopted as option 3-2. The above-mentioned option 1-3 may be adopted as option 3-3. The above-mentioned option 1-4 may be adopted as option 3-4. The above-mentioned option 1-5 may be adopted as option 3-5. The above-mentioned option 1-6 may be adopted as option 3-6. The above-mentioned option 1-7 may be adopted as option 3-7.

In such cases, failure to receive the PDSCH and/or PDCCH may be interpreted as a CSI report of poor measurement quality.

(4.4) Operation example 4
In the operation example 4, the specific event may be defined by a CSI/CMR (Codec Mode Request) instance with poor measurement quality. For example, the specific event may be an event in which the number of CSI reports in which any/maximum/minimum L1-SINR is lower than a threshold is greater than (or equal to) a threshold N (N≧1) (Option 4A). The specific event may be an event in which the number of CSI reports in which any/maximum/minimum CQI (wideband or subband) is lower than a threshold is greater than (or equal to) a threshold N (N≧1) (Option 4B). Option 4A and Option 4B may be combined. The CSI/CMR instance with poor measurement quality is an example of a poor quality measurement of a DL signal.

In operation example 4, the above-mentioned option 1-1 may be adopted as option 4-1. The above-mentioned option 1-2 may be adopted as option 4-2. The above-mentioned option 1-3 may be adopted as option 4-3. The above-mentioned option 1-4 may be adopted as option 4-4. The above-mentioned option 1-5 may be adopted as option 4-5. The above-mentioned option 1-6 may be adopted as option 4-6. The above-mentioned option 1-7 may be adopted as option 4-7.

In such cases, failure to receive PDSCH and/or PDCCH may be interpreted as a CSI/CMR instance of poor measurement quality.

(4.5) Operation example 5
In the operation example 5, a case where a beam-specific CLI report may be introduced is assumed. For example, a case where a TCI (Transmission Configuration Indicator) state, a spatial filter, or a QCL type-D is set as a CLI measurement (resource) is assumed. In such a case, the specific condition may include a condition that considers the beam, or may include a condition that does not consider the beam. The following options are considered as the specific condition.

In option 5-1, the specific conditions may be conditions that are not specific to a beam. Specific conditions include conditions under which DL reception failures are counted regardless of the beam.

Taking the above-mentioned operation example 1 as an example, failure to receive PDSCH and/or PDCCH is counted regardless of the beam.

Take the above-mentioned example operation 2 as an example: instances where the BFD-RS measurement quality is poor are counted regardless of the beam.

Take the example of operation 3 above as an example: CSI reports with poor measurement quality are counted regardless of the beam.

Taking the above-mentioned example of operation 4 as an example, CSI/CMR instances with poor measurement quality are counted regardless of the beam.

Under these conditions, the following actions may be performed if certain conditions are met.

UE200 may send a CLI measurement result (e.g., a filtered layer 3 CLI measurement result) derived based on the SRS RSRP or the CLI RSSI as a CLI report when certain conditions are met. Alternatively, UE200 may send an extended CLI report when certain conditions are met. The extended CLI report may include one or more measurement results selected from beam-specific CLI measurement results, sub-band based CLI measurement results, and non-contiguous CLI measurement resource measurement results.

Here, option 5-1 does not have to be adopted for beam-specific CLI measurements or reports. Option 5-1 may be adopted for existing CLI measurements or reports (e.g., Layer 3 CLI measurement/report).

In option 5-2, the specific conditions may be beam-specific. The specific conditions include conditions under which DL reception failures are counted taking into account the beam.

In option 5-2-1, a DL reception failure may be counted only once per beam (see Figure 14).

Taking the above-mentioned operation example 1 as an example, a failure to receive the PDSCH and/or PDCCH is counted only once per beam.

Take the above example of operation example 2 as an example: instances of poor BFD-RS measurement quality are counted only once per beam.

Take operation example 3 above as an example: a CSI report with poor measurement quality is counted only once per beam.

Take operation example 4 above as an example: CSI/CMR instances with poor measurement quality are counted only once per beam.

Under these conditions, the following actions may be performed if certain conditions are met.

UE200 may send a CLI measurement result (e.g., a filtered layer 3 CLI measurement result) derived based on the SRS RSRP or the CLI RSSI as a CLI report when certain conditions are met. Alternatively, UE200 may send an extended CLI report when certain conditions are met. The extended CLI report may include one or more measurement results selected from beam-specific CLI measurement results, sub-band based CLI measurement results, and non-contiguous CLI measurement resource measurement results.

Here, option 5-2 requires failed or poor quality reception for each beam, but since reception or measurement based on aperiodic signals/channels cannot guarantee reception or measurement for each beam, option 5-2 may not be adopted when trigger conditions are defined based on aperiodic signals/channels.

In option 5-2-2, DL reception failures may be counted separately for each beam (see Figure 15).

Taking the above-mentioned example of operation example 1 as an example, a failure to receive the PDSCH and/or PDCCH is counted only once for each beam separately.

Taking the above example of operation example 2 as an example, instances of poor BFD-RS measurement quality are counted only once for each beam separately.

Taking the example of operation example 3 above as an example, a CSI report with poor measurement quality is counted only once for each beam separately.

Taking the above-mentioned example of operation 4 as an example, CSI/CMR instances with poor measurement quality are counted only once for each beam separately.

Under these conditions, the following actions may be performed if certain conditions are met.

In Alt.1, UE200 may send the SRS RSRP or CLI RSSI as a CLI report for a CLI measurement resource having the same TCI state, spatial filter or QCL type-D as a specific beam when a specific condition is met for the specific beam.

In Alt.2, UE200 may transmit the RSRP of the SRS or the RSSI of the CLI for a CLI measurement resource configured or associated with a specific beam as a CLI report when a specific condition is met for the specific beam.

In Alt.3, UE200 may send the SRS RSRP or CLI RSSI for the configured CLI measurement resource as a CLI report when a specific condition is met for a specific beam.

In Alt.4, UE200 may send the SRS RSRP or CLI RSSI for the configured CLI measurement resources as a CLI report when certain conditions are met for each beam.

Here, it is desirable to adopt Alt.1 since UE200 can report CLI measurement results only for beams with poor quality.

(4.6) Operation example 6
In the above-mentioned operation examples 1-5, the reporting of CLI in Layer 3 has been mainly described. In operation example 6, the reporting of CLI in a lower layer is also assumed. For example, the lower layer may be Layer 1. Note that, in the measurement of CLI in Layer 3, two or more CLI values in a certain period may be smoothed by Layer 3 filtering. Therefore, it may be considered that the measurement of CLI in Layer 1 indicates a short-term value, and the measurement of CLI in Layer 3 indicates a long-term value.

Under these assumptions, new candidate values for the report type setting (e.g., EventTriggering) may be supported for CLI reporting for the Layer 1 CLI reporting mechanism or the Layer 3 CLI mechanism. New candidate values may include the following:

In Alt.1, candidate values may include an existing event (Event I1). For example, Event I1 is an event that compares a CLI measurement result at layer 3 (e.g., a filtered layer 3 CLI measurement result) with a threshold.

In Alt.2, candidate values may include Enhanced/Modified Event I1. For example, Enhanced/Modified Event I1 is an event that compares a CLI measurement result at Layer 1 (Layer 1 filtered or 1 non-filtered CLI measurement result) with a threshold.

In Alt.3, the candidate values may include at least one or more specific events in operation examples 1-5.

Which of Alt.1 to Alt.3 is to be applied may be predefined in the wireless communication system 10 or may be set by the RRC. For example, the candidate value (triggering event) may be defined as an information element included in the EventTriggering parameter.

If the trigger condition for a CLI report event is met, UE200 may perform the following actions:

In Alt.-A, UE200 reports the measured CLI results. For example, for a CLI reporting configuration, or for a CLI reporting configuration with reporting content included in the CLI report, UE200 may send the CLI report shown below.

In Alt.-A-1, when the non-filtered or Layer 1/3 filtered CLI-RSSI/SRS-RSRP of the measurement resource of the CLI corresponding to the CLI/CSI reporting configuration satisfies Event I1 or Enhanced/Modified Event I1, the UE 200 may report the CLI measurement results related to the CLI/CSI reporting configuration via the MAC CE. The CLI measurement results may include the CLI measurement results of the measurement resource of the CLI having the non-filtered or Layer 1/3 filtered CLI-RSSI/SRS-RSRP that satisfies Event I1 or Enhanced/Modified Event I1. Alternatively, the CLI measurement results may include the CLI report contents specified in the CLI/CSI reporting configuration.

In Alt.-A-2, when at least one of the specific events in operation example 1-5 is satisfied for a specific beam, UE200 may transmit the SRS RSRP or CLI RSSI for a CLI measurement resource having the same TCI state, spatial filter, or QCL type-D as the specific beam as a CLI report. Alternatively, UE200 may transmit the CLI report content specified in the CLI/CSI reporting setting as a CLI report.

In Alt.-3, when at least one of the specific events in operation examples 1-5 is satisfied for each beam, UE200 may transmit the CLI report content specified in the CLI/CSI reporting setting as a CLI report.

In Alt.-B, UE200 may report information or requests to assist in reporting CLIs triggered by gNB100.

For example, if the non-filtered or Layer 1/3 filtered CLI-RSSI/SRS-RSRP of the CLI measurement resource associated with the CLI/CSI reporting configuration satisfies Event I1 or Enhanced/Modified Event I1, the following actions may be performed:

In Alt.-B-1, the UE 200 may report to the gNB 100 the indexes of measurement resources of the CLIs (e.g., CLI-RSSI/SRS-RSRP measurement resource indexes) that meet the trigger conditions of the event.

　With such a configuration, gNB100 can trigger a CLI/CSI associated with the index and the measurement resource of the corresponding CLI, and can exchange information for coordination with gNBs adjacent to gNB100.

In Alt.-B-2, UE200 may report to gNB100 the index of the CLI/CSI reporting setting associated with the measurement resource of the CLI that satisfies the trigger condition of the event.

With this configuration, the gNB100 can trigger the CLI/CSI that corresponds to the index.

In Alt.-B-3, the UE 200 may send information requesting a CLI report (e.g., a CLI report triggering request) to the gNB 100.

For example, if at least one of the specific events in operation examples 1-5 is satisfied for a specific beam, the following operations may be performed.

In Alt.-B-4, UE200 may report to gNB100 the index of the beam that meets the trigger condition of the event.

　With such a configuration, gNB100 can trigger a CLI/CSI associated with the index and the measurement resource of the corresponding CLI, and can exchange information for coordination with gNBs adjacent to gNB100.

In Alt.-B-5, UE200 reports to gNB100 the index of the CLI/CSI reporting setting associated with the CLI measurement resource having the same TCI state, spatial filter or QCL type-D as the specific beam that satisfies the trigger condition of the event.

With this configuration, the gNB100 can trigger the CLI/CSI that corresponds to the index.

In Alt.-B-6, the UE 200 may send information requesting a CLI report (e.g., a CLI report triggering request) to the gNB 100.

(5) Actions and Effects In the embodiment, a CLI report is transmitted based on a specific event (e.g., Operation Example 1-4) defined by the reception status of a DL signal. With such a configuration, it is possible to reduce the possibility that a large CLI is not appropriately reflected in the CLI report, and it is possible to appropriately execute the CLI report.

(6) Other Embodiments The contents of the present invention have been described above in accordance with the embodiments. However, the present invention is not limited to these descriptions, and it will be obvious to those skilled in the art that various modifications and improvements are possible.

Although not specifically mentioned in the above disclosure, the UE capabilities shown below may be defined. The UE capabilities shown below may be reported from UE200 to gNB100.

The UE capability may include information indicating whether or not a specific event is supported for reporting CLI at Layer 3. The UE capability may include information indicating whether or not a specific event of operation example 1 (failed reception of PDSCH and/or PDCCH) is supported for reporting CLI at Layer 3. The UE capability may include information indicating whether or not a specific event of operation example 2 (instance of poor measurement quality of BFD-RS) is supported for reporting CLI at Layer 3. The UE capability may include information indicating whether or not a specific event of operation example 3 (CSI report with poor measurement quality) is supported for reporting CLI at Layer 3. The UE capability may include information indicating whether or not a specific event of operation example 4 (CSI/CMR instance with poor measurement quality) is supported for reporting CLI at Layer 3.

The UE capability may include information indicating whether or not a specific event is supported for CLI reporting at Layer 1. The UE capability may include information indicating whether or not a specific event of operation example 1 (failed reception of PDSCH and/or PDCCH) is supported for CLI reporting at Layer 1. The UE capability may include information indicating whether or not a specific event of operation example 2 (instance of poor measurement quality of BFD-RS) is supported for CLI reporting at Layer 1. The UE capability may include information indicating whether or not a specific event of operation example 3 (CSI report with poor measurement quality) is supported for CLI reporting at Layer 1. The UE capability may include information indicating whether or not a specific event of operation example 4 (CSI/CMR instance with poor measurement quality) is supported for CLI reporting at Layer 1.

In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be read as interchangeable. Similarly, link, associate, correspond, and map may be read as interchangeable, and allocate, assign, monitor, and map may also be read as interchangeable.

Furthermore, specific, dedicated, UE-specific, and UE-individual may be read as interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be read as interchangeable.

The block diagrams (FIGS. 4 and 5) used to explain the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically combined, or may be realized using two or more devices that are physically or logically separated and connected directly or indirectly (for example, using wires, wirelessly, etc.) and these multiple devices. The functional blocks may be realized by combining the one device or the multiple devices with software.

Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for any of these.

Furthermore, the above-mentioned gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 16 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 16, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

In the following explanation, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

Each functional block of the device (see Figures 4 and 5) is realized by any hardware element of the computer device, or a combination of the hardware elements.

Furthermore, each function of the device is realized by loading a specific software (program) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications by the communications device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) that includes an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc.

The processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

Memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 may store a program (program code), software module, etc. capable of executing a method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc.

The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

Furthermore, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

Furthermore, the notification of information is not limited to the aspects/embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in this disclosure may be combined with other aspects/embodiments of the present invention, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system ( The present invention may be applied to at least one of systems using LTE, LTE-A, LTE-G (xG) (x is, for example, an integer or decimal point), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate systems, and next-generation systems that are based on and extend these systems. The present invention may also be applied to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

The processing steps, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

In this disclosure, certain operations that are described as being performed by a base station may in some cases also be performed by its upper node. In a network consisting of one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by at least one of the base station and other network nodes other than the base station (such as, but not limited to, an MME or S-GW). Although the above example shows a case where there is one other network node other than the base station, it may also be a combination of multiple other network nodes (such as an MME and an S-GW).

Information, signals (information, etc.) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may be input and output via multiple network nodes.

The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be sent to another device.

The determination may be based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., a comparison with a predetermined value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched depending on the execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

In addition, software, instructions, information, etc. may be transmitted and received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

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

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

The names used for the above-mentioned parameters are not limiting in any respect. Furthermore, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.

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

A base station can accommodate one or more (e.g., three) cells (also called sectors). If a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or a base station subsystem that provides communication services within that coverage.

In this disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving object, or the moving object itself, etc. The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

Furthermore, the base station in the present disclosure may be interpreted as a mobile station (user terminal, the same applies below). For example, each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to communication between terminals (for example, "side"). For example, the uplink channel, downlink channel, etc. may be interpreted as a side channel.

Similarly, the mobile station in this disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions of the mobile station.

A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe.

A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate, for example, at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, a particular filtering operation performed by the transceiver in the frequency domain, a particular windowing operation performed by the transceiver in the time domain, etc.

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

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

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name that corresponds to the radio frame, subframe, slot, minislot, and symbol.

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

Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length of 1 ms or more but less than the TTI length of a long TTI.

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

Furthermore, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

Furthermore, a resource block may be composed of one or more resource elements (RE). For example, one RE may be a radio resource area of one subcarrier and one symbol.

A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell," "carrier," etc. in this disclosure may be read as "BWP."

The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

The reference signal may also be abbreviated as Reference Signal (RS) or referred to as a pilot depending on the applicable standard.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the noun following these articles is in the plural form.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), and considering ascertaining as "judging" or "determining." Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and considering ascertaining as "judging" or "determining." Additionally, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to have been "judged" or "decided." In other words, "judgment" and "decision" can include considering some action to have been "judged" or "decided." Additionally, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

FIG. 17 shows an example of the configuration of a vehicle 2001. As shown in FIG. 17, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013.

The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

Signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels acquired by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels acquired by an air pressure sensor 2023, a vehicle speed signal acquired by a vehicle speed sensor 2024, an acceleration signal acquired by an acceleration sensor 2025, an accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, a brake pedal depression amount signal acquired by a brake pedal sensor 2026, a shift lever operation signal acquired by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028.

The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

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

The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, etc.

The communication module 2013 transmits a current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits to an external device via wireless communication the following signals input to the electronic control unit 2010: a front wheel or rear wheel rotation speed signal acquired by a rotation speed sensor 2022, a front wheel or rear wheel air pressure signal acquired by an air pressure sensor 2023, a vehicle speed signal acquired by a vehicle speed sensor 2024, an acceleration signal acquired by an acceleration sensor 2025, an accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, a brake pedal depression amount signal acquired by a brake pedal sensor 2026, a shift lever operation signal acquired by a shift lever sensor 2027, and a detection signal for detecting an obstacle, a vehicle, a pedestrian, etc. acquired by an object detection sensor 2028.

The communication module 2013 receives various information (traffic information, signal information, vehicle distance information, etc.) transmitted from an external device, and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, and the like provided in the vehicle 2001.

　Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended as an illustrative example and does not have any limiting meaning with respect to the present disclosure.

(Additional Note)
The above disclosure may be expressed as follows:

The first feature is a terminal that includes a control unit that controls measurement of inter-link interference and a transmission unit that transmits a report of the inter-link interference, and the transmission unit transmits the report of the inter-link interference based on a specific event defined by the reception status of a downlink signal.

The second feature is that in the first feature, the specific event is defined based on the number of times reception of the downlink signal is unsuccessful or the number of times poor quality measurements of the downlink signal are made.

The third feature is the terminal according to the first or second feature, wherein the specific event is defined based on a timer that is activated by a failure to receive the downlink signal or a poor quality measurement of the downlink signal.

The fourth feature is a base station that includes a receiver that receives a report of inter-link interference and a controller that assumes receipt of the report of inter-link interference, and the controller assumes that a terminal transmits the report of inter-link interference based on a specific event that is defined by the reception status of a downlink signal.

The fifth feature is a wireless communication system comprising a terminal and a base station, the terminal comprising a control unit that controls measurement of inter-link interference and a transmission unit that transmits a report of the inter-link interference, and the transmission unit transmits the report of the inter-link interference based on a specific event defined by the reception status of a downlink signal.

The sixth feature is a wireless communication method comprising step A of controlling measurement of inter-link interference and step B of transmitting a report of the inter-link interference, the step B including a step of transmitting the report of the inter-link interference based on a specific event defined by a reception status of a downlink signal.

10 Wireless Communication Systems 20 NG-RAN
100 gNB
110 Receiving unit 120 Transmitting unit 130 Control unit 200 UE
210 Radio signal transmitting/receiving unit 220 Amplifier unit 230 Modulation/demodulation unit 240 Control signal/reference signal processing unit 250 Encoding/decoding unit 260 Data transmitting/receiving unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM)
2033 communication port

Claims (6)

A control unit for controlling measurement of inter-link interference;
a transmitter configured to transmit the report of the inter-link interference;
The terminal, wherein the transmitter transmits a report of the link interference based on a specific event defined by a reception status of a downlink signal. The terminal according to claim 1, wherein the specific event is defined based on the number of failures to receive the downlink signal or the number of poor quality measurements of the downlink signal. The terminal according to claim 1, wherein the specific event is defined based on a timer that is triggered by failure to receive the downlink signal or a poor quality measurement of the downlink signal. a receiver for receiving a report of inter-link interference;
a control unit configured to receive a report of the inter-link interference;
The control unit assumes that the terminal transmits the report of the link interference based on a specific event defined by a reception status of a downlink signal. A terminal and a base station,
The terminal includes:
A control unit for controlling measurement of inter-link interference;
a transmitter configured to transmit the report of the inter-link interference;
A wireless communication system, wherein the transmitter transmits the report of the link interference based on a specific event defined by a reception status of a downlink signal. A step A of controlling a measurement of inter-link interference;
B. transmitting the inter-link interference report;
The wireless communication method, wherein the step B includes a step of transmitting a report of the link interference based on a specific event defined by a reception status of a downlink signal.

Images