Method and device for interference measurement in communication system
By determining valid SRS symbols and performing interference measurements, the method and device improve communication quality for terminals at the edge of a base station's coverage area by managing interference effectively.
Patent Information
- Application Number
- PCT/KR2025/008370
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-27
- Filing Date
- 2025-06-18
- Publication Date
- 2025-12-26
AI Technical Summary
Communication quality deteriorates for terminals located at the edge of a base station's coverage area, leading to potential communication failures.
A method and device for measuring interference in a communication system by determining valid SRS symbols based on symbol types, performing SRS-RSRP and CLI-RSSI measurements, and transmitting CSI reports to improve communication performance.
Enhances communication system performance by accurately measuring and managing interference, ensuring effective communication for terminals at the edge of the base station's coverage area.
Smart Images

Figure KR2025008370_26122025_PF_FP_ABST
Abstract
Description
Method and device for measuring interference in communication systems
[0001] The present disclosure relates to communication technology, and more particularly, to a technique for measuring interference for a signal in a communication system.
[0002] With the advancement of information and communication technology, various wireless communication technologies are being developed. Representative wireless communication technologies include LTE (long term evolution) and NR (new radio), both of which are defined by the 3rd generation partnership project (3GPP) standards. LTE can be one of the 4th generation (4G) wireless communication technologies, and NR can be one of the 5th generation (5G) wireless communication technologies.
[0003] To handle the rapidly increasing volume of wireless data following the commercialization of 4G communication systems (e.g., communication systems supporting LTE), 5G communication systems (e.g., communication systems supporting NR) that utilize higher frequency bands (e.g., frequency bands higher than 6 GHz) than the frequency bands of 4G communication systems (e.g., frequency bands below 6 GHz) are being considered. 5G communication systems can support enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC). Discussions are ongoing regarding 6G communication systems that will follow 5G communication systems.
[0004] Meanwhile, if a terminal is located at the edge of a base station's coverage area, communication quality between the terminal and the base station may deteriorate. In this case, the terminal may not be able to communicate with the base station. Methods to address the above-mentioned issues are needed.
[0005] The purpose of the present disclosure to solve the above problems is to provide a method and device for measuring interference of a signal in a communication system.
[0006] According to embodiments of the present disclosure for achieving the above object, a method of a first UE (user equipment) includes the steps of: receiving sounding reference signal (SRS) configuration information from a base station; determining one or more valid SRS symbols within the SRS resource based on a symbol type for the SRS resource indicated by the SRS configuration information; and transmitting an SRS to the base station using the one or more valid SRS symbols, wherein the symbol type is a subband full duplex (SBFD) symbol or an N(non)-SBFD symbol.
[0007] Based on the symbol type indicated by the SBFD symbol, one or more SBFD symbols within the SRS resource can be determined as the one or more valid SRS symbols.
[0008] Based on the symbol type indicated by the N-SBFD symbol, one or more N-SBFD symbols within the SRS resource can be determined as the one or more valid SRS symbols.
[0009] Transmission of the SRS in an invalid SRS symbol within the SRS resource indicated by the SRS configuration information may be dropped on a symbol-by-symbol basis.
[0010] The above SRS resource can be set to be associated with a CMR (channel measurement resource) set or an IMR (interference measurement resource) set, and SRS-RSRP (reference signal received power) measurement or CLI (cross link interference)-RSSI (received signal strength indicator) measurement for the SRS resource can be performed.
[0011] The transmission time of the above SRS can be determined by considering TA (timing advance).
[0012] The above SRS configuration information may include information on an SRS resource set, and the SRS resource set indicated by the SRS configuration information may include information indicating the symbol type.
[0013] The above symbol type can be commonly applied to one or more SRS resources belonging to the above SRS resource set.
[0014] According to embodiments of the present disclosure for achieving the above object, a method of a second UE (user equipment) includes the steps of: receiving sounding reference signal (SRS) configuration information from a base station; determining one or more valid SRS symbols within the SRS resource based on a symbol type for the SRS resource indicated by the SRS configuration information; and performing a measurement operation on an SRS transmitted by a first UE in the one or more valid SRS symbols, wherein the symbol type is a subband full duplex (SBFD) symbol or an N(non)-SBFD symbol.
[0015] Based on the symbol type indicated by the SBFD symbol, one or more SBFD symbols within the SRS resource can be determined as the one or more valid SRS symbols.
[0016] Based on the symbol type indicated by the N-SBFD symbol, one or more N-SBFD symbols within the SRS resource can be determined as the one or more valid SRS symbols.
[0017] The above SRS resource can be set to be associated with a CMR (channel measurement resource) set or an IMR (interference measurement resource) set, and SRS-RSRP (reference signal received power) measurement or CLI (cross link interference)-RSSI (received signal strength indicator) measurement for the SRS resource can be performed.
[0018] The measurement time for the above SRS can be determined by considering TA (timing advance).
[0019] The method of the second UE may further include a step of determining a priority for a CSI (channel state information) report including SRS-RSRP or CLI-RSSI, which is a measurement result for the SRS; and a step of transmitting the CSI report to the base station based on the priority, wherein the priority for the CSI report including the SRS-RSRP or the CLI-RSSI may be determined based on L1 (layer1)-RSRP.
[0020] The above measurement operation for the above SRS can be performed based on a TCI state indicated for a synchronization signal block (SSB) or a downlink (DL) reference signal (RS).
[0021] The above measurement operation for the above SRS can be performed based on the TCI status received by the second UE.
[0022] The method of the second UE may further include a step of receiving, from the base station, downlink control information (DCI) that triggers CSI reporting, wherein the measurement operation for the SRS is performed in a slot after an offset from a slot in which the DCI is received, and the offset may be indicated by the base station.
[0023] The method of the second UE may further include a step of receiving information on a frequency band for measuring CLI-RSSI from the base station, wherein the information on the frequency band may include a position of a first PRB (physical resource block) of the frequency band and the number of PRBs constituting the frequency band, and the CLI-RSSI may be measured within the frequency band indicated by the base station.
[0024] The above SRS configuration information may include information on an SRS resource set, and the SRS resource set may include information indicating the symbol type.
[0025] The above symbol type can be commonly applied to SRS resources belonging to the above SRS resource set.
[0026] According to the present disclosure, an attacker terminal can determine valid sounding reference signal (SRS) resource(s) based on a symbol type, and transmit an SRS using the valid SRS resource(s). A victim terminal can determine valid SRS resource(s) based on a symbol type, perform a measurement operation (e.g., a cross link interference (CLI) measurement operation) on the valid SRS resource(s), and transmit a CSI (channel state information) report including the measurement result to a base station. Based on the above-described operations, interference in a link between an attacker terminal and a victim terminal can be measured, and the base station can control communication for the attacker terminal and / or the victim terminal based on the measured interference. Accordingly, the performance of a communication system can be improved.
[0027] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.
[0028] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.
[0029] FIG. 3 is a conceptual diagram illustrating embodiments of subband filtering masks for DL subbands and UL subbands in an SD symbol.
[0030] FIG. 4 is a conceptual diagram illustrating embodiments of slot patterns (e.g., TDD slot patterns) including SD symbols.
[0031] Figure 5 is a conceptual diagram illustrating embodiments of a base station implementing a TDD system.
[0032] Figure 6 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0033] Figure 7 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0034] Figure 8 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0035] Figure 9 is a conceptual diagram illustrating an interference scenario due to SBFD operation when an attacker terminal and a victim terminal receive services from the same TRP.
[0036] Figure 10 is a conceptual diagram illustrating an interference scenario due to SBFD operation when an attacker terminal and a victim terminal receive services from different TRPs.
[0037] Figure 11 is a conceptual diagram illustrating extended embodiments of CSI reporting settings of a victim terminal.
[0038] Figure 12 is a conceptual diagram illustrating extended embodiments of SRS settings of an attacker terminal.
[0039] Figure 13 is a conceptual diagram illustrating embodiments in which an attacker terminal that has received scheduling information of a UL signal / channel transmits an SRS.
[0040] FIG. 14 is a conceptual diagram illustrating embodiments for determining the location of time resources for measuring UE-to-UE CLI.
[0041] FIG. 15 is a conceptual diagram illustrating embodiments of SRS resources for measuring UE-to-UE CLI.
[0042] Figure 16 is a conceptual diagram illustrating examples of time relationships in which a victim terminal transmits aperiodic CSI reports using SRS.
[0043] FIG. 17 is a conceptual diagram illustrating extended embodiments of CSI reporting settings for measuring UE-to-UE-CLI of a victim terminal.
[0044] FIG. 18a and FIG. 18b are conceptual diagrams illustrating extended embodiments of a CSI reporting configuration for measuring UE-to-UE-CLI of a victim terminal.
[0045] FIG. 19 is a conceptual diagram illustrating embodiments in which a victim terminal that has received scheduling information of a DL signal / channel measures UE-to-UE CLI.
[0046] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.
[0047] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" encompasses any combination of multiple related items or any one of multiple related items.
[0048] In embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”
[0049] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.
[0050] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0051] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.
[0052] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, identical reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted.
[0053] A communication system to which embodiments according to the present disclosure are applied will be described. The communication system to which embodiments according to the present disclosure are applied is not limited to the scope described below, and embodiments according to the present disclosure can be applied to various communication systems. Here, the term "communication system" may be used interchangeably with "communication network."
[0054] In an embodiment, "an operation (e.g., a transmission operation) is set" may mean that "setting information for the operation (e.g., information, information elements, parameters)" and / or "information instructing performance of the operation" are signaled. "Information (e.g., information elements, parameters) is set" may mean that the information is signaled. The signaling may be at least one of SI (system information) signaling (e.g., transmission of a SIB (system information block) and / or MIB (master information block)), RRC signaling (e.g., transmission of an RRC message, an RRC parameter, and / or an upper layer parameter), MAC signaling (e.g., transmission of a MAC message and / or a MAC CE (control element)), or PHY signaling (e.g., transmission of a PHY message, DCI (downlink control information), UCI (uplink control information), and / or SCI (sidelink control information)).
[0055] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.
[0056] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.
[0057] A plurality of communication nodes (110 to 130) can support a communication protocol specified in the 3rd generation partnership project (3GPP) standard (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). The plurality of communication nodes (110 to 130) may support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the plurality of communication nodes may have the following structure.
[0058] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.
[0059] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.
[0060] However, each component included in the communication node (200) may be connected through an individual interface or individual bus centered around the processor (210), rather than a common bus (270). For example, the processor (210) may be connected to at least one of a memory (220), a transmission / reception device (230), an input interface device (240), an output interface device (250), and a storage device (260) through a dedicated interface.
[0061] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).
[0062] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 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. 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 of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).
[0063] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as a NodeB (NB), an evolved NodeB (eNB), a gNB, an advanced base station (ABS), a high reliability-base station (HR-BS), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a radio access station (RAS), a mobile multihop relay-base station (MMR-BS), a relay station (RS), an advanced relay station (ARS), a high reliability-relay station (HR-RS), a home NodeB (HNB), a home eNodeB (HeNB), a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), etc.
[0064] Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a 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, device, on board unit (OBU), etc.
[0065] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.
[0066] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support multi-input multi-output (MIMO) transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, device to device communication (D2D) (or, proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive signals from the second base station (110-2) based on the MU-MIMO method.
[0067] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP scheme, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control D2D between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform D2D under the control of the second base station (110-2) and the third base station (110-3).
[0068] Next, the operating methods of communication nodes in a communication system will be described. Even if a method (e.g., signal transmission or reception) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., signal reception or transmission) corresponding to the method performed by the first communication node. In other words, if the operation of a terminal is described, the corresponding base station can perform an operation corresponding to the operation of the terminal. Conversely, if the operation of a base station is described, the corresponding terminal can perform an operation corresponding to the operation of the base station.
[0069] To reduce data error rates, a lower modulation and coding scheme (MCS) level (e.g., a lower MCS index) can be applied. To prevent the size of the field indicated by the downlink control information (DCI) from increasing, the most frequently used MCS(s) can be selected. Subsequently, to apply a lower MCS, a repetitive transmission operation can be supported. Since quadrature phase shift keying (QPSK) has the lowest modulation rate, this can further reduce the code rate. In particular, since the transmit power in uplink (UL) transmission is limited, the repetitive transmission operation can be performed in the time domain rather than the frequency domain.
[0070] eMBB (enhanced Mobile Broadband) traffic and URLLC (Ultra-Reliable and Low Latency Communication) traffic can use low MCS for different purposes. eMBB traffic can use low MCS to extend the reach. On the other hand, URLLC traffic can use low MCS to reduce latency and achieve low error rates. Because of their different requirements, eMBB traffic can be transmitted repeatedly even if latency occurs, while URLLC traffic can be transmitted using a new MCS (e.g., a lower MCS) rather than repeated transmissions. The new MCS can be set by an RRC message and / or DCI.
[0071] To support repetitive transmissions for eMBB traffic in the time domain, physical uplink shared channel (PUSCH) repetition (e.g., PUSCH repetition type A) may be introduced. In the present disclosure, PUSCH repetition may mean a PUSCH instance. In other words, depending on the context, PUSCH repetition may be interpreted as having the same meaning as a PUSCH instance. Repeated transmission of a PUSCH may be performed in units of PUSCH instances. When repeated transmission of a PUSCH is performed, a PUSCH allocated in units of slots may be repeatedly transmitted. To extend the reach, time resources may be allocated to multiple slots. When PUSCH repetition type A is used, the time resources may be configured by an RRC message and / or DCI. The number of repetitions of PUSCH can be indicated by an RRC message, and the time resource in which PUSCH is transmitted in the first slot can be indicated by a DCI (e.g., a type 2 CG (configured grant) or a dynamic grant) or an RRC message (e.g., a type 1 CG). In the present disclosure, the number of repetitions can mean the number of repeated transmissions or the number of transmissions.
[0072] Repeated transmission of URLLC traffic may not be appropriate because it incurs delay when the traffic is repeatedly transmitted. However, if a sufficiently low MCS is used, the delay for decoding URLLC traffic can be reduced. In other words, if a sufficiently low MCS is used, the number of REs (resource elements) to which URLLC traffic is mapped can increase, and the base station (e.g., the base station decoder) can wait until all REs are received. In this case, the delay for decoding URLLC traffic can be reduced.
[0073] When a PUSCH with a relatively high MCS is repeatedly transmitted, the base station can perform a decoding operation using only some REs. The time to first successful decoding in a PUSCH repeated transmission (e.g., a PUSCH repeated transmission with a relatively high MCS) may be faster than the time to first successful decoding in a PUSCH transmission without repetition (e.g., a PUSCH transmission with a low MCS). When PUSCH repetition type A is used, unnecessary delay may occur, and PUSCH repetition type B may be introduced to reduce the delay time for PUSCH repeated transmission. When PUSCH repetition type B is used, a PUSCH allocated in units of mini-slots may be repeatedly transmitted. When PUSCH repetition type B is used, the time resource may be set by an RRC message and / or DCI. The combination of the reference time resource and the number of repeated transmissions of a PUSCH instance can be indicated by a DCI (e.g., Type 2 CG and / or dynamic grant) or an RRC message (e.g., Type 1 CG).
[0074] In order to control the transmit power of SRS resources indicated by SRI (SRS (sounding reference signal) resource indicator), the base station can estimate the path attenuation for each SRS resource. The base station can control the transmit power for the SRS resource(s) using DCI. The transmit power of the SRS resource(s) can be controlled based on the estimated path attenuation. The DCI can be 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 group common (GC)-DCI (e.g., DCI format 2_2 or DCI format 2_3). The DCI can include a field indicating a transmit power control (TPC) command, and the TPC command can be used to control the transmit power of the terminal. For example, the transmission power of a terminal may be increased or decreased based on a TPC command included in the DCI. To determine the transmission power of a PUSCH, the terminal may consider a value obtained based on path attenuation, a value according to a TPC command included in the DCI, and / or a PUSCH bandwidth indicated by the DCI.
[0075] A base station can configure two or more sets for a terminal using higher layer signaling. The terminal can receive configuration information for the two or more sets from the base station. Each element constituting the two or more sets can be a transmit power parameter(s), which can be designated to suit different scenarios (e.g., a URLLC scenario, an eMBB scenario). The terminal can receive a scheduling DCI or an activating DCI from the base station that allocates PUSCH resources, and the scheduling DCI or the activating DCI can indicate a set for interpreting the transmit power parameter(s). If the sets of transmit power parameter(s) are different, the magnitude of the increase or decrease in transmit power designated by the same TPC command can be different.
[0076] When Type 1 CG or Type 2 CG is used, the transmit power may be determined based on DCI format 2_3 for the SRI associated with the PUSCH instance. When Type 2 CG is used, the activation DCI may indicate a set of transmit power parameter(s) applicable to a PUSCH occasion. A PUSCH occasion may mean a PUSCH instance. The UE may obtain a TPC command for the SRI by receiving a GC (group common)-DCI, interpret the TPC command to be suitable for the set of transmit power parameter(s) indicated by the base station, and derive the transmit power applicable to the PUSCH instance based on the interpretation result.
[0077] In a dynamically scheduled PUSCH transmission, the UE can derive the transmit power applied to the PUSCH instance based on a combination of GC-DCI and scheduling DCI. The UE can identify the TPC command of the SRI by receiving the GC-DCI and store the identified TPC command. In a dynamically scheduled PUSCH transmission, a set of transmit power parameter(s) and / or TPC command applied to the PUSCH occasion can be indicated by scheduling DCI. The UE can derive the transmit power applied to the PUSCH instance based on the transmit power of the SRI associated with the PUSCH instance.
[0078] Repeated HARQ-ACK transmissions can be indicated (or configured) by higher-layer signaling for each physical uplink control channel (PUCCH) format. The number of repeated transmissions for PUCCH format i can be independently configured. i can be 1, 3, or 4. A terminal can repeatedly transmit a PUCCH format in slots. In this case, the PUCCH format can be transmitted using the same time resource in each slot.
[0079] Uplink control information (UCI) types can be classified according to the type of information included in the UCI. UCI can include at least one of scheduling request (SR), L1-RSRP (reference signal received power), HARQ-ACK, or channel state information (CSI). In embodiments, UCI and UCI type can be used interchangeably. In a repeated transmission operation of UCI, only one UCI type can be transmitted. To support this operation, the priority of UCI types can be defined in a technical specification. One UCI type can be selected, and a PUCCH including one UCI type can be repeatedly transmitted. In this case, the terminal can assume that no other UCI types are transmitted before the transmission of the corresponding UCI type is completed. To support this operation, the base station can instruct the terminal to transmit UCI (e.g., SR or HARQ-ACK) after the PUCCH transmission is completed. The latency for such UCI transmissions can be long, and this latency can act as a scheduling constraint for the base station.
[0080] "When HARQ-ACKs are instructed to be transmitted in the same slot (or the same sub-slot)" or "when PUCCH time resources indicated by DCI and / or RRC messages allocating PDSCH (physical downlink shared channel) overlap each other," the terminal may generate the HARQ codebook so that the HARQ codebook is transmitted in one PUCCH (e.g., one PUCCH time resource). Within the HARQ codebook, HARQ-ACK bits may be arranged according to an order defined in a technical specification. Information bits may be generated by the above-described operation. The terminal may generate coded bits by performing an coding operation.
[0081] In encoding operations, Reed-Muller codes or polar codes may be used. The code rate applied in encoding operations may be indicated by higher-layer signaling. For example, in the PUCCH format, a single value may be the code rate and may be indicated to the terminal.
[0082] One codeword can be mapped to one PUCCH. In a PUCCH repeated transmission operation, one UCI type can be generated as a codeword. When a PUCCH is transmitted once, information bits of one UCI type or two or more UCI types can be concatenated, and the terminal can generate one codeword by performing the same encoding operation on the information bits. When a Reed-Muller code or a polar code is used, performing a soft combining operation may be difficult in implementation. Therefore, even when a PUCCH is repeatedly transmitted, the same codeword can be transmitted, and the base station can perform a chase combining operation on the same codeword. The encoded bits or codeword can mean a bit string in which multiple code blocks are concatenated. A modulation operation can be performed on the codeword, and the result of the modulation operation can be mapped to an RE.
[0083] Meanwhile, identical UCI types may be considered different information. Identical UCI types that are considered different information can be mapped. For example, UCIs may be created to support traffic with different priorities. UCIs supporting eMBB traffic (e.g., SR or HARQ-ACK) may be considered distinct information from UCIs supporting URLLC traffic (e.g., SR or HARQ-ACK). In this case, even if the UCI types are identical, UCIs with the same UCI type may be distinguished as different information.
[0084] Encoded UCI can be mapped to PUCCH. The same preprocessing scheme (e.g., spatial information, spatial relations) can be maintained during PUCCH transmission. Alternatively, the use of different preprocessing schemes for each PUCCH can be permitted through RRC signaling from the base station.
[0085] To support URLLC traffic, it may be desirable for a terminal to perform frequent reception operations on downlink (DL) resources and / or frequent transmission operations on uplink (UL) resources. In a time division duplex (TDD) system, a terminal may operate based on a half-duplex scheme. Therefore, the support time for DL traffic and / or UL traffic may increase depending on the slot pattern. On the other hand, in a frequency division duplex (FDD) system, a terminal can utilize DL resources and UL resources. Therefore, the above-described problem in a TDD system may not occur in an FDD system. An FDD system can use two or more carriers. If two or more serving cells are configured for a terminal in a TDD system, the terminal can utilize DL resources and UL resources.
[0086] In a communication system including at least one carrier to which FDD is applied (hereinafter referred to as an "FDD carrier"), there may be no problem with the delay time of the terminal. In a communication system including only carrier(s) to which TDD is applied (hereinafter referred to as "TDD carrier(s)"), there may be a problem with the delay time of the terminal. To solve the above problem, slots in TDD carriers may be configured according to different patterns.
[0087] Carrier aggregation (CA) can be configured in the UE, and PCell and SCell(s) can be activated. Depending on whether a common search space (CSS) set is configured in the cell, the cell can be classified as a PCell or SCell. For example, a CSS set can be configured in the PCell, and a CSS set can be unconfigured in the SCell. To reduce latency in a communication system supporting URLLC traffic, slots with different patterns can be configured and / or indicated to the UE.
[0088] Transmission of eMBB or URLLC traffic can be supported in licensed and / or unlicensed bands. Carrier(s) in the licensed band or carrier(s) in the unlicensed band can be utilized independently. Alternatively, depending on the base station configuration, carrier(s) in the licensed band and carrier(s) in the unlicensed band can be utilized together through frequency aggregation.
[0089] In an embodiment, two or more terminals may receive data from one or more TRPs and transmit data to one or more TRPs. It may be assumed that one base station or one server performs management operations and / or scheduling operations for one or more TRPs among the plurality of TRPs. The TRPs may be directly connected. Alternatively, the TRPs may be connected via a base station. The above-described connection may be a connection according to an Xn interface or a wireless interface (e.g., an interface of 3GPP NR).
[0090] Shadow regions may exist between the areas supported by TRPs. TRPs can resolve shadow regions through cooperative transmission. Cooperative transmission can be performed on terminals located between TRPs. Even in the absence of shadow regions, numerous TRPs (e.g., base stations) can be installed to transmit and receive large amounts of data, and the quality of the wireless link can be improved by having multiple TRPs.
[0091] Depending on the cooperative transmission and reception of TRPs, communication methods can be classified into dynamic point selection (DPS) and joint transmission (JT). For a specific set of physical resource blocks (PRBs), DPS may be a method in which a terminal receives data through a single TRP, and JT may be a method in which a terminal receives data through two or more TRPs. Dynamic point blanking (DPB) may be a type of JT. When DPB is used, a terminal may not receive data from some TRPs and may receive data from the remaining TRPs. JT can be classified into coherent JP and noncoherent JP. Depending on whether a coherent combining operation is performed on signals received from TRPs, either coherent JP or noncoherent JP may be used.
[0092] Depending on the latency and traffic capacity of the backhaul network to which base stations or TRPs are connected, TRPs may or may not participate in real-time cooperative transmission and reception. A terminal may support JT based on a single DCI (e.g., single DCI (sDCI)). Alternatively, a terminal may support JT based on multiple DCIs (e.g., multi-DCI (mDCI)).
[0093] When using sDCI, a terminal can transmit and receive data with TRPs. When using sDCI, it may be desirable for TRPs to cooperate without delay through a backhaul network. When using mDCI, a terminal can transmit and receive data with some TRPs. If a terminal transmits and receives data with other TRPs, it may be difficult for the other TRPs to cooperate in real time through the backhaul network. It may be desirable for other TRPs to be allocated semi-fixed resources.
[0094] A CORESET (control resource set) pool index can be used to identify a TRP. A CORESET pool can be a collection of CORESETs, and the transmission configuration indication (TCI) state applied to each CORESET can be independently indicated to the UE through RRC signaling and / or MAC control element (CE) signaling. A CORESET pool index may not necessarily correspond to a TRP. Specifically, a TRP can be divided into a transmission point (TxP) and a reception point (RxP). A CORESET pool index can correspond to an RxP. For example, an Rx beam for a TxP can be derived from a TCI state, and uplink signals / channels scheduled from DCIs discovered in CORESETs belonging to a CORESET pool indicated by a single CORESET pool index can be interpreted as being received by the same RxP.
[0095] For a terminal to benefit from coherent combining, the TRPs for that terminal must be synchronized to a certain degree, and CSI reports for those TRPs must be shared. If this is not the case, performing noncoherent combining may provide performance advantages.
[0096] If the terminal is mounted on a vehicle, constraints on its size and weight can be relaxed. If the terminal is carried by a person, portability can be considered.
[0097] To expand the signal coverage area, small cells or Integrated Access Backhaul (IAB) nodes can be deployed. The transmission capacity of small cells or IAB nodes may vary depending on the quality of the backhaul link. Securing a backhaul network can be costly. As an alternative to the above embodiment, a wireless relay device can be deployed, which can transmit high-quality signals to terminals. Wireless relay devices can be categorized into several types depending on the method of signal transmission. A wireless relay device supporting multiple functions can exhibit performance similar to that of a base station. A wireless relay device supporting fewer functions can be deployed at a lower cost. In the present disclosure, a wireless relay device can perform the function of forming a beam to terminals and the minimum function of transmitting data. A base station can transmit wireless signals to control the wireless relay device. Appropriate parameters can be set for the wireless relay device based on the wireless signals.
[0098] In this embodiment, transmission of a channel may mean transmission of a message, data, signal, and / or information on the channel, and reception of a channel may mean transmission of a message, data, signal, and / or information on the channel. The channel may 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).
[0099] In a communication system supporting TDD, downlink (DL) communication and uplink (UL) communication can be performed in different time resources. The ratio between the DL time, in which DL communication is performed, and the UL time, in which UL communication is performed, can be determined based on the ratio of traffic (e.g., DL traffic and / or UL traffic). For example, in an NR system, since the amount of DL traffic is greater than the amount of UL traffic, more DL slots can be allocated than UL slots. For example, slots (e.g., slot patterns) can be configured to repeat a DDDSU pattern. D can denote a DL slot, S can denote a special slot including DL symbol(s), FL (flexible) symbol(s), and UL symbol(s), and U can denote a UL slot. The arrangement order of symbols in an S slot can be DL symbol(s)-FL symbol(s)-UL symbol(s). The base station can instruct or set the slot pattern to the terminal(s) through signaling (e.g., RRC signaling). The base station can indicate some FL symbol(s) among the FL symbols set by the RRC signaling as DL symbol(s) or UL symbol(s). The some FL symbol(s) can be indicated as DL symbol(s) or UL symbol(s) through DCI.
[0100] A terminal located at the edge of a cell may repeatedly transmit a UL signal / channel to transmit UL traffic to a base station. In this case, the signal to interference plus noise ratio (SINR) may be improved and the block error rate (BLER) may be reduced at the base station. In the present disclosure, a UL signal / channel may refer to a UL signal and / or a UL channel, and a DL signal / channel may refer to a DL signal and / or a DL channel. The base station may instruct a terminal to repeatedly transmit a UL signal / channel, and the terminal may repeatedly transmit the UL signal / channel based on the instruction of the base station. The base station may instruct a terminal to repeatedly transmit a DL signal / channel, and the terminal may repeatedly receive the DL signal / channel based on the instruction of the base station. If UL slots do not occur frequently, a significant delay may occur for the terminal to obtain sufficient UL slots for repeated transmission. For example, if "the DDDSU pattern is set in the terminal and the SCS (subcarrier spacing) is 30 kHz," UL slots may occur every 2.5 ms (milliseconds). In this case, the time required for four repetitions of the UL signal / channel may be 10 ms.
[0101] To reduce the above time delay, a method of improving the frequency shape of the slot may be considered. The base station may perform full duplex communication. The frequency domain for the DL symbol (or FL symbol) of the DL slot (or DL slot and S slot) may be divided into subbands. The base station may perform a transmission operation of a DL signal / channel or a reception operation of an UL signal / channel in some subbands of the DL slot (e.g., a DL symbol or an FL symbol). Although the terminal performs half-duplex communication, the terminal may perform a transmission operation of an UL signal / channel in the DL slot (e.g., a DL symbol or an FL symbol). A symbol capable of DL communication and UL communication may be referred to as an SBFD (subband full duplex) symbol. The SBFD symbol may be referred to as an SD symbol for convenience. In other words, in the present disclosure, the SD symbol may mean an SBFD symbol. SD may be an abbreviation for SBFD. An SD symbol can be interpreted as an SD resource, and an SBFD symbol can be interpreted as an SBFD resource. The base station can configure an SD symbol and / or a non-SD symbol (e.g., an N-SD symbol or an ND (non-SD) symbol) to a terminal through signaling. The terminal can receive configuration information of the SD symbol and / or the ND symbol from the base station. The configuration information of the SD symbol can be SBFD configuration information. The configuration information of the ND symbol can be UL-DL configuration information. The ND symbol can include an UL symbol, a DL symbol, and / or an FL symbol. The UL symbol, the DL symbol, and / or the FL symbol can be indicated (e.g., configured) based on the UL-DL configuration information. DL communication or UL communication can be performed in the ND symbol. The ND symbol can be interpreted as a non-SD resource or an ND resource. The SBFD configuration information and the UL-DL configuration information can be included in system information (e.g., SIB1).
[0102] Since DL and UL communications are performed within a single SD symbol (e.g., within the same time resource), a guard band may be introduced. The bandwidth of the guard band may vary depending on the level of interference at the base station. When different antenna arrays are used, coupling between DL and UL communications may be reduced. If there is little coupling between DL and UL communications, a guard band may be unnecessary or a small amount of bandwidth may be required for the guard band. In this case, a guard band may not be allocated separately. Alternatively, a small number of PRBs may be allocated for the guard band.
[0103] When there is little coupling between DL communication and UL communication, a separate Rx filtering operation or Rx processing operation may be performed at the base station, but a separate Tx filtering operation or Tx processing operation may not be necessary at the terminal. The filtering operation may be an RF (radio frequency) filtering operation. When an RF filtering operation is performed, spectral emission (e.g., out-of-band emission (OOB) or adjacent channel leakage ratio (ACLR)) affecting adjacent PRB(s) can be reduced, and saturation of RF components can be prevented.
[0104] The DL and UL subbands can have different frequencies. The DL subband can indicate DL usable PRB(s). The UL subband can indicate UL usable PRB(s). If leakage occurs, the analog-to-digital converter (ADC) can become saturated, causing small signals to be ignored. The base station can appropriately arrange shielding between antenna arrays or apply signal processing methods. The base station can also allocate a guard band with a smaller bandwidth.
[0105] FIG. 3 is a conceptual diagram illustrating embodiments of subband filtering masks for DL subbands and UL subbands in an SD symbol.
[0106] Referring to FIG. 3, a power spectral density or spectrum mask for DL-related filtering and / or UL-related filtering may be illustrated. DL-related filtering may be performed at a base station, and UL-related filtering may be performed at a terminal. A UL subband may be located at the center of a carrier, and two DL subbands may exist. A DL frequency band may be divided into two DL subbands by the UL subband. In another example, two or more UL subbands may exist, and DL subbands may exist in the remaining frequency band.
[0107] The base station may not perform DL-related filtering by additionally considering the locations of the DL subbands and / or UL subbands. The terminal may perform UL-related filtering by considering the locations of the UL subbands.
[0108] In order to add (e.g., transmit) a UL signal / channel while minimizing the number of UL slots in a slot pattern, an SD symbol may be introduced. A base station may instruct or configure repeated transmission of a UL signal / channel to a terminal located at a cell edge. The terminal may determine that repeated transmission of the UL signal / channel is required based on the instruction or configuration of the base station. Scheduling information for allocating a PUSCH / PUCCH may include a repetition factor for time resources. The terminal may determine the repetition factor included in the scheduling information. The repetition factor may indicate n repeated transmissions of the PUSCH / PUCCH. n may be a natural number. One repeated transmission may mean one transmission of the PUSCH / PUCCH. If the repetition factor is not instructed to the terminal (e.g., if the scheduling information does not include a repetition factor), the terminal may transmit the PUSCH / PUCCH once. In the present disclosure, PUSCH / PUCCH may refer to PUSCH and / or PUCCH. Scheduling information may include resource allocation information, resource activation information, and / or resource deactivation information. Scheduling information may be included in an RRC message, a MAC message (e.g., MAC CE), and / or a PHY message (e.g., DCI).
[0109] To extend the reach of UL signals / channels, a base station can instruct a terminal to perform demodulation-reference signal (DM-RS) bundling via signaling (e.g., RRC signaling). The terminal can determine that DM-RS bundling is required based on the signaling from the base station. Performing DM-RS bundling can mean "maintaining power consistency / phase continuity in repeated PUSCH / PUCCH transmissions." While power consistency / phase continuity is maintained, the base station can perform channel estimation operations simultaneously. Therefore, the reception performance of PUSCH / PUCCH at the base station can be improved. Power consistency / phase continuity can mean power consistency and / or phase continuity. Power consistency / phase continuity can mean coherence (e.g., time coherence).
[0110] The base station can allocate SD symbols. The order of symbols in a slot can be DL symbol-SD symbol-UL symbol. An FL symbol can be placed between a DL symbol and an SD symbol. Alternatively, an FL symbol can be omitted between a DL symbol and an SD symbol. An FL symbol can be placed between an SD symbol and an UL symbol. Alternatively, an FL symbol can be omitted between an SD symbol and an UL symbol.
[0111] FIG. 4 is a conceptual diagram illustrating embodiments of slot patterns (e.g., TDD slot patterns) including SD symbols.
[0112] Referring to FIG. 4, SD symbol(s) may be positioned after DL symbol(s), and UL symbol(s) may be positioned after SD symbol(s). The frequency band for SD symbol(s) may be divided into DL subbands and UL subbands.
[0113] The UL bandwidth for SD symbols may differ from the UL bandwidth for UL symbols. The base station may apply different filtering operations to SD and UL symbols. Optionally, the terminal may apply different filtering operations to SD and UL symbols (or DL symbols). The application of different filtering operations may mean that different filtering operations are applied based on the boundary between SD and UL symbols. In this case, power consistency / phase continuity may not be maintained during the transmission and reception of UL signals / channels.
[0114] The shape of the base station for implementing the SBFD operation can be given in various ways, and FIGS. 5 to 8 can show embodiments of the base station.
[0115] Figure 5 is a conceptual diagram illustrating embodiments of a base station implementing a TDD system.
[0116] Referring to FIG. 5, a base station can have K Tx chains and K Rx chains. The Tx chains and the Rx chains can be connected to an array having L element antennas (e.g., a shared-Tx / Rx antenna array). Each of K and L can be a natural number. In a DL resource, the shared-Tx / Rx antenna array can be connected to a Tx chain, and in a UL resource, the shared-Tx / Rx antenna array can be connected to an Rx chain. In other words, the shared-Tx / Rx antenna array can be switched according to time resources and can be utilized in both DL and UL.
[0117] Figure 6 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0118] Referring to Fig. 6, a base station may have K Tx chains and K Rx chains, and a panel group may be formed by L element antennas. Each of K and L may be a natural number. Panel group #1 utilized in DL resources and panel group #2 utilized in UL resources may be distinguished from each other. In SD resources, both panel group #1 and panel group #2 may be utilized.
[0119] From the perspective of base station transmit power, the transmit power in a DL symbol may be the same as the transmit power in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., energy per resource element (EPRE)) in an SD symbol may be greater than the power density (e.g., EPRE) in a DL symbol.
[0120] Figure 7 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0121] Referring to FIG. 7, a base station can have K / 2 Tx chains and K / 2 Rx chains, and a panel group can be formed with L / 2 element antennas. Each of K and L can be a natural number. Panel group #1 and panel group #2 can be utilized in DL resources and / or UL resources. In DL resources, both panel group #1 and panel group #2 can be connected to a Tx chain, and in UL resources, both panel group #1 and panel group #2 can be connected to an Rx chain. In SD resources, panel group #1 can be connected to a Tx chain, and panel group #2 can be connected to an Rx chain.
[0122] From the perspective of base station transmit power, the transmit power in a DL symbol may differ from that in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., EPRE) in an SD symbol may be the same as the power density (e.g., EPRE) in a DL symbol.
[0123] Figure 8 is a conceptual diagram illustrating embodiments of a base station implementing SBFD operation.
[0124] Referring to FIG. 8, a base station can have K / 2 Tx chains and K / 2 Rx chains, and a panel group can be formed by L / 2 element antennas. Each of K and L can be a natural number. Panel group #1 can be utilized in DL resources, and panel group #2 can be utilized in UL resources. In DL resources and SD resources, panel group #1 can be connected to a Tx chain, and in SD resources and UL resources, panel group #2 can be connected to an Rx chain.
[0125] From the perspective of base station transmit power, the transmit power in a DL symbol may differ from that in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., EPRE) in an SD symbol may be the same as the power density (e.g., EPRE) in a DL symbol.
[0126] To handle the traffic demand of a terminal, a base station can establish an RRC connection with the terminal. An unspecified number of terminals can select or reselect a base station using a cell search procedure. The base station (or cell) can periodically transmit a synchronization signal and / or system information. System information can be divided into a master information block (MIB) and a system information block (SIB). SIBs can be classified as SIB1, SIB2, etc. A terminal can camp on a specific base station (or cell) using the MIB and SIB. The synchronization signal and MIB can be combined, and a synchronization signal block (SSB) including the synchronization signal and MIB can be transmitted. In the examples below, SIB may mainly refer to SIB1, but SIB may not necessarily be interpreted as SIB1. Depending on the context, SIB may be interpreted as SIBx (x=1, 2, 3, etc.).
[0127] When DL traffic to be transmitted to a terminal occurs in a network or base station, the network or base station can transmit a paging message to an unspecified number of terminals to search for the terminal and establish an RRC connection with the terminal. The terminal can receive the paging message and perform a random access procedure for the network or base station, and can establish an RRC connection with the network or base station through the random access procedure.
[0128] When UL traffic to be transmitted from a terminal to a network or base station occurs, the terminal can perform a random access procedure to establish an RRC connection with the base station (or network) on which the terminal is camping.
[0129] After the RRC connection between the terminal and the base station is established, the terminal can operate based on the control of the base station (e.g., serving cell). For example, the terminal can transmit and receive data with the base station.
[0130] Because the base station cannot monitor the status of the camping terminals, its power may be wasted by the SSB and / or SIB that it periodically transmits. For example, a base station operating in normal mode may transmit SIBs at a predetermined interval. A base station operating in low-power mode may transmit SIBs at a longer interval. Alternatively, a base station operating in low-power mode may not transmit SIBs at all.
[0131] Figure 9 is a conceptual diagram illustrating an interference scenario due to SBFD operation when an attacker terminal and a victim terminal receive services from the same TRP.
[0132] Referring to FIG. 9, when interference occurs between terminals, an aggressor terminal causing interference and a victim terminal receiving interference can be distinguished at a base station or a TRP. In the present disclosure, the aggressor terminal may refer to an aggressor UE or aUE (aggressor UE), and the victim terminal may refer to a victim UE or vUE (victim UE). The terminals may be interpreted as the aggressor terminal and / or the victim terminal depending on the context. The aggressor 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 aggressor terminal may be referred to as a second terminal (e.g., a second UE). In the present disclosure, the base station may be interpreted as a serving base station depending on the context.
[0133] framework
[0134] A base station or TRP performing SBFD operation can distinguish between SD symbols and ND symbols. The ND symbol may mean a symbol in which all PRBs are utilized (or indicated) for downlink or uplink. The SD symbol may mean a symbol in which some PRBs are utilized (or indicated) for downlink or uplink. There may be a terminal that receives a DL signal / channel in the DL subband of the SD symbol. There may be a terminal that transmits a UL signal / channel in the UL subband of the SD symbol. The terminals may have a relationship in which they interfere with each other. In other words, interference may occur between a terminal operating in the DL subband of the SD symbol and a terminal operating in the UL subband of the SD symbol. In the present disclosure, a DL signal / channel may mean a DL signal and / or a DL channel, and a UL signal / channel may mean a UL signal and / or a UL channel.
[0135] Figure 10 is a conceptual diagram illustrating an interference scenario due to SBFD operation when an attacker terminal and a victim terminal receive services from different TRPs.
[0136] Referring to FIG. 10, the attacker terminal and the victim terminal may belong to different TRPs or different base stations. The attacker terminal may transmit a UL signal / channel to the first TRP (e.g., the first base station) after establishing an RRC connection with the first TRP (e.g., the first base station). The attacker terminal may transmit a UL signal / channel to the first TRP (e.g., the first base station) even in an RRC disconnected state (e.g., an RRC inactive state or an RRC idle state). The victim terminal may receive a DL signal / channel from the second TRP (e.g., the second base station) after establishing an RRC connection with the second TRP (e.g., the second base station).
[0137] A serving base station may perform a coordination operation between an attacker terminal and a victim terminal to determine the size of UE-to-UE CLI (Cross Link Interference). The UE-to-UE CLI may be referred to as UE-UE CLI. In the present disclosure, CLI may be interpreted as UE-to-UE CLI depending on the context. The victim terminal may measure a CLI-RSSI (received signal strength indicator) and / or CLI-RSRP based on a CLI-RS (reference signal). The CLI-RS may be an SRS (e.g., an SRS transmitted by the attacker terminal). The CLI-RSSI may be an SRS-RSSI, and the CLI-RSRP may be an SRS-RSRP. The victim terminal may generate CSI based on a CSI reporting configuration indicated by the base station and transmit (e.g., report) the CSI to the base station. The victim terminal may transmit the CSI on an UL signal / channel through a UL priority setting / multiplexing procedure. The attacker terminal can receive information (e.g., instructions) from the base station via signaling to transmit UL signals / channels (e.g., SRS) for CLI measurement. The UL priority setting / multiplexing procedure may refer to a UL priority setting procedure and / or a UL multiplexing procedure.
[0138] A CSI framework can be applied to measure CLI-RSSI or SRS-RSRP. A terminal (e.g., an attacker terminal and / or a victim terminal) can receive a CSI reporting configuration from a base station via RRC signaling. The terminal can identify a Channel Measurement Resource (CMR) and an Interference Measurement Resource (IMR) based on the information included in the CSI reporting configuration. In other words, the CSI reporting configuration can include CMR information (e.g., CMR set information) and IMR information (e.g., IMR set information). Alternatively, the CSI reporting configuration can include CMR information without IMR information. A CMR can refer to a resource and / or a resource set of a DL signal / channel for measuring a channel. An IMR can refer to a resource and / or a resource set of a DL signal / channel for measuring interference. An IMR can refer to resources (e.g., REs) belonging to a DL subband. According to the proposed method, a CMR may include "resources (e.g., REs) belonging to a UL signal / channel" and / or "resources (e.g., REs) belonging to a UL subband." An IMR may include "resources (e.g., REs) belonging to a UL signal / channel" and / or "resources (e.g., REs) belonging to a UL subband."
[0139] CSI reporting configuration for measuring CLI (e.g., CLI-RSSI) may be considered. CMR information may indicate the locations of SD symbols and / or PRBs for measuring CLI (e.g., CLI-RSSI). IMR information may indicate the locations of SD symbols and / or PRBs for measuring CLI (e.g., CLI-RSSI). Appropriate TCI state (e.g., qcl-typeD) for the victim terminal may be required for measuring CLI (e.g., CLI-RSSI).
[0140] CSI reporting configurations for measuring CLI-RSSI may be considered. CMRs may be associated with a CLI resource set or CLI resources. IMRs may be associated with a CLI resource set or CLI resources. To measure (e.g., acquire) CLI, only a subset of CLI measurement information may be required. Appropriate TCI states (e.g., qcl-typeD) for the victim UE may be required to measure CLI. Appropriate priorities may be assigned, and appropriate priorities may be mapped to UL signals / channels. SRSs may be utilized as CLI-RSs for measuring CLI.
[0141] Figure 11 is a conceptual diagram illustrating extended embodiments of CSI reporting settings of a victim terminal.
[0142] Referring to FIG. 11, the CSI reporting configuration of the victim terminal may include an SRS resource set for the CMR configuration. The victim terminal may measure SRS-RSRP using the SRS. The attacker terminal may transmit the SRS in the UL subband of the SD symbol. The SRS may be transmitted in the SRS resource set. The SRS transmitted by the attacker terminal may be for the purpose of measuring UE-to-UE CLI. The method of transmitting the SRS for measuring UE-to-UE CLI may be distinguished from the method by which the attacker terminal transmits the SRS to the serving base station.
[0143] Transmission settings
[0144] SRS can be utilized as a CLI-RS instructing an attacker terminal. SRS can be transmitted in UL BWP. SRS can be utilized for various purposes in UL signaling / channel. The usage of SRS can be expressed as usage among RRC variables associated with an SRS resource set. Usage can be classified into CB (codebook), NCB (noncodebook), BM (beam management), AS (antenna switching), etc. RRC variables can mean RRC parameters. An SRS resource set can include one or more SRS resources. In order for SRS resources belonging to an SRS resource set to have the same behavior (e.g., usage), RRC variables can be applied in common. For example, RRC variables can include an SRS transmission period (e.g., a period of an SRS resource), a slot index in which an SRS is transmitted (e.g., a slot index of an SRS resource), and / or an SRS transmission power. An SRS resource can mean SRS symbols (e.g., all SRS symbols). In other words, an SRS resource may contain SRS symbols.
[0145] usage
[0146] According to the proposed method, the BM can be interpreted as indicating the purpose for CLI measurement. In the above-described method, the purpose of the SRS for CLI measurement can be interpreted as the BM. According to another method, the purpose of the SRS for CLI measurement can be separately indicated (e.g., configured). The purpose of the SRS can be expressed as the CLI. In the above-described method, the newly configured purpose of the SRS for CLI measurement can be indicated to the terminal.
[0147] Figure 12 is a conceptual diagram illustrating extended embodiments of SRS settings of an attacker terminal.
[0148] Referring to FIG. 12, an SRS resource set in an SRS configuration may have multiple purposes. The purposes of SRS may include CB, NCB, BM, AS, and POS (positioning). CLI measurement (e.g., CLI) may be introduced as a new purpose of the SRS resource set. The number of SRS resource sets indicated by the SRS configuration may be one. If there are two or more serving cells measuring UE-to-UE CLI, two or more SRS resource sets for CLI may be indicated to the UE. For example, a case may be considered where a supplementary (SUL) carrier may be configured for the victim UE, and SBFD operation may be supported (e.g., performed) on each of the normal uplink (NUL) carrier and the SUL carrier. In this case, an SRS resource set for CLI may be indicated independently in each serving cell.
[0149] The SRS resources of the SRS resource set for BM (e.g., conventional BM) can be used as UL BM. According to the proposed method, BM can mean that SRS is used for CLI measurement. The serving base station of the attacker 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 may be the same as the serving base station of the attacker terminal. Alternatively, the serving base station of the victim terminal (e.g., the first serving base station) may be different from the serving base station of the attacker terminal (e.g., the second serving base station).
[0150] To support the victim terminal to measure the CLI, the base station can signal to the terminal(s) (e.g., upper layer signaling) that the attacker terminal transmits an SRS in an SD symbol (e.g., an SRS resource within an SD symbol). The duplex type (e.g., a symbol type) for the SRS transmission can be indicated based on information included in the SRS resource set. If the symbol type indicated by the base station is an SBFD symbol and SRS resources belonging to the same SRS resource set are SD symbols, the attacker terminal can transmit an SRS in the SRS resource (e.g., an SD symbol). The duplex type for the SRS transmission can be independently indicated to the terminal for each SRS resource. Some SRS resources among the SRS resources belonging to the same SRS resource set can be SD symbols, and other SRS resources among the SRS resources can be ND symbols. In this case, the attacker terminal may transmit SRS in some SRS resources (e.g., SD symbols) and may not transmit SRS in other SRS resources (e.g., ND symbols). The base station may set the duplex type for the SRS transmission (e.g., SRS resources) of the attacker terminal in units of SRS resource sets, SRS resources, or SRS symbols through signaling. The attacker terminal may determine the duplex type for the SRS transmission (e.g., SRS resources, SRS symbols) based on the signaling of the base station (e.g., higher layer signaling).
[0151] An SRS resource belonging to an SRS resource set may belong to an SD symbol. In other words, a terminal (e.g., an attacker terminal) may transmit an SRS using an SRS resource within an SD symbol. The SRS resource within the SD symbol may belong to an UL subband (e.g., UL available PRB(s)). An SRS resource belonging to an SRS resource set may be determined to be invalid in an ND symbol, and an SRS transmission may be dropped in an SRS resource within an ND symbol (e.g., an invalid resource, an invalid SRS symbol). An SRS transmission may be dropped on a symbol-by-symbol basis. In the present disclosure, an SRS resource may be interpreted as all SRS symbols or one SRS symbol depending on the context. An SRS transmission may be dropped in all symbols. An attacker terminal may transmit an SRS in valid SRS symbol(s) and may not transmit an SRS in invalid SRS symbol(s). If all PRBs to which an SRS sequence is mapped belong to a UL subband, an SRS symbol (e.g., an SRS resource) belonging to the UL subband may be a valid SRS symbol (e.g., a valid SRS resource).
[0152] The above-described embodiment can be performed when the symbol type is set to SBFD (e.g., SBFD symbol). For example, the base station can transmit information indicating that the symbol type is set to SBFD to the terminal (e.g., the attacker terminal and / or the victim terminal) through signaling. The attacker terminal can determine one or more valid symbols (e.g., one or more valid SRS symbols) based on the symbol type among the resources (e.g., SRS resources) indicated by the SRS configuration information, and can transmit an SRS using the one or more valid symbols. In the present disclosure, a valid resource may mean a valid symbol or a valid SRS symbol. The SRS configuration information may include information on an SRS resource set. In other words, the SRS configuration information may indicate an SRS resource set. The SRS resource set may indicate one or more SRS resources. Each SRS resource may include SRS symbols. SRS configuration information (e.g., information about an SRS resource set) may include information indicating a symbol type (e.g., a symbol type for an SRS resource and / or an SRS symbol). The symbol type may be commonly applied to one or more SRS resources belonging to the SRS resource set.
[0153] When the symbol type is set to SBFD, the attacker terminal can transmit SRS in the SBFD symbol (e.g., UL subband within the SBFD symbol), and the victim terminal can perform measurements (e.g., CLI measurements) on the SRS in the SBFD symbol (e.g., UL subband within the SBFD symbol). In other words, the attacker terminal and / or the victim terminal can determine the SBFD symbol as a valid symbol(s) for transmitting and receiving SRS. The attacker terminal and / or the victim terminal can expect that the SRS is transmitted and received in the SBFD symbol.
[0154] For another example, the base station can transmit information indicating that the symbol type is set to N(non)-SBFD (e.g., an N-SBFD symbol) to the terminal (e.g., an attacker terminal and / or a victim terminal) via signaling. The attacker terminal can determine one or more valid symbols (e.g., one or more valid SRS symbols) based on the symbol type among the resources (e.g., an SRS resource) indicated by the SRS configuration information, and can transmit an SRS using the one or more valid symbols. When the symbol type is set to N-SBFD, the attacker terminal can transmit an SRS in an N-SBFD symbol (e.g., an UL symbol and / or an FL (flexible) symbol), and the victim terminal can perform measurements (e.g., CLI measurements) on the SRS in the N-SBFD symbol (e.g., an UL symbol and / or an FL symbol). In other words, the attacker terminal and / or the victim terminal can determine the N-SBFD symbol as a valid symbol(s) for transmitting and receiving an SRS. The attacker terminal and / or the victim terminal can expect SRS to be transmitted and received in the N-SBFD symbol.
[0155] The TCI state (e.g., spatial relationship information) of an SRS resource can be indicated by an RRC variable, and the TCI state of the SRS resource can be associated with a DL signal / channel and / or an UL signal / channel. The associated signal / channel can be changed using a DCI format or MAC CE. The SRS resource can be indicated to a terminal periodically, semi-persistently, or aperiodically. The TCI state can be independently indicated to the terminal. According to the proposed method, the same TCI state can be applied to an SRS resource when the purpose of the SRS resource set is CLI measurement, an SRS resource when the purpose of the SRS resource set is CB, an SRS resource when the purpose of the SRS resource set is NCB, and / or an SRS resource when the purpose of the SRS resource set is BM. In other words, TCI states associated with SRS resources for other purposes (e.g., CB, NCB, and / or BM) can be applied to SRS resources for CLI measurements (e.g., UE-to-UE CLI).
[0156] SRS settings
[0157] A base station can generate SRS configuration information and transmit the SRS configuration information to a terminal (e.g., an attacker terminal and / or a victim terminal) through signaling. The terminal can receive the SRS configuration information through signaling from the base station. The attacker terminal can transmit an SRS based on the SRS configuration information. The victim terminal can perform measurements (e.g., CLI measurements) on the SRS transmitted by the attacker terminal based on the SRS configuration information or CMR configuration information. The SRS configuration information can include information on an SRS resource set, information on an SRS location resource set, etc.
[0158] UL multiplexing priority
[0159] UCI prioritization / multiplexing may be a procedure performed by a UE to transmit PUCCH, PUSCH, SRS, and / or PRACH. UCI prioritization / multiplexing may refer to UCI prioritization and / or UL multiplexing. The UE may transmit one or two UL signals / channels to reduce peak-to-average power ratio (PAPR) / intermodulation distortion (IMD). To support the above operation, UCI and UL-SCH (e.g., PUSCH) may be multiplexed. Alternatively, the UE may select one of the UCI and UL-SCH and transmit the selected UL signal / channel. At least one of the multiplexed UCI / UL-SCH, UCI, or UL-SCH may be mapped to one or two UL signals / channels.
[0160] Two UL signals / channels may be selected from frequency combinations that allow simultaneous transmission of UL signals / channels other than "PUCCH and PUSCH," "PUSCH and SRS," or "PRACH and PRACH." A feature or capability of the terminal supporting simultaneous transmission may be required. If the above-mentioned restrictions do not exist, the terminal may transmit UCI and / or UL-SCH on one UL channel. Alternatively, if the above-mentioned restrictions do not exist, the terminal may transmit only PRACH on one UL channel.
[0161] According to the proposed method, the priority of L1-RSRP can be reused as the priority of reports of SRS-RSRP or CLI-RSSI. In other words, the priority of reports of SRS-RSRP or CLI-RSSI can be determined based on the priority of L1-RSRP. The priority may not be the priority for UL signals / channels of URLLC and eMBB distinguished by priority indices. The priority can be utilized as a priority to drop some CSI reports when the code rate cannot be maintained in CSI reports with the same priority indices.
[0162] CSI reports may be prioritized. CSI reports may be prioritized based on the following mathematical formula:
[0163]
[0164] may be a priority for CSI reporting. y may be determined based on the physical channel through which the CSI report is transmitted and the trigger characteristics of the CSI report. k may be determined based on whether L1-RSRP and L1-SINR are present in the CSI report, respectively. c may denote a serving cell index. s may be an identifier of a CSI reporting configuration. can mean the maximum number of serving cells. may mean the maximum number of CSI reports. For the first CSI report The value of is for the second CSI report. If the value is less than , the first CSI report may be considered more important than the second CSI report. In other words, The smaller the value of , the higher the CSI reports associated with may have high importance. CSI reports may be distinguished by a single identifier. Multiple CSI reports may be concatenated based on preset rules. Encoding and modulation procedures may be applied to the concatenated CSI reports. Each CSI report may be divided into Part 1 and Part 2. The payload belonging to a CSI report may be divided into two parts, and independent encoding procedures may be applied to each of the two parts.
[0165] When a CSI report includes a 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 for part 1 may be fixed, and the payload size for part 2 may change according to the information included in part 1. The base station may first decode part 1, determine the payload size of part 2 based on the decoding result of part 1, and attempt to decode part 2 considering the payload size.
[0166] When Part 1 and Part 2 are distinguished, 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.
[0167] When Part 1 and Part 2 are distinct, a CSI report containing SRS-RSRP may consist of Part 1 only. When Part 1 and Part 2 are distinct, a CSI report containing CLI-RSSI may consist of Part 1 only.
[0168] When measuring CLI, the mathematical formula for deriving the priority of CSI reporting (e.g., mathematical formula 1 described above) can be extended and applied. Both SRS-RSRP and CLI-RSSI can be processed at the physical layer, and the UE can express SRS-RSRP and / or CLI-RSSI with 7-bit (or 4-bit) accuracy. The UE can derive the channel power by coherently demodulating the SRS. In other words, the UE can derive SRS-RSRP for the SRS received from the base station. To support the above-described operation, the UE may need to know all the resource configurations of the SRS to be measured. On the other hand, since CLI-RSSI does not utilize a separate RS, the UE can derive the received power by applying non-coherent demodulation. To support the above-described operation, the UE may need to know the time and frequency positions of the resources to be measured. Although SRS-RSRP and CLI-RSSI have different characteristics, the terminal can process SRS-RSRP and CLI-RSSI in a similar procedure. The terminal can set the priority of SRS-RSRP and CLI-RSSI (e.g., ) can be derived in the same way.
[0169] Based on the similarity between L1-RSRP and SRS-RSRP, L1-RSRP and SRS-RSRP can be derived in the same manner, and the values of k for CLI-RSSI, SRS-RSRP, and L1-RSRP can be considered as 1, and k=1 can be applied to the above-described mathematical expression 1.
[0170] Equivalence of Measurement Purposes: RSRP can indicate link quality (e.g., link quality for the downlink), while CLI-RSSI can indicate cross-link interference. Cross-link interference can refer to interference on the link from the attacker terminal to the victim terminal. Both RSRP and CLI-RSSI can provide information on the received power level of the terminal in the current radio environment. The network (e.g., the base station) can use RSRP and CLI-RSSI together to perform beam selection operations, UL muting operations, power control operations, etc. Therefore, there is no need to differentiate the importance of RSRP and CLI-RSSI.
[0171] Diversity of configuration scenarios: Measurements for CLI-RSSI can be configured for CLI mitigation purposes, measurements for both RSRP and CLI-RSSI can be configured to simultaneously assess link performance and interference conditions, and measurements for RSRP can be configured when UL interference is minimal. If different CSI reports collide, setting one CSI report to lower priority (k=1) may result in delay and / or loss of essential information.
[0172] Ensuring simplicity of the priority system: If the scope of application of k=0 is set to CSI reports including L1-RSRP, L1-CLI-RSSI, and / or L1-SINR, the terminal can resolve collisions based on a single comparison logic. If k=1 is set to apply to CLI-RSSI, the combination of y, k, and / or Pri values (e.g., priority) may become complex, and the possibility of processing delay and code errors may increase. Due to the above-described problem, the scope of application of k=0 in the present disclosure can be expanded. Accordingly, the priority of L1-CLI-RSSI may be set to be the same as the priority of LI-RSRP and / or L1-SINR.
[0173] Terminal conflict resolution procedure
[0174] The terminal can identify (y,k,c,s) for each CSI report based on the interpretation result of PDCCH or MAC CE, and based on (y,k,c,s), the Pri value (e.g., ) can be determined. If two CSI reports in the same slot and the same carrier share at least one symbol (e.g., OFDM symbol), the terminal can consider (e.g., determine) the collision of the CSI reports and process them in the following order.
[0175] (1) If the values of y for CSI reports are different, the terminal may transmit the CSI report with the value of y having a higher priority. The y having a higher priority may be determined based on the table defined in the technical specifications.
[0176] (2) If the values of y for CSI reports are the same and the values of k for CSI reports are different, the terminal may maintain (e.g., transmit) the CSI reports (e.g., L1-RSRP, L1-CLI-RSSI, and / or L1-SINR) with k=0 and omit the CSI reports with K=1.
[0177] (3) If the values of y for the CSI reports are the same and the values of k for the CSI reports are the same, the terminal can maintain (e.g., transmit) the CSI report with the low Pri value and omit the CSI report with the high Pri value.
[0178] (4) If the values of y for the CSI reports are the same, the values of k for the CSI reports are the same, and the values of Pri for the CSI reports are the same, the terminal can multiplex the CSI reports and transmit the multiplexed CSI reports. The multiplexing operation of the CSI reports can be performed based on the procedure specified in the technical specification (e.g., TS 38.213).
[0179] When a network (e.g., a base station) simultaneously allocates a quasi-persistent PUSCH and a data PUSCH, the terminal can operate based on the procedure described above. The terminal can perform N2+ d 2,1 Semi-persistent CSI reports that do not meet the timeline conditions may not be transmitted.
[0180] Based on the above-described operations, immediate response to interference can be possible, implementation can be simplified, and standards compatibility can be maintained. In other words, CLI-RSSI can be considered high priority, and commands for mitigating cross-link interference (e.g., beam switching, UL muting, etc.) can be executed without delay. Since the UE prioritizes CSI reporting based on a single k, the UE's firmware complexity and / or memory usage can be reduced. Since the y value structure remains unchanged, the priority of service quality (e.g., eMBB, URLLC, etc.) can remain unchanged, and the CLI measurement function can be integrated with the existing CSI framework.
[0181] The above-described priority definitions can be applied to both RSRP and CLI-RSSI. Consistent collision resolution can be guaranteed for any configuration that includes either RSRP or CLI-RSSI. Consequently, efficient use of radio resources and / or interference control performance can be improved. For processing CSI reports, the same number of CPUs (e.g., the terminal's CPU) as L1-RSRP can be allocated.
[0182] When a transmission for PUCCH / PUSCH is scheduled for an attacker terminal, the attacker terminal may drop SRS transmission (e.g., SRS resources). PUCCH / PUSCH may refer to PUCCH and / or PUSCH.
[0183] According to another proposed method, the priorities of SRS resource(s) belonging to the SRS resource set for CLI can be changed in the UL prioritization / multiplexing procedure.
[0184] The priority of SRS resources can be compared with the priority of PUSCH / PUCCH. Based on the result of the priority comparison, the UE can drop SRS transmission and transmit PUSCH / PUCCH. PUSCH / PUCCH and SRS can be scheduled by the same serving base station. Even if an SRS transmission is dropped, the serving base station may not perform UL BM in the corresponding UL symbol (e.g., the UL symbol in which the SRS transmission was dropped).
[0185] In the measurement procedure of UE-to-UE CLI, if the attacker terminal drops the transmission of CLI-RS (e.g., SRS), the CLI (e.g., SRS-RSRP, CLI-RSSI) derived by the victim terminal may be inaccurate. The victim terminal may report a CSI report to the serving base station of the victim terminal. The serving base station may implementally ignore the CSI report of the victim terminal. It may be inefficient for the serving base station to ignore the CSI report of the victim terminal. Therefore, it may be desirable for the victim terminal not to measure the CLI. It may be desirable for the victim terminal to know whether the attacker terminal drops the CLI-RS transmission.
[0186] The attacker's SRS may have a lower priority than the PUSCH / PUCCH. Alternatively, the attacker's SRS may have a higher priority than the PUSCH / PUCCH. To allow the SRS to be transmitted, a portion of the PUSCH / PUCCH may be dropped. The attacker's terminal may drop a portion of the PUSCH / PUCCH by performing puncturing or rate matching.
[0187] Figure 13 is a conceptual diagram illustrating embodiments in which an attacker terminal that has received scheduling information of a UL signal / channel transmits an SRS.
[0188] Referring to Fig. 13, SRS resources for CLI can be time-division multiplexed (TDM) in some symbols in which UL signals / channels are transmitted. The frequency resources of the UL signals / channels can be configured as continuous PRBs or non-consecutive PRBs depending on the resource allocation method. According to the proposed method, since the SRS has a high priority, the terminal can transmit the SRS and drop some of the UL signals / channels. In order to transmit the SRS, a change in the Tx beam (e.g., TCI state or spatial relationship information) may be required.
[0189] The attacker terminal can schedule the repeated transmission of the UL signal / channel. In other words, the attacker terminal can receive scheduling information for the repeated transmission of the UL signal / channel. The above-described operation can be performed on one UL signal / channel instance where the transmission of the SRS overlaps among the UL signal / channel instances. The transmission of the SRS can be considered to overlap in all instances of the UL signal / channel. For example, in a PUSCH transmission procedure, the attacker terminal can perform rate matching of the UL-SCH (shared channel) for the resources (e.g., symbols and subcarriers) on which the SRS is transmitted.
[0190] The attacker terminal may not transmit SRS. Even in this case, the attacker terminal can perform rate matching of the UL-SCH to transmit the UL signal / channel. The SRS (e.g., the SRS not transmitted by the attacker terminal) can be considered as a zero power (ZP) SRS. The serving base station of the attacker terminal can measure the CLI (e.g., BS (base station)-BS CLI) between base stations in the resources occupied for the ZP SRS.
[0191] Tx beam reuse
[0192] When the transmission beam of SRS (e.g., Tx beam) and the transmission beam of PUCCH / PUSCH are different, the attacker terminal may need time to change the transmission beam. The time required by the attacker terminal can be expressed as Δ1 and / or Δ2. Δ1 (≥0) symbol(s) from the first symbol of the SRS resource to the preceding first symbol can be used to change the transmission beam. Δ2 (≥0) symbol(s) from the last symbol of the SRS resource to the following last symbol can be used to change the transmission beam.
[0193] The time resources of PUSCH / PUCCH can be divided into y10, y20, y30, and / or y40. At times corresponding to y10 and y40, the attacker terminal can perform transmission using the transmission beam of PUSCH / PUCCH. At time corresponding to y20, the attacker terminal can perform an operation to change the transmission beam of PUSCH / PUCCH to the transmission beam of SRS. Depending on certain capabilities of the attacker terminal, the attacker terminal may not be able to transmit PUCCH / PUSCH. Depending on other capabilities of the attacker terminal, the attacker terminal may be able to transmit PUCCH / PUSCH.
[0194] At a time corresponding to y30, the attacker terminal may perform an operation to change the transmission beam of the SRS to the transmission beam of the PUSCH / PUCCH. Depending on certain capabilities of the attacker terminal, the attacker terminal may not be able to transmit the PUCCH / PUSCH. Depending on other capabilities of the attacker terminal, the attacker terminal may be able to transmit the PUCCH / PUSCH. The values of Δ1 and Δ2 may be different. When frequency hopping of the PUSCH / PUCCH is performed, the embodiments of FIG. 13 may be applied to at least one frequency hop.
[0195] If the transmission of PUSCH / PUCCH is scheduled to start before the transmission of SRS, PUSCH / PUCCH can be transmitted in the region of "y10" or "y10 and y20". If the transmission of SRS is scheduled to start before the transmission of PUSCH / PUCCH, PUSCH / PUCCH can be transmitted in the region of "y30" or "y30 and y40". If the symbol(s) for which PUSCH / PUCCH transmission is scheduled include y10 or y40, the attacker terminal can transmit PUSCH / PUCCH at least in y10 and / or y40.
[0196] If the transmit beams of PUSCH / PUCCH and SRS are the same, the interval y20 or y30 may be unnecessary. If the transmit beams are the same, the attacker terminal may regard the value of Δ1 or Δ2 as 0. Alternatively, the attacker terminal may regard the value of Δ1 or Δ2 as always greater than 0 without performing the procedure of comparing the transmit beams.
[0197] The transmission beam of the SRS and the transmission beam of the PUSCH / PUCCH can be determined by priority. The transmission beam of the SRS can be derived from the TCI state associated with the SRS resource. When the SRS is TDM'd with the PUSCH / PUCCH, the transmission beam (e.g., the TCI state) of the PUSCH / PUCCH can be applied for transmission of the SRS. The TDM of the PUSCH / PUCCH and the SRS can occur in the same slot. The UE can transmit the PUSCH / PUCCH and the SRS in the TDM manner within the same slot. Alternatively, the TDM of the PUSCH / PUCCH and the SRS can occur in the same slot and the same serving cell. The UE can transmit the PUSCH / PUCCH and the SRS in the TDM manner in the same slot of the same serving cell. According to the proposed method, the terminal can check whether PUSCH / PUCCH and SRS are TDM-enabled in order to derive the transmission beam of the SRS, and based on the checked result, can apply the TCI state of the SRS resource or the TCI state of the PUSCH / PUCCH to the transmission beam of the SRS. If the TCI state for the transmission beam of the SRS (e.g., the SRS resource) is not indicated, the terminal can regard the default beam applied to the SRS (e.g., the SRS resource) as the TCI state, and can check whether PUSCH / PUCCH and SRS are TDM-enabled.
[0198] According to the proposed method, the attacker terminal can maintain the transmission beam during the time period in which the PUSCH / PUCCH and SRS are TDMed. The TDM of the PUSCH / PUCCH and SRS can occur in the same slot. The terminal can transmit the PUSCH / PUCCH and SRS in a TDM manner within the same slot. Alternatively, the TDM of the PUSCH / PUCCH and SRS can occur in the same slot and the same serving cell. The terminal can transmit the PUSCH / PUCCH and SRS in a TDM manner in the same slot of the same serving cell. The coherence of the PUSCH / PUCCH may not be maintained due to the SRS transmission. For example, in the embodiment of FIG. 13, the antenna port for y10, where the PUSCH / PUCCH is transmitted, may not be considered to be the same as the antenna port for y40, where the PUSCH / PUCCH is transmitted. According to the proposed method, the necessary condition(s) for the antenna port for y10 to be considered identical to the antenna port for y40 can be satisfied because the same transmission beam is maintained. If the sufficient condition(s) are obtained by a combination of the above-described condition(s) and other conditions described below, the attacker terminal can maintain consistency while transmitting SRS and PUSCH / PUCCH in TDM mode.
[0199] A victim terminal can receive an indication of a unified TCI state from a serving base station. A terminal capable of following the unified TCI state can derive a transmit filter for a UL RS and / or a receive filter for a DL RS from the same TCI state index. To indicate a TCI state, only an RS indicating qcl-typeA, qcl-typeB, or qcl-typeC may not be configured, and an RS indicating qcl-typeD may be additionally configured. The RS indicating qcl-typeD may be an SSB or a DL RS. If there is a derived receive filter (Rx filter) for receiving an SSB / DL RS indicating qcl-typeD, the victim terminal can receive an SRS using the Rx filter. In other words, the victim terminal can perform a measurement operation for an SRS based on information (e.g., qcl-typeD) derived from the TCI state indicated for the SSB and / or DL RS. The above described behavior can also be applied when aperiodic CSI reporting is triggered.
[0200] The base station can set TCI state(s) with qcl-typeD and / or unified TCI state (e.g., unifiedTCI-StateType) to the terminal (e.g., attacker terminal and / or victim terminal). The terminal can expect that TCI state(s) with qcl-typeD and / or unified TCI state (e.g., unifiedTCI-StateType) is set. The terminal can perform measurements (e.g., CLI measurements) on the SRS by applying QCL estimation based on the TCI state(s) with qcl-typeD and / or unified TCI state.
[0201] center frequency
[0202] Frequency resources for PUSCH / PUCCH transmission and frequency resources for SRS transmission may be different. The center frequencies of PRBs where PUSCH / PUCCH is scheduled may not be the same as the center frequencies of PRBs where SRS is transmitted. The attacker terminal may not operate based on the center frequency of the UL BWP. Referring to an embodiment in which PUSCH / PUCCH and SRS are TDMed (e.g., the embodiment of FIG. 13), the attacker terminal may need to change the center frequency. To support the above-described operation, a change time (e.g., a retuning time, etc.) of the RF (radio frequency) circuit may be required. This may cause inconsistency. The attacker terminal may determine (e.g., adjust, consider) the center frequency as the center frequency of the union of the frequency resources of PUSCH / PUCCH and SRS. In other words, the attacker terminal can operate based on the center frequency of the union of the frequency resources of PUSCH / PUCCH and SRS.
[0203] The frequency resources of PUSCH / PUCCH and SRS may be misaligned, and there may not be a common PRB between PUSCH / PUCCH and SRS. If the frequency resources of PUSCH / PUCCH and SRS are misaligned, it may mean that the attacker terminal transmits SRS in a narrowband. In this case, the victim terminal may not measure SRS (e.g., SRS-RSRP) in a wideband. For accurate measurement of SRS (e.g., SRS-RSRP), it may be desirable for the attacker terminal to transmit SRS in a wideband. A wideband SRS transmission may mean a transmission that occupies all or most of the PRBs belonging to the UL subband of the SD symbol (e.g., UL available PRB(s)).
[0204] The victim terminal can measure UE-to-UE CLI to support SBFD operation. The victim terminal can measure RSRP by performing coherent demodulation on CLI-RS (e.g., SRS). In other words, the victim terminal can perform measurements on SRS (e.g., CLI measurements). The victim terminal can measure CLI-RSSI based on CLI-RS.
[0205] In the transmission and configuration of SRS, some information may be cell-specifically indicated to the UE, and other information may be UE-specifically indicated to the UE. Subframes in which SRS can be transmitted may be cell-specifically indicated to the UE. The UE may derive a subframe in which the SRS is transmitted based on UE-specific configuration among the subframes indicated in a cell-specific manner. The resource in which the SRS is transmitted may be UE-specifically indicated. The resource in which the SRS is transmitted may include time resources, frequency resources, and / or sequence resources. When the base station performs SBFD operation, the base station may utilize the SRS for UE-to-UE CLI measurement. The SRS transmitted in the UL subband (e.g., UL available PRB(s)) and SD symbols may be derived based on cell-specific and / or BWP-specific information. An attacker UE may transmit an SRS derived based on cell-specific and / or BWP-specific information.
[0206] 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 can include at least one of the generation information, length, or cyclic shift of the Zadoff-Chu (ZC) sequence. To set the same sequence information, the sequence group shift and / or sequence hopping can be set identically.
[0207] The frequency information of the SRS can be indicated to the terminal in a cell-specific or BWP-specific manner. The frequency information of the SRS can include at least one of the bandwidth, hopping pattern, or tone index of the SRS. The length of the sequence can be derived based on the frequency information of the SRS. A ZC sequence having a length longer than the bandwidth of the SRS can be generated. The generated ZC sequence can be punctured to match the bandwidth of the SRS, and transmission of the SRS (e.g., an SRS including a punctured ZC sequence) can be performed.
[0208] When attacker terminals belong to more than one serving TRP (e.g., different serving TRPs), the information used to derive the SRS can be applied in common to apply the proposed method. The above information can be applied in common to an area wider than the cell or to an area where SBFD is performed.
[0209] Depending on the SRS configuration, a bandwidth that includes an integer number of PRBs may not always be configured. This is because the number of UL-available PRBs in an SD symbol (e.g., the bandwidth of a UL subband) may not always match the number of PRBs supported by the SRS. In such cases, the SRS that occupies the largest number of UL-available PRBs may be configured.
[0210] SRS configuration information can be used as transmission information on the attacker's terminal, and SRS configuration information can be used as measurement information on the victim's terminal. The attacker's terminal and the victim's terminal may require different information. For example, SRS transmission power does not necessarily need to be indicated to measure SRS-RSRP. In this case, SRS transmission power information may be indicated to the attacker's terminal, but may not be indicated to the victim's terminal.
[0211] TA(timing advance)
[0212] When the purpose is CLI measurement or BM, the time at which SRS transmission (e.g., transmission based on SRS resources) is performed may be different from the time defined in the technical specification. The time at which an SRS symbol (e.g., SRS) transmitted by an attacker terminal can be determined by considering the position of the SRS symbol on the boundary of an UL slot. The UL slot boundary can be considered as a time point that is TA advanced from the boundary of a DL slot. 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 attacker terminal receives the SRS symbol, the transmission time of the SRS symbol can be determined by considering the TA 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. The transmission time of the SRS symbol can be a time point that considers the TA.
[0213] FIG. 14 is a conceptual diagram illustrating embodiments for determining the location of time resources for measuring UE-to-UE CLI.
[0214] Referring to Fig. 14, a terminal (e.g., an attacker terminal) can transmit an SRS (e.g., an SRS symbol) at z10. In other words, the attacker terminal can transmit an SRS by applying TA. For example, the attacker terminal can transmit an SRS at z10 before the TA from z20. The victim terminal can consider z10 as the time point for measuring the SRS (e.g., SRS-RSRP). In other words, the victim terminal can determine the reception time point (e.g., the measurement time point) of the SRS by considering the TA. The SRS symbol can mean an SRS (e.g., a part of the SRS).
[0215] The transmission time of the SRS symbol may be a time point that does not consider TA. Not considering TA may mean considering TA as 0. A terminal (e.g., an attacker terminal) may transmit an SRS symbol at z20. If the attacker terminal is geographically adjacent to the victim terminal and the TA values of the attacker terminal and the victim terminal are similar, the attacker terminal may have a significant impact on the victim terminal. It may be desirable to measure the amount of interference at z20, the time point when the victim terminal receives the DL signal / channel. The attacker terminal may transmit an SRS symbol at z20. The victim terminal may receive the SRS symbol at z20.
[0216] The transmission timing of an SRS symbol can be controlled by an RRC variable (e.g., an RRC parameter). According to the control based on the RRC variable, the attacker terminal can transmit the SRS symbol at z10. According to another control based on the RRC variable, the attacker terminal can transmit the SRS symbol at z20. In the proposed method, the transmission timing of an SRS symbol can be controlled (e.g., determined) based on the configuration of an SRS resource set. The transmission timing of an SRS symbol can be controlled commonly for all SRS resources belonging to the SRS resource set. According to another proposed method, the transmission timing of an SRS symbol can be controlled for each SRS resource.
[0217] electrical energy
[0218] A set of SRS resources for BM, CB, NCB, AS, and / or POS can be transmitted (e.g., configured) at a serving base station for UL maintenance. Closed-loop control for an attacker terminal can be performed to maintain an appropriate level of transmit power in the SRS resources. If 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 (e.g., long-term fading, large-scale fading, etc.) between the serving base station and the attacker terminal. Since the victim terminal is expected to be geographically adjacent to the attacker terminal, even if the transmit power of the SRS is determined by considering the fading between the victim terminal and the attacker terminal, an SRS-RSRP with sufficient quality can be measured. In such cases, since the attacker terminal does not need to apply large transmission power for SRS transmission, it may be desirable for the attacker terminal to transmit SRS by applying low transmission power (e.g., appropriate transmission power).
[0219] According to the proposed method, the transmission power applied by the attacker terminal can be independently controlled for the SRS resources belonging to the SRS resource set for CLI. The transmission power of the SRS resources can be independent of an independent closed-loop control (e.g., a power adjustment state or a power control loop). The SRS resource set for BM, CB, NCB, AS, and / or POS can belong to any one of the control loops, and a command in the DCI format can be reflected in the SRS resource set. If the SRS resource set for CLI does not belong to the control loop or if the SRS resource set for CLI belongs to the control loop, a command in the DCI format may not be reflected in the SRS resource set for CLI.
[0220] According to the proposed method, when an attacker terminal transmits an SRS, the transmission power may be different from the transmission power when the attacker terminal transmits the SRS and PUCCH / PUSCH in TDM mode. When TDM is used, the attacker terminal can transmit the SRS by reusing the transmission power of the PUCCH / PUSCH. When TDM is not used, the attacker terminal can transmit the SRS based on individual power control, the transmission power separately indicated by the base station, or the transmission power defined in the technical specification. When TDM is used, since the transmission power does not change while the attacker terminal transmits the PUCCH / PUSCH and SRS, the transmission power consistency can be maintained.
[0221] AGC (automatic gain control) effect
[0222] An attacker terminal can apply the transmission power indicated by the serving base station to transmit SRS. The serving base station can receive signals from multiple users (e.g., multiple terminals) and perform multi-carrier demodulation on the signals through a single DFT operation. If one user uses excessively high or low transmission power, the ADC or AGC of the serving base station may become saturated. Because large signals increase quantization noise, small signals may be ignored. The serving base station can minimize the occurrence of the above-described exception by maintaining the transmission power of the UL signal / channel to a certain level.
[0223] The victim terminal measuring UE-to-UE CLI cannot know the geographical distance between the attacker terminal and the victim terminal. If the attacker terminal allocates a large or small transmission power, the victim terminal cannot properly measure the CLI received from the attacker terminal. The victim terminal can measure the CLI using at least two symbols. The victim terminal can use the first of the two symbols to train the ADC or AGC.
[0224] According to the proposed method, SRS resources belonging to the set of SRS resources for the CLI associated with the SRS transmitted by the attacker terminal may include two or more consecutive symbols. The repetition of the SRS resources may be configured to be performed twice. The CMR or IMR of the victim terminal may be instructed (e.g., configured) to include two or more consecutive symbols.
[0225] FIG. 15 is a conceptual diagram illustrating embodiments of SRS resources for measuring UE-to-UE CLI.
[0226] Referring to FIG. 15, two or more antenna ports may be configured for an SRS resource. One antenna port may be associated with a Tx panel of an attacker terminal. When two or more antenna ports are configured, since each Tx panel may be associated with different SSBs or different TCI states, two or more SRS resources may be configured instead of one SRS resource for configuring a source RS for a separate qcl-typeD. In the embodiment of FIG. 15, the SRS resource may be interpreted as being configured with two symbols.
[0227] According to the proposed method, for a set of SRS resources for CLI, it is permissible for a single SRS resource to have different antenna ports and / or different TCI states. Although an SRS resource has a single antenna port, an attacker terminal can be instructed to perform SRS transmissions on the SRS resource using "the same time and frequency resources" and / or "the same sequence resources."
[0228] Although an SRS resource has a single symbol, it can be used as a duplicated SRS resource AGC symbol, and transmissions for the same SRS symbol can be repeated. The cyclic prefix (CP) of the SRS symbol can be set to a long length, and the SRS symbol can be extended by additional OFDM symbols and cyclic prefixes (e.g., an extended CP). In the embodiment of FIG. 15, the first symbol can be generated using the second symbol.
[0229] When SRS and PUCCH / PUSCH are TDM'd, the aforementioned constraint(s) may be unnecessary. According to the proposed method, the transmit power of the SRS may not be determined separately, and the transmit power of the PUSCH / PUCCH may be applied as is for SRS transmission. Retraining the AGC and / or ADC of the victim terminal may be unnecessary.
[0230] Reception settings
[0231] Rx beam reuse
[0232] The victim terminal can measure SRS-RSRP or CLI-RSSI to measure UE-to-UE CLI. The CSI reporting configuration of the victim terminal can include information indicating an Rx beam or TCI state assumed by the victim terminal. The CMR configuration or IMR configuration can indicate a set of non-zero power (NZP) CSI-RS resources or SSB resources (e.g., a set of SSB resources) to the victim terminal. The NZP CSI-RS resource information can include information indicating a DL TCI state, a joint TCI state, and / or a TCI state. The NZP CSI-RS resource information (e.g., NZP CSI-RS resource) can indicate an Rx beam assumed by the victim terminal. The Rx beam can mean an identifier of a DL signal / channel for reusing the assumed Rx beam for any one DL signal / channel received by the victim terminal. The victim terminal can derive (e.g., generate) a CSI report based on the TCI status associated with the DL signal / channel using the CMR and / or IMR. For measuring SRS-RSRP, the CMR may include the UL signal / channel, and a CMR including the UL signal / channel may not be supported by existing technical specifications.
[0233] The configuration information for measuring CLI-RSSI and / or reporting the measurement result of CLI-RSSI may include information on ZP RS for CMR and / or IMR. The victim terminal may identify ZP RS for CMR and / or IMR based on the configuration information. The victim terminal may report the measurement result of CLI-RSSI to the serving base station. The victim terminal may derive (e.g., determine) a TCI state for receiving ZP RS based on the CSI reporting configuration, the IMR configuration, and / or the CMR configuration. The TCI state indicated to the victim terminal may be applied to the IMR. Alternatively, the TCI state indicated to the victim terminal may be commonly applied to the CMR and the IMR.
[0234] The configuration information for measuring SRS-RSRP and / or reporting the measurement results of SRS-RSRP may include information on SRS resources associated with CMR and / or IMR. The configuration information may include information on the association between CMR and SRS resources and / or information on the association between IMR and SRS resources. The victim terminal may identify SRS resources associated with CMR and / or IMR based on the configuration information. The victim terminal may report the measurement results of SRS-RSRP to the serving base station. The victim terminal may derive (e.g., determine) a TCI state for receiving SRS based on a CSI reporting configuration, a CMR configuration, or an IMR configuration. The TCI state indicated to the victim terminal may be applied to the CMR. Alternatively, the TCI state indicated to the victim terminal may be commonly applied to the CMR and the IMR.
[0235] According to the proposed method, TCI states for measuring CLI-RSSI or SRS-RSRP can be derived based on DL / joint TCI states indicated to the victim terminal. The base station can indicate multiple TCI states to the victim terminal through signaling (e.g., RRC signaling) and can activate some TCI state(s) among the multiple TCI states using MAC CE. When MAC CE is used to activate or deactivate TCI states, the TCI state indicated by the MAC CE format can be selectively activated or deactivated. The terminal can operate based on the TCI state that is activated among the TCI states indicated by the new MAC CE format.
[0236] A base station can use the DCI format to indicate a TCI state to a victim terminal. In other words, the DCI format can include information indicating a TCI state. The TCI state applied to a CMR or IMR can be limited to the indicated TCI state.
[0237] The TCI state indicated by the non-scheduled DCI format or the scheduled DCI format may correspond to the Rx beam applied by the victim terminal to receive the DL signal / channel after the beam application time (BAT). The victim terminal may apply the above-described operation to the Rx beam for measuring CLI-RSSI or SRS-RSRP. In other words, the victim terminal may use the indicated TCI state to measure CLI-RSSI or SRS-RSRP after the BAT.
[0238] If the TCI state is not indicated in the DCI format, the Rx beam can be indicated by independent signaling for each DL signal / channel. In this case, the victim terminal can apply a TCI state that is independent of the TCI state of the PDSCH to obtain a CMR or IMR for measuring CLI-RSSI or SRS-RSRP. The victim terminal can obtain (e.g., determine) the TCI state of CLI-RSSI or SRS-RSRP by applying a TCI state indicated by a CSI reporting configuration or CMR configuration that configures CLI-RSSI or SRS-RSRP.
[0239] There may be instances where the CMR / IMR and PDSCH for CLI-RSSI or SRS-RSRP measurements overlap in time resources. In such cases, the victim UE may perform either one of the actions (e.g., CLI / SRS measurement or PDSCH reception). Alternatively, the victim UE may perform all actions.
[0240] The victim terminal can set priorities for actions. The victim terminal can receive the PDSCH and may not generate a CSI report. In other words, the priority of PDSCH reception may be higher than the priority of CSI reporting (e.g., measurement of CLI-RSSI or SRS-RSRP). If the CMR / IMR for measuring CLI-RSSI or SRS-RSRP and the SPS PDSCH overlap in time resources, the victim terminal may be instructed to perform only one action. If the priority of CSI reporting (e.g., measurement of CLI-RSSI or SRS-RSRP) is higher than the priority of receiving the SPS PDSCH, the victim terminal may measure CLI-RSSI or SRS-RSRP and may not receive the SPS PDSCH. Alternatively, the victim terminal may receive a portion of the SPS PDSCH. When PDSCH is scheduled using DCI format, the victim terminal may not report CLI-RSSI or SRS-RSRP to the base station based on the periodic / quasi-persistent CSI reporting configuration. If the reception operation of PDSCH scheduled using DCI format and the measurement operation of CLI-RSSI or SRS-RSRP using aperiodic CSI reporting configuration overlap in the same time resource or affected resource, it can be assumed that the victim terminal is not instructed to perform the two operations. The two operations may include the reception operation of PDSCH and the measurement operation of CLI-RSSI (or SRS-RSRP).
[0241] Alternatively, the victim terminal can perform both actions. In this case, the victim terminal can measure CLI-RSSI or SRS-RSRP using the TCI state for receiving the PDSCH. CLI-RSSI or SRS-RSRP can be measured using the indicated TCI state.
[0242] The indicated TCI state may not be indicated by the DCI format that triggers the measurement report of CLI-RSSI or SRS-RSRP. The indicated TCI state may be indicated by another DCI format. Even if the TCI state is indicated to the victim terminal and the BAT has not yet elapsed, a situation may arise where the victim terminal must measure CLI-RSSI or SRS-RSRP. The indicated TCI state may be applied after the BAT. In this case, the victim terminal may measure CLI-RSSI or SRS-RSRP by applying the default QCL assumption or the last indication of the TCI state. In other words, if the TCI state for SRS is not indicated (e.g., the indicated TCI state is invalid), the victim terminal may measure CLI-RSSI or SRS-RSRP by applying the default QCL assumption or the last indication of the TCI state. The last indication of the TCI state may mean an indication of the TCI state for the last PDSCH (e.g., the last PDSCH received by the victim terminal).
[0243] The victim terminal can receive the TCI state indicated for measuring CLI-RSSI or SRS-RSRP. The victim terminal can then receive a separate DCI format (or MAC CE, RRC signaling) and determine (e.g., determine) whether to update the TCI state based on the received separate DCI format (or MAC CE, RRC signaling).
[0244] Report Trigger
[0245] To determine the dynamic influence of the attacker terminal and the victim terminal, quasi-persistent CSI reporting or aperiodic CSI reporting may be more appropriate than periodic CSI reporting. The serving base station may consider a case where an aperiodic CSI report including SRS-RSRP is indicated to the victim terminal. The aperiodic CSI report may be indicated in a UL-related DCI format. The time resources for CMRs and / or IMRs may be derived from the CSI reporting configuration. The terminal may derive the slot where the CMR / IMR is located (e.g., the slot where the SRS is received) by applying an offset (e.g., aperiodicTriggeringOffset) to the slot where the DCI format (e.g., the DCI format that triggers the CSI report) is received. In order to apply SRS-RSRP, a method may be needed to reinterpret the slot (e.g., the slot where the CMR / IMR is located) as a slot where the attacker terminal transmits an SRS.
[0246] Figure 16 is a conceptual diagram illustrating examples of time relationships in which a victim terminal transmits aperiodic CSI reports using SRS.
[0247] Referring to FIG. 16, a victim terminal can receive a PDCCH (e.g., in DCI format) from a base station and transmit a PUSCH to the base station. The PDCCH can schedule PUSCH transmission. The offset between the PDCCH reception time and the PUSCH transmission time can be aperiodicTriggeringOffset. Within or after the offset, the victim terminal can receive an SRS from the attacker terminal. A CSI reference resource can be set within the offset.
[0248] There may be a certain offset between the slot in which the PDCCH (e.g., the DCI format that triggers the CSI report) is received and the slot in which the CMR / IMR is located (e.g., the slot in which the SRS is received and / or the slot in which the SRS is measured). To support the SRS transmission of the attacker terminal, the serving base station of the attacker terminal may schedule the SRS. The CMR / IMR may have a certain relationship with the CSI reference resource. The serving base station of the victim terminal may determine the slot in which to transmit the PDCCH based on the slot in which the SRS is received. A method in which the above-described restriction(s) do not occur at the serving base station of the victim terminal may be required.
[0249] According to the proposed method, a base station can transmit an offset for a time (e.g., a slot) at which an SRS is received to a terminal (e.g., an attacker terminal and / or a victim terminal) through signaling. The offset can be applied at least to aperiodic CSI reporting. The offset can be derived based on a CSI reporting configuration of a victim terminal. In other words, the CSI reporting configuration can include the offset. The CMR configuration of the CSI reporting configuration can include information indicating an offset for a time (e.g., a slot) at which an SRS of an attacker terminal is received. The offset can be the difference between the reception time of a DCI format indicating aperiodic CSI reporting and the reception time of the SRS. The offset can be the difference between a slot at which the DCI format is received and a slot at which the SRS is received. Considering periodic / quasi-persistent CSI reporting, the offset for SRS reception of an attacker terminal can be derived based on the CSI reporting configuration.
[0250] According to the proposed method, the SRS transmitted by the attacker terminal can be cell-specifically indicated. Alternatively, the SRS transmitted by the attacker terminal can be separately indicated to the victim terminal. The SRS (e.g., the reception time or reception slot of the SRS) can be derived regardless of the DCI format or offset that triggers aperiodic CSI reporting. The slot interval between the PDCCH and the SRS received by the victim terminal may not be interpreted as a single value, but rather as a minimum or maximum interval. The slot interval may be interpreted as an interval.
[0251] The victim UE may already be aware of the SRS time resource. The victim UE 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 UE can determine whether to transmit an updated CSI report by considering the processing time for receiving the SRS. If the time interval between the SRS and the PUCCH / PUSCH is too short, the victim UE may not necessarily measure SRS-RSRP because it cannot derive an appropriate CSI reference resource. If the victim UE's CPU is already heavily occupied, the victim UE may apply the priority defined in the technical specification for SRS-RSRP measurement. Therefore, if the victim UE's CPU is insufficient, SRS-RSRP may not be measured.
[0252] CMR / IMR
[0253] The victim terminal can measure at least one of SRS-RSRP or CLI-RSSI. The configuration information that triggers aperiodic CSI reporting may include information indicating whether the victim terminal measures SRS-RSRP and / or information indicating whether the victim terminal measures CLI-RSSI. The configuration information for CSI reporting may include information for deducing whether the value measured by the victim terminal is SRS-RSRP or CLI-RSSI.
[0254] If the attacker terminal receives scheduling information for PUSCH / PUCCH, the attacker terminal may not transmit SRS. In this case, the victim terminal may not be able to measure SRS-RSRP and may measure CLI-RSSI instead of SRS-RSRP.
[0255] The victim terminal can measure CLI-RSSI using PUSCH / PUCCH transmitted by the attacker terminal to the serving base station of the attacker terminal. CLI-RSSI can be measured in UL available PRB(s). Alternatively, CLI-RSSI can be measured in DL available PRB(s). CLI-RSSI can be a wideband report and can be measured in DL / UL available PRB(s). DL / UL available PRB(s) can refer to DL available PRB(s) and / or UL available PRB(s). Depending on the instruction of the victim terminal, CLI-RSSI can be a subband report and CLI-RSSI can be measured in some of DL / UL available PRBs.
[0256] When CLI-RSSI is measured on DL-available PRBs, the DL-available PRBs may be divided into two parts, and each of the two parts may belong to different DL subbands. In other words, the two parts of the DL-available PRBs may belong to two DL subbands. The CMR / IMR measured by the victim terminal may include discontinuous PRBs. The victim terminal may measure CLI-RSSI using the DL-available PRB(s).
[0257] CLI-RSSI can be measured on UL available PRB(s). The victim terminal can measure CLI-RSSI using UL available PRB(s). To measure CLI-RSSI, the victim terminal may not receive a configuration (e.g., indication) of a CMR / IMR that includes both DL available PRB(s) and UL available PRB(s).
[0258] For SRS-RSRP measurement, the victim terminal can use the SRS-cli associated with the CMR. The CMR can be associated with an SRS resource set, and the SRS resource set for beam management can be reused. The SRS can belong to an SRS resource set (e.g., an SRS resource set for beam management). For CLI-RSSI measurement, the victim terminal can use the resources associated with the IMR. The CSI reporting configuration indicated to the victim terminal can include both CMR and IMR. For CSI reporting triggered to the victim terminal, either the CMR or IMR configuration can be applied.
[0259] FIG. 17 is a conceptual diagram illustrating extended embodiments of CSI reporting settings for measuring UE-to-UE-CLI of a victim terminal.
[0260] Referring to FIG. 17, in order for the CSI report to include the measurement value of UE-to-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 may receive a configuration (e.g., an indication) of one of the CMR (e.g., SRS resource, SRS resource set) or the IMR (e.g., CLI resource, CLI resource set) from the base station, and may generate a CSI report based on one configuration. For the measurement of CLI-RSSI, the victim terminal may measure RSSI in the CLI measurement resource set or the CLI measurement resource. The CLI measurement resource set may mean a CLI resource set, and the CLI measurement resource may mean a CLI resource.
[0261] To measure UE-to-UE CLI, CMR and IMR may not be configured simultaneously. The victim terminal may only receive CMR configurations to measure SRS-RSRP. The victim terminal may only receive IMR configurations to measure CLI-RSSI. Alternatively, the victim terminal may receive CMR configurations to measure CLI-RSSI.
[0262] IMR
[0263] The victim terminal can receive a CSI reporting configuration containing IMR information from the base station to measure CLI-RSSI. Even if the CSI reporting configuration includes both CMR and IMR information, the victim terminal may not use the CMR information and instead generate a CSI report based on the IMR information. The victim terminal can interpret the CMR for CLI-RSSI measurement based on the CSI reporting configuration containing CMR information.
[0264] FIG. 18a and FIG. 18b are conceptual diagrams illustrating extended embodiments of a CSI reporting configuration for measuring UE-to-UE-CLI of a victim terminal.
[0265] Referring to FIGS. 18A and 18B , a CSI reporting configuration may include a CLI measurement resource or a set of CLI measurement resources. An IMR may include a set of NZP DL / UL RS resources or NZP DL / UL RS resources. An IMR may include PRBs in symbol units. In this case, the IMR may include consecutive PRBs, and the consecutive PRBs may be configured to include only DL-available PRBs or UL-available PRBs. The location of the first PRB and the number of PRBs may be indicated to the terminal. The location of the first PRB and the number of PRBs may be derived based on a single index. The location of the first PRB and the number of PRBs may indicate a frequency resource (e.g., a frequency band) of the IMR.
[0266] A base station can transmit information indicating a frequency band (e.g., frequency resource) in which CLI measurement is performed to a terminal (e.g., an attacker terminal and / or a victim terminal) via signaling. The information indicating a frequency band in which CLI measurement is performed can include the position of a first PRB of the frequency band and the number of PRBs constituting the frequency band. The position of the first PRB of the frequency band and the number of PRBs constituting the frequency band can be expressed based on a single index. The first PRB can be a PRB having a lowest index or a PRB having a highest index among the PRBs constituting the frequency band. The position of the first PRB can be expressed by a PRB index.
[0267] A terminal can receive information indicating a frequency band (e.g., frequency resource) in which CLI measurements are performed via signaling from a base station. The terminal can determine (e.g., confirm) the frequency band in which CLI measurements are performed based on the position of the first PRB of the frequency band and the number of PRBs constituting the frequency band. An attacker terminal can transmit an SRS (e.g., an SRS for CLI measurements) in the frequency band indicated by the base station. A victim terminal can perform a measurement operation (e.g., a CLI measurement operation) for the SRS in the frequency band indicated by the base station.
[0268] PDSCH handling
[0269] TCI state switching
[0270] A portion of the DL signal / channel received by the victim UE may be designated to be used for CLI measurement. The scheduled DL signal / channel may overlap with the time and frequency resources used for CLI-RSSI / SRS-RSRP. Rather than the victim UE receiving the PDSCH (e.g., PDSCH RE) in a PRB and measuring CLI-RSSI / SRS-RSRP, it may be preferable that the time and / or frequency resources be orthogonally allocated to the victim UE. CLI-RSSI may be measured in DL-available PRB(s). SRS-RSRP may be measured in UL-available PRB(s). Both CLI-RSSI and SRS-RSRP may be measured in UL-available PRB(s). CLI-RSSI may be measured in DL-available PRB(s) and UL-available PRB(s).
[0271] The procedure for reporting the measurement values of CLI-RSSI and / or SRS-RSRP may be performed aperiodically. The serving base station may indicate the resources of the DL signal / channel and the CMR / IMR to the victim terminal so that the resources of the DL signal / channel and the CMR / IMR do not overlap. The victim terminal may assume that the resources of the DL signal / channel and the CMR / IMR do not overlap. The victim terminal may transmit an UL signal / channel (e.g., PUCCH) to report a HARQ-ACK for the DL signal / channel. The victim terminal may assume that the resources of the UL signal / channel and the CMR / IMR do not overlap.
[0272] The base station can signal the priority of the DL signal / channel and the priority of the UL signal / channel to the victim terminal. The victim terminal can select one of the signals / channels based on the priority. The priority can be defined in the technical specifications supporting the SBFD operation. The victim terminal may not transmit the UL signal / channel and may measure SRS-RSRP in the UL available PRBs. The victim terminal can operate based on the UL priority and / or DL priority defined in the technical specifications supporting the SBFD operation.
[0273] When dynamically scheduled signals / channels and statically scheduled signals / channels are allocated from overlapping resources, the victim terminal may select the dynamically scheduled signal / channel among the signals / channels. When the PDSCH is scheduled by the DCI format received by the victim terminal, the victim terminal may not measure some or all of the CLI-RSSI / SRS-RSRP. When the DCI format received by the victim terminal indicates measurement and / or reporting of CLI-RSSI / SRS-RSRP, the victim terminal may not receive some or all of the PDSCH. The PDSCH may be an SPS PDSCH. The DCI format may not be scrambled by C-RNTI or MCS-C-RNTI.
[0274] Measurement of CLI-RSSI or SRS-RSRP can be performed in DL-available PRB(s). In this case, the DL priority and / or UL priority derived from the SBFD operation may not be applied as is. The victim terminal can perform a dynamically indicated operation. The victim terminal can assume other inconsistent operations as operations that are not dynamically indicated. The victim terminal can receive a DCI format that schedules the PDSCH of the victim terminal and a DCI format that indicates measurement and / or reporting of CLI-RSSI / SRS-RSRP. The CMR / IMR and PDSCH of CLI-RSSI / SRS-RSRP can be allocated to non-overlapping resources. The PUCCH associated with the CMR / IMR and PDSCH of CLI-RSSI / SRS-RSRP can be allocated to non-overlapping resources. According to another proposed method, the victim terminal can receive a part of the PDSCH.
[0275] FIG. 19 is a conceptual diagram illustrating embodiments in which a victim terminal that has received scheduling information of a DL signal / channel measures UE-to-UE CLI.
[0276] Referring to FIG. 19, symbols allocated for PDSCH may be distinguished as w00, w10, w20, w30, and / or w40. In CMR / IMR (w00), symbol(s) before the CMR / IMR (w00), and / or symbol(s) after the CMR / IMR (w00), the victim terminal may not receive PDSCH to measure CLI-RSSI or SRS-RSRP. w20 may be symbols located before CMR / IMR (w00), and w20 may include Δ1 (≥0) symbols. w30 may be symbols located after CMR / IMR (w00), and w30 may include Δ2 (≥0) symbols. The values of Δ1 and Δ2 may be defined as numbers including 0. The values of Δ1 and Δ2 may be defined as numbers greater than or equal to 1. The values of Δ1 and Δ2 can be set based on the subcarrier spacing (SCS) of the BWP.
[0277] If the TCI state for receiving PDSCH and the TCI state applied to CMR / IMR are different, the victim terminal may not receive PDSCH in w20 and / or w30. The TCI state of PDSCH may be indicated by a scheduling DCI format or an activation DCI format. The TCI state of CMR / IMR may be indicated by a CSI triggering UL related format. Alternatively, the TCI state of CMR / IMR may be indicated by an activation DCI format or MAC CE that triggers SP-CSI reporting.
[0278] If the TCI state for receiving a PDSCH is the same as the TCI state applied to a CMR / IMR, the victim terminal can perform reception operations for the PDSCH at w20 and / or w30. Although the TCI state of the PDSCH is indicated differently from the TCI state of the CMR / IMR, the victim terminal can apply the common TCI state in the reception operation.
[0279] The TCI state of the PDSCH may be prioritized, and the TCI state of the PDSCH may be applied instead of the TCI state of the CMR / IMR for measurements on the CMR / IMR. The victim terminal may derive the TCI state assumed for measuring CLI-RSSI or SRS-RSRP based on the scheduling information of the PDSCH. The values of Δ1 and / or Δ2 may be interpreted as 0.
[0280] The TCI state of the CMR / IMR and the TCI state of the PDSCH can be independently indicated to the UE. Even when the TCI state of the CMR / IMR and the TCI state of the PDSCH are independently indicated, a situation may arise where the TCI state of the CMR / IMR and the TCI state of the PDSCH have the same value. The victim UE can know in advance that the TCI state of the CMR / IMR and the TCI state of the PDSCH are the same. The serving base station can anticipate that the TCI state of the CMR / IMR and the TCI state of the PDSCH are the same. In this case, a separate time may not be necessary, and the values of Δ1 and / or Δ2 may be interpreted as 0.
[0281] Even if the victim terminal knows in advance that the TCI states of the CMR / IMR and the PDSCH are identical, separate times may be consumed. The scheduling information of different signals / channels may not affect each other, and the victim terminal can independently process the scheduling information of different signals / channels. The reception processing of the PDSCH and the measurement processing of CLI-RSSI / SRS-RSRP may be performed independently, and the TCI states may be identical as a result. The identical TCI states may be a coincidence of the independent processing. In this case, the values of Δ1 and / or Δ2 may be interpreted as values greater than 1. The victim terminal may not maintain consistency in PDSCH reception at w20 and w30 even though the TCI state is maintained.
[0282] If the victim terminal maintains the TCI state, consistency in PDSCH reception can be maintained at w20 and w30, depending on the victim terminal's implementation. The victim terminal can assume the same antenna port for PDSCH reception at w20 and w30. The DM-RS of the PDSCH may not be included in w20 and / or CMR / IMR (w00). The victim terminal can apply the channel estimate value derived for demodulation and / or decoding for w10 and / or w20 to w30 and / or w40.
[0283] According to the proposed method, the victim terminal can assume the same antenna port for PDSCH reception at w10 and w40 based on RRC signaling. The victim terminal can change the TCI state of the CMR / IMR. Alternatively, the victim terminal may not change the TCI state of the CMR / IMR.
[0284] If gap symbols are unnecessary for changing the TCI state, the victim terminal may assume the same antenna port for w20 or w30. Even if gap symbols are required for changing the TCI state, the victim terminal may assume the same antenna port for w20 or w30.
[0285] RE mapping
[0286] The PDSCH scheduled to the victim terminal may not be received at w00. The PDSCH may also not be received at w20 and / or w30. The victim terminal must be able to know how to map the coded bits in some symbols of the PDSCH (e.g., w00 and / or gaps (e.g., w20 and / or w30)).
[0287] The bits coded in w00 and the gap may not be mapped. In the rate matching procedure, the coded bits may be mapped in the area excluding w00 and / or the gap (e.g., w20 and / or w30). When deriving the amount of scheduled resources to derive the transport block (TB) size, the victim terminal may regard w00 and the gap as resources (e.g., scheduled resources). The victim terminal may derive the TB size based on resources other than w00 and the gap.
[0288] It can be assumed that the coded bits are mapped to w00 and the gap. The above assumption can be interpreted as a puncturing procedure. The victim terminal can derive the TB size based on the area containing w00 and the gap.
[0289] In a region (e.g., w10) before a gap (e.g., w00), a PDSCH can be received by the victim terminal. In w00, in a region before w00 (e.g., w20), and / or in a region after w00 (e.g., w30, w40), the victim terminal can maintain the same antenna port. Alternatively, in w00, in a region before w00 (e.g., w20), and / or in a region after w00 (e.g., w30, w40), the victim terminal may not maintain the same antenna port.
[0290] According to the proposed method, the victim terminal may not receive the PDSCH in the area w00 and after w00 (e.g., w30 and / or w40). The victim terminal may perform demodulation and decoding for the PDSCH mapped in w10 and / or w20. A case where the serving base station schedules repeated reception (e.g., repeated transmission) of the PDSCH may be considered. The PDSCH instance (or PDSCH repetition) may be scheduled, and the PDSCH instance (or PDSCH repetition) may overlap with the CMR / IMR in w00. The victim terminal may not receive the PDSCH in the PDSCH instance (e.g., w00).
[0291] Time lag between measurements and reports
[0292] A method for deriving RSRP using the SRS received by the victim terminal may be considered. The victim terminal may apply CSI reference resources before reporting the SRS-RSRP to the serving base station. When the victim terminal transmits a PUSCH or PUCCH in the first slot n, the victim terminal may receive an SRS from the attacker terminal in the second slot m. Although the SRS is received in the second slot m, the RSRP for the SRS received in the second slot m may be converted into an SRS-RSRP derived in the third slot based on the CSI reference resource definition.
[0293] Even if the victim terminal derives SRS-RSRP, separate processing for applying CSI reference resources may not be specified. It may be permissible for the victim terminal to transmit a PUSCH or PUCCH in the first slot based on the SRS-RSRP measured in the second slot.
[0294] The SRS-RSRP received by the serving base station in the first slot may differ from the SRS-RSRP estimated to have been measured by the victim terminal in the third slot. It may be desirable for the serving base station to schedule the attacker terminal and the victim terminal so that the difference between the SRS-RSRP in the first slot and the SRS-RSRP in the third slot is not significant.
[0295] The base station can transmit a CSI report configuration containing separate information to the victim terminal. Based on the above-described operation, the instantaneous value of SRS-RSRP can be indirectly determined. The victim terminal can quantize the instantaneous value of SRS-RSRP and transmit a CSI report containing the quantized value to the base station. To support the above-described operation, a separate threshold can be indicated to the terminal.
[0296] The victim terminal can derive an RSRP for a specific SRS resource and compare the derived RSRP with a threshold. If the victim terminal derives 1 bit of information, one value of the information may indicate that the SRS-RSRP is less than the threshold, and another value of the information may indicate that the SRS-RSRP is greater than the threshold.
[0297] When the victim terminal is instructed to derive information from multiple bits, the victim terminal can derive an interval within which the SRS-RSRP value falls for multiple thresholds. The range within which the SRS-RSRP value falls can be inferred based on the interval index.
[0298] There may be differences in the derivation time of SRS-RSRP in the above information. It cannot be ruled out that the victim terminal derives SRS-RSRP in the first slot. Derivation of the above information (e.g., SRS-RSRP) in the third slot may be enforced.
[0299] According to the proposed method, if SRS-RSRP satisfies a certain condition, the victim terminal can transmit a CSI report including SRS-RSRP. The serving base station may be interested in a sufficiently large SRS-RSRP. The victim terminal can measure SRS-RSRP for all SRS resources belonging to a CMR set or an SRS resource set corresponding to the CMR set, and report some SRS-RSRP to the base station. The serving cell (e.g., the serving base station) can utilize some SRS-RSRP to identify attacker terminals that cause 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 not report information about other SRS resources to the base station. Or, even if the victim terminal reports information about other SRS resources, the victim terminal may not update information about other SRS resources. Because attacker terminals generate large CLIs, it may be desirable for the serving base station to implement additional work (e.g., configuration, scheduling, or beam management) to avoid large CLIs.
[0300] The victim terminal can generate a bitmap and report the bitmap to a base station (e.g., a 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 an SRS resource set associated with a CMR set configuration of a CSI report configuration. The SRS resources can include deactivated SRS resources. The victim terminal can generate a CSI report that includes not only the bitmap but also the value of SRS-RSRP and the identifier (e.g., index) of the SRS resource associated with the SRS-RSRP.
[0301] The SRS-RSRP for one SRS resource can be expressed as an absolute value, and the SRS-RSRPs for the remaining SRS resources can be expressed as differential values. The SRS-RSRP expressed as an absolute value can be the largest SRS-RSRP.
[0302] A CSI report may include at least one of a bitmap, a list of identifiers (e.g., indices) of SRS resources, or a list of SRS-RSRPs. Alternatively, the CSI report may include at least one of a list of identifiers (e.g., indices) of SRS resources or a list of SRS-RSRPs. An identifier of an SRS resource may indicate an SRS resource expressed as an absolute value, and identifiers of other SRS resources may not be included in the CSI report. In this case, SRS-RSRPs may be arranged in the order of identifiers of SRS resources expressed as differential values within the CSI report.
[0303] When a victim terminal generates a CSI report that includes measurement results for some SRS resources, the size of the UCI (e.g., CSI report) generated by the victim terminal may be variable. For a CMR set including four SRS resources, the victim terminal may quantize the SRS-RSRP into 1 bit using a threshold. The length (e.g., size) of the bitmap may be 4 bits. The absolute value of the SRS-RSRP may be expressed in 7 bits, and the difference value of the SRS-RSRP may be expressed in 4 bits. The identifier of the SRS resource may be expressed in 2 bits (e.g., log2(the number of SRS resources)).
[0304] When SRS-RSRP measurement is performed and the victim terminal selects two SRS resources, the length of the bitmap may still be 4 bits. SRS-RSRP may be expressed in 11 (= 7 + 4) bits. The identifier of the SRS resource corresponding to the absolute value and the identifier of the SRS resource corresponding to the differential value may be expressed. In the above-described embodiment, the size of the UCI may be 19 (= 4 + 7 + 4 + 2 + 2) bits.
[0305] When a victim terminal generates a CSI report containing four SRS-RSRPs, the UCI may have a fixed size. The UCI may include a bitmap (4 bits), an SRS-RSRP (7 bits + 4 bits + 4 bits + 4 bits), and an SRS resource identifier (2 bits + 2 bits + 2 bits + 2 bits). In the above embodiment, the size of the UCI may be 31 (= 4 + 7 + 4 + 4 + 2 + 2 + 2 + 2) bits.
[0306] According to the proposed method, a serving base station can configure a CSI report with a size of 31 bits 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 known bits. Alternatively, the victim terminal can generate a CSI report in a conventional format. The victim terminal can place information in a position related to a required SRS resource within the UCI (e.g., a CSI report). The victim terminal can place an arbitrary value in a position related to another SRS resource within the UCI (e.g., a CSI report). The victim terminal may not have an obligation to update a conventional SRS-RSRP. The serving base station can verify (e.g., obtain) an SRS-RSRP at a required position within the UCI (e.g., a CSI report) received from the victim terminal. The CPU of the victim terminal that generates the bitmap may not be separately occupied.
[0307] UE initiated reporting
[0308] The victim terminal can receive UE-to-UE CLI reporting settings from the serving base station. The victim terminal can receive "aperiodic CSI reporting, periodic CSI reporting, and / or semi-persistent CSI reporting" as well as specific condition settings (e.g., instructions) from the serving base station. The victim terminal can transmit CSI reports to the serving base station only when specific conditions occur.
[0309] The proposed condition (e.g., a specific condition) may be "at least one SRS-RSRP maintains a threshold for a certain period of time or a certain number of times." The victim terminal may receive from the serving base station the setting of a time window for determining whether a specific condition occurs. The victim terminal may determine whether a specific condition occurs within the time window.
[0310] The operations of the method according to the embodiments of the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.
[0311] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by the computer using an interpreter, etc.
[0312] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.
[0313] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.
[0314] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.
Claims
1. As a method of the first UE (user equipment), A step of receiving SRS (sounding reference signal) setting information from a base station; A step of determining one or more valid SRS symbols within the SRS resource based on a symbol type for the SRS resource indicated by the SRS configuration information; and A step of transmitting an SRS to the base station using one or more valid SRS symbols, The above symbol type is a SBFD (subband full duplex) symbol or an N (non)-SBFD symbol. Method of the first UE.
2. In claim 1, Based on the symbol type indicated by the SBFD symbol, one or more SBFD symbols within the SRS resource are determined to be one or more valid SRS symbols. Method of the first UE.
3. In claim 1, Based on the symbol type indicated by the N-SBFD symbol, one or more N-SBFD symbols in the SRS resource are determined as the one or more valid SRS symbols. Method of the first UE.
4. In claim 1, Transmission of the SRS in an invalid SRS symbol within the SRS resource indicated by the SRS configuration information is dropped on a symbol-by-symbol basis. Method of the first UE.
5. In claim 1, The above SRS resource is set to be associated with a CMR (channel measurement resource) set or an IMR (interference measurement resource) set, and SRS-RSRP (reference signal received power) measurement or CLI (cross link interference)-RSSI (received signal strength indicator) measurement for the SRS resource is performed. Method of the first UE.
6. In claim 1, The transmission time of the above SRS is determined by considering TA (timing advance). Method of the first UE.
7. In claim 1, The above SRS configuration information includes information on an SRS resource set, and the SRS resource set indicated by the SRS configuration information includes information indicating the symbol type. Method of the first UE.
8. In claim 1, The above symbol type is commonly applied to one or more SRS resources belonging to the above SRS resource set. Method of the first UE.
9. As a method of the second UE (user equipment), A step of receiving SRS (sounding reference signal) setting information from a base station; A step of determining one or more valid SRS symbols within the SRS resource based on a symbol type for the SRS resource indicated by the SRS configuration information; and A step of performing a measurement operation on an SRS transmitted by a first UE in one or more of the valid SRS symbols, The above symbol type is a SBFD (subband full duplex) symbol or an N (non)-SBFD symbol. Method of the second UE.
10. In claim 9, Based on the symbol type indicated by the SBFD symbol, one or more SBFD symbols within the SRS resource are determined to be one or more valid SRS symbols. Method of the second UE.
11. In claim 9, Based on the symbol type indicated by the N-SBFD symbol, one or more N-SBFD symbols in the SRS resource are determined as the one or more valid SRS symbols. Method of the second UE.
12. In claim 9, The above SRS resource is set to be associated with a CMR (channel measurement resource) set or an IMR (interference measurement resource) set, and SRS-RSRP (reference signal received power) measurement or CLI (cross link interference)-RSSI (received signal strength indicator) measurement for the SRS resource is performed. Method of the second UE.
13. In claim 9, The measurement time for the above SRS is determined by considering TA (timing advance). Method of the second UE.
14. In claim 9, A step for determining a priority for a CSI (channel state information) report including SRS-RSRP or CLI-RSSI, which is a measurement result for the above SRS; and Further comprising a step of transmitting the CSI report to the base station based on the above priority, The priority for the CSI report including the SRS-RSRP or the CLI-RSSI is determined based on L1 (layer1)-RSRP. Method of the second UE.
15. In claim 9, The above measurement operation for the above SRS is performed based on the TCI state indicated for the SSB (synchronization signal block) or the DL (downlink) RS (reference signal). Method of the second UE.
16. In claim 9, The above measurement operation for the above SRS is performed based on the TCI status received by the second UE. Method of the second UE.
17. In claim 9, Further comprising a step of receiving DCI (downlink control information) that triggers CSI reporting from the base station, The above measurement operation for the above SRS is performed in a slot after an offset from the slot in which the DCI is received, wherein the offset is indicated by the base station. Method of the second UE.
18. In claim 9, It further includes a step of receiving information on a frequency band for measuring CLI-RSSI from the base station, Information of the frequency band includes the location of the first PRB (physical resource block) 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. Method of the second UE.
19. In claim 9, The above SRS configuration information includes information of an SRS resource set, and the SRS resource set includes information indicating the symbol type. Method of the second UE.
20. In claim 9, The above symbol type is commonly applied to SRS resources belonging to the above SRS resource set. Method of the second UE.
Citation Information
Patent Citations
Upper structure of bridge with precast concrete decks
KR1020250146551A
Method and apparatus for CLI reporting
US20220014954A1
Cross-link interference (CLI) radio resource management (RRM) measurement
US20220159662A1
KR20240072997A