Methods and apparatus for interference measurement in communication systems

By configuring the sounding reference signal (SRS) symbol type and measurement method in the communication system, the communication quality problem at the edge of the base station coverage area was solved, and effective measurement of interference and improvement of communication quality were achieved.

CN123125933APending Publication Date: 2026-11-17ELECTRONICS & TELECOMM RES INST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580029498.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-27
Filing Date
2025-06-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In communication systems, especially at the edge of base station coverage, the communication quality between terminals and base stations may be reduced, resulting in ineffective communication.

Method used

By configuring sounding reference signals (SRS) between the user equipment (UE) and the base station, the valid SRS symbol type is determined, and channel and interference measurements are performed based on the symbol type. Transmission time is determined using timing advance (TA), SRS-RSRP or CLI-RSSI measurements are performed, and CSI reports are generated and sent to the base station with priority.

Benefits of technology

This improves the performance of the communication system. By measuring the link interference between the attacker and the victim, the base station can better control communication and improve the communication quality of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125933A_ABST
    Figure CN123125933A_ABST
Patent Text Reader

Abstract

A method and apparatus for interference measurement in a communication system are disclosed. The method for a first user equipment (UE) includes the following steps: receiving sounding reference signal (SRS) configuration information from a base station; determining one or more valid SRS symbols in the SRS resource based on the symbol type of the SRS resource indicated by the SRS configuration information; and transmitting the SRS to the base station using the one or more valid SRS symbols.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to communication technology, and more specifically, to techniques for measuring interference with signals in communication systems. Background Technology

[0002] Furthermore, with the advancement of information and communication technologies, various wireless communication technologies are being developed. Representative wireless communication technologies may include Long Term Evolution (LTE) and New Radio (NR) as specified in the 3GPP standards. LTE can be one of the wireless communication technologies in fourth-generation (4G) wireless communication technology, while NR can be one of the wireless communication technologies in fifth-generation (5G) wireless communication technology.

[0003] With the commercialization of 4G communication systems (e.g., LTE-enabled systems), in addition to the frequency bands used by 4G systems (e.g., below 6 GHz), 5G communication systems (e.g., NR-enabled systems) are being considered, utilizing frequency bands above 4G (e.g., above 6 GHz) to address the growing demand for wireless data processing. 5G communication systems can support enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC). Discussions regarding 6G communication systems following 5G are ongoing.

[0004] Furthermore, when the terminal is located at the edge of a base station's coverage area, the communication quality between the terminal and the base station may degrade. In this case, the terminal may be unable to communicate with the base station. A method is needed to address this problem. Summary of the Invention

[0005] [Technical Issues]

[0006] This disclosure aims to provide a method and apparatus for measuring interference with signals in a communication system.

[0007] A method for achieving the above objectives according to an exemplary embodiment of the present disclosure may include: receiving sounding reference signal (SRS) configuration information from a base station; determining one or more valid SRS symbols within an SRS resource indicated by the SRS configuration information based on the symbol type of the SRS resource; and transmitting the SRS to the base station using the one or more valid SRS symbols, wherein the symbol type indicates a subband full duplex (SBFD) symbol or a non-SBFD (N-SBFD) symbol.

[0008] Based on the symbol type being indicated as SBFD symbol, one or more SBFD symbols within an SRS resource can be identified as one or more valid SRS symbols.

[0009] Based on the symbol type being indicated as N-SBFD symbol, one or more N-SBFD symbols within an SRS resource can be identified as one or more valid SRS symbols.

[0010] The transmission of SRS within invalid SRS symbols in an SRS resource indicated by the SRS configuration information can be discarded on a symbol-by-symbol basis.

[0011] SRS resources can be configured to be associated with a set of channel measurement resources (CMR) or interference measurement resources (IMR), and measurements of SRS-reference signal received power (SRS-RSRP) or cross-link interference-received signal strength indicator (CLI-RSSI) can be performed on the SRS resources.

[0012] Timing advance (TA) can be considered to determine the transmission time of SRS.

[0013] SRS configuration information may include information about SRS resource sets, and the SRS resource sets indicated by the SRS configuration information may include information about the indicator symbol type.

[0014] Symbol types can be applied together to one or more SRS resources belonging to an SRS resource set.

[0015] A method for a second user equipment (UE) to achieve the above objectives according to an exemplary embodiment of the present disclosure may include: receiving probe reference signal (SRS) configuration information from a base station; determining one or more valid SRS symbols within an SRS resource indicated by the SRS configuration information based on the symbol type of the SRS resource; and performing a measurement operation on an SRS transmitted by a first UE in one or more valid SRS symbols, wherein the symbol type indicates a subband full-duplex (SBFD) symbol or a non-SBFD (N-SBFD) symbol.

[0016] Based on the symbol type being indicated as SBFD symbol, one or more SBFD symbols within an SRS resource can be identified as one or more valid SRS symbols.

[0017] Based on the symbol type being indicated as N-SBFD symbol, one or more N-SBFD symbols within an SRS resource can be identified as one or more valid SRS symbols.

[0018] SRS resources can be configured to be associated with a set of channel measurement resources (CMR) or an interference measurement resource (IMR) set, and measurements of SRS reference signal received power (SRS-RSRP) or cross-link interference received signal strength indicator (CLI-RSSI) can be performed on the SRS resources.

[0019] Timing advance (TA) can be considered to determine the measurement time of SRS.

[0020] The method may further include: determining the priority of a channel state information (CSI) report that includes an SRS-RSRP or CLI-RSSI as a measurement result of SRS; and sending a CSI report to a base station based on the priority, wherein the priority of the CSI report including the SRS-RSRP or CLI-RSSI may be determined based on Layer 1 (L1)-RSRP.

[0021] Measurements of the SRS can be performed based on the Transmission Configuration Indicator (TCI) status indicated for the Synchronization Signal Block (SSB) or Downlink Reference Signal (RS).

[0022] Measurement operations on the SRS can be performed based on the TCI status received by the second UE.

[0023] The method may further include receiving downlink control information (DCI) that triggers a CSI report from a base station, wherein the measurement operation of SRS can be performed in a time slot offset from the time slot in which the DCI is received, and the offset can be indicated by the base station.

[0024] The method may further include: receiving information from a base station about a frequency band for measuring CLI-RSSI, wherein the information about the frequency band may include the location of a first physical resource block (PRB) of the frequency band and the number of PRBs constituting the frequency band, and CLI-RSSI can be measured within the frequency band indicated by the base station.

[0025] SRS configuration information may include information about SRS resource sets, and SRS resource sets may include information about indicator symbol types.

[0026] Symbol types can be applied together to SRS resources that belong to an SRS resource set.

[0027] [Beneficial Effects]

[0028] According to this disclosure, an attacker terminal can determine valid Sounding Reference Signal (SRS) resources based on symbol type and can use these valid SRS resources to transmit SRS. A victim terminal can determine valid SRS resources based on symbol type, perform measurement operations (e.g., cross-link interference (CLI) measurement operations) on these valid SRS resources, and send a Channel State Information (CSI) report including the measurement results to the base station. Based on these operations, interference on the link between the attacker and victim terminals can be measured, and the base station can control communication between the attacker and / or victim terminals based on the measured interference. Therefore, the performance of the communication system can be improved. Attached Figure Description

[0029] Figure 1 This is a conceptual diagram illustrating an exemplary embodiment of a communication system.

[0030] Figure 2 This is a block diagram illustrating an exemplary embodiment of a communication node constituting a communication system.

[0031] Figure 3 This is a conceptual diagram illustrating an exemplary embodiment of a subband filtering mask used for DL ​​and UL subbands in SD symbols.

[0032] Figure 4 This is a conceptual diagram illustrating an exemplary embodiment of a slotted mode (e.g., TDD slotted mode) that includes SD symbols.

[0033] Figure 5 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing a TDD system.

[0034] Figure 6 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0035] Figure 7 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0036] Figure 8 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0037] Figure 9 This is a conceptual diagram illustrating an interference scenario where both the attacker's and victim's terminals are provided with services from the same TRP, based on SBFD operations.

[0038] Figure 10 This is a conceptual diagram illustrating an interference scenario based on SBFD operation where the attacker's terminal and the victim's terminal are provided with services from different TRPs.

[0039] Figure 11 This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI reporting configuration of the victim's terminal.

[0040] Figure 12 This is a conceptual diagram illustrating an extended exemplary embodiment of the SRS configuration of the attacker's terminal.

[0041] Figure 13 This is a conceptual diagram illustrating an exemplary embodiment of an attacking terminal sending an SRS after receiving scheduling information from a UL signal / channel.

[0042] Figure 14 This is a conceptual diagram illustrating an exemplary embodiment for determining the location of time resources for measuring the UE to the UE CLI.

[0043] Figure 15 This is a conceptual diagram illustrating an exemplary embodiment of SRS resources used for measuring UE to UE CLI.

[0044] Figure 16 This is a conceptual diagram illustrating an exemplary embodiment of the timing relationship of a victim's terminal using SRS to send non-periodic CSI reports.

[0045] Figure 17 This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI report configuration for measuring the victim's terminal from the UE to the UE-CLI.

[0046] Figure 18a and Figure 18b This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI report configuration for measuring the victim's terminal from the UE to the UE-CLI.

[0047] Figure 19This is a conceptual diagram illustrating an exemplary embodiment of a victim terminal measuring UE to UE CLI that receives scheduling information for DL ​​signals / channels. Detailed Implementation

[0048] Because this disclosure can be modified in various ways and has many forms, specific exemplary embodiments will be shown in the accompanying drawings and described in detail in the detailed description. However, it should be understood that this is not intended to limit this disclosure to the specific exemplary embodiments, but rather, this disclosure will cover all modifications and substitutions that fall within the spirit and scope of this disclosure.

[0049] Related terms such as "first," "second," etc., may be used to describe various elements, but the elements should not be limited by the terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of this disclosure, a first component may be named a second component, and a second component may similarly be named a first component. The term "and / or" means any one or a combination of a plurality of related and described items.

[0050] In exemplary embodiments of this disclosure, "at least one of A and B" may refer to "at least one of A or B" or "at least one of a combination of one or more of A and B". Furthermore, "one or more of A and B" may refer to "one or more of A or B" or "one or more of a combination of one or more of A and B".

[0051] When it is said that a component is "coupled" or "connected" to another component, it should be understood that the component is directly "coupled" or "connected" to the other component, or that another component may be placed between them. Conversely, when it is said that a component is "directly coupled" or "directly connected" to another component, it should be understood that no other component is placed between them.

[0052] The terminology used in this disclosure is used only to describe particular exemplary embodiments and is not intended to limit the disclosure. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this disclosure, terms such as 'comprising' or 'having' are intended to specify the presence of features, quantities, steps, operations, components, parts, or combinations thereof described in the specification; however, it should be understood that these terms do not exclude the presence or addition of one or more features, quantities, steps, operations, components, parts, or combinations thereof.

[0053] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms that are commonly used and already in dictionaries should be interpreted as having the meaning appropriate to the context in this art. In this specification, terms are not necessarily construed as having a formal meaning unless explicitly defined.

[0054] In the following description, the form of this disclosure will be described in detail with reference to the accompanying drawings. In describing this disclosure, for the purpose of facilitating an overall understanding of the disclosure, similar numerals will refer to similar elements throughout the description of the drawings, and repeated descriptions thereof will be omitted.

[0055] A communication system based on exemplary embodiments of the present disclosure will be described. The communication system based on exemplary embodiments of the present disclosure is not limited to what is described below, and can be applied to various communication systems. Here, "communication system" can be used in the same sense as "communication network".

[0056] In an exemplary embodiment, 'configuration of an operation (e.g., a transmission operation)' may mean 'signaling of configuration information (e.g., information elements, parameters) of the operation' and / or 'signaling of information instructing the execution of the operation'. 'Configuration of information elements (e.g., parameters)' may mean signaling the corresponding information element. The signaling may be at least one of the following: system information (SI) signaling (e.g., transmission of system information block (SIB) and / or master information block (MIB)), radio resource control (RRC) signaling (e.g., transmission of RRC messages, RRC parameters, and / or higher-level parameters), MAC control element (CE) signaling (e.g., transmission of MAC messages and / or MAC CE), PHY signaling (e.g., transmission of downlink control information (DCI), uplink control information (UCI), and / or sidelink control information (SCI)), or combinations thereof.

[0057] Figure 1 This is a conceptual diagram illustrating an exemplary embodiment of a communication system.

[0058] refer to Figure 1The communication system 100 may include multiple communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6. Furthermore, the communication system 100 may also include a core network (e.g., a serving gateway (S-GW), a packet data network-gateway (P-GW), and a mobility management entity (MME)). When the communication system 100 is a 5G communication system (e.g., an NR system), the core network may include access and mobility management functions (AMF), user plane functions (UPF), session management functions (SMF), etc.

[0059] Multiple communication nodes 110 to 130 can support communication protocols defined by the technical specifications of the 3rd Generation Partnership Project (3GPP) (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). Multiple communication nodes 110 to 130 can support communication protocols based on Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiplexing (OFDM), Filtered OFDM, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier FDMA (SC-FDMA), and Non-Orthogonal Multiple Access (NOMA). Communication protocols include those based on generalized frequency division multiplexing (GFDM), filter bank multi-carrier (FBMC), universal filtered multi-carrier (UFMC), and space division multiple access (SDMA). Each of the multiple communication nodes can have the following structure.

[0060] Figure 2 This is a block diagram illustrating an exemplary embodiment of a communication node constituting a communication system.

[0061] refer to Figure 2The communication node 200 may include at least one processor 210, a memory 220, and a transceiver 230 connected to a network to perform communication. Furthermore, the communication node 200 may also include an input interface device 240, an output interface device 250, a storage device 260, etc. The corresponding components included in the communication node 200 can be connected to each other via a bus 270 to communicate.

[0062] However, each component included in communication node 200 may be connected to processor 210 via a separate interface or independent bus, rather than via a common bus 270. For example, processor 210 may be connected to at least one of memory 220, transceiver 230, input interface device 240, output interface device 250, and storage device 260 via a dedicated interface.

[0063] Processor 210 can execute a program stored in at least one of memory 220 and storage device 260. Processor 210 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor that executes methods according to embodiments of the present disclosure thereon. Each of memory 220 and storage device 260 may be constituted by at least one of volatile storage medium and non-volatile storage medium. For example, memory 220 may include at least one of read-only memory (ROM) and random access memory (RAM).

[0064] Refer again Figure 1 The communication system 100 may include multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2, and multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6. Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell, and each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may be within the cell coverage area of ​​the first base station 110-1. Furthermore, the second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may be within the cell coverage area of ​​the second base station 110-2. Furthermore, the fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 can all fall within the cell coverage area of ​​the third base station 110-3. Additionally, the first terminal 130-1 can fall within the cell coverage area of ​​the fourth base station 120-1, and the sixth terminal 130-6 can fall within the cell coverage area of ​​the fifth base station 120-2.

[0065] Here, each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can refer to Node-B, Evolved Node-B (eNB), gNB, Advanced Base Station (ABS), High Reliability Base Station (HR-BS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Access Point, Access Node, Radio Access Station (RAS), Mobile Multi-hop Relay Base Station (MMR-BS), Relay Station (RS), Advanced Relay Station (ARS), High Reliability Relay Station (HR-RS), Home Node B (HNB), Home eNode B (HeNB), Roadside Unit (RSU), Radio Remotehead (RRH), and Transmission Point (TP). Points, transmission and reception points (TRPs), etc.

[0066] Each of the multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 can refer to User Equipment (UE), Terminal Equipment (TE), Advanced Mobile Station (AMS), High Reliability Mobile Station (HR-MS), Terminal, Access Terminal, Mobile Terminal, Station, Subscriber Station, Mobile Station, Portable Subscriber Station, Node, Equipment, On Board Unit (OBU), etc.

[0067] Furthermore, each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can operate in the same or different frequency bands. The multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can be interconnected via ideal or non-ideal backhaul, and exchange information with each other via ideal or non-ideal backhaul. In addition, each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can be connected to the core network via ideal or non-ideal backhaul. Each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can transmit signals received from the core network to the corresponding terminal 130-1, 130-2, 130-3, 130-4, 130-5, or 130-6, or transmit signals received from the corresponding terminal 130-1, 130-2, 130-3, 130-4, 130-5, or 130-6 to the core network.

[0068] In addition, each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can support multi-input multi-output (MIMO) transmission (e.g., single-user MIMO, multi-user MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in unlicensed frequency bands, device-to-device (D2D) communication (or proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), etc. Here, each of the multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 can perform an operation corresponding to the operation of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 (i.e., an operation supported by the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2). For example, the second base station 110-2 can transmit signals to the fourth terminal 130-4 in SU-MIMO mode, and the fourth terminal 130-4 can receive signals from the second base station 110-2 in SU-MIMO mode. Alternatively, the second base station 110-2 can transmit signals to the fourth terminal 130-4 and the fifth terminal 130-5 in MU-MIMO mode, and the fourth terminal 130-4 and the fifth terminal 130-5 can receive signals from the second base station 110-2 in MU-MIMO mode.

[0069] The first base station 110-1, the second base station 110-2, and the third base station 110-3 can transmit signals to the fourth terminal 130-4 in CoMP mode, and the fourth terminal 130-4 can receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 in CoMP mode. Furthermore, each of the multiple base stations 110-1, 110-2, 110-3, 120-1, and 120-2 can exchange signals with corresponding terminals 130-1, 130-2, 130-3, 130-4, 130-5, or 130-6 within its cell coverage area in CA mode. Each of base stations 110-1, 110-2 and 110-3 can control the D2D communication between the fourth terminal 130-4 and the fifth terminal 130-5, so the fourth terminal 130-4 and the fifth terminal 130-5 can perform D2D communication under the control of the second base station 110-2 and the third base station 110-3.

[0070] The following describes the operation methods of communication nodes in a communication system. Even when describing a method performed at a first communication node (e.g., transmitting or receiving a signal), a corresponding second communication node can also perform a method corresponding to the method performed at the first communication node (e.g., receiving or transmitting a signal). That is, when describing the operation of a terminal, the corresponding base station can perform an operation corresponding to the terminal's operation. Conversely, when describing the operation of a base station, the corresponding terminal can perform an operation corresponding to the base station's operation.

[0071] To reduce the data error rate, a low modulation coding scheme (MCS) level (or, a low MCS index) can be applied. To avoid increasing the size of the field indicated by the downlink control information (DCI), frequently used MCSs can be selected. Applying a lower MCS allows for repeated transmission operations. Further rate reduction may occur when applying quadrature phase shift keying (QPSK) at the lowest modulation rate. In particular, since transmit power is limited in uplink (UL) transmissions, repeated transmission operations can be performed in the time domain rather than the frequency domain.

[0072] In the cases of eMBB and URLLC services, a lower MCS can be used for different purposes. For example, for eMBB services, a lower MCS might be needed to extend coverage. On the other hand, for URLLC services, a lower MCS might be needed to reduce latency and achieve a lower error rate. Due to the different requirements, eMBB services can be retransmitted even when relatively large latency occurs. URLLC services can be transmitted using a new MCS (e.g., a low MCS) instead of retransmission. The new MCS can be configured by RRC messages and / or DCI.

[0073] To support repeated transmissions of eMBB services in the time domain, physical uplink shared channel (PUSCH) repetition (e.g., PUSCH repetition type A) can be introduced. In this disclosure, PUSCH repetition can refer to a PUSCH instance. In other words, depending on the context, PUSCH repetition can be interpreted as having the same meaning as a PUSCH instance. Repeated transmissions of PUSCH can be performed on a per-PUSCH-in-instance basis. When performing repeated transmissions of PUSCH, PUSCHs can be repeatedly transmitted based on time slot allocation. To extend coverage, time resources can be allocated across multiple time slots. When using PUSCH repetition type A, time resources can be configured via RRC messages and / or DCI. The number of PUSCH repetitions can be indicated by RRC messages, and the time resources used to transmit PUSCHs in the first time slot can be indicated by DCI (e.g., in the case of type 2 configuration grant (CG) or dynamic grant) or RRC messages (e.g., in the case of type 1 CG). In this disclosure, the number of repetitions can refer to the number of repeated transmissions or the number of transmissions.

[0074] Repeatedly transmitting URLLC services may be unsuitable due to the latency incurred. However, using a sufficiently low MCS can reduce the latency during URLLC service decoding. That is, with a sufficiently low MCS, the number of resource elements (REs) mapped to the URLLC service may increase, and the base station (e.g., the base station's decoder) should wait until all REs are received. In this case, the latency during URLLC service decoding can be reduced.

[0075] When repeatedly transmitting PUSCHs with a slightly higher MCS, the base station can perform decoding operations using only a few REs. The first successful decoding in a repeated PUSCH transmission (e.g., a repeated PUSCH transmission with a slightly higher MCS) can occur earlier than the first successful decoding in a non-repeated PUSCH transmission (e.g., a PUSCH transmission with a low MCS). Unnecessary delays may occur when using PUSCH repetition type A, and therefore PUSCH repetition type B can be introduced to reduce delays due to repeated transmissions. When using PUSCH repetition type B, PUSCHs based on micro-slot allocation can be repeatedly transmitted. When using PUSCH repetition type B, time resources can be configured via RRC messages and / or DCI. The combination of the reference time resources and repetition count for a PUSCH instance can be indicated by DCI (e.g., type 2 CG and / or dynamic granting) or RRC messages (e.g., type 1 CG).

[0076] To control the transmit power of Sounding Reference Signals (SRS) resources indicated by SRS Resource Indicators (SRIs), the base station can estimate the path loss for each SRS resource. The base station can use a Directive Interpreter Code (DCI) to control the transmit power of SRS resources. The transmit power of SRS resources can be controlled based on the estimated path loss. The DCI can be a scheduling DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, or DCI format 1_2) or a group common (GC)-DCI (e.g., DCI format 2_2 or DCI format 2_3). The DCI may include fields indicating transmit power control (TPC) commands, and TPC commands can be used to control the transmit power of the terminal. For example, the transmit power of the terminal can be increased or decreased based on the TPC commands included in the DCI. To determine the transmit power of the PUSCH, the terminal can consider values ​​obtained based on path loss, values ​​according to the TPC commands included in the DCI, and / or the PUSCH bandwidth indicated by the DCI.

[0077] The base station can configure two or more sets in the terminal using higher-layer signaling. The terminal can receive configuration information for the two or more sets from the base station. The elements constituting the two or more sets can be transmit power parameters and can be indicated to be suitable for different scenarios (e.g., URLLC scenario, eMBB scenario). The terminal can receive a scheduling DCI or activation DCI for allocating PUSCH resources from the base station, and the scheduling DCI or activation DCI can indicate the set used to interpret the transmit power parameters. If different sets of transmit power parameters are used, the magnitude of the increase or decrease in transmit power indicated by the same TPC command may vary.

[0078] When using Type 1 Configuration Grant (CG) or Type 2 CG, the transmit power can be determined based on the DCI format 2_3 of the SRI associated with the PUSCH instance. When using Type 2 CG, activating the DCI can indicate the set of transmit power parameters applicable to the PUSCH timing. The PUSCH timing can refer to the PUSCH instance. The terminal can obtain the TPC command for the SRI by receiving the GC-DCI, interpret the TPC command to suit the set of transmit power parameters indicated by the base station, and derive the transmit power to be applied to the PUSCH instance based on the interpretation result.

[0079] In dynamically scheduled PUSCH transmissions, the terminal can derive the transmit power to be applied to the PUSCH instance based on a combination of GC-DCI and scheduling DCI. By receiving GC-DCI, the terminal can identify the TPC command corresponding to the SRI and store the identified TPC command. In dynamically scheduled PUSCH transmissions, the scheduling DCI can indicate the set of transmit power parameters and / or TPC commands applicable to the PUSCH timing. The terminal can derive the transmit power to be applied to the PUSCH instance based on the transmit power of the SRI associated with the PUSCH instance.

[0080] Repeated HARQ-ACK transmissions can be indicated (or configured) by higher-layer signaling for each Physical Uplink Control Channel (PUCCH) format. The number of repetitions for PUCCH format i can be set independently. i can be 1, 3, or 4. Terminals can repeatedly transmit the PUCCH format within a time slot. In this case, the same time resources can be used to transmit the PUCCH format within the corresponding time slot.

[0081] Uplink Control Information (UCI) types can be categorized based on the type of information included in the UCI. A UCI may include at least one of a scheduling request (SR), Layer 1 Reference Signal Received Power (L1-RSRP), HARQ-ACK, or Channel State Information (CSI). In an exemplary embodiment, 'UCI' and 'UCI type' can be used interchangeably. In a UCI retransmission operation, only one UCI type can be transmitted. To support this operation, the priority of UCI types can be defined in the technical specification. A UCI type can be selected, and a PUCCH including that UCI type can be repeatedly transmitted. In this case, the terminal can assume that no other UCI types will be transmitted until the transmission of the selected UCI type is complete. To support the above operation, the base station can instruct the terminal to transmit a UCI (e.g., SR or HARQ-ACK) after the PUCCH transmission is complete. The waiting time for transmitting a UCI may be long, and this waiting time can act as a scheduling constraint on the base station.

[0082] When an instruction to transmit HARQ-ACK is made in the same time slot (or the same sub-time slot), or when PUCCH time resources indicated by DCI and / or RRC messages allocating a physical downlink shared channel (PDSCH) overlap, the terminal can generate a HARQ codebook such that the HARQ codebook is transmitted on a single PUCCH (e.g., a single PUCCH time resource). Within the HARQ codebook, HARQ-ACK bits can be arranged according to the order defined in the technical specification. Information bits can be generated based on the above operations. The terminal can generate encoded bits by performing encoding operations.

[0083] Reed Muller codes or polar codes can be used in encoding operations. The code rate applied in the encoding operation can be indicated by higher-layer signaling. For example, a value in the PUCCH format can be the code rate and can be indicated to the terminal.

[0084] A codeword can be mapped to a PUCCH. In repeated PUCCH transmissions, a UCI type can be generated as a codeword. When a PUCCH is transmitted once, information bits of one or more UCI types can be concatenated, and the terminal can generate a codeword by performing the same encoding operation on the information bits. Performing soft combining operations can be difficult to implement when using Reed-Muller codes or polar codes. Therefore, even when repeatedly transmitting PUCCHs, the same codeword can be transmitted, and the base station can perform chase combining operations on the same codeword. A codeword or encoded bit can refer to a bit string where multiple code blocks are concatenated. Modulation operations can be performed on the codeword, and the result of the modulation operation can be mapped to a RE.

[0085] Furthermore, UCIs with the same UCI type can be considered as different information. UCIs with the same UCI type that are considered as different information can be mapped. For example, UCIs can be generated to support services with different priorities. A UCI supporting eMBB services (e.g., SR or HARQ-ACK) can be considered as different information from a UCI supporting URLLC services (e.g., SR or HARQ-ACK). In this case, information with the same UCI type can be distinguished as different information.

[0086] The encoded UCI can be mapped to the PUCCH. The same preprocessing scheme (e.g., spatial information, spatial relationships) can be maintained during PUCCH transmission operations. Alternatively, the base station's RRC signaling can allow different preprocessing schemes to be used for each PUCCH during PUCCH transmission operations.

[0087] To support URLLC services, it may be preferable for the terminal to perform frequent receive operations in DL resources and / or frequent transmit operations in UL resources. In Time Division Duplex (TDD) systems, the terminal can operate based on a half-duplex scheme. Therefore, depending on the time slot mode, the support time for DL ​​and / or UL services may increase. On the other hand, in Frequency Division Duplex (FDD) systems, the terminal can utilize both DL and UL resources simultaneously. Therefore, the aforementioned problems in TDD systems may not occur in FDD systems. FDD systems can use two or more carriers. When configuring two or more serving cells for a terminal in a TDD system, the terminal can utilize both DL and UL resources.

[0088] In a communication system that includes at least one carrier using FDD (hereinafter referred to as 'FDD carrier'), there may be no latency issue in the terminal. In a communication system that includes only carriers using TDD (hereinafter referred to as 'TDD carrier'), latency issues may exist in the terminal. To address these issues, time slots in the TDD carrier can be configured according to different modes.

[0089] Carrier aggregation (CA) can be configured in the terminal, and PCell and SCell can be activated. A cell can be classified as either a PCell or an SCell based on whether a common search space (CSS) set is configured within it. For example, a CSS set can be configured in a PCell, while it may not be configured in an SCell. To reduce latency in communication systems supporting URLLC services, time slots with different modes can be configured and / or indicated to the terminal.

[0090] The transmission of eMBB or URLLC services can be supported in licensed and / or unlicensed frequency bands. Carriers belonging to licensed or unlicensed frequency bands can be used individually. Alternatively, depending on the base station configuration, frequency aggregation can be used to utilize all carriers belonging to licensed and unlicensed frequency bands.

[0091] In an exemplary embodiment, two or more terminals may receive data from and send data to one or more TRPs. It may be assumed that a base station or a server performs management and / or scheduling operations for one or more of the multiple TRPs. TRPs may be directly connected. Alternatively, TRPs may be connected via a base station. The connection may be based on an Xn interface or a radio interface (e.g., a 3GPP NR interface).

[0092] Shadow areas may exist between areas supported by TRPs. Therefore, TRPs can resolve shadow areas through cooperative transmission. Cooperative transmission can be performed for terminals located between TRPs. Even when shadow areas do not exist, a large number of TRPs (or base stations) can be deployed to send and receive large amounts of data, and the quality of radio links can be improved through TRPs.

[0093] Based on the cooperative transmission and reception of TRPs, communication schemes can be classified into dynamic point selection (DPS) and joint transmission (JT). For a specific set of Physical Resource Blocks (PRBs), DPS can be a method of receiving data through one TRP, while JT can be a method of receiving data through two or more TRPs. Dynamic point blanking (DPB) can be a type of JT. When using DPB, the terminal can receive data from the remaining TRPs instead of some. JTs can be further classified into coherent JP and incoherent JP. Depending on whether coherent combining operations are performed on the signals received from the TRPs, coherent JP or incoherent JP can be used.

[0094] Depending on the latency and / or traffic quota of the backhaul to which the base station or TRP is connected, the TRP can participate in cooperative transmission and / or cooperative reception in real time. A terminal can support JT by receiving a DCI (e.g., a single DCI (sDCI)). Alternatively, a terminal can support JT by receiving multiple DCIs (e.g., multiple DCIs (mDCI)).

[0095] When using sDCI, the terminal can use TRPs to send and receive data. When using sDCI, it is likely preferable that the TRPs cooperate via backhaul without latency. When using mDCI, the terminal can send and receive data using some TRPs. When the terminal sends and receives data with other TRPs, those other TRPs may have difficulty cooperating in real-time via backhaul. Allocating semi-static resources to other TRPs may be preferable.

[0096] CORESET pool indices can be used to identify TRPs. A CORESET pool can be a set of CORESETs, and the Transmission Configuration Indication (TCI) status applied to each CORESET can be independently indicated to the terminal via RRC signaling and / or MAC Control Element (CE) signaling. A CORESET pool index does not necessarily correspond to a TRP. Specifically, TRPs can be classified as Transmitting Points (TxPs) and Receiving Points (RxPs). A CORESET pool index can correspond to an RxP. For example, the Rx beam for a TxP can be derived from the TCI status, and an uplink signal / channel detected in a CORESET belonging to a CORESET pool indicated by a CORESET pool index and scheduled by the DCI can be interpreted as being received at the same RxP.

[0097] For terminals to gain an advantage through coherent combining, a certain degree of synchronization is required between the terminal's TRPs, and the TRP CSI reports need to be shared. In situations where these are not feasible, performing incoherent combining within the terminal may be advantageous in terms of performance.

[0098] When the terminal is installed in a vehicle, restrictions on its size and weight can be relaxed. When the terminal is carried by a person, portability can be considered.

[0099] Small cell or integrated access backhaul (IAB) nodes can be deployed to extend signal reach. The throughput of small cell or IAB nodes can be affected by the quality of the backhaul link, and establishing a backhaul network can be expensive. As an alternative, wireless relay devices can be deployed to deliver higher quality signals to terminals. Depending on the signal delivery scheme, wireless relay devices can be classified into several types. Because wireless relay devices support more functions, they can exhibit performance similar to base stations, and because they support fewer functions, they can be deployed at a lower cost. The wireless relay devices considered in this disclosure can perform the functions of beamforming terminals and minimal data forwarding. Base stations can transmit wireless signals to control these wireless relay devices. These wireless signals can be used to configure appropriate parameters of the wireless relay devices.

[0100] In this disclosure, channel transmission can refer to the transmission of messages, data, signals, and / or information on the channel, and channel reception can refer to the reception of messages, data, signals, and / or information on the channel. The channel can be a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), a physical sidelink broadcast channel (PSBCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), and / or a physical sidelink feedback channel (PSFCH).

[0101] In time-division duplex (TDD) communication systems, downlink (DL) communication and uplink (UL) communication can be performed in different time resources. The ratio between DL time (for DL ​​communication during its period) and UL time (for UL communication during its period) can be determined based on the ratio of services (e.g., DL services and / or UL services). For example, in an NR system, because the volume of DL services is greater than the volume of UL services, more DL time slots can be allocated than UL time slots. For example, time slots (e.g., time slot patterns) can be configured as a repeating pattern 'DDDSU'. D can indicate DL time slots, S can indicate special time slots including DL symbols, flexible (FL) symbols, and UL symbols, and U can indicate UL time slots. The arrangement order of symbols in the S time slot can be DL symbols-FL symbols-UL symbols. The base station can indicate or configure the time slot pattern to the terminal via signaling (e.g., RRC signaling). The base station can indicate some FL symbols among those configured by RRC signaling as DL symbols or UL symbols. Through DCI, some FL symbols can be indicated as DL symbols or UL symbols.

[0102] Terminals located in the cell boundary area can perform repeated transmission of UL signals / channels to deliver UL services to the base station. In this case, the signal-to-interference-plus-noise ratio (SINR) can be improved and the block error rate (BLER) can be reduced at the base station. In this disclosure, UL signal / channel can refer to UL signal and / or UL channel, while DL signal / channel can refer to DL signal and / or DL ​​channel. The base station can instruct the terminal to perform repeated transmission of UL signals / channels, and the terminal can perform repeated transmission of UL signals / channels based on instructions from the base station. The base station can instruct the terminal to perform repeated reception of DL signals / channels, and the terminal can perform repeated reception of DL signals / channels based on instructions from the base station. When UL time slots do not occur frequently, a long delay may occur for the terminal to obtain sufficient UL time slots for repeated transmission. For example, when the terminal is configured with mode 'DDDSU' and the subcarrier spacing (SCS) is 30 kHz, UL time slots may occur once every 2.5 ms. In this case, the time required for four repetitions of the UL signal / channel transmission can be 10 ms.

[0103] To reduce time delay, methods to improve the frequency structure of time slots can be considered. The base station can perform full-duplex communication. The frequency region of the DL symbol (or FL symbol) in the DL time slot (or DL ​​time slot and S time slot) can be divided into subbands. The base station can perform DL signal / channel transmission or UL signal / channel reception operations in some subbands of the DL time slot (e.g., DL symbols or FL symbols). Although the terminal performs half-duplex communication, the terminal can perform UL signal / channel transmission operations in the DL time slot (e.g., DL symbols or FL symbols). Symbols that allow both DL and UL communication can be referred to as Subband Full-Duplex (SBFD) symbols. For convenience, SBFD symbols can be referred to as 'SD symbols'. In other words, in this disclosure, SD symbols can refer to SBFD symbols. SD can be an abbreviation for SBFD. SD symbols can be interpreted as SD resources, and SBFD symbols can be interpreted as SBFD resources. The base station can configure SD symbols and / or non-SD symbols (e.g., N-SD symbols or ND symbols) to the terminal via signaling. The terminal can receive configuration information for SD symbols and / or ND symbols from the base station. The configuration information for SD symbols can be SBFD configuration information. The configuration information for ND symbols can be UL-DL configuration information. ND symbols can include UL symbols, DL symbols, and / or FL symbols. UL symbols, DL symbols, and / or FL symbols can be indicated (e.g., configured) based on UL-DL configuration information. DL communication or UL communication can be performed within ND symbols. ND symbols can be interpreted as either non-SD resources or ND resources. SBFD configuration information and UL-DL configuration information can be included in system information (e.g., SIB1).

[0104] Since DL and UL communications are performed within a single SD symbol (e.g., with the same time resources), a guard band can be introduced. The bandwidth of the guard band can vary depending on the interference level at the base station. Using different antenna arrays can reduce coupling between DL and UL communications. When minimal coupling occurs between DL and UL communications, a guard band may be unnecessary, or a small bandwidth may be required. In such cases, a separate guard band allocation may not be necessary. Alternatively, a small amount of PRB can be allocated to the guard band.

[0105] When there is minimal coupling between DL and UL communications, a separate Rx filtering or Rx processing operation can be performed at the base station, but a separate Tx filtering or Tx processing operation may not be necessary at the terminal. The filtering operation can be a radio frequency (RF) filtering operation. When performing RF filtering, spectral emissions affecting adjacent PRBs (e.g., out-of-band (OOB) emissions or adjacent channel leakage ratio (ACLR)) can be reduced, and saturation of RF components can be prevented.

[0106] DL subband and UL subband can have different frequencies. DL subband can refer to DL-available PRB. UL subband can refer to UL-available PRB. When leakage occurs, the analog-to-digital converter (ADC) may become saturated, and small signals may be ignored. The base station can appropriately arrange masks or apply signal processing methods between the antenna arrays. The base station can allocate guard bands with narrow bandwidths.

[0107] Figure 3 This is a conceptual diagram illustrating an exemplary embodiment of a subband filtering mask used for DL ​​and UL subbands in SD symbols.

[0108] refer to Figure 3 This can show the power spectral density or spectral mask used for DL ​​correlation filtering and / or UL correlation filtering. DL correlation filtering can be performed at the base station, and UL correlation filtering can be performed at the terminal. The UL subband can be located at the center of the carrier, and there can be two DL subbands. The DL band can be divided into two DL subbands by the UL subband. As another example, there can be two or more UL subbands, and DL subbands can exist in the remaining frequency bands.

[0109] Considering the location of the DL subband and / or UL subband, the base station may not need to perform DL correlation filtering. The terminal may perform UL correlation filtering considering the location of the UL subband.

[0110] To add (e.g., transmit) UL signals / channels while minimizing the number of UL time slots in the time slot pattern, SD symbols can be introduced. The base station can instruct or configure the terminal to repeatedly transmit UL signals / channels for terminals located at the cell edge. The terminal can determine the need for repeated transmission of UL signals / channels based on instructions or configuration from the base station. Scheduling information for allocating PUSCH / PUCCH can include a repetition factor for time resources. The terminal can identify the repetition factor included in the scheduling information. The repetition factor can indicate n repeated transmissions of PUSCH / PUCCH. n can be a natural number. One repeated transmission can mean one transmission of PUSCH / PUCCH. When no repetition factor is indicated to the terminal (e.g., when the scheduling information does not include a repetition factor), the terminal can transmit PUSCH / PUCCH once. In this disclosure, 'PUSCH / PUCCH' can refer to PUSCH and / or PUCCH. Scheduling information can include resource allocation information, resource activation information, and / or resource deactivation information. Scheduling information can be included in RRC messages, MAC messages (e.g., MAC CE), and / or PHY messages (e.g., DCI).

[0111] To extend the reach of the UL signal / channel, the base station can instruct the terminal to perform demodulation-reference signal (DM-RS) bundling via signaling (e.g., RRC signaling). The terminal can determine the need for DM-RS bundling based on signaling from the base station. The execution of DM-RS bundling can mean maintaining power consistency / phase continuity during repeated transmissions of PUSCH / PUCCH. When maintaining power consistency / phase continuity, the base station can perform channel estimation operations at once. Therefore, the reception performance of PUSCH / PUCCH at the base station can be improved. Power consistency / phase continuity can refer to power consistency and / or phase continuity. Power consistency / phase continuity can also refer to coherence (e.g., temporal coherence).

[0112] The base station can allocate SD symbols. The arrangement order of symbols within a time slot can be 'DL symbol - SD symbol - UL symbol'. FL symbols can be placed between DL symbols and SD symbols. Alternatively, FL symbols can be omitted between DL symbols and SD symbols.

[0113] Figure 4 This is a conceptual diagram illustrating an exemplary embodiment of a slotted mode (e.g., TDD slotted mode) that includes SD symbols.

[0114] refer to Figure 4The SD symbol can be placed after the DL symbol, and the UL symbol can be placed after the SD symbol. The frequency band used for the SD symbol can be divided into DL subband and UL subband.

[0115] The UL bandwidth of an SD symbol can differ from that of a UL symbol. The base station can apply different filtering operations to the SD and UL symbols. If necessary, the terminal can apply different filtering operations to the SD and UL symbols (or DL ​​symbols). The application of different filtering operations may mean applying different filtering operations based on the boundary between the SD and UL symbols. In this case, power consistency / phase continuity may not be maintained during the transmission and reception of the UL signal / channel.

[0116] Various types of base stations can be provided for implementing SBFD operation, and Figures 5 to 8 An exemplary embodiment of the base station can be shown.

[0117] Figure 5 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing a TDD system.

[0118] refer to Figure 5 A base station can have K Tx chains and K Rx chains. The Tx and Rx chains can maintain connectivity with an array of L antenna elements (e.g., a shared-Tx / Rx antenna array). K and L can each be a natural number. In DL resources, the shared-Tx / Rx antenna array can be connected to a Tx chain, and in UL resources, it can be connected to an Rx chain. In other words, the shared-Tx / Rx antenna array can be switched based on time resources and can be used in both DL and UL.

[0119] Figure 6 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0120] refer to Figure 6 A base station can have K Tx chains and K Rx chains, and a panel group can be formed by L element antennas. K and L can each be a natural number. Panel group #1 used in DL resources and panel group #2 used in UL resources can be distinguished from each other. In SD resources, both panel group #1 and panel group #2 can be used.

[0121] Regarding the base station's transmit power, the transmit power in DL symbols and SD symbols can be the same. Since the DL bandwidth in SD symbols is narrower than that in DL symbols, the power density in SD symbols (e.g., energy per resource element (EPRE)) may be greater than the power density in DL symbols (e.g., EPRE).

[0122] Figure 7 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0123] refer to Figure 7 The base station can have K / 2 Tx chains and K / 2 Rx chains, and the panel group can be formed by L / 2 element antennas. K and L can each be a natural number. Panel group #1 and panel group #2 can be used in DL resources and / or UL resources. In DL resources, both panel group #1 and panel group #2 can be connected to the Tx chains, and in UL resources, both panel group #1 and panel group #2 can be connected to the Rx chains. In SD resources, panel group #1 can be connected to the Tx chains, and panel group #2 can be connected to the Rx chains.

[0124] Regarding the base station's transmit power, the transmit power in DL symbols and SD symbols can be different. Since the DL bandwidth in SD symbols is narrower than that in DL symbols, the power density (e.g., EPRE) in SD symbols can be the same as the power density (e.g., EPRE) in DL symbols.

[0125] Figure 8 This is a conceptual diagram illustrating an exemplary embodiment of a base station implementing SBFD operation.

[0126] refer to Figure 8 The base station can have K / 2 Tx chains and K / 2 Rx chains, and the panel group can be formed by L / 2 element antennas. K and L can each be a natural number. Panel group #1 can be used in DL resources, and panel group #2 can be used in UL resources. In DL and SD resources, panel group #1 can be connected to the Tx chain, and in SD and UL resources, panel group #2 can be connected to the Rx chain.

[0127] Regarding the base station's transmit power, the transmit power in DL symbols and SD symbols can be different. Since the DL bandwidth in SD symbols is narrower than that in DL symbols, the power density (e.g., EPRE) in SD symbols can be the same as the power density (e.g., EPRE) in DL symbols.

[0128] To handle the service needs of terminals, base stations can establish RRC connections with terminals. Multiple unspecified terminals can select or reselect base stations using a cell search procedure. Base stations (or cells) can periodically transmit synchronization signals and / or system information. System information can be divided into Master Information Blocks (MIBs) and System Information Blocks (SIBs). SIBs can be distinguished as SIB1, SIB2, etc. Terminals can use MIBs and SIBs to camp on a specific base station (or cell). Synchronization signals and MIBs can be combined, and synchronization signal blocks (SSBs) including synchronization signals and MIBs can be transmitted. In the exemplary embodiments below, SIB may primarily refer to SIB1. However, SIB may not necessarily be interpreted as SIB1. Depending on the context, SIB can be interpreted as SIBx (x = 1, 2, 3, etc.).

[0129] When a DL service to be sent to a terminal occurs in a network or base station, the network or base station may send paging messages to multiple unspecified terminals to discover the terminal and establish an RRC connection with it. The terminal may receive the paging message and perform a random access procedure to the network or base station, and may establish an RRC connection with the network or base station through the random access procedure.

[0130] When a UL service needs to be sent from the terminal to the network or base station, the terminal can perform a random access procedure to establish an RRC connection with the base station (or network) where the terminal is camped.

[0131] After an RRC connection is established between the terminal and the base station, the terminal can operate based on the control of the base station (e.g., the serving cell). For example, the terminal can perform data transmission and reception with the base station.

[0132] Because base stations cannot know the status of terminals camped on them, base station power may be wasted due to the periodic transmission of SSBs and / or SIBs. For example, a base station operating in normal mode may transmit SIBs at predetermined intervals. A base station operating in low-power mode may transmit SIBs at longer intervals. Alternatively, a base station operating in low-power mode may not transmit SIBs.

[0133] Figure 9 This is a conceptual diagram illustrating an interference scenario where both the attacker's and victim's terminals are provided with services from the same TRP, based on SBFD operations.

[0134] refer to Figure 9When inter-terminal interference occurs, the attacking terminal causing the interference and the victim terminal receiving the interference can be distinguished within a base station or a TRP. In this disclosure, the attacking terminal may refer to the attacking UE or aUE, and the victim terminal may refer to the victim UE or vUE. Depending on the context, a terminal can be interpreted as both the attacking terminal and / or the victim terminal. The attacking terminal may be referred to as a first terminal (e.g., a first UE), and the victim terminal may be referred to as a second terminal (e.g., a second UE). Alternatively, the victim terminal may be referred to as a first terminal (e.g., a first UE), and the attacking terminal may be referred to as a second terminal (e.g., a second UE). In this disclosure, depending on the context, a base station may be interpreted as a serving base station.

[0135] frame

[0136] A base station or TRP performing SBFD operation can distinguish between SD symbols and ND symbols. An ND symbol can refer to a symbol in which all PRBs are used (or indicate use for) downlink or uplink. An SD symbol can refer to a symbol in which some PRBs are used (or indicate use for) downlink or uplink. There may be terminals receiving DL signals / channels in the DL subband of an SD symbol. There may be terminals transmitting UL signals / channels in the UL subband of an SD symbol. Terminals may have a relationship of mutual interference. In other words, interference may occur between terminals operating in the DL subband of an SD symbol and terminals operating in the UL subband of an SD symbol. In this disclosure, the term 'DL signal / channel' can refer to DL signals and / or DL ​​channels, and the term 'UL signal / channel' can refer to UL signals and / or UL channels.

[0137] Figure 10 This is a conceptual diagram illustrating an interference scenario based on SBFD operation where the attacker's terminal and the victim's terminal are provided with services from different TRPs.

[0138] refer to Figure 10 The attacking terminal and the victim terminal can belong to different TRPs or different base stations. After establishing an RRC connection with the first TRP (e.g., the first base station), the attacking terminal can send UL signals / channels to the first TRP (e.g., the first base station). Even in an RRC disconnected state (e.g., RRC inactive state or RRC idle state), the attacking terminal can still send UL signals / channels to the first TRP (e.g., the first base station). After establishing an RRC connection with the second TRP (e.g., the second base station), the victim terminal can receive DL signals / channels from the second TRP (e.g., the second base station).

[0139] The serving base station can perform coordination operations between the attacking terminal and the victim terminal to identify the magnitude of UE-UE cross-link interference (CLI). UE-UE CLI can be referred to as UE-UE CLI. In this disclosure, CLI can be interpreted as UE-UE CLI depending on the context. The victim terminal can measure the CLI Received Signal Strength Indicator (RSSI) and / or CLI Reference Signal Received Power (RSRP) based on the CLI Reference Signal (RS). CLI-RS can be SRS (e.g., an SRS transmitted by the attacking terminal). CLI-RSSI can be SRS-RSSI, and CLI-RSRP can be SRS-RSRP. The victim terminal can generate CSI based on a CSI reporting configuration indicated by the base station and can transmit (e.g., report) the CSI to the base station. The victim terminal can transmit CSI on UL signals / channels via a UL prioritization / multiplexing process. The attacking terminal can receive information (e.g., indications) from the base station via signaling for transmitting UL signals / channels (e.g., SRS) for CLI measurements. The UL priority / reuse process can refer to the UL priority process and / or the UL reuse process.

[0140] The CSI framework can be applied to measure CLI-RSSI or SRS-RSRP. Terminals (e.g., attacker terminals and / or victim terminals) can receive CSI report configuration from the base station via RRC signaling. Terminals can identify Channel Measurement Resources (CMR) and Interference Measurement Resources (IMR) based on the information included in the CSI report configuration. In other words, the CSI report configuration can include CMR information (e.g., CMR set information) and IMR information (e.g., IMR set information). Alternatively, the CSI report configuration can include CMR information without IMR information. CMR can refer to the resources and / or resource sets of the DL signal / channel used for channel measurement. IMR can refer to the resources and / or resource sets of the DL signal / channel used for interference measurement. IMR can refer to resources belonging to the DL subband (e.g., RE). According to the proposed method, CMR can include resources belonging to the UL signal / channel (e.g., RE) and / or resources belonging to the UL subband (e.g., RE). IMR may include resources belonging to UL signals / channels (e.g., REs) and / or resources belonging to UL subbands (e.g., REs).

[0141] A CSI reporting configuration for measuring CLI (e.g., CLI-RSSI) can be considered. CMR information can indicate the location of the SD symbol and / or PRB used to measure CLI (e.g., CLI-RSSI). IMR information can indicate the location of the SD symbol and / or PRB used to measure CLI (e.g., CLI-RSSI). An appropriate TCI status (e.g., qcl-typeD) of the victim's terminal may be required for CLI (e.g., CLI-RSSI) measurement.

[0142] A CSI reporting configuration for measuring CLI-RSSI can be considered. CMR can be associated with a CLI resource set or a CLI resource. IMR can be associated with a CLI resource set or a CLI resource. To measure (e.g., acquire) CLI, only a portion of the CLI measurement information may be needed. An appropriate TCI state (e.g., qcl-typeD) of the victim terminal may be required to measure CLI. An appropriate priority can be specified, and that appropriate priority can be mapped to a UL signal / channel. SRS can be used as a CLI-RS for measuring CLI.

[0143] Figure 11 This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI reporting configuration of the victim's terminal.

[0144] refer to Figure 11 The victim terminal's CSI report configuration may include an SRS resource set for CMR configuration. The victim terminal can use SRS to measure SRS-RSRP. The attacker terminal can transmit SRS in the UL subband of the SD symbol. SRS can be transmitted within the SRS resource set. The SRS transmitted by the attacker terminal may be for the purpose of measuring UE-to-UE CLI. The transmission method for measuring UE-to-UE CLI SRS can differ from the method by which the attacker terminal transmits SRS to the serving base station.

[0145] Transmission configuration

[0146] SRS can be used as a CLI-RS to indicate to an attacking terminal. SRS can be transmitted within a UL BWP. In a UL signal / channel, SRS can be used for various purposes. The purpose of an SRS can be represented as 'purpose' in the RRC variable associated with the SRS resource set. Purposes can be categorized as 'codebook (CB)', 'non-codebook (NCB)', 'beam management (BM)', 'antenna switching (AS)', etc. RRC variables can refer to RRC parameters. An SRS resource set can include one or more SRS resources. To allow SRS resources belonging to an SRS resource set to have the same behavior (e.g., purpose), RRC variables can be applied collectively. For example, RRC variables can include the transmission period of the SRS (e.g., the period of the SRS resource), the index of the time slot in which the SRS is transmitted (e.g., the time slot index of the SRS resource), and / or the transmit power of the SRS. An SRS resource can refer to an SRS symbol (e.g., all SRS symbols). In other words, an SRS resource can include SRS symbols.

[0147] use

[0148] According to the proposed method, BM can be interpreted as indicating the purpose of CLI measurements. In the above method, the purpose of the SRS used for CLI measurements can be interpreted as BM. According to another method, the purpose of the SRS used for CLI measurements can be indicated (e.g., configured) separately. For example, the purpose of the SRS can be represented as 'CLI'. In the above method, the terminal can be indicated with a newly configured purpose for the SRS used for CLI measurements.

[0149] Figure 12 This is a conceptual diagram illustrating an extended exemplary embodiment of the SRS configuration of the attacker's terminal.

[0150] refer to Figure 12 In an SRS configuration, SRS resource sets can have various uses. These uses can include CB, NCB, BM, AS, and positioning (POS). As a new use of SRS resource sets, CLI measurements (e.g., CLI) can be introduced. The number of SRS resource sets indicated by the SRS configuration can be one. When two or more serving cells measure the UE to the UE CLI, two or more SRS resource sets for CLI can be indicated to the terminal. For example, consider configuring a supplementary uplink (SUL) carrier for the victim terminal and supporting (e.g., performing) SBFD operation in each of the normal uplink (NUL) and SUL carriers. In this case, an SRS resource set for CLI can be indicated independently in each serving cell.

[0151] The SRS resources of the SRS resource set used for BM (e.g., conventional BM) can be used for UL BM. According to the proposed method, BM can indicate that SRS is used for CLI measurement. The serving base station of the attacking terminal may not measure CLI. The victim terminal can measure CLI (e.g., CLI-RSRP, SRS-RSRP). The serving base station of the victim terminal can be the same as that of the attacking terminal. Alternatively, the serving base station of the victim terminal (e.g., a first serving base station) can be different from the serving base station of the attacking terminal (e.g., a second serving base station).

[0152] To support the victim terminal's CLI measurements, the base station can instruct the attacker terminal to transmit SRS (e.g., SRS resources within SD symbols) in SD symbols via signaling (e.g., higher-layer signaling). The duplex type (e.g., symbol type) of the SRS transmission can be indicated based on information included in the SRS resource set. When the symbol type indicated by the base station is SBFD symbol and the SRS resources belonging to the same SRS resource set are SD symbols, the attacker terminal can transmit SRS (e.g., SD symbols) in the SRS resources. For each SRS resource, the duplex type of the SRS transmission can be indicated to the terminal independently. Among SRS resources belonging to the same SRS resource set, some SRS resources can be SD symbols, while others can be ND symbols. In this case, the attacker terminal can transmit SRS in some SRS resources (e.g., SD symbols) but not in others. The base station can configure the duplex type of the attacker terminal's SRS transmission (e.g., SRS resources) on a per-SRS resource-set, per-SRS-resource, or per-SRS-symbol basis via signaling. An attacker's terminal can identify the duplex type (e.g., SRS resource, SRS symbol) of SRS transmission based on the base station's signaling (e.g., higher-layer signaling).

[0153] SRS resources belonging to an SRS resource set can belong to SD symbols. In other words, a terminal (e.g., an attacking terminal) can use SRS resources within an SD symbol to transmit SRS. SRS resources within an SD symbol can belong to a UL subband (e.g., a UL-available PRB). SRS resources belonging to an SRS resource set can be determined to be invalid in an ND symbol, and SRS transmissions can be discarded within SRS resources in an ND symbol (e.g., invalid resources, invalid SRS symbols). SRS transmissions can be discarded on a symbol-by-symbol basis. In this disclosure, depending on the context, an SRS resource can be interpreted as all SRS symbols or a single SRS symbol. SRS transmissions can be discarded across all symbols. An attacking terminal can transmit SRS within valid SRS symbols, but not necessarily within invalid SRS symbols. When the PRBs mapped to by the SRS sequence all belong to a UL subband, SRS symbols belonging to a UL subband (e.g., SRS resources) can be valid SRS symbols (e.g., valid SRS resources).

[0154] The exemplary embodiments described above can be performed when the symbol type is configured as SBFD (e.g., SBFD symbol). For example, a base station can send information indicating that the symbol type is configured as SBFD symbol to a terminal (e.g., an attacker's terminal and / or a victim's terminal) via signaling. The attacker's terminal can determine one or more valid symbols (e.g., one or more valid SRS symbols) from the resources (e.g., SRS resources) indicated by the SRS configuration information based on the symbol type, and can use the one or more valid symbols to send SRS. In this disclosure, a valid resource can refer to a valid symbol or a valid SRS symbol. The SRS configuration information can include information about an SRS resource set. In other words, the SRS configuration information can indicate an SRS resource set. An SRS resource set can indicate one or more SRS resources. Each SRS resource can include an SRS symbol. The SRS configuration information (e.g., information about an SRS resource set) can include information indicating the symbol type (e.g., the symbol type of the SRS resource and / or SRS symbol). The symbol type can be applied collectively to one or more SRS resources belonging to the SRS resource set.

[0155] When the symbol type is configured as SBFD symbol, an attacking terminal can transmit SRS within an SBFD symbol (e.g., a UL subband within an SBFD symbol), while a victim terminal can perform measurements (e.g., CLI measurements) on the SRS within the SBFD symbol (e.g., a UL subband within an SBFD symbol). In other words, the attacking terminal and / or the victim terminal can determine that the SBFD symbol is a valid symbol for transmitting and receiving SRS. The attacking terminal and / or the victim terminal may expect to transmit and receive SRS within an SBFD symbol.

[0156] In another example, the base station can send information via signaling to a terminal (e.g., an attacker's terminal and / or a victim's terminal) indicating that the symbol type is configured as non-(N)-SBFD (e.g., N-SBFD symbols). The attacker's terminal can determine one or more valid symbols (e.g., one or more valid SRS symbols) from the resources (e.g., SRS resources) indicated by the SRS configuration information based on the symbol type, and can use these one or more valid symbols to transmit SRS. When the symbol type is configured as N-SBFD, the attacker's terminal can transmit SRS in N-SBFD symbols (e.g., UL symbols and / or flexible (FL) symbols), and the victim's terminal can perform measurements (e.g., CLI measurements) on the SRS in N-SBFD symbols (e.g., UL symbols and / or FL symbols). In other words, the attacker's terminal and / or the victim's terminal can determine N-SBFD symbols as valid symbols for transmitting and receiving SRS. The attacker's terminal and / or the victim's terminal may expect to transmit and receive SRS in N-SBFD symbols.

[0157] The TCI status (e.g., spatial relationship information) of SRS resources can be indicated by RRC variables, and the TCI status of SRS resources can be associated with DL signals / channels and / or UL signals / channels. The associated signals / channels can be changed using DCI format or MAC CE. SRS resources can be indicated to the terminal periodically, semi-persistently, or aperiodically. The TCI status can also be indicated to the terminal independently. According to the proposed method, the same TCI status can be applied to SRS resources belonging to an SRS resource set whose purpose is set to CLI measurement, SRS resources belonging to an SRS resource set whose purpose is set to CB, SRS resources belonging to an SRS resource set whose purpose is set to NCB, and / or SRS resources belonging to an SRS resource set whose purpose is set to BM. In other words, the TCI status associated with SRS resources used for other purposes (e.g., CB, NCB, and / or BM) can be applied to SRS resources used for CLI measurements (e.g., UE-to-UE CLI).

[0158] SRS Configuration

[0159] The base station can generate SRS configuration information and send it to terminals (e.g., attacker terminals and / or victim terminals) via signaling. Terminals can receive the SRS configuration information via base station signaling. Attacker terminals can send SRS based on the SRS configuration information. Victim terminals can perform measurements (e.g., CLI measurements) on the SRS sent by the attacker terminal based on the SRS configuration information or CMR configuration information. The SRS configuration information may include information about SRS resource sets, SRS location resource sets, etc.

[0160] UL reuse priority

[0161] UCI prioritization / multiplexing can be a process performed by the terminal for transmitting PUCCH, PUSCH, SRS, and / or PRACH. UCI prioritization / multiplexing can refer to UCI prioritization and / or UL multiplexing. The terminal can transmit one or two UL signals / channels to reduce peak-to-average power ratio (PAPR) and / or intermodulation distortion (IMD). To support the above operations, UCI and UL-SCH (e.g., PUSCH) can be multiplexed. Alternatively, the terminal can select one of UCI and UL-SCH and can transmit the selected UL signal / channel. At least one of the multiplexed UCI / UL-SCH, UCI, or UL-SCH can be mapped to one or two UL signals / channels.

[0162] Within a frequency combination that allows simultaneous transmission of UL signal / channel combinations other than 'PUCCH and PUSCH', 'PUSCH and SRS', or 'PRACH and PRACH', two UL signals / channels may be selected. The terminal may need to support the capability or feature of simultaneous transmission. If the above constraints do not exist, the terminal may transmit UCI and / or UL-SCH on a single UL channel. Alternatively, if the above constraints do not exist, the terminal may transmit PRACH on only a single UL channel.

[0163] According to the proposed method, the L1-RSRP priority can be reused as the reporting priority for SRS-RSRP or CLI-RSSI. In other words, the priority for reporting SRS-RSRP or CLI-RSSI can be determined based on the L1-RSRP priority. The priority may not correspond to the priority of the UL signal / channel in URLLC and eMBB distinguished by the priority index. When the code rate cannot be maintained in CSI reports with the same priority index, this priority can be used as the priority for discarding a portion of the CSI reports.

[0164] You can specify the priority of CSI reports. The priority of CSI reports can be determined based on Equation 1 below.

[0165] [Equation 1]

[0166] .

[0167] The priority of CSI reports can be indicated. y can be determined based on the physical channel through which the CSI report is sent and the triggering characteristics of the CSI report. k can be determined based on whether L1-RSRP and L1-SINR are present in the CSI report. c can represent the serving cell index. s can represent the identifier configured for the CSI report. N cells This can represent the maximum number of serving cells. M s This can represent the maximum number of CSI reports. When the first CSI report... The value is less than that reported by the second CSI. When the value is [value missing], the first CSI report can be considered more important than the second CSI report. In other words, as [value missing]... The value becomes smaller, compared to Associated CSI reports may be of higher importance. CSI reports can be distinguished by an identifier. Multiple CSI reports can be concatenated based on pre-configured rules. Encoding and modulation processes can be applied to the concatenated CSI reports. Each CSI report can be divided into Part 1 and Part 2. The payload belonging to the CSI report can be divided into two parts, and independent encoding processes can be applied to each of these two parts.

[0168] When the CSI report includes PMI, Part 1 of the CSI report may include RI, CQI, CRI, etc., and Part 2 of the CSI report may include PMI, additional CQI, etc. The payload size of Part 1 can be fixed, while the payload size of Part 2 can vary depending on the information included in Part 1. The base station can first decode Part 1, and can determine the payload size of Part 2 based on the decoding result of Part 1, and can attempt to decode Part 2 while taking the payload size into account.

[0169] When distinguishing between Part 1 and Part 2, L1-RSRP and L1-SINR can be classified as Part 1. RSRP can be derived based on CSI-RS or SSB. CSI-RS or SSB can be used to measure CLI.

[0170] When distinguishing between Part 1 and Part 2, CSI reports including SRS-RSRP can be configured with only Part 1. When distinguishing between Part 1 and Part 2, CSI reports including CLI-RSSI can be configured with only Part 1.

[0171] When measuring CLI, the equations for deriving the priority of the CSI report can be extended and applied (e.g., Equation 1 above). Both SRS-RSRP and CLI-RSSI can be processed at the physical layer, and the terminal can represent SRS-RSRP and / or CLI-RSSI with 7-bit or 4-bit precision. The terminal can derive the channel power by coherently demodulating the SRS. In other words, the terminal can derive the SRS-RSRP of the SRS received from the base station. To support this operation, the terminal may need to know all resource configurations of the SRS to be measured. Conversely, because CLI-RSSI does not utilize a separate RS, the terminal can derive the received power by applying incoherent demodulation. To support this operation, the terminal may need to know the time and frequency location of the resource to be measured. Although SRS-RSRP and CLI-RSSI have different characteristics, the terminal can process SRS-RSRP and CLI-RSSI through a similar process. The terminal can derive the priority of SRS-RSRP and CLI-RSSI in the same way (e.g., ).

[0172] Based on the similarity between L1-RSRP and SRS-RSRP, L1-RSRP can be derived in the same way. and SRS-RSRP The k value for CLI-RSSI, SRS-RSRP, and L1-RSRP can be considered as 1, and k=1 can be applied to Equation 1 above.

[0173] Similarity in measurement purpose: RSRP can indicate link quality (e.g., downlink link quality), while CLI-RSSI can indicate cross-link interference. Cross-link interference can refer to interference in the link from the attacker's terminal to the victim's terminal. Both RSRP and CLI-RSSI can provide the received power level of a terminal in the current propagation environment. Networks (e.g., base stations) can use RSRP and CLI-RSSI together to perform beam selection, UL silence, power control, etc. Therefore, it is not necessary to distinguish the importance of RSRP and CLI-RSSI.

[0174] Versatile configuration scenarios: CLI-RSSI measurements can be configured for CLI mitigation purposes; both RSRP and CLI-RSSI measurements can be configured to simultaneously identify link performance and interference status; and RSRP measurements can be configured when UL interference is low. When different CSI reports conflict and one CSI report is set to a lower priority (k=1), there is a risk that necessary information may be delayed and / or lost.

[0175] To ensure the simplicity of the prioritization scheme: When the application scope of k=0 is configured to include CSI reports of L1-RSRP, L1-CLI-RSSI, and / or L1-SINR, the terminal can resolve conflicts based on a single comparison logic. When k=1 is configured to be applied to CLI-RSSI, the combination of y, k, and / or Pri values ​​(e.g., priority) can become complex, and the likelihood of handling delays and code errors may increase. Due to the above issues, the application scope of k=0 can be extended in this disclosure. Therefore, the priority of L1-CLI-RSSI can be set to be the same as the priority of L1-RSRP and / or L1-SINR.

[0176] Terminal conflict resolution process

[0177] The terminal can identify (y, k, c, s) for each CSI report based on the interpretation results of PDCCH or MAC CE, and can determine the Pri value based on (y, k, c, s) (e.g., When two CSI reports share at least one symbol (e.g., an OFDM symbol) in the same time slot and on the same carrier, the terminal can treat it as a conflict of CSI reports and process the conflict in the following order.

[0178] (1) When the y-values ​​of the CSI reports are different, the terminal may send a CSI report with a higher priority y-value. The higher priority y-value can be determined based on a table defined in the technical specification.

[0179] (2) When the y values ​​of the CSI reports are the same but the k values ​​of the CSI reports are different, the terminal may maintain (e.g., send) CSI reports with k=0 (e.g., L1-RSRP, L1-CLI-RSSI and / or L1-SINR) and may omit CSI reports with k=1.

[0180] (3) When the y-values ​​of the CSI reports are the same and the k-values ​​of the CSI reports are the same, the terminal may maintain (e.g., send) the CSI report with the lower Pri value and may omit the CSI report with the higher Pri value.

[0181] (4) When the y-values, k-values, and Pri-values ​​of the CSI reports are the same, the terminal can reuse the CSI reports and send the reused CSI reports. The reuse of CSI reports can be performed based on the procedures specified in the technical specifications (e.g., TS 38.213).

[0182] When the network (e.g., a base station) simultaneously allocates semi-persistent PUSCH and data PUSCH, the terminal can operate based on the above procedure. The terminal may choose not to send PUSCH that does not satisfy N² + d.2,1 Semi-persistent CSI report for timeline conditions.

[0183] Based on the above operations, immediate response to interference is possible, implementation can be simplified, and standards compatibility can be maintained. In other words, CLI-RSSI can be considered as having high priority, and commands for mitigating cross-link interference (e.g., beam switching, UL silence, etc.) can be executed without delay. Because the terminal determines the priority of CSI reports based on a single k, the firmware complexity and / or memory usage of the terminal can be reduced. Because the scheme for y-values ​​remains unchanged, the priority of quality of service (e.g., eMBB, URLLC, etc.) can remain unchanged, and CLI measurement functions can be integrated with existing CSI frameworks.

[0184] The priorities defined above can be applied to both RSRP and CLI-RSSI. Consistent conflict resolution can be ensured for any configuration including either RSRP or CLI-RSSI. Therefore, radio resource utilization efficiency and / or interference control performance can be improved. The processing of CSI reports can utilize the same number of CPUs (e.g., the terminal's CPU) as L1-RSRP.

[0185] When a PUCCH / PUSCH transmission is scheduled to an attacking terminal, the attacking terminal may discard an SRS transmission (e.g., an SRS resource). PUCCH / PUSCH can refer to PUCCH and / or PUSCH.

[0186] According to another proposed method, during the UL prioritization / reuse process, the priority of SRS resources belonging to the SRS resource set used for CLI can be changed.

[0187] The priority of SRS resources can be compared with the priority of PUSCH / PUCCH. Based on the result of the priority comparison, the terminal can discard the SRS transmission and send PUSCH / PUCCH. PUSCH / PUCCH and SRS can be scheduled by the same serving base station. Even when an SRS transmission is discarded, the serving base station may not perform UL BM in the corresponding UL symbol (e.g., the UL symbol where the SRS transmission was discarded).

[0188] During UE-to-UE CLI measurement, when the attacking terminal discards CLI-RS (e.g., SRS) transmissions, the CLI (e.g., SRS-RSRP, CLI-RSSI) derived by the victim terminal may be inaccurate. The victim terminal can report the CSI to its serving base station. According to one implementation, the serving base station may ignore the victim terminal's CSI report. Ignoring the victim terminal's CSI report may be inefficient. Therefore, it may be preferable for the victim terminal not to measure the CLI. It may also be preferable for the victim terminal to know whether the attacking terminal has discarded CLI-RS transmissions.

[0189] The attacker's SRS can have a lower priority than PUSCH / PUCCH. Alternatively, the attacker's SRS can have a higher priority than PUSCH / PUCCH. A portion of the PUSCH / PUCCH can be discarded to send the SRS. The attacker can discard a portion of the PUSCH / PUCCH by performing puncturing or rate matching.

[0190] Figure 13 This is a conceptual diagram illustrating an exemplary embodiment of an attacking terminal sending an SRS after receiving scheduling information from a UL signal / channel.

[0191] refer to Figure 13 SRS resources used for CLI can be time-division multiplexed within a portion of the symbols used to transmit the UL signal / channel. Depending on the resource allocation scheme, the frequency resources of the UL signal / channel can be configured as contiguous or discontinuous PRBs. According to the proposed method, because SRS has high priority, the terminal can transmit SRS and can discard a portion of the UL signal / channel. Transmitting SRS may require altering the Tx beam (e.g., TCI status or spatial relationship information).

[0192] Repeated transmissions of UL signals / channels by the attacking terminal can be scheduled. In other words, the attacking terminal can receive scheduling information for repeated transmissions of UL signals / channels. This operation can be performed in one of multiple UL signal / channel instances that overlaps with SRS transmissions. SRS transmissions can be considered overlapping across all instances of UL signals / channels. For example, during PUSCH transmission, the attacking terminal can perform UL shared channel (UL-SCH) rate matching on the resources (e.g., symbols and subcarriers) transmitting SRS.

[0193] The attacking terminal may not transmit SRS. Even in this case, the attacking terminal can still perform UL-SCH rate matching to transmit UL signals / channels. SRS (e.g., SRS not transmitted by the attacking terminal) can be considered as zero-power (ZP) SRS. The attacking terminal's serving base station can measure the resources occupied by the ZP SRS in the inter-base station CLI (e.g., BS-BS CLI).

[0194] Tx beam reuse

[0195] When the transmit beam of the SRS (e.g., the Tx beam) differs from the transmit beam of the PUCCH / PUSCH, the attacking terminal may require time to change the transmit beam. The time required by the attacking terminal can be represented as Δ1 and / or Δ2. Δ1 (≥0) symbols before the first symbol of the SRS resource can be used to change the transmit beam. Δ2 (≥0) symbols after the last symbol of the SRS resource can be used to change the transmit beam.

[0196] The time resources for PUSCH / PUCCH can be categorized into y10, y20, y30, and / or y40. During times corresponding to y10 and y40, the attacking terminal can use the PUSCH / PUCCH transmission beam to perform transmission. During time corresponding to y20, the attacking terminal can perform operations to change the transmission beam from the PUSCH / PUCCH to the SRS transmission beam. Depending on the specific capabilities of the attacking terminal, the attacking terminal may choose not to transmit PUSCH / PUCCH. Depending on another capability of the attacking terminal, the attacking terminal may transmit PUSCH / PUCCH.

[0197] At time y30, the attacking terminal can perform an operation to change the transmit beam from SRS to PUSCH / PUCCH. Depending on the specific capability of the attacking terminal, it may choose not to transmit PUCCH / PUSCH. Depending on another capability, it may transmit PUCCH / PUSCH. The values ​​of Δ1 and Δ2 can be different from each other. When performing frequency hopping of PUSCH / PUCCH, Figure 13 An exemplary embodiment can be applied to at least one frequency hopping frequency.

[0198] When scheduling PUSCH / PUCCH transmissions so that they begin earlier than SRS transmissions, PUSCH / PUCCH can be sent in region y10 or in both regions y10 and y20. When scheduling SRS transmissions so that they begin earlier than PUSCH / PUCCH transmissions, PUSCH / PUCCH can be sent in region y30 or in both regions y30 and y40. When the symbol for scheduling PUSCH / PUCCH transmissions includes y10 or y40, the attacking terminal can send PUSCH / PUCCH in at least y10 and / or y40.

[0199] When the transmit beams of PUSCH / PUCCH and SRS are the same, the y20 or y30 region may be unnecessary. When the transmit beams are the same, the attacking terminal can treat the value of Δ1 or Δ2 as 0. Alternatively, the attacking terminal can always treat the value of Δ1 or Δ2 as greater than 0 without performing the transmit beam comparison process.

[0200] The transmit beams for SRS and PUSCH / PUCCH can be determined based on priority. The SRS transmit beam can be derived from the TCI state associated with the SRS resource. When SRS is time-division multiplexed (TDM) together with PUSCH / PUCCH, the PUSCH / PUCCH transmit beam (e.g., TCI state) can be applied to the SRS transmission. TDM for PUSCH / PUCCH and SRS can occur in the same time slot. The terminal can transmit PUSCH / PUCCH and SRS in TDM mode within the same time slot. Alternatively, TDM for PUSCH / PUCCH and SRS can occur in the same time slot and within the same serving cell. The terminal can transmit PUSCH / PUCCH and SRS in TDM mode within the same serving cell and within the same time slot. According to the proposed method, the terminal can identify whether TDM is being performed on the PUSCH / PUCCH and SRS in order to derive the transmit beam of the SRS. Based on the identification result, the TCI state of the SRS resource or the TCI state of the PUSCH / PUCCH can be applied as the transmit beam of the SRS. When there is no indication of the TCI state of the transmit beam of the SRS (e.g., SRS resource), the terminal can regard the default beam applied to the SRS (e.g., SRS resource) as the TCI state and can identify whether TDM is being performed on the PUSCH / PUCCH and SRS.

[0201] According to the proposed method, the attacking terminal can maintain its transmit beam as is during the TDM period of PUSCH / PUCCH and SRS. The TDM of PUSCH / PUCCH and SRS can occur in the same time slot. The terminal can transmit PUSCH / PUCCH and SRS in TDM mode within the same time slot. Alternatively, the TDM of PUSCH / PUCCH and SRS can occur in the same time slot and within the same serving cell. The terminal can transmit PUSCH / PUCCH and SRS in TDM mode within the same time slot of the same serving cell. Due to the transmission of SRS, the coherence of PUSCH / PUCCH may not be maintained. For example, in... Figure 13 In an exemplary embodiment, the antenna port of y10 transmitting PUSCH / PUCCH may not be considered the same as the antenna port of y40 transmitting PUSCH / PUCCH. According to the proposed method, since the same transmission beam is maintained, the necessary condition of considering the antenna port of y10 as the same as the antenna port of y40 can be satisfied. When the combination of the above conditions and other conditions described later satisfies the sufficient condition, the attacking terminal can maintain coherence while transmitting SRS and PUSCH / PUCCH in TDM mode.

[0202] The victim terminal can receive an indication of the unified TCI status from the serving base station. Terminals capable of following the unified TCI status can derive the transmit filter for UL RS and / or the receive filter for DL ​​RS from the same TCI status index. To indicate the TCI status, not only can RS indicating qcl-type A, qcl-type B, or qcl-type C be configured, but RS indicating qcl-type D can also be configured. The RS indicating qcl-type D can be an SSB or DL ​​RS. When a receive filter is derived to receive the SSB or DL ​​RS indicating qcl-type D, the victim terminal can receive SRS by using the receive filter. In other words, the victim terminal can perform SRS measurement operations based on information derived from the TCI status indicated for the SSB and / or DL ​​RS (e.g., qcl-type D). The above operations can be applied even when a non-periodic CSI report is triggered.

[0203] The base station can configure a TCI state with qcl-typeD and / or a unified TCI state (e.g., unifiedTCI-StateType) for a terminal (e.g., an attacker's terminal and / or a victim's terminal). The terminal can expect to be configured with a TCI state and / or a unified TCI state with qcl-typeD (e.g., unifiedTCI-StateType). The terminal can perform SRS measurements (e.g., CLI measurements) by applying QCL estimation based on the TCI state with qcl-typeD and / or the unified TCI state.

[0204] Center frequency

[0205] The frequency resources used for PUSCH / PUCCH transmission and the frequency resources used for SRS transmission can be different. The center frequency of the PRB that schedules PUSCH / PUCCH can be different from the center frequency of the PRB that transmits SRS. The attacking terminal can operate without being based on the center frequency of the UL BWP. Refer to an exemplary embodiment where PUSCH / PUCCH and SRS are TDMed (e.g., Figure 13 (As illustrated in the exemplary embodiment), the attacking terminal may need to change the center frequency. To support the above operations, time may be required to change the radio frequency (RF) circuitry (e.g., retuning time). This could be a reason why coherence cannot be maintained. The attacking terminal may determine the center frequency as (e.g., adjust to or consider as) the center frequency of the union of the PUSCH / PUCCH frequency resources and the SRS frequency resources. In other words, the attacking terminal may operate based on the center frequency of the union of the PUSCH / PUCCH frequency resources and the SRS frequency resources.

[0206] The frequency resources of PUSCH / PUCCH and SRS can be offset from each other, and a common PRB between PUSCH / PUCCH and SRS may not exist. This offset of PUSCH / PUCCH and SRS frequency resources can correspond to the situation where the attacking terminal transmits SRS in narrowband. In this case, the victim terminal may not measure SRS in wideband (e.g., SRS-RSRP). To accurately measure SRS (e.g., SRS-RSRP), it may be preferable for the attacking terminal to transmit SRS in wideband. Wideband SRS transmission can refer to a transmission occupying all or most of the PRBs (e.g., UL-available PRBs) of a UL subband belonging to the SD symbol.

[0207] The victim terminal can measure UE-to-UE CLI to support SBFD operation. The victim terminal can measure RSRP by performing coherent demodulation on the CLI-RS (e.g., SRS). In other words, the victim terminal can perform measurements on the SRS (e.g., CLI measurements). The victim terminal can measure CLI-RSSI based on the CLI-RS.

[0208] In the transmission and configuration of SRS, some information can be indicated to the terminal in a cell-specific manner, while other information can be indicated to the terminal in a UE-specific manner. Cell-specific subframes that can transmit SRS can be indicated to the terminal. The terminal can derive the subframes for transmitting SRS based on the UE-specific configuration within the cell-specific subframes. UE-specific resources for transmitting SRS can be indicated. Resources for transmitting SRS may include time resources, frequency resources, and / or sequence resources. When the base station performs SBFD operation, the base station can use SRS for UE-to-UE CLI measurements. SRS transmitted in the UL subband of the SD symbol (e.g., UL can use PRB) can be derived based on cell-specific and / or BWP-specific information. An attacking terminal can transmit SRS derived based on cell-specific and / or BWP-specific information.

[0209] The sequence information of the SRS can be indicated to the terminal in a cell-specific or BWP-specific manner. The sequence information of the SRS may include at least one of the following: Zadoff-Chu (ZC) sequence generation information, length, or cyclic shift. To configure the same sequence information, sequence group shifts and / or sequence transitions can be configured in the same way.

[0210] The SRS frequency information can be indicated to the terminal in a cell-specific or BWP-specific manner. The SRS frequency information may include at least one of the SRS bandwidth, hopping pattern, or subcarrier tone index. The sequence length can be derived based on the SRS frequency information. A ZC sequence with a length greater than the SRS bandwidth can be generated. The generated ZC sequence can be punctured according to the SRS bandwidth, and SRS transmission (e.g., SRS including the punctured ZC sequence) can be performed.

[0211] When the attacking terminal belongs to two or more serving TRPs (e.g., different serving TRPs), information used to derive the SRS can be jointly applied to apply the proposed method. This information can be jointly applied to an area wider than the cell or to an area where SBFD is performed.

[0212] Depending on the SRS configuration, bandwidth may not always be configured to include an integer number of PRBs. This is because the number of UL-available PRBs in the SD symbol (e.g., the bandwidth of the UL subband) may not always match the number of PRBs supported by the SRS. In this case, the SRS can be configured to occupy the maximum number of PRBs among the UL-available PRBs.

[0213] SRS configuration information can be used as information transmitted at the attacker's terminal and as information measured at the victim's terminal. The attacker and victim terminals may require different information. For example, to measure SRS-RSRP, it may not be necessary to indicate the SRS transmission power. In this case, information about the SRS transmission power can be indicated to the attacker's terminal, while information about the SRS transmission power may not be indicated to the victim's terminal.

[0214] Timing advance (TA)

[0215] When the purpose is set to CLI measurement or BM, the timing of SRS transmission (e.g., SRS resource-based transmission) may differ from the timing defined in the technical specification. The timing of an SRS symbol (SRS) transmitted by the attacking terminal can be determined considering the location of the SRS symbol at the UL timeslot boundary. The UL timeslot boundary can be considered as a time advance of the TA relative to the DL timeslot boundary. According to the proposed method, the transmission time of the SRS symbol can be determined without considering the TA. When the serving base station of the attacking terminal receives the SRS symbol, the TA can be considered to determine the transmission time of the SRS symbol in order to maintain the discrete Fourier transform (DFT) window. Since the victim terminal receives the SRS symbol for CLI measurement, the transmission time of the SRS symbol can be determined without considering the TA. Alternatively, the transmission time of the SRS symbol can be the time considering the TA.

[0216] Figure 14 This is a conceptual diagram illustrating an exemplary embodiment for determining the location of time resources used to measure the UE to UE CLI.

[0217] refer to Figure 14A terminal (e.g., an attacking terminal) can transmit SRS (e.g., an SRS symbol) at z10. In other words, the attacking terminal can transmit SRS by applying TA. For example, the attacking terminal can transmit SRS at z10, where z10 is earlier than z20 by TA. The victim terminal can consider the time of SRS measurement (e.g., SRS-RSRP) as z10. In other words, the victim terminal can determine the reception time of SRS (e.g., measurement time) taking TA into account. An SRS symbol can refer to SRS (e.g., a portion of SRS).

[0218] The transmission time of the SRS symbol can be a time without considering the TA (Transmission Time). Ignoring the TA might mean that the TA is considered 0. A terminal (e.g., an attacking terminal) can transmit the SRS symbol at z20. When the attacking terminal is geographically adjacent to the victim terminal, and their TA values ​​are similar, the attacking terminal can have a significant impact on the victim terminal. It is likely preferable that the victim terminal measures the interference at z20, which is the time when the victim terminal receives the DL signal / channel. The attacking terminal can transmit the SRS symbol at z20. The victim terminal receives the SRS symbol at z20.

[0219] The transmission time of SRS symbols can be controlled by RRC variables (e.g., RRC parameters). Based on RRC variable-based control, the attacking terminal transmits SRS symbols at z10. Based on another RRC variable-based control, the attacking terminal can transmit SRS symbols at z20. In the proposed method, the transmission time of SRS symbols can be controlled (e.g., determined) based on the configuration of the SRS resource set. For all SRS resources belonging to the SRS resource set, the transmission time of SRS symbols can be jointly controlled. According to another proposed method, the transmission time of SRS symbols can be controlled for each SRS resource.

[0220] power

[0221] The serving base station can transmit (e.g., configure) a set of SRS resources for BM, CB, NCB, AS, and / or POS for UL maintenance. To maintain an appropriate transmit power level in the SRS resources, closed-loop control can be performed on the attacking terminal. When the purpose of configuring SRS resources (e.g., transmitting SRS) is to measure UE-to-UE CLI, the transmit power of the SRS can be determined without considering fading between the serving base station and the attacking terminal (e.g., long-term fading or large-scale fading). Since the victim terminal is expected to be geographically adjacent to the attacking terminal, a sufficiently high quality SRS-RSRP can be measured even when considering fading between the victim and attacking terminals to determine the SRS transmit power. In this case, since the attacking terminal does not need to apply high transmit power for SRS transmission, it may be preferable for the attacking terminal to transmit SRS with low transmit power (e.g., appropriate transmit power).

[0222] According to the proposed method, for SRS resources belonging to the SRS resource set used for CLI, the transmission power applied by the attacker's terminal can be controlled independently. The transmission power of the SRS resources can be independent of closed-loop control (e.g., power adjustment state or power control loop). The SRS resource sets used for BM, CB, NCB, AS, and / or POS can belong to a control loop, and commands in DCI format can be reflected in the SRS resource sets. When the SRS resource set used for CLI does not belong to a control loop, or when the SRS resource set used for CLI does belong to a control loop, commands in DCI format may not be reflected in the SRS resource set used for CLI.

[0223] According to the proposed method, the transmission power of the attacking terminal when transmitting SRS can differ from the transmission power when transmitting SRS and PUCCH / PUSCH in TDM mode. When using TDM mode, the attacking terminal can transmit SRS by reusing the transmission power of PUCCH / PUSCH. When not using TDM mode, the attacking terminal can transmit SRS based on separate power control, transmission power individually indicated by the base station, or transmission power defined in the technical specifications. When using TDM mode, since the transmission power does not change when the attacking terminal transmits PUCCH / PUSCH and SRS, consistency in transmission power can be maintained.

[0224] Automatic gain control (AGC) effect

[0225] An attacking terminal can transmit SRS using the transmit power indicated by the serving base station. The serving base station can receive signals from multiple users (e.g., multiple terminals) and can perform multicarrier demodulation through a single DFT operation on the signals. When a user uses excessive or insufficient transmit power, the serving base station's ADC or AGC may saturate. Small signals can be ignored because quantization noise increases with large signals. The serving base station can minimize the occurrence of the above-mentioned anomalies by maintaining the transmit power of the UL signal / channel at an appropriate level.

[0226] The victim terminal measuring the UE-to-UE CLI may not know the geographical distance between the attacker terminal and the victim terminal. When the transmit power allocated to the attacker terminal is high or low, the victim terminal may not be able to accurately measure the CLI received from the attacker terminal. The victim terminal can measure the CLI by using at least two symbols. The victim terminal can use the first of the at least two symbols to train the ADC or AGC.

[0227] According to the proposed method, SRS resources belonging to the set of SRS resources for CLI associated with an SRS sent by the attacker's terminal can include two or more consecutive symbols. Repetition of SRS resources can be configured to be performed twice. The victim's terminal's CMR or IMR can be instructed (e.g., configured) to include two or more consecutive symbols.

[0228] Figure 15 This is a conceptual diagram illustrating an exemplary embodiment of SRS resources used for measuring UE to UE CLI.

[0229] refer to Figure 15 Two or more antenna ports can be configured for SRS resources. One antenna port can be associated with the attacker's terminal's Tx panel. When configuring two or more antenna ports, since the corresponding Tx panels can be associated with different SSBs or different TCI states, two or more SRS resources can be configured instead of one SRS resource to configure a source RS for a single qcl-typeD. Figure 15 In an exemplary embodiment, an SRS resource can be interpreted as being configured with two symbols.

[0230] According to the proposed method, for an SRS resource set used for CLI, an SRS resource can be allowed to have different antenna ports and / or different TCI states. An SRS resource has one antenna port; however, an attacking terminal can be instructed to perform SRS transmissions within the SRS resource using the same time and frequency resources and / or the same sequence resources.

[0231] Although an SRS resource has one symbol, a replicated instance of the SRS resource can be used as an AGC symbol, and transmissions of the same SRS symbol can be repeated. The cyclic prefix (CP) of the SRS symbol can be configured to be long, and the SRS symbol can be extended using additional OFDM symbols and CPs (e.g., extended CPs). Figure 15 In an exemplary embodiment, the first symbol can be generated by using the second symbol.

[0232] The aforementioned constraints may be unnecessary when SRS and PUCCH / PUSCH are used in TDM. According to the proposed method, the SRS transmit power does not need to be determined separately, and the PUSCH / PUCCH transmit power can be applied to the SRS transmission as is. It may not be necessary to retrain the victim terminal's AGC and / or ADC.

[0233] Receive configuration

[0234] Rx beam reuse

[0235] To measure UE-to-UE CLI, the victim terminal can measure SRS-RSRP or CLI-RSSI. The victim terminal's CSI report configuration can include information indicating the Rx beam or TCI state to be assumed by the victim terminal. CMR or IMR configuration can indicate a non-zero power (NZP) CSI-RS resource set or SSB resource (e.g., an SSB resource set) to the victim terminal. NZP CSI-RS resource information can include information indicating the DL TCI state, joint TCI state, and / or TCI state. NZP CSI-RS resource information (e.g., NZP CSI-RS resources) can indicate the Rx beam to be assumed by the victim terminal. The Rx beam can refer to an identifier of the DL signal / channel used for reusing the assumed Rx beam for the DL signal / channel received by the victim terminal. The victim terminal can derive (e.g., generate) a CSI report based on the TCI state associated with the DL signal / channel by using CMR and / or IMR. To measure SRS-RSRP, CMR may include UL signals / channels, and CMRs that include UL signals / channels may not be supported by conventional technical specifications.

[0236] Configuration information used for measuring CLI-RSSI and / or reporting CLI-RSSI measurement results may include information about ZP RS for CMR and / or IMR. The victim terminal can identify the ZP RS for CMR and / or IMR based on the configuration information. The victim terminal can report the CLI-RSSI measurement results to the serving base station. The victim terminal can derive (e.g., determine) the TCI state for receiving ZP RS based on the CSI reporting configuration, IMR configuration, and / or CMR configuration. The TCI state indicated to the victim terminal can be applied to the IMR. Alternatively, the TCI state indicated to the victim terminal can be applied jointly to both CMR and IMR.

[0237] Configuration information used for measuring SRS-RSRP and / or reporting SRS-RSRP measurement results may include information about SRS resources associated with CMR and / or IMR. The configuration information may include information about the association between CMR and SRS resources and / or about the association between IMR and SRS resources. The victim terminal can identify the SRS resources associated with CMR and / or IMR based on the configuration information. The victim terminal can report the SRS-RSRP measurement results to the serving base station. The victim terminal can derive (e.g., determine) the TCI state for receiving SRS based on CSI reporting configuration, CMR configuration, or IMR configuration. The TCI state indicated to the victim terminal can be applied to CMR. Alternatively, the TCI state indicated to the victim terminal can be applied jointly to CMR and IMR.

[0238] According to the proposed method, TCI states for measuring CLI-RSSI or SRS-RSRP can be derived based on the DL / joint TCI states indicated to the victim terminal. The base station can indicate multiple TCI states to the victim terminal via signaling (e.g., RRC signaling), and some of these TCI states can be activated using MAC CE. When MAC CE is used to activate or deactivate a TCI state, the TCI state indicated by the MAC CE can be selectively activated or deactivated. The terminal can operate based on the activated TCI states indicated by the new MAC CE format.

[0239] A base station can indicate a TCI status to a victim terminal using a DCI format. In other words, the DCI format can include information indicating a TCI status. The TCI status applied to CMR or IMR may be limited to the indicated TCI status.

[0240] The TCI state indicated by the unscheduled DCI format or the scheduled DCI format can correspond to the Rx beam used by the victim terminal to receive DL signals or channels after the beam application time (BAT). The victim terminal can apply the above operation to the Rx beam used to measure CLI-RSSI or SRS-RSRP. In other words, the victim terminal can use the indicated TCI state after BAT to measure CLI-RSSI or SRS-RSRP.

[0241] When the DCI format does not indicate the TCI status, the Rx beam can be indicated by independent signaling for each DL signal / channel. In this case, to obtain the CMR or IMR for measuring CLI-RSSI or SRS-RSRP, the victim terminal can apply a TCI status independent of the PDSCH. The victim terminal can obtain (e.g., determine) the TCI status of CLI-RSSI or SRS-RSRP by applying the TCI status indicated by the CSI report configuration or CMR configuration configured for CLI-RSSI or SRS-RSRP.

[0242] There may be situations where the CMR or IMR used to measure CLI-RSSI or SRS-RSRP overlaps with the PDSCH in the time resources. In this case, the victim terminal may perform one operation (e.g., CLI or SRS measurement or PDSCH reception). Alternatively, the victim terminal may perform all operations.

[0243] The victim terminal can configure the priority of operations. The victim terminal can receive PDSCH and may not export CSI reports. In other words, the priority of PDSCH reception can be higher than the priority of CSI reporting (e.g., measurements of CLI-RSSI or SRS-RSRP). When the CMR / IMR used to measure CLI-RSSI or SRS-RSRP overlaps with the SPS PDSCH in terms of time resources, the victim terminal can be instructed to perform only one operation. When the priority of CSI reporting (e.g., measurements of CLI-RSSI or SRS-RSRP) is higher than the priority of SPS PDSCH reception, the victim terminal can measure CLI-RSSI or SRS-RSRP and may not receive the SPS PDSCH. Alternatively, the victim terminal may receive only a portion of the SPS PDSCH. When scheduling PDSCH using the DCI format, the victim terminal may not report CLI-RSSI or SRS-RSRP to the base station based on periodic or semi-persistent CSI reporting configurations. When a PDSCH reception operation scheduled using the DCI format and a CLI-RSSI or SRS-RSRP measurement operation configured using aperiodic CSI reports overlap in the same time resources or affected resources, it can be assumed that the victim terminal is not instructed to perform either of these operations. These two operations include the PDSCH reception operation and the CLI-RSSI or SRS-RSRP measurement operation.

[0244] Alternatively, the victim terminal can perform both operations. In this case, the victim terminal can use the TCI state used to receive the PDSCH to measure CLI-RSSI or SRS-RSRP. CLI-RSSI or SRS-RSRP can be measured using the specified TCI state.

[0245] The indicated TCI status may not be indicated by the DCI format of the measurement report that triggered CLI-RSSI or SRS-RSRP. The indicated TCI status may be indicated by another DCI format. Even when the TCI status is indicated to the victim terminal and BAT has not yet occurred, it is possible that the victim terminal may need to measure CLI-RSSI or SRS-RSRP. The indicated TCI status can be applied after BAT. In this case, the victim terminal can measure CLI-RSSI or SRS-RSRP by applying the default QCL assumption or the last indication of the TCI status. In other words, when there is no TCI status indicating SRS (e.g., when the indicated TCI status is invalid), the victim terminal can measure CLI-RSSI or SRS-RSRP by applying the default QCL assumption or the last indication of the TCI status. The last indication of the TCI status may refer to the TCI status indication of the last PDSCH (e.g., the last PDSCH received by the victim terminal).

[0246] The victim terminal can receive the indicated TCI status for measuring CLI-RSSI or SRS-RSRP. Subsequently, the victim terminal can receive a separate DCI format (or MAC CE or RRC signaling) and can identify (e.g., determine) whether the TCI status has been updated based on the received separate DCI format (or MAC CE or RRC signaling).

[0247] Report triggered

[0248] To identify the dynamic impact between the attacker and victim terminals, semi-persistent or aperiodic CSI reporting may be more appropriate than periodic CSI reporting. The serving base station may consider indicating to the victim terminal the presence of aperiodic CSI reporting, including SRS-RSRP. Aperiodic CSI reporting can be indicated by a UL-related DCI format. The time resources used for CMR and / or IMR can be derived from the CSI reporting configuration. The terminal can derive the time slot where the CMR / IMR resides (e.g., the time slot for receiving SRS) by applying an offset (e.g., aperiodicTriggeringOffset) to the time slot of the received DCI format (e.g., the DCI format that triggers the CSI report). To apply SRS-RSRP, it may be necessary to reinterpret the time slot (e.g., the time slot where the CMR / IMR resides) as the time slot where the attacker terminal transmits SRS.

[0249] Figure 16 This is a conceptual diagram illustrating an exemplary embodiment of the timing relationship of a victim's terminal using SRS to send non-periodic CSI reports.

[0250] refer to Figure 16The victim terminal can receive PDCCH (e.g., DCI format) from the base station and can send PUSCH to the base station. PDCCH can schedule PUSCH transmissions. The offset between the PDCCH reception time and the PUSCH transmission time can be indicated by aperiodicTriggeringOffset. Within or after the offset, the victim terminal can receive SRS from the attacker terminal. CSI reference resources can be configured within the offset.

[0251] There may be an offset between the time slot in which the PDCCH (e.g., in DCI format) triggering the CSI report is received and the time slot in which the CMR / IMR is located (e.g., the time slot in which the SRS is received and / or the time slot in which the SRS is measured). To support the attacker's SRS transmission, the attacker's serving base station can schedule the SRS. The CMR / IMR can have a predetermined relationship with the CSI reference resource. The victim's serving base station can determine the time slot for transmitting the PDCCH based on the time slot in which the SRS is received. A method may be needed that avoids the aforementioned constraints in the victim's serving base station.

[0252] According to the proposed method, a base station can send an offset of the time (e.g., time slot) at which SRS is received to a terminal (e.g., an attacker's terminal and / or a victim's terminal) via signaling. This offset can be applied at least to aperiodic CSI reports. The offset can be derived based on the victim's terminal's CSI reporting configuration. In other words, the CSI reporting configuration can include an offset. The CMR configuration of the CSI reporting configuration can include information indicating the offset of the time (e.g., time slot) at which SRS is received from the attacker's terminal. The offset can indicate the difference between the reception time of the DCI format indicating aperiodic CSI reports and the reception time of the SRS. The offset can indicate the difference between the time slot at which the DCI format is received and the time slot at which the SRS is received. When considering periodic or semi-persistent CSI reports, the offset for receiving SRS from the attacker's terminal can be derived based on the CSI reporting configuration.

[0253] According to the proposed method, SRS transmitted by the attacking terminal can be indicated in a cell-specific manner. Alternatively, SRS transmitted by the attacking terminal can be indicated separately to the victim terminal. SRS (e.g., the reception time or reception slot of the SRS) can be derived regardless of the DCI format or offset that triggers the aperiodic CSI report. The slot interval between the SRS received by the victim terminal and the PDCCH does not need to be interpreted as a single value, and the slot interval can be interpreted as a minimum or maximum interval. The slot interval can be interpreted as a range.

[0254] The victim terminal may already be aware of the SRS time resources. The victim terminal can determine whether to measure SRS-RSRP based on the value of the CSI report trigger bit field in the PDCCH (e.g., DCI format). The victim terminal can determine whether to send an updated CSI report, taking into account the processing time for receiving the SRS. When the time interval between SRS and PUCCH / PUSCH is too small, the victim terminal may not necessarily measure SRS-RSRP because it cannot derive appropriate CSI reference resources. When the victim terminal's CPU is heavily utilized, it may apply the priority defined in the technical specification for measuring SRS-RSRP. Therefore, when the victim terminal's CPU is insufficient, it may be unable to measure SRS-RSRP.

[0255] CMR / IMR

[0256] The victim's terminal can measure at least one of SRS-RSRP and CLI-RSSI. Configuration information triggering aperiodic CSI reporting may include information indicating whether the victim's terminal measures SRS-RSRP and / or whether the victim's terminal measures CLI-RSSI. CSI reporting configuration information may include information for deriving whether the value measured by the victim's terminal is SRS-RSRP or CLI-RSSI.

[0257] When the attacking terminal receives scheduling information for PUSCH / PUCCH, it may choose not to send SRS. In this case, the victim terminal may not be able to measure SRS-RSRP, and may measure CLI-RSSI instead of SRS-RSRP.

[0258] The victim terminal can measure CLI-RSSI using the PUSCH / PUCCH sent by the attacker terminal to the attacker terminal's serving base station. CLI-RSSI can be measured on a UL-available PRB. Alternatively, CLI-RSSI can be measured on a DL-available PRB. CLI-RSSI can be a broadband report and can be measured on a DL / UL-available PRB. DL / UL-available PRB can refer to both a DL-available PRB and / or a UL-available PRB. Depending on the instructions given to the victim terminal, CLI-RSSI can be a subband report and can be measured on a subset of the DL / UL-available PRB.

[0259] When measuring CLI-RSSI on a DL-available PRB, the DL-available PRB can be divided into two parts, and these two parts can belong to different DL subbands. In other words, the two parts of the DL-available PRB can belong to two different DL subbands. CMR / IMR measured by the victim's terminal may include discontinuous PRBs. The victim's terminal can use the DL-available PRB to measure CLI-RSSI.

[0260] CLI-RSSI can be measured on a UL-available PRB. The victim terminal can use a UL-available PRB to measure CLI-RSSI. To measure CLI-RSSI, the victim terminal may not receive configuration (e.g., indication) of both the DL-available PRB and the UL-available PRB.

[0261] To measure SRS-RSRP, the victim terminal can use the SRS-cli associated with CMR. CMR can be associated with an SRS resource set and can reuse an SRS resource set used for beam management. An SRS can belong to an SRS resource set (e.g., an SRS resource set used for beam management). To measure CLI-RSSI, the victim terminal can use the resource associated with IMR. The CSI report configuration indicated to the victim terminal can include both CMR and IMR. For CSI reports triggered for the victim terminal, one of the CMR or IMR configurations can be applied.

[0262] Figure 17 This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI report configuration for measuring the victim's terminal from the UE to the UE-CLI.

[0263] refer to Figure 17 For a CSI report that includes measurements from the UE to the UE CLI, the CMR may include a resource set for measuring SRS-RSRP, and the IMR may include a resource set for measuring CLI-RSSI. The victim terminal can receive a configuration (e.g., an indication) of one of the CMR (e.g., an SRS resource or an SRS resource set) and the IMR (e.g., a CLI resource or a CLI resource set) from the base station, and can generate a CSI report based on that configuration. To measure CLI-RSSI, the victim terminal can measure RSSI on a CLI measurement resource set or a CLI measurement resource. A CLI measurement resource set may refer to a CLI resource set, and a CLI measurement resource may refer to a CLI resource.

[0264] To measure UE-to-UE CLI, CMR and IMR do not need to be configured simultaneously. The victim terminal can receive only the CMR configuration to measure SRS-RSRP. The victim terminal can receive only the IMR configuration to measure CLI-RSSI. Alternatively, the victim terminal can receive the CMR configuration to measure CLI-RSSI.

[0265] IMR

[0266] The victim terminal can receive a CSI report configuration including IMR information from the base station to measure CLI-RSSI. Even when the CSI report configuration includes both CMR and IMR information, the victim terminal can choose not to use the CMR information and can generate a CSI report based on the IMR information. The victim terminal can interpret the CMR used to measure CLI-RSSI based on the CSI report configuration including CMR information.

[0267] Figure 18a and Figure 18b This is a conceptual diagram illustrating an extended exemplary embodiment of the CSI report configuration for measuring the victim's terminal from the UE to the UE-CLI.

[0268] refer to Figure 18a and Figure 18b The CSI report configuration may include CLI measurement resources or a set of CLI measurement resources. The IMR may include an NZP DL / UL RS resource set or NZP DL / UL RS resources. The IMR may include PRBs in symbol units. In this case, the IMR may include consecutive PRBs, and consecutive PRBs may be configured with only DL-available PRBs or only UL-available PRBs. The location and number of the first PRB can be indicated to the terminal. The location and number of the first PRB can be derived based on a single index. The location and number of the first PRB can indicate the frequency resources (e.g., frequency bands) of the IMR.

[0269] A base station can send information via signaling to a terminal (e.g., an attacker's terminal and / or a victim's terminal) instructing the execution of CLI measurements on a frequency band (e.g., a frequency resource). The information instructing the execution of CLI measurements on a frequency band may include the location of the first PRB in that band and the number of PRBs constituting that band. The location of the first PRB and the number of PRBs constituting the band can be represented based on a single index. The first PRB can be the PRB with the lowest or highest index among the PRBs constituting the band. The location of the first PRB can be represented using a PRB index.

[0270] A terminal can receive information from a base station indicating the frequency band (e.g., frequency resources) from which CLI measurements are performed. The terminal can determine (e.g., identify) the frequency band for CLI measurements based on the location of the first PRB (Programmable Buffer) within the band and the number of PRBs constituting that band. An attacking terminal can transmit SRS (e.g., SRS for CLI measurements) within the frequency band indicated by the base station. A victim terminal can perform measurement operations (e.g., CLI measurement operations) against the SRS within the frequency band indicated by the base station.

[0271] PDSCH processing

[0272] TCI status switching

[0273] A portion of the DL signal / channel received by the victim terminal can be designated for CLI measurements. The scheduled DL signal / channel may overlap with time and frequency resources used for CLI-RSSI or SRS-RSRP. Orthogonally allocating time and / or frequency resources for the victim terminal may be preferred over receiving a PDSCH (e.g., PDSCH RE) and measuring CLI-RSSI / SRS-RSRP on a PRB. CLI-RSSI can be measured on a DL-available PRB. SRS-RSRP can be measured on a UL-available PRB. Both CLI-RSSI and SRS-RSRP can be measured on a UL-available PRB. CLI-RSSI can be measured on both a DL-available PRB and a UL-available PRB.

[0274] The process for reporting CLI-RSSI and / or SRS-RSRP measurements can be performed non-periodically. The serving base station can indicate the resources of the DL signal / channel and CMR / IMR to the victim terminal, ensuring that the resources of the DL signal / channel and CMR / IMR do not overlap. The victim terminal can assume that the resources of the DL signal / channel and CMR / IMR do not overlap. The victim terminal can send a UL signal / channel (e.g., PUCCH) to report a HARQ-ACK for the DL signal / channel. The victim terminal can assume that the resources of the UL signal / channel and CMR / IMR do not overlap.

[0275] The base station can indicate the priority of the DL signal / channel and the priority of the UL signal / channel to the victim terminal via signaling. The victim terminal can select a signal / channel based on the priority. The priority can be determined in the technical specifications supporting SBFD operation. The victim terminal may not transmit the UL signal / channel and can measure the SRS-RSRP on the UL-available PRB. The victim terminal can operate based on the UL priority and / or DL ​​priority defined in the technical specifications supporting SBFD operation.

[0276] When dynamically scheduled signals / channels and statically scheduled signals / channels are allocated in overlapping resources, the victim terminal can select the dynamically scheduled signal / channel among them. When PDSCH is scheduled via the DCI format received by the victim terminal, the victim terminal may not perform some or all CLI-RSSI / SRS-RSRP measurements. When the DCI format received by the victim terminal indicates CLI-RSSI / SRS-RSRP measurements and / or reporting, the victim terminal may not receive some or all of the PDSCH. PDSCH can be SPS PDSCH. The DCI format may not require C-RNTI or MCS-C-RNTI scrambling.

[0277] CLI-RSSI or SRS-RSRP measurements can be performed on a DL-available PRB. In this case, the DL priority and / or UL priority derived in SBFD operation may not be directly applied. The victim terminal can perform dynamically indicated operations. The victim terminal can assume that another inconsistent operation is an operation not dynamically indicated. The victim terminal can receive the DCI format of the PDSCH scheduled for the victim terminal and the DCI format indicating CLI-RSSI / SRS-RSRP measurements and / or reports. The CMR / IMR for CLI-RSSI / SRS-RSRP and the PDSCH can be allocated in non-overlapping resources. The CMR / IMR for CLI-RSSI / SRS-RSRP and the PUCCH associated with the PDSCH can be allocated in non-overlapping resources. According to another proposed method, the victim terminal can receive a portion of the PDSCH.

[0278] Figure 19 This is a conceptual diagram illustrating an exemplary embodiment of a victim terminal measuring UE to UE CLI when receiving scheduling information for DL ​​signals / channels.

[0279] refer to Figure 19 The symbols allocated to the PDSCH can be divided into w00, w10, w20, w30, and / or w40. In the symbols preceding and / or following CMR / IMR (w00), the victim terminal may not receive the PDSCH for CLI-RSSI or SRS-RSRP measurements. w20 may correspond to the symbols preceding CMR / IMR (w00), and w20 may include Δ1 (≥0) symbols. w30 may correspond to the symbols following CMR / IMR (w00), and w30 may include Δ2 (≥0) symbols. The values ​​of Δ1 and Δ2 can be defined as numbers including zeros. The values ​​of Δ1 and Δ2 can be defined as numbers greater than or equal to 1. The values ​​of Δ1 and Δ2 can be configured based on the subcarrier spacing of the BWP.

[0280] When the TCI status used to receive the PDSCH differs from the TCI status applied to the CMR / IMR, the victim's terminal may not receive the PDSCH in w20 and / or w30. The TCI status of the PDSCH can be indicated by a scheduled DCI format or an active DCI format. The TCI status of the CMR / IMR can be indicated by a CSI-triggered UL-related format. Alternatively, the TCI status of the CMR / IMR can be indicated by an active DCI format or MAC CE used to trigger an SP-CSI report.

[0281] When the TCI state used to receive PDSCH is the same as the TCI state applied to CMR / IMR, the victim terminal can perform PDSCH reception operations in w20 and / or w30. The TCI state of PDSCH can be indicated in a different way than the TCI state of CMR / IMR, but the victim terminal can apply a common TCI state in the reception operation.

[0282] The TCI status of the PDSCH can be given priority, and the TCI status of the PDSCH can be used instead of the TCI status of CMR / IMR for CMR / IMR measurement. The victim terminal can derive the assumed TCI status for measuring CLI-RSSI or SRS-RSRP based on the scheduling information of the PDSCH. The values ​​of Δ1 and / or Δ2 can be interpreted as 0.

[0283] The TCI states of the CMR / IMR and PDSCH can be independently indicated to the terminal. Even when the TCI states of the CMR / IMR and PDSCH are indicated independently, it is possible for their TCI states to have the same value. The victim terminal can know in advance that the TCI states of the CMR / IMR and PDSCH are the same. The serving base station can predict that the TCI states of the CMR / IMR and PDSCH are the same. In this case, the additional time may be unnecessary, and the values ​​of Δ1 and / or Δ2 can be interpreted as 0.

[0284] Even if the victim terminal knows in advance that the TCI state of CMR / IMR and the TCI state of PDSCH are the same, the victim terminal may still consume additional time. Scheduling information for different signals / channels can be independent, and the victim terminal can process the scheduling information for different signals / channels independently. PDSCH reception processing and CLI-RSSI / SRS-RSRP measurement processing can be performed independently, and the resulting TCI state can be the same. The same TCI state may be a chance result of independent processing. In this case, the values ​​of Δ1 and / or Δ2 can be interpreted as values ​​greater than or equal to 1. Even if the TCI state is maintained, the victim terminal may not maintain consistency in PDSCH reception in w20 and w30.

[0285] When the victim terminal maintains the TCI state as is, the consistency of PDSCH reception in w20 and w30 can be maintained, depending on the implementation of the victim terminal. The victim terminal can assume the same antenna port for PDSCH reception in w20 and w30. The DM-RS of PDSCH may not be included in w20 and / or CMR / IMR (w00). The victim terminal can apply the channel estimates derived from demodulation and / or decoding for w10 and / or w20 to w30 and / or w40.

[0286] According to the proposed method, the victim terminal can assume the same antenna port for PDSCH reception in w10 and w40 based on RRC signaling. The victim terminal can change the TCI state of the CMR / IMR. Alternatively, the victim terminal can choose not to change the TCI state of the CMR / IMR.

[0287] When the gap symbol used to change the TCI state is not required, the victim terminal may assume the same antenna port for w20 or w30. Even when the gap symbol used to change the TCI state is necessary, the victim terminal may assume the same antenna port for w20 or w30.

[0288] RE mapping

[0289] The PDSCH scheduled to the victim terminal may not be received in w00. The PDSCH may not be received in w20 and / or w30. The victim terminal needs to know the mapping method of the encoded bits on some symbols of the PDSCH (e.g., w00 and / or gaps (e.g., w20 and / or w30)).

[0290] Encoded bits may not be mapped to w00 and gaps. During rate matching, encoded bits may be mapped to areas other than w00 and / or gaps (e.g., w20 and / or w30). When deriving the amount of scheduling resources to derive the transport block (TB) size, the victim terminal may treat w00 and gaps as resources (e.g., scheduling resources). The victim terminal may derive the transport block size based on resources other than w00 and gaps.

[0291] It can be assumed that the encoded bits are mapped onto w00 and the gaps. This assumption can be interpreted as a punching process. The victim terminal can derive the transport block size based on the region including w00 and the gaps.

[0292] The victim terminal can receive the PDSCH in the region before the gap (e.g., w10). In the regions before w00 (e.g., w20) and / or after w00 (e.g., w30, w40), the victim terminal can maintain the same antenna port. Alternatively, the victim terminal can not maintain the same antenna port in the regions before w00 (e.g., w20) and / or after w00 (e.g., w30, w40).

[0293] According to the proposed method, the victim terminal may not receive PDSCH in areas w00 and beyond (e.g., w30 and / or w40). The victim terminal may perform demodulation and decoding for PDSCH mapped on w10 and / or w20. The scenario of the serving base station scheduling repeated reception (e.g., repeated transmission) of PDSCH can be considered. PDSCH instances (or PDSCH repetitions) may be scheduled, and these instances (or repetitions) may overlap with CMR / IMR in w00. The victim terminal may choose not to receive PDSCH in the PDSCH instance (e.g., w00).

[0294] Time difference between measurement and reporting

[0295] One approach is to derive the RSRP using the SRS received by the victim terminal. The victim terminal can apply CSI reference resources before reporting the SRS-RSRP to the serving base station. When the victim terminal sends a PUSCH or PUCCH in the first time slot n, it can receive the SRS from the attacker terminal in the second time slot m. Although the SRS is received in the second time slot m, based on the definition of the CSI reference resources, the RSRP of this SRS can be mapped to the SRS-RSRP derived for the third time slot.

[0296] Even when the victim terminal exports the SRS-RSRP, the additional processing used to apply the CSI reference resource may not be explicitly specified. Based on the SRS-RSRP measured in the second time slot, the victim terminal may be allowed to send PUSCH or PUCCH in the first time slot.

[0297] The SRS-RSRP received by the serving base station in the first time slot may differ from the estimated SRS-RSRP measured by the victim terminal in the third time slot. Preferably, the serving cell performs scheduling for both the attacker and victim terminals such that the difference between the SRS-RSRP in the first and third time slots is minimal.

[0298] The base station can send a CSI report configuration including additional information to the victim's terminal. Based on the above operations, the instantaneous value of SRS-RSRP can be indirectly identified. The victim's terminal can quantify the instantaneous value of SRS-RSRP and send a CSI report including the quantized value to the base station. To support the above operations, additional thresholds can be indicated to the terminal.

[0299] The victim terminal can export the RSRP of a specific SRS resource and compare the exported RSRP with a threshold. When the victim terminal exports 1 bit of information, one value of that information can indicate that the SRS-RSRP is less than the threshold, and another value of that information can indicate that the SRS-RSRP is greater than the threshold.

[0300] When instructing the victim's terminal to export multiple bits of information, the victim's terminal can export an interval to which the SRS-RSRP belongs among multiple thresholds. The range of SRS-RSRP values ​​can be estimated based on the index of this interval.

[0301] There may be discrepancies in the derivation time of SRS-RSRP within the information. It cannot be ruled out that the victim's terminal may have derived SRS-RSRP in the first time slot. It is possible to force the extraction of information (e.g., SRS-RSRP) from the third time slot.

[0302] According to the proposed method, when the SRS-RSRP meets predetermined conditions, the victim terminal can send a CSI report including the SRS-RSRP. The serving base station may be interested in a sufficiently large SRS-RSRP. The victim terminal can measure the SRS-RSRP of all SRS resources belonging to a CMR set or a corresponding SRS resource set, and can report a portion of the SRS-RSRP to the base station. The serving cell (e.g., the serving base station) can use a portion of the SRS-RSRP to identify the attacker terminal causing interference to the victim terminal. The victim terminal can report information about SRS resources associated with a sufficiently large RSRP to the base station. The victim terminal may choose not to report information about other SRS resources to the base station. Alternatively, even when the victim terminal reports information about other SRS resources, it may not update its information about those other SRS resources. Since the attacker terminal generates a large CLI, it may be preferable for the serving base station to perform additional operations (e.g., configuration, scheduling, or beam management) to avoid a large CLI.

[0303] The victim terminal can generate a bitmap and report it to a base station (e.g., the serving base station). The bitmap can be included in a CSI report. The length of the bitmap can correspond to the number of SRS resources belonging to the SRS resource set associated with the CMR set configuration configured with the CSI report. SRS resources may include deactivated SRS resources. The victim terminal can generate a CSI report that includes not only the bitmap but also the value of the SRS-RSRP and the identifier (e.g., index) of the SRS resource associated with the SRS-RSRP.

[0304] The SRS-RSRP of an SRS resource can be represented as an absolute value, while the SRS-RSRP of the remaining SRS resources can be represented as differential values. The SRS-RSRP expressed as an absolute value is likely to be the largest SRS-RSRP.

[0305] A CSI report may include at least one of a bitmap, a list of SRS resource identifiers (e.g., indexes), and a list of SRS-RSRPs. Alternatively, a CSI report may include at least one of a list of SRS resource identifiers (e.g., indexes) and a list of SRS-RSRPs. The identifiers of SRS resources may indicate SRS resources represented as absolute values, and identifiers of other SRS resources may not be included in the CSI report. In this case, the SRS-RSRPs may be arranged in the CSI report in the order of the identifiers of the SRS resources represented as differential values.

[0306] When a victim terminal generates a CSI report that includes measurements of some SRS resources, the size of the UCI (e.g., the CSI report) generated by the victim terminal can be variable. For a CMR set including four SRS resources, the victim terminal can use a threshold to quantize the SRS-RSRP with 1 bit. The length (e.g., size) of the bitmap can be 4 bits. The absolute value of the SRS-RSRP can be represented with 7 bits, and the difference value of the SRS-RSRP can be represented with 4 bits. The identifier of the SRS resource can be represented with 2 bits (e.g., log2(number of SRS resources)).

[0307] When performing an SRS-RSRP measurement and the victim terminal selects two SRS resources, the bitmap length can still be 4 bits. The SRS-RSRP can be represented using 11 bits, equal to 7 + 4. This can represent identifiers for SRS resources corresponding to absolute values ​​and identifiers for SRS resources corresponding to differential values. In the exemplary embodiment described above, the UCI size can be 19 bits, equal to 4 + 7 + 4 + 2 + 2.

[0308] When the victim's terminal generates a CSI report including four SRS-RSRPs, the UCI can have a fixed size. The UCI may include a bitmap (4 bits), SRS-RSRPs (7 bits + 4 bits + 4 bits + 4 bits), and an identifier for the SRS resource (2 bits + 2 bits + 2 bits + 2 bits). In the exemplary embodiment described above, the size of the UCI can be 31 bits, equal to 4 + 7 + 4 + 4 + 4 + 2 + 2 + 2 + 2.

[0309] According to the proposed method, the serving base station can configure a CSI report of 31 bits in size to a terminal (e.g., a victim terminal). The victim terminal may not generate information corresponding to 12 bits. The victim terminal can generate 31 bits by padding with known bits. Alternatively, the victim terminal can generate a CSI report in an existing form. The victim terminal can place information at a location within the UCI (e.g., the CSI report) associated with a desired SRS resource. The victim terminal can place arbitrary values ​​at a location within the UCI (e.g., the CSI report) associated with another SRS resource. The victim terminal may not be obligated to update existing SRS-RSRPs. The serving base station can identify (e.g., obtain) the SRS-RSRP at the desired location within the UCI (e.g., the CSI report) received from the victim terminal. The CPU of the victim terminal generating the bitmap may not be exclusively occupied.

[0310] UE-initiated report

[0311] The victim terminal can receive configurations for UE-to-UE CLI reports from the serving base station. The victim terminal can receive configurations for not-periodic, periodic, and / or semi-persistent CSI reports from the serving base station, as well as configurations for specific conditions (e.g., indications). The victim terminal can send CSI reports to the serving base station only when specific conditions occur.

[0312] The proposed condition (e.g., a specific condition) may be that at least one SRS-RSRP remains above a threshold for a predetermined time or a predetermined number of times. The victim terminal can receive a configuration from the serving base station for a time window used to determine whether the specific condition has occurred. The victim terminal can then determine whether the specific condition has occurred within the time window.

[0313] The operation of the method according to exemplary embodiments of this disclosure can be implemented as a computer-readable program or code in a computer-readable recording medium. The computer-readable recording medium may include all kinds of recording means for storing data readable by a computer system. Furthermore, the computer-readable recording medium may store and execute programs or code that may be distributed across computer systems connected via a network and read in a distributed manner by a computer.

[0314] Computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, or flash memory. Program instructions may include not only machine language code created by a compiler, but also high-level language code that can be executed by a computer using an interpreter.

[0315] Although some aspects of this disclosure have been described in the context of apparatus, these aspects may indicate corresponding descriptions according to the method, and blocks or apparatuses may correspond to steps or features of steps of the method. Similarly, aspects described in the context of the method may be represented as features of corresponding blocks or items or corresponding apparatuses. Some or all steps of the method may be performed by (or using) hardware apparatuses such as microprocessors, programmable computers, or electronic circuits. In some embodiments, one or more of the most important steps of the method may be performed by such apparatuses.

[0316] In some exemplary embodiments, a programmable logic device, such as a field-programmable gate array (FPGA), can be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, the FPGA can operate in conjunction with a microprocessor to perform one of the methods described herein. Typically, these methods are preferably performed by a hardware device.

[0317] The description in this disclosure is merely exemplary in nature, and therefore, variations without departing from the spirit of this disclosure are intended to be within its scope. Such changes should not be considered as departing from the spirit and scope of this disclosure. Consequently, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope defined by the appended claims.

Claims

1. A method for a first user equipment (UE), comprising: Receive detection reference signal (SRS) configuration information from the base station; Based on the symbol type of the SRS resource, determine one or more valid SRS symbols within the SRS resource indicated by the SRS configuration information; as well as SRS is sent to the base station using one or more valid SRS symbols. The symbol type indicates whether the subband is a full-duplex (SBFD) symbol or a non-SBFD (N-SBFD) symbol.

2. The method according to claim 1, wherein, Based on the symbol type being indicated as the SBFD symbol, one or more SBFD symbols within the SRS resource are determined to be the one or more valid SRS symbols.

3. The method according to claim 1, wherein, Based on the symbol type being indicated as the N-SBFD symbol, one or more N-SBFD symbols within the SRS resource are determined as the one or more valid SRS symbols.

4. The method according to claim 1, wherein, Transmissions of the SRS in invalid SRS symbols within the SRS resource indicated by the SRS configuration information are dropped on a symbol-by-symbol basis.

5. The method according to claim 1, wherein, The SRS resource is configured to be associated with a set of channel measurement resources (CMR) or an interference measurement resource (IMR) set, and to perform measurements of the SRS reference signal received power (SRS-RSRP) or cross-link interference received signal strength indicator (CLI-RSSI) for the SRS resource.

6. The method according to claim 1, wherein, The transmission time of the SRS is determined taking into account timing advance (TA).

7. The method according to claim 1, wherein, The SRS configuration information includes information about the SRS resource set, and the SRS resource set indicated by the SRS configuration information includes information indicating the symbol type.

8. The method according to claim 1, wherein, The symbol type is applied collectively to one or more SRS resources belonging to the SRS resource set.

9. A method for a second user equipment (UE), comprising: Receive detection reference signal (SRS) configuration information from the base station; Based on the symbol type of the SRS resource, determine one or more valid SRS symbols within the SRS resource indicated by the SRS configuration information; as well as A measurement operation is performed on the SRS transmitted by the first UE in one or more valid SRS symbols. The symbol type indicates whether the subband is a full-duplex (SBFD) symbol or a non-SBFD (N-SBFD) symbol.

10. The method according to claim 9, wherein, Based on the symbol type being indicated as the SBFD symbol, one or more SBFD symbols within the SRS resource are determined to be the one or more valid SRS symbols.

11. The method according to claim 9, wherein, Based on the symbol type being indicated as the N-SBFD symbol, one or more N-SBFD symbols within the SRS resource are determined as the one or more valid SRS symbols.

12. The method according to claim 9, wherein, The SRS resource is configured to be associated with a set of channel measurement resources (CMR) or an interference measurement resource (IMR) set, and to perform measurements of the SRS reference signal received power (SRS-RSRP) or cross-link interference received signal strength indicator (CLI-RSSI) for the SRS resource.

13. The method according to claim 9, wherein, The measurement time of the SRS is determined taking into account timing advance (TA).

14. The method of claim 9, further comprising: Determine the priority of Channel State Information (CSI) reports, which include SRS-RSRP or CLI-RSSI as a measurement result of the SRS; as well as The CSI report is sent to the base station based on the priority. The priority of the CSI report, including the SRS-RSRP or the CLI-RSSI, is determined based on the Layer 1 (L1)-RSRP.

15. The method according to claim 9, wherein, The measurement operation on the SRS is performed based on the Transmission Configuration Indicator (TCI) state indicated for the Synchronization Signal Block (SSB) or Downlink (DL) Reference Signal (RS).

16. The method according to claim 9, wherein, The measurement operation of the SRS is performed based on the TCI state received by the second UE.

17. The method of claim 9, further comprising: Receive downlink control information (DCI) that triggers a CSI report from the base station. The measurement operation of the SRS is performed in a time slot after an offset from the time slot from which the DCI is received, and the offset is indicated by the base station.

18. The method of claim 9, further comprising: Receive information from the base station regarding the frequency band used for measuring CLI-RSSI. The information regarding the frequency band includes the location of the first physical resource block (PRB) of the frequency band and the number of PRBs constituting the frequency band, and the CLI-RSSI is measured within the frequency band indicated by the base station.

19. The method according to claim 9, wherein, The SRS configuration information includes information about the SRS resource set, and the SRS resource set includes information indicating the symbol type.

20. The method according to claim 9, wherein, The symbol type is applied collectively to SRS resources belonging to the SRS resource set.