Systems and methods for managing uplink transmissions and cross-link interference measurements
Patent Information
- Application Number
- CN202380028228.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-31
- Filing Date
- 2023-01-27
- Publication Date
- 2024-11-12
AI Technical Summary
当设备正在使用全双工通信模式(诸如子带全双工模式或带内全双工模式)时,干扰可能更有可能存在
Smart Images

Figure CN118947076A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to and the benefit of U.S. Patent Application No. 17 / 710,402, filed on March 31, 2022, the disclosure of which is incorporated herein by reference in its entirety as if fully set forth below and for all applicable purposes. Background Art
[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include several base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may be otherwise referred to as user equipment (UE).
[0004] To meet the growing demand for extended mobile broadband connections, wireless communication technology is evolving from long term evolution (LTE) technology to next generation new radio (NR) technology, which may be referred to as fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate over a wide range of frequency bands, such as from low frequency bands below about 1 gigahertz (GHz) and mid frequency bands from about 1 GHz to about 6 GHz, to high frequency bands, such as mmWave bands.
[0005] Wireless communication devices may experience one or more types of interference from devices in their own cells and / or devices associated with other cells. When the device is using a full-duplex communication mode (such as a sub-band full-duplex mode or an in-band full-duplex mode), interference may be more likely to exist. In some aspects, the sub-band full-duplex mode may be referred to as a half-duplex mode. On the other hand, the in-band full-duplex mode may be referred to as a same-band full-duplex (SBFD) mode. For example, a wireless communication device operating in the SBFD mode may experience cross-link interference (CLI) from other wireless communication devices based on signal energy leakage in the SBFD frame. For example, CLI may refer to interference from one UE to another nearby UE. When the interference source UE continues to send to the base station, if the UL symbol of the interference source conflicts with at least one DL symbol of the interfered object UE, the interfered object UE may receive the transmission as interference in its DL symbol. CLI may occur between two UEs in the same cell or in different cells. Summary of the invention
[0006] The following summarizes some aspects of the disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all expected features of the disclosure, and is neither intended to identify key or important elements of all aspects of the disclosure, nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a summarized form as a prelude to further specific embodiments presented later.
[0007] According to one aspect of the present disclosure, a wireless communication method performed by a user equipment (UE) includes: receiving a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, sending a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes the CLI-SRS.
[0008] According to another aspect of the present disclosure, a user equipment (UE) includes: a processor; and a transceiver communicating with the processor, wherein the UE is configured to: receive a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, send a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes the CLI-SRS.
[0009] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions executable by a processor of a user equipment (UE) to enable the UE to perform the following operations: receive a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, send a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes the CLI-SRS.
[0010] According to another aspect of the present disclosure, a UE includes: a component for receiving a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and a component for sending a first communication in a first time period based on the CLI-SRS timing and the CLI-SRS priority configuration, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes the CLI-SRS.
[0011] After studying the following description of the specific exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, other aspects, features and embodiments of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain embodiments and the accompanying drawings, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments of the present disclosure discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1A A wireless communication network according to some aspects of the present disclosure is illustrated.
[0013] Figure 1B is a diagram illustrating an example decomposed BS architecture according to some aspects of the present disclosure.
[0014] Figure 2 A sidelink communication network according to some aspects of the present disclosure is illustrated.
[0015] Figure 3 A radio frame structure according to some aspects of the present disclosure is illustrated.
[0016] Figure 4A A full-duplex communication configuration according to some aspects of the present disclosure is illustrated.
[0017] Figure 4B A full-duplex communication configuration according to some aspects of the present disclosure is illustrated.
[0018] Figure 4C A full-duplex communication configuration according to some aspects of the present disclosure is illustrated.
[0019] Figure 5 A sub-band full-duplex (SBFD) communication configuration according to some aspects of the present disclosure is illustrated.
[0020] Figure 6 is an illustration of an example cross-link interference scenario according to some embodiments.
[0021] Figure 7 is a signaling diagram of a wireless communication method based on a cross-link interference (CLI) sounding reference signal (SRS) prioritization configuration according to some aspects of the present disclosure.
[0022] Figure 8is a signaling diagram of a wireless communication method based on CLI-SRS power allocation priority configuration according to some aspects of the present disclosure.
[0023] Fig. 9 is a signaling diagram of a wireless communication method based on CLI-SRS prioritization configuration according to some aspects of the present disclosure.
[0024] Fig.10 is a signaling diagram of a wireless communication method based on CLI-SRS power allocation priority configuration according to some aspects of the present disclosure.
[0025] Fig.11 is a timing diagram of UL communication conflicts according to some aspects of the present disclosure.
[0026] Fig.12 is a timing diagram of UL communication conflicts according to some aspects of the present disclosure.
[0027] Fig.13 is a timing diagram of UL communication conflicts according to some aspects of the present disclosure.
[0028] Fig.14 is a timing diagram of UL and SL communication conflicts according to some aspects of the present disclosure.
[0029] Fig.15 is a timing diagram of UL communication conflicts according to some aspects of the present disclosure.
[0030] Fig.16 is a timing diagram of UL and SL communication conflicts on different CCs according to some aspects of the present disclosure.
[0031] Fig.17 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.
[0032] Fig.18 is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.
[0033] Fig.19 is a flow chart of a method of wireless communication according to some aspects of the present disclosure.
[0034] Fig. 20 is a flow chart of a method of wireless communication according to some aspects of the present disclosure. DETAILED DESCRIPTION
[0035] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. In order to provide a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some examples, in order to avoid obscuring such concepts, known structures and components are shown in block diagram form.
[0036] The present disclosure as a whole relates to wireless communication systems, which are also referred to as wireless communication networks. In various specific implementations, various techniques and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.
[0037] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups with the goal of defining globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving UMTS mobile phone standards. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR and beyond wireless technologies, where access to wireless spectrum is shared between networks using a range of new and different radio access technologies or radio air interfaces.
[0038] Specifically, 5G networks consider various deployments, various spectrums, and various services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to expand to provide coverage for the following: (1) Ultra-high density (e.g., about 1M nodes / km 2 (1) provide a massive Internet of Things (IoT) with ultra-low complexity (e.g., on the order of tens of bits / second), ultra-low energy consumption (e.g., on the order of 10+ years battery life), and deep coverage capable of reaching challenging locations; (2) provide coverage including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., on the order of 99.9999% reliability), ultra-low latency (e.g., on the order of 1 millisecond), and users with extensive mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including extremely high capacity (e.g., on the order of 10Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).
[0039] 5G NR can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, subcarrier spacing (SCS) may occur, for example, at 15kHz on bandwidths (BW) such as 5MHz, 10MHz, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, subcarrier spacing may occur at 30kHz on 80 / 100MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over 160 MHz BW. Finally, for various deployments transmitting with the mmWave component at 28 GHz TDD, subcarrier spacing may occur at 120 kHz over 500 MHz BW.
[0040] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long TTIs and short TTIs allows transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink (UL) and downlink (DL) to meet current business needs.
[0041] The various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, such devices can be implemented, or such methods can be practiced, using other structures, functionality, or structures and functionality other than or different from one or more aspects of the aspects set forth herein. For example, the method can be implemented as a part of a system, device, device, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.
[0042] As described above, a wireless communication device operating in SBFD mode may experience cross-link interference (CLI) from other wireless communication devices based on signal energy leakage in an SBFD frame. To illustrate CLI, a wireless communication device (including a UE) may be configured with CLI measurement resources to measure potential CLI and send a CLI report to a base station. A UE measuring or experiencing CLI may be referred to as an interfered UE. According to one aspect of the present disclosure, one or more UEs in a network may be configured with transmission resources to send one or more reference signals to facilitate measurement of CLI by other UEs during a CLI measurement window. A UE that causes CLI interference or sends a CLI reference signal may be referred to as an interference source UE. In some aspects, an interference source UE may be configured to send one or more SRS communications to facilitate CLI measurements. For the purposes of the present disclosure, these SRS signals may be referred to as CLI-SRS.
[0043] In some aspects, the SRS for CLI may have a format and structure similar to or identical to a non-CLI SRS. In other aspects, the CLI-SRS may have a structure or format that is different from a non-CLI SRS in at least one aspect. On the other hand, the CLI-SRS may be configured at the cell level so that the CLI-SRS resources may be aligned for different UEs communicating in the network. In some aspects, the cell configuration, which may also be referred to as a component carrier (CC) configuration and / or a bandwidth part (BWP) configuration, may indicate one or more parameters for the CLI-SRS. In addition, the interfered UE may be configured with a cell-level CLI measurement resource. For example, one or more UEs operating in a cell using full-duplex mode may be configured with a zero-power (ZP) CLI-SRS measurement resource. Therefore, in some aspects, both the CLI-SRS transmission resource and the CLI-SRS measurement resource may be a cell-level resource based on or associated with one or more cell configurations.
[0044] The CLI-SRS resources may include periodic, semi-persistent, and / or aperiodic resources. For example, the CLI-SRS resources may be periodic and configured to be transmitted without receiving an activation. In other aspects, the CLI-SRS resources may be semi-persistent so that the periodicity and resources are known and triggered by the activation. In some aspects, receiving the activation may include receiving a medium access control control element (MAC-CE) indicating the activation of the CLI-SRS resources. In another aspect, receiving the activation may include receiving a DCI activating one or more aperiodic CLI-SRS resources.
[0045] Similarly as described above with respect to CLI measurements, there may be a conflict or scheduling conflict between CLI-SRS and UL transmissions. For example, the UE may be configured with a periodic SRS that conflicts with at least one opportunity of a semi-persistent or aperiodic CLI-SRS. In some aspects, it may not be desirable for the UE to handle conflicts between at least some UL transmissions and / or SL transmissions (e.g., PUCCH, PSFCH) and CLI-SRS.
[0046] The present disclosure describes a scheme and mechanism for handling and / or avoiding scheduling conflicts between CLI-SRS and at least one other UL and / or SL communication scheduled for transmission. Other aspects of the present disclosure describe power allocation rules and configurations for transmitting CLI-SRS concurrently with one or more other UL / SL communications on different carriers in a carrier aggregation (CA) mode. Various aspects of the present disclosure are applicable to Uu communication and SL communication. Uu communication may include communication on a Uu interface between a UE and a radio access network (RAN). For example, Uu communication may include communication between a UE and a network device or entity. In some aspects, Uu communication may be performed between a UE and a BS in a wireless communication network. The Uu interface may be referred to as an air interface. For example, Uu communication includes UL and DL communications between one or more UEs and one or more BSs. In some aspects, Uu communication may be communicated on 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 broadcast channel (PBCH) and / or any other UE-BS communication channel. Uu communications may include control information, data and / or reference signals. SL communications may include communications between multiple UEs. SL communications may communicate directly with other UEs without routing through a RAN or network entity. In some aspects, the SL interface may be referred to as a PC5 interface. SL communications may communicate on a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink feedback channel (PSFCH) and / or any other SL communication channel.
[0047] The CLI-SRS priority configuration can be used to resolve conflicts (collision / conflict) between multiple Uu communications, between multiple SL communications, and / or between Uu and SL communications. In addition, the CLI-SRS power allocation priority configuration can be used to allocate or distribute power between multiple Uu communications, between multiple SL communications, and / or between Uu and SL communications.
[0048] The methods, mechanisms and other aspects of the present disclosure provide several advantages. For example, the CLI-SRS prioritization scheme described herein provides communication of CLI-SRS signals to facilitate CLI measurements in the event of scheduling conflicts for lower priority signals. In this regard, it may be necessary or more efficient to send CLI-SRS instead of conflicting UL / SL communications, but not in other UL / SL communications. In some instances, another type of communication may take precedence over CLI-SRS. In addition, by configuring CLI as a cell-level configuration, there may be less network management overhead because CLI-SRS transmission and / or measurement resources can be aligned for different UEs operating in the cell. In addition, cell-level CLI-SRS resources and configurations can be used on both Uu and SL communications. Therefore, a separate Uu / SL configuration may not be necessary. By establishing a transmission priority and power allocation for CLI-SRS relative to other signals, the network can ensure that CLI-SRS measurements do not cause delays in higher priority communications, but even if there will be conflicts with lower priority UL / SL communications, CLI-SRS communications can continue. Therefore, undesirable delays, latency and network overhead can be reduced, and network efficiency and user experience can be improved.
[0049] Figure 1A A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes several network devices and / or network entities, including base stations (BSs) 105 (labeled as 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with the UE 115, and may also be referred to as: an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the particular geographic coverage area of the BS 105 and / or a BS subsystem serving the coverage area, depending on the context in which the term is used. Figures 7 to 10 The actions may be performed by any BS of BS 105 and / or any UE of UE 115. The devices of network 100 may be configured to communicate using one or more interfaces, including a Uu interface or an air interface, and a side link (SL) interface. In some aspects, the SL interface may be referred to as a PC5 interface.
[0050] BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1A In the example shown in , BS105b, 105d and 105e can be conventional macro BSs, while BS105a and 105c can be macro BSs enabled with one of three-dimensional (3D), full-dimensional (FD) or massive MIMO. BS 105a and 105c can utilize their higher dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS105f can be a small cell BS, which can be a home node or a portable access point. BS105 can support one or more (e.g., two, three, four, etc.) cells.
[0051] The network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
[0052] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, a mobile station, a user unit, a station, etc. UE 115 can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). On the other hand, UE can be a device that does not include UICC. In some aspects, UE 115 that does not include UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a to 115d are examples of mobile smart phone type devices that access the network 100. UE 115 can also be a machine that is specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). UEs 115e to 115h are examples of various machines configured for communication to access network 100. UEs 115i to 115k are examples of vehicles equipped with wireless communication devices configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1A In the figure, lightning (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105 (which is a BS designated to serve UE 115 on downlink (DL) and / or uplink (UL)), desired transmission between BS 105, backhaul transmission between BSs, or sidelink transmission between UE 115.
[0053] Returning now to FIG. 1 , in operation, BSs 105a and 105c may use 3D beamforming and coordinated spatial techniques such as coordinated multipoint (CoMP) or multi-connectivity to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BSs 105a and 105c, and small cell BS 105f. Macro BS 105d may also transmit multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
[0054] The BSs 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.), and may perform wireless configuration and scheduling for communications with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., via a core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.
[0055] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine-type devices such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with BSs such as small cell BS 105f and macro BS 105e through the network 100, or communicate through the network in a multi-step configuration by communicating with another user device such as UE 115f that communicates temperature measurement information to a smart meter (UE 115g), which then reports to the network through the small cell BS 105f, which relays its information to the network. The network 100 can also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), cellular V2X (C-V2X) communications between UE 115i, 115j or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j or 115k and BS 105. Additionally, BS 105b is shown as a non-terrestrial network (NTN) resource, such as a satellite orbiting the earth. In this example, BS 105b may include multiple antenna arrays, each array forming a relatively fixed beam. BS 105b may be configured as a single cell with multiple beams and BWP, as explained in more detail below.
[0056] In some implementations, network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, frequency modulations, frequency slots, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.
[0057] In some aspects, BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. The communication may be in the form of a radio frame. A radio frame may be divided into a plurality of subframes or time slots, such as about 10. Each time slot may also be divided into micro-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subframe subset (e.g., a DL subframe) in a radio frame may be used for DL transmission, and another subframe subset (e.g., an UL subframe) in a radio frame may be used for UL transmission.
[0058] DL subframes and UL subframes can also be divided into several zones. For example, each DL or UL subframe can have a predefined zone for the transmission of reference signals, control information and data. Reference signals are predetermined signals that facilitate communication between BS105 and UE 115. For example, reference signals can have a specific pilot pattern or structure, wherein pilot tones can span an operational BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS105 can send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 can send a sounding reference signal (SRS) to enable BS105 to estimate an UL channel. Control information may include resource assignments and protocol control. Data may include protocol data and / or operational data. In some aspects, BS105 and UE 115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a duration longer for DL communications than for UL communications. A UL-centric subframe may include a duration longer for UL communications than for UL communications.
[0059] In some aspects, network 100 may be an NR network deployed on a licensed spectrum. BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS 105 may broadcast system information associated with network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, BS 105 may broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast RMSI and / or OSI on a physical downlink shared channel (PDSCH).
[0060] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with the physical layer identification value to identify the cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.
[0061] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.
[0062] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.
[0063] After establishing the connection, the UE 115 and the BS 105 may enter a normal operation phase, in which operation data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL communications. The BS 105 may send UL and / or DL scheduling grants to the UE 115 via the PDCCH. The scheduling grant may be sent in the form of DL control information (DCI). The BS 105 may send DL communication signals (e.g., carrying data) to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send UL communication signals to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.
[0064] In some aspects, BS105 may communicate with UE 115 using hybrid automatic repeat request (HARQ) technology to improve communication reliability, for example, to provide ultra-reliable low-latency communication (URLLC) services. BS105 may schedule UE 115 for PDSCH communication by sending DL grants in PDCCH. BS105 may send DL data packets to UE 115 according to the scheduling in PDSCH. DL data packets may be sent in the form of transport blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 may send a HARQ confirmation (ACK) to BS105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may send a HARQ negative confirmation (NACK) to BS105. Once HARQ NACK is received from UE 115, BS105 may resend the DL data packet to UE 115. The retransmission may include a decoded version of the DL data that is the same as the initial transmission. Alternatively, the retransmission may include a decoded version of the DL data that is different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ to UL communications using a substantially similar mechanism as DL HARQ.
[0065] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into a plurality of bandwidth parts (BWPs) (e.g., parts). The BS 105 may dynamically assign the UE 115 to operate on a specific BWP (e.g., a specific part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within the CC to the UE 115 for UL and DL communications. For example, the BWP pair may include a BWP for UL communications and a BWP for DL communications.
[0066] In some aspects, network 100 may operate on a shared channel, which may include a shared frequency band or an unlicensed frequency band. For example, network 100 may be an NR unlicensed (NR-U) network. BS105 and UE 115 may be operated by multiple network operation entities. In order to avoid conflicts, BS105 and UE 115 may use a listen-before-talk (LBT) procedure to monitor transmission opportunities (TXOPs) in a shared channel. For example, a transmitting node (e.g., BS105 or UE 115) may perform LBT before transmitting in a channel. When LBT passes, the transmitting node may continue to transmit. When LBT fails, the transmitting node may prohibit transmitting in the channel. In one example, LBT may be based on energy detection. For example, when the signal energy measured from the channel is lower than a threshold, the LBT result is passed. Conversely, when the signal energy measured from the channel exceeds a threshold, the LBT result is a failure. In another example, LBT may be based on signal detection. For example, when a channel reservation signal (eg, a predetermined preamble signal) is not detected in the channel, the LBT result is passed.
[0067] In some aspects, the network 100 may operate on a high frequency band (e.g., in a frequency range 1 (FR1) band or a frequency range 2 (FR2) band). FR1 may refer to frequencies in the range below 6 GHz, while FR2 may refer to frequencies in the mmWave range. In order to overcome the high path loss at high frequencies, the BS 105 and the UE 115 may communicate with each other using directional beams. For example, the BS 105 may send an SSB by scanning across a predefined set of beam directions, and may repeat the SSB transmission at a certain time interval on the set of beam directions to allow the UE 115 to perform initial network access. In the example of the NTN resource 105b, it may send an SSB on each beam in its beam at a scheduled time, even if the beam is not steered. In some instances, each beam and its corresponding characteristics may be identified by a beam index. For example, each SSB may include an indication of a beam index corresponding to the beam used for the SSB transmission.
[0068] The UE 115 may determine signal measurements (such as reference signal received power (RSRP) and / or reference signal received quality (RSRQ)) for SSBs in different beam directions and select the best DL beam. The UE 115 may indicate the selection by sending a physical random access channel (PRACH) signal (e.g., MSG1) using a PRACH resource associated with the selected beam direction. For example, an SSB sent in a particular beam direction or on a particular beam may indicate a PRACH resource that the UE 115 may use to communicate with the BS 105 in the particular beam direction. After selecting the best DL beam, the UE 115 may complete a random access procedure (e.g., a 4-step random access or a 2-step random access) and proceed with network registration and normal operational data exchange with the BS 105. In some instances, the initially selected beam may not be optimal or channel conditions may change, and therefore the BS 105 and the UE 115 may perform a beam refinement procedure to refine the beam selection. For example, BS 105 may transmit CSI-RS by scanning a narrower beam over a narrower angular range, and UE 115 may report the best DL beam to BS 105. When BS 105 transmits using a narrower beam, BS 105 may apply a higher gain and thus may provide better performance (e.g., a higher signal-to-noise ratio (SNR)). In some instances, channel conditions may degrade and / or UE 115 may move out of the coverage of the initially selected beam, and thus UE 115 may detect a beam failure condition. Upon detecting a beam failure, UE 115 may perform a beam handover.
[0069] In some aspects, network 100 may be an IoT network, and UE 115 may be an IoT node, such as a smart printer, monitor, gaming node, camera, audio-video (AV) production equipment, industrial IoT device, etc. The transmit payload data size of an IoT node may typically be relatively small (e.g., on the order of tens of bytes). In some aspects, network 100 may be a large-scale IoT network serving tens of thousands of nodes (e.g., UE 115) on a high frequency band (e.g., FR1 band or FR2 band).
[0070] Figure 1BA diagram illustrating an example disaggregated base station 102 architecture is shown. The disaggregated base station 102 architecture may include one or more central units (CUs) 150 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 100 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 145 associated with a service management and orchestration (SMO) framework 135, or both. The CU 150 may communicate with one or more distributed units (DUs) 130 via respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more radio units (RUs) 140 via respective fronthaul links. The RU 140 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 140.
[0071] Each of the units (i.e., CU 150, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 145, and SMO framework 135) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0072] In some aspects, CU 150 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 150. CU150 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 150 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 150 may be implemented to communicate with DU 130 for network control and signaling.
[0073] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional partitioning such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 150.
[0074] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 150 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0075] The SMO framework 135 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 135 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 135 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 150, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 135 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 135 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 135 may also include a non-RT RIC 145 configured to support the functionality of the SMO framework 135 .
[0076] The non-RT RIC 145 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 145 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 150, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.
[0077] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 145 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 135 or the non-RT RIC 145. In some examples, the non-RT RIC 145 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 145 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 135 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0078] Figure 2 1 illustrates an example of a wireless communication network 200 that provides side link communications according to aspects of the present disclosure. The network 200 may correspond to a portion of the network 100. For the purpose of simplifying the discussion, Figure 2 Two BSs 205 (shown as 205a and 205b) and six UEs 215 (shown as 215a1, 215a2, 215a3, 215a4, 215b1, and 215b2) are illustrated, although it will be appreciated that aspects of the present disclosure may be scaled to any suitable number of UEs 215 (e.g., approximately 2, 3, 4, 5, 7, or more) and / or BSs 205 (e.g., approximately 1, 3, or more). BSs 205 and UEs 215 may be similar to BSs 105 and UEs 115, respectively. BSs 205 and UEs 215 may share the same radio frequency band for communication. In some instances, the radio frequency band may be a 2.4 GHz unlicensed band, a 5 GHz unlicensed band, or a 6 GHz unlicensed band. In general, the shared radio frequency band may be at any suitable frequency.
[0079] BS205a and UE 215a1-215a4 may be operated by a first network operating entity. BS205b and UE 215b1-215b2 may be operated by a second network operating entity. In some aspects, the first network operating entity may use the same RAT as the second network operating entity. For example, BS205a and UE 215a1-215a4 of the first network operating entity and BS205b and UE 215b1-215b2 of the second network operating entity are NR-U devices. In some other aspects, the first network operating entity may use a different RAT from the second network operating entity. For example, BS205a and UE 215a1-215a4 of the first network operating entity may utilize NR-U technology, while BS205b and UE 215b1-215b2 of the second network operating entity may utilize WiFi or LAA technology.
[0080] In network 200, some UEs in UE 215a1-215a4 can communicate with each other in peer-to-peer communication. For example, UE 215a1 can communicate with UE 215a2 through side link 252, UE 215a3 can communicate with UE 215a4 through another side link 251, and UE 215b1 can communicate with UE 215b2 through another side link 254. Side links 251, 252 and 254 are unicast bidirectional links. Some UEs in UE 215 can also communicate with BS 205a or BS 205b in UL direction and / or DL direction via communication link 253. For example, UE 215a1, 215a3 and 215a4 are in the coverage area 210 of BS 205a, and therefore can communicate with BS 205a. UE 215a2 is outside the coverage area 210, and therefore can not communicate directly with BS 205a. In some instances, UE 215a1 may operate as a repeater for UE 215a2 to reach BS 205a. Similarly, UE 215b1 is within the coverage area 212 of BS 205b and may therefore communicate with BS 205b and may operate as a repeater for UE 215b2 to reach BS 205b. In some aspects, some of UEs 215 are associated with vehicles (e.g., similar to UEs 115i-115k), and the communications conducted through side links 251, 252, and 254 may be C-V2X communications. C-V2X communications may refer to communications between a vehicle and any other wireless communication device in a cellular network.
[0081] Figure 3 3 is a timing diagram illustrating a radio frame structure 300 according to some aspects of the present disclosure. Radio frame structure 300 may be employed by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) for communication. Specifically, the BS may communicate with the UE using the time-frequency resources configured as shown in radio frame structure 300. Figure 3 , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. Transmit frame structure 300 includes radio frame 301. The duration of radio frame 301 can vary according to various aspects. In one example, radio frame 301 can have a duration of about ten milliseconds. Radio frame 301 includes M time slots 302, where M can be any suitable positive integer. In one example, M can be about 10.
[0082] Each slot 302 includes a plurality of subcarriers 304 in frequency and a plurality of symbols 306 in time. The number of subcarriers 304 and / or the number of symbols 306 in a slot 302 may vary according to various aspects, such as based on channel bandwidth, subcarrier spacing (SCS), and / or cyclic prefix (CP). One subcarrier 304 in frequency and one symbol 306 in time form one resource element (RE) 312 for transmission. A resource block (RB) 310 is formed by a plurality of consecutive subcarriers 304 in frequency and a plurality of consecutive symbols 306 in time.
[0083] In one example, a BS (e.g., Figure 1A BS 105 in the example may schedule UEs (eg, Figure 1A UE 115 in the UE 115) performs UL and / or DL communication. Each time slot 302 can be time-divided into K micro-time slots 308. Each micro-time slot 308 can include one or more symbols 306. The micro-time slots 308 in the time slot 302 can have variable lengths. For example, when the time slot 302 includes N symbols 306, the micro-time slot 308 can have a length between one symbol 306 and (N-1) symbols 306. In some aspects, the micro-time slot 308 can have a length of about two symbols 306, about four symbols 306, or about seven symbols 306. In some examples, the BS can schedule UEs at a frequency granularity of RB 310 (e.g., including about 12 subcarriers 304).
[0084] The time slot 302 may be configured as a DL time slot having a DL frequency band spanning a channel frequency BW, a UL time slot having a UL frequency band spanning a channel frequency BW, or a full-duplex time slot including a UL frequency band and a DL frequency band in the channel frequency BW. FIG. 4A to FIG. 4C Various full-duplex configurations are illustrated.
[0085] Figure 4A 4 illustrates a full-duplex communication configuration 410 according to some aspects of the present disclosure. Configuration 410 may be used by BS 105 and UE 115 in a network (such as network 100) for communication in conjunction with radio frame structure 300. Figure 4A 410, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. In configuration 410, UL band 414 may completely overlap DL band 412 in channel frequency BW 416 (e.g., in a single unpaired spectrum band). As shown, UL band 414 is within DL band 412. UL band 414 may be used by UE 115 for UL transmissions. DL band 412 may be used by BS 105 for DL transmissions. Configuration 410 may be referred to as IBFD mode.
[0086] Figure 4B4 illustrates a full-duplex communication configuration 420 according to some aspects of the present disclosure. Configuration 420 may be used by BS 105 and UE 115 in a network (such as network 100) for communication in conjunction with radio frame structure 300. Figure 4B 4, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. In configuration 420, UL frequency band 424 may partially overlap with DL frequency band 422 in channel frequency BW 426 (e.g., in a single unpaired spectrum band). UL frequency band 424 may be used by UE 115 for UL transmissions. DL frequency band 422 may be used by BS 105 for DL transmissions. Configuration 420 may also be referred to as IBFD mode.
[0087] Figure 4C 4. A full-duplex communication configuration 430 is illustrated in accordance with some aspects of the present disclosure. Configuration 430 may be employed by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) in conjunction with radio frame structure 300 to communicate. Figure 4C 430, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. In configuration 430, UL band 434 may be separated from DL band 432 by guard band 433 in channel frequency BW 436 (e.g., in a single unpaired spectrum band). UL band 434 may be used by UE 115 for UL transmissions. DL band 432 may be used by BS 105 for DL transmissions. Guard band 433 may be small or narrow, for example, including about 5 RBs (e.g., RB 210). Configuration 420 may be referred to as SFBD mode.
[0088] Figure 5 A full-duplex communication scenario 500 according to some aspects of the present disclosure is illustrated. Scenario 500 may correspond to a wireless communication scenario in network 100. The x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. BS 105 may schedule SSBs 510 to be sent periodically, for example, with a periodicity of about 10 ms, 20 ms, 50 ms, 80 ms, or more.
[0089] exist Figure 5In the illustrated example of , BS105 may send SSB 510 every other radio frame 502 (e.g., repetition interval 501). SSBs are shown as 510a and 510b. Radio frame 502 may have a frame structure similar to structure 300. For example, each radio frame 502 may have a duration of approximately 10 ms. In NR or 5G, the SCS may be 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz, the carrier frequency may be less than 3 GHz, between 3 GHz and about 6 GHz, or greater than 6 GHz, and the SSB burst may be sent in the first half of the radio frame 502 (e.g., the first 5 ms of the radio frame 502). In some instances, BS105 may send all pre-scheduled SSBs 510. BS105 may send PSS 512, SSS 514, and PBCH signal 516 in each SSB 510, as shown in the expanded diagram 507. PSS 512 and SSS 514 may assist UE 115 in synchronizing to the network and may provide cell identification information.PBCH signal 516 may carry a MIB indicating network system information, such as the SCS used by the network and / or resources where BS 105 may send SIB scheduling information.
[0090] As discussed above, the BS 105 may configure a combination of DL time slots, UL time slots, and / or full-duplex time slots in the channel frequency BW. The DL time slot 504d may include a DL frequency band 520. The DL frequency band 520 may correspond to a channel frequency BW (e.g., channel frequency BW 316, 326, and / or 336). The channel frequency BW may be at any suitable frequency band (e.g., below 3 GHz, between about 3 GHz and about 6 GHz, or greater than 6 GHz). The channel frequency BW may include any suitable number of frequencies (e.g., about 20 MHz, about 80 MHz, about 100 MHz, or more). The DL time slot 504d may correspond to Figure 3 The DL time slot 504d may include a DL control portion 532, a DL data portion 534, and a UL control portion 536. Each portion 532, 534, 536 may include time-frequency resources, such as Figure 3306 in time and a number of REs 312 or RBs 310 in frequency as shown in . The BS 105 may send DL control information (e.g., PDCCH) in the DL control portion 532. For example, the BS 105 may send DL data (e.g., PDSCH) in the DL data portion 534. The BS 105 may schedule the UE 115 to send UL control information (e.g., PUCCH including SRS, HARQ ACK / NACK, and / or channel quality indicator (CQI)) in the UL control portion 536. The UL control portion 536 may be separated from the DL data portion 534 by a gap period 506 to provide time for switching between UL and DL.
[0091] When BS105 utilizes the combination of DL time slot, UL time slot and / or full-duplex time slot, BS105 can dynamically or semi-statically reconfigure time slot to switch between any mode in DL, UL and / or full-duplex mode. In other words, BS105 can utilize the channel frequency BW similar to TDD mode, but some time slots can be additionally configured as full-duplex time slots. For example, BS105 can initially configure time slot as DL time slot and can subsequently reconfigure this time slot as full-duplex time slot, for example, can meet the time delay criterion of a certain UL URLLC communication. DL time slot 504d can include the UL frequency band 524 between the upper DL frequency band 522a and the lower DL frequency band 522b located in the channel frequency BW. UL frequency band 524 can be separated from a guard band 523 by the upper DL frequency band 522a and can be separated from another guard band 523 by the lower DL frequency band 522b. The guard band 523 may be much narrower than the UL band 524 and the DL band 522. In some instances, the guard band 523 may include about 5 RBs. Each of the DL bands 522a, 522b, and the UL band 524 may include any suitable BW. In one example, the BW of each of the DL bands 522a, 522b, and the UL band 524 may be predetermined. In another example, the BS 105 may determine the BW of each of the DL bands 522a, 522b, and the UL band 524 based on traffic load and / or latency requirements. The full-duplex time slot 504f may correspond to Figure 3 The full-duplex time slot 504f may include a DL control portion 532 and a DL data portion 534 in each of the DL frequency bands 522a and 522b. The full-duplex time slot 504f may include a UL data portion 538 and a UL control portion 536 in the UL frequency band 524. Similar to portions 532, 534, 536, the UL data portion 538 may include time-frequency resources, such as Figure 3509 . The BS 105 may schedule the UE 115 to send UL data (e.g., PUSCH) in the UL data portion 538. In some instances, the full-duplex time slot 504f may be followed by the UL time slot 504u shown in the expanded diagram 509. The UL time slot 504u may include a UL frequency band in the channel frequency BW and may include a UL data portion 538 following the UL control portion 536. In some other instances, the full-duplex time slot 504f may be followed by a DL time slot similar to the DL time slot 504d. Generally speaking, the full-duplex time slot 504f may be adjacent to the UL time slot 504u and / or the DL time slot 504d.
[0092] Figure 6 is an illustration of an example cross-link interference scenario according to some embodiments. Figure 6 The UE and BS may be the same or similar to the UE and BS discussed above with reference to FIG. 1. In short, cross-link interference (CLI) is interference from one UE to another nearby UE. CLI may occur when one or more networks configure different TDD UL and DL time slot formats to nearby UEs. When the interferer UE continues to transmit to the base station, if the UL symbol of the interferer collides with at least one DL symbol of the victim UE, the victim UE may receive the transmission as interference in its DL symbol. CLI may occur between two UEs on the same cell or different cells.
[0093] In the "inter-cell" scenario, UE 1 is the interferer and its UL transmission causes interference in the downlink symbols of the victim UE (UE 2). In the "intra-cell" scenario, the interferer UE (UE 1) and the victim UE (UE 2) are in the same cell and communicate with the same BS. Similarly, the UL from UE 1 causes interference in the DL of UE 2.
[0094] Figure 6 Also included is an illustration of example interference with reference time slots 601 and 602. Time slot 601 is assigned to UE 1, and time slot 602 is assigned to UE 2. Each of time slots 601, 602 has a time slot format. That is, the network configures which symbols within time slots 601, 602 are used for DL, UL and is flexible. Figure 6 , symbols marked with "D" are configured for DL, symbols marked with "U" are configured for UL, and symbols marked with "F" are configured as flexible and can be configured for both transmission and reception at any time. Specifically, the flexible symbols can be configured for both CLI measurements and UL transmissions, as explained in more detail below.
[0095] In this example, CLI occurs when UL transmission from an interference source UE interferes with DL reception at an interfered object UE, as shown by symbol 610. Either or both of UE 1 and UE 2 can measure CLI, and this example focuses on UE 2. UE 2 can be referred to as an interfered object UE. UE 2 measures CLI in response to a network configuration. For example, UE 2 can measure CLI based on an RRC configuration. The RRC configuration can configure one or more CLI measurement resources. The CLI measurement in this example is a layer 3 periodic measurement used to determine the presence of an inhibiting or interfering UE (such as UL from UE 1). For example, UE 2 may be configured with one or more sounding reference signal (SRS) resources (such as time-frequency resources, sequences, cyclic shifts, periodicity, etc.) to measure UE-to-UE CLI. With reference to such measurements, SRS reference signal received power (SRS-RSRP) and received signal strength indicator (RSSI) can be used as metrics for CLI measurements. SRS-RSRP may include a linear average of the power contribution of the SRS measured on the configured resource elements within the measurement frequency bandwidth to be considered in the timer resources in the configured measurement opportunity. RSSI may include a linear average of the total received power only in certain symbols (e.g., OFDM symbols) of the measurement time resources, in the measurement bandwidth, and on the configured resource elements for the CLI measurement of the UE. The interfered UE (UE 2) may transmit a measurement report to the network. Based on the CLI measurement report, the network may coordinate the scheduling of the interference source and the interfered UE to balance the UL and DL throughput. Of course, in this example, the CLI measurement is not limited to the interfered UE, because UE 1 may be the interfered object of another UE (not shown) and may measure and report CLI in the same or similar manner as UE2.
[0096] Looking at time slot 602, CLI can be RRC configured for either of the symbols marked D or F. UL can also be independently configured for either of the symbols marked U or F. Therefore, in some instances, there may be a conflict between CLI measurements and UL transmissions in a given flexible (F) symbol. For example, UE 2 can be RRC configured for CLI measurements in either or both of symbols 611, and can also be RRC configured or dynamically (via the physical layer) scheduled or triggered for UL in either or both of symbols 611. The current NR protocol may specify that the UE is not expected to handle conflicts between UL and CLI measurements. For example, if a symbol has been configured as a CLI measurement opportunity, it is not expected to configure or schedule the UE with PUCCH, PUSCH and SRS in the symbol.
[0097] However, UE 1 and UE 2 in this example include hardware and / or software logic to provide different functionality.UE 1 and UE 2 in this example may deprioritize CLI measurement over UL transmission by allowing the UE to transmit PUCCH, PUSCH or SRS in symbols in which CLI measurement is configured.
[0098] In some aspects, in order to facilitate CLI measurements obtained by nearby UEs, one or more neighboring UEs in the network may be configured to send one or more reference signals during one or more CLI measurement windows or opportunities. For example, the UE may be configured to send a sounding reference signal (SRS) to facilitate CLI measurements performed by other UEs. In some aspects, the SRS for CLI may have a format and structure similar to or identical to a non-CLI SRS. In other aspects, the CLI-SRS may have a structure or format that is different from a non-CLI SRS in at least one aspect. On the other hand, the CLI-SRS may be configured at the cell level so that the CLI-SRS resources may be aligned for different UEs communicating in the network. For the purposes of this disclosure, if the configuration is common to multiple devices connected to a cell, the configuration may be a cell-level configuration. For example, the UE may perform a cell selection or RACH process to connect to the cell. If successful, the network may send a cell configuration to the UE to indicate one or more parameters for communicating on the cell. The cell configuration may include or indicate, for example, reference signal resources, measurement resources, transmit power parameters, and / or any other suitable parameters for communicating on the cell. The cell configuration may indicate CLI-SRS transmission resources and / or measurement resources for the cell. In some aspects, the cell configuration may also be referred to as a component carrier (CC) configuration, a frequency resource configuration, and / or a bandwidth part (BWP) configuration. The cell configuration may indicate one or more parameters for the CLI-SRS. In addition, one or more of the UEs may be configured with CLI measurement resources. For example, one or more of the UEs operating in a cell using full-duplex mode may be configured with non-zero power (NZP) CLI-SRS or zero power (ZP) CLI-SRS measurement resources. Therefore, in some aspects, both CLI-SRS transmission resources and CLI-SRS measurement resources may be cell-level resources based on or associated with one or more cell configurations.
[0099] CLI-SRS resources may include periodic, semi-persistent, and / or aperiodic resources. For example, a CLI-SRS resource may be periodic and configured to be transmitted without receiving an activation. In other aspects, a CLI-SRS resource may be semi-persistent. For example, the periodicity and resources are known and triggered by activation. In some aspects, receiving activation may include receiving a medium access control element (MAC-CE) indicating activation of a CLI-SRS resource. On the other hand, receiving activation may include receiving a DCI activating one or more aperiodic CLI-SRS resources.
[0100] Similarly as described above with respect to CLI measurements, there may be a conflict or scheduling conflict between CLI-SRS and UL transmissions. For example, the UE may be configured with a periodic SRS that conflicts with at least one timing of a semi-persistent or aperiodic CLI-SRS. In some aspects, it may not be expected that the UE handles conflicts between at least some UL transmissions and / or SL transmissions (e.g., PUCCH, PSFCH) and CLI-SRS. The present disclosure describes schemes and mechanisms for handling and / or avoiding scheduling conflicts between CLI-SRS and at least one other UL and / or SL communication scheduled for transmission. Other aspects of the present disclosure describe power allocation rules and configurations for transmitting CLI-SRS concurrently with one or more other UL / SL communications on different carriers in a carrier aggregation (CA) mode. As explained below, various aspects of the present disclosure are applicable to Uu communications as well as SL communications. For example, a CLI-SRS priority configuration may be used to resolve collisions / conflicts between multiple Uu communications, between multiple SL communications, and / or between Uu and SL communications. Furthermore, the CLI-SRS power allocation priority configuration may be used to allocate or distribute power between multiple Uu communications, between multiple SL communications, and / or between Uu and SL communications.
[0101] Figure 7 is a signaling diagram illustrating a method 700 for handling collisions between a CLI-SRS and one or more other UL and / or SL communications scheduled for transmission according to aspects of the present invention. Figure 7 The action of is performed by the first UE 715a, the second UE 715b and the BS 705. For example, the UE 715 may be Figure 1A or Figure 2 In some aspects, Figure 7 One or more actions may be performed by executing computer code to perform Figure 7 The functionality shown in FIG. 1 is performed by a processor in the UE.
[0102] At action 702, BS 705 sends a cell configuration of at least a first cell, and the first UE 715a receives the configuration. In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. The cell configuration may indicate a CC and / or a BWP or be associated with a CC and / or a BWP. The cell configuration may be associated with Uu communication and / or SL communication. The cell configuration may indicate UL, DL and / or SL BWP configurations, measurement parameters, DL control channel monitoring configurations, timing advance parameters, beam management parameters and / or any other suitable parameters or configurations associated with the first cell. The first cell may be a primary cell (Pcell), a special cell (SpCell), a secondary cell (Scell) and / or any suitable type of cell. In some aspects, action 702 may include more than one cell configuration communication associated with more than one serving cell. For example, the first UE 715a may be configured to operate in a carrier aggregation (CA) mode, in which the first UE 715a may communicate with more than one serving cell. For example, the first UE 715a may receive cell configuration for a Pcell and at least one Scell.
[0103] The cell configuration may be associated with a serving cell index. In some aspects, the first UE 715a may be configured with one or more CLI-SRS transmission resources and / or parameters. In this regard, multiple UEs operating in a cell may be configured with the same CLI-SRS transmission resources. Therefore, the CLI-SRS transmission resources or configurations may be referred to as cell-level resources or configurations.
[0104] At action 704, the BS 705 sends at least one of a UL grant or an SRS activation signal, and the first UE 715a receives at least one of the UL grant or the SRS activation signal. The UL grant may indicate the time / frequency resources for PUCCH and / or PUSCH. In other aspects, action 704 may include receiving a DL communication signal. The DL communication signal may include DCI and / or DL data. The first UE 715a may be configured to send ACK / NACK for DL data based on a HARQ protocol. In some aspects, the SRS activation communication may include DCI communication to dynamically trigger one or more non-periodic SRS opportunities. In other aspects, the SRS activation communication may include MAC-CE communication to activate a semi-persistent SRS resource set.
[0105] As discussed further below, the UL grant and / or SRS activation communicated at action 704 may trigger or indicate communication by the first UE 715a for a set of time / frequency resources. In some aspects, the set of time / frequency resources indicated in the UL grant and / or SRS activation may indicate one or more time windows for the first UE 715a to send UL communications and / or SRS. On the other hand, if the first UE 715a receives a DL signal at action 704, the UE 715a may be configured to send a response within the one or more time windows.
[0106] At action 706, the BS 705 sends a CLI-SRS activation associated with the first cell, and the first UE 715a receives the CLI-SRS activation associated with the first cell. In some aspects, the CLI-SRS activation communication may include a DCI communication to dynamically trigger one or more non-periodic CLI-SRS opportunities. In other aspects, the CLI-SRS activation communication may include a MAC-CE communication to activate a semi-persistent CLI-SRS resource set. However, in some aspects, the method 700 may not include receiving a CLI-SRS activation. For example, the first UE 715a may be configured with a periodic CLI-SRS resource set that is activated based on the cell configuration received at action 702. The CLI-SRS resource set may include periodic, semi-persistent and / or non-periodic CLI-SRS resource sets.
[0107] In some aspects, the CLI-SRS resource set for the serving cell may include one or more CLI-SRS opportunities that occupy the time resource set. In some instances, one or more of the CLI-SRS opportunities may overlap in time at least partially with UL communications or SL communications scheduled based on UL grants, SRS activations, and / or DL communications received at action 706. In some aspects, one or more of the CLI-SRS opportunities may also overlap in frequency at least partially with UL communications or SL communications scheduled based on UL grants, SRS activations, and / or DL communications received at action 706. Therefore, the first UE 715a may experience a scheduling conflict or collision within at least one time window.
[0108] At action 708, the first UE 715a resolves scheduling conflicts between CLI-SRS and UL / SL communications. The present disclosure describes a variety of conflict resolution and avoidance schemes that may be used. For example, the present disclosure provides priority rules and power allocation rules for cell-level CLI-SRS relative to other UL and / or SL communications (including PUCCH, PUSCH, PSCCH, PSSCH, PSFCH, SRS, and / or any other UL / SL communications). An example of a priority-based conflict resolution scheme for CLI-SRS as employed in action 708 is described in Figures 11 to 14 Shown in.
[0109] refer to Figure 7 and Fig.11 , a conflict resolution may be used in the first full-duplex communication scenario 1100. Scenario 1100 may occur in at least the first carrier CC1. For example, the first UE 715a may be configured with a periodic or semi-persistent SRS resource set including a plurality of SRS opportunities 1102. It will be understood that the SRS opportunity 1102 may be a non-CLI SRS opportunity. The first UE 715a may receive an activation signal 1104 that activates or indicates a CLI-SRS resource 1106. As explained above, receiving the activation signal 1104 may include receiving a MAC-CE that activates a semi-persistent CLI-SRS resource set. On the other hand, receiving the activation signal 1104 may include receiving a DCI indicating a non-periodic CLI-SRS resource or resource set. The CLI-SRS resource 1106 collide / conflicts with the scheduled SRS resource 1102. In this regard, the CLI-SRS resource 1106 may overlap at least partially with at least one of the SRS resources 1102 in time and frequency.
[0110] refer to Figure 7 and Fig.12 , a conflict resolution may be used in the second full-duplex communication scenario 1200. Scenario 1200 may occur in at least the first carrier CC1. The first UE 715a may receive DCI 1202 and an accompanying PDSCH communication 1204 in a PDCCH monitoring opportunity. DCI 1202 may indicate a time resource for sending ACK / NACK 1206. In addition, the first UE 715a may be configured with a semi-persistent or periodic CLI-SRS resource set including a plurality of CLI-SRS opportunities 1210. At least one CLI-SRS opportunity in the CLI-SRS opportunities 1210 collides / conflicts with a scheduled ACK / NACK resource 1206. At this point, the CLI-SRS resource 1210 may overlap at least partially with the scheduled ACK / NACK resource 1206 in time and frequency.
[0111] refer to Figure 7 and Fig.13 , a conflict resolution may be used in the third full-duplex communication scenario 1300. Scenario 1300 may occur in at least the first carrier CC1. For example, the first UE 715a may be configured with a periodic or semi-persistent SRS resource set including a plurality of SRS opportunities 1302. It will be understood that the SRS opportunity 1302 may be a non-CLI SRS opportunity. The first UE 715a may receive an activation signal 1304 that activates or indicates a CLI-SRS resource 1306. As explained above, receiving the activation signal 1304 may include receiving a MAC-CE that activates a semi-persistent CLI-SRS resource set. On the other hand, receiving the activation signal 1304 may include receiving a DCI indicating a non-periodic CLI-SRS resource or resource set. The CLI-SRS resource 1306 collide / conflicts with the scheduled SRS resource 1302. In this regard, the CLI-SRS resource 1306 may overlap at least partially with at least one of the SRS resources 1302 in time and frequency. In this regard, at least one SRS resource 1302 may include a non-overlapping portion 1301 and an overlapping portion 1303. In some aspects, the overlapping portion 1303 may include any symbol of the SRS resource 1302 that is aligned in time within any symbol of the CLI-SRS resource 1306, and may further include one or more symbols before and / or after the first and / or last symbol of the CLI-SRS resource 1306.
[0112] With reference to scenarios 1100 to 1300 and method 700, the first UE 715a may apply one or more CLI-SRS priority rules or configurations to resolve conflicts with CLI-SRS resources and other SL and / or UL resources or scheduled communications. In some aspects, resolving conflicting / colliding resources may involve prohibiting the transmission of one communication and continuing to transmit another communication. In other aspects, resolving conflicting resources may involve discarding one or more overlapping symbols from at least one of the communications.
[0113] For purposes of this disclosure, a CLI-SRS priority configuration may refer to one or more rules or protocols executed by a UE 715 and / or BS 705 to resolve and / or prevent conflicts of CLI-SRS resources with other UL / SL resources. In some aspects, the CLI-SRS priority configuration may be a static or hard-coded configuration. Further, in some aspects, the CLI-SRS priority configuration may include a hard-coded BS configuration that may prevent activation or configuration of a UL / SL resource that would conflict with a CLI-SRS resource and / or may prevent activation or configuration of a CLI-SRS resource that would conflict with another UL / SL resource.
[0114] In some aspects, the first UE 715a may discard the CLI-SRS or one or more concurrent UL / SL scheduled resources. For example, the UE 715a may determine which of the CLI-SRS or the concurrent UL / SL communications is associated with a higher priority. Therefore, the first UE 715a may send the CLI-SRS or the concurrent UL / SL communications based on a comparison of the priority of the CLI-SRS with the priority of the concurrent UL / SL communications. In other aspects, the priority of the CLI-SRS relative to other UL / SL communications may depend on the time configuration and / or type of the UL / SL communications. In some aspects, the priority of the CLI-SRS may be based on the time configuration of the CLI-SRS. For example, the priority of the CLI-SRS relative to other UL / SL communications may be based on whether the CLI-SRS resource is periodic, semi-persistent or aperiodic. In some aspects, the priority of CLI-SRS relative to another UL / SL communication can be based on whether the other UL / SL communication includes PUCCH communication, PUSCH communication, PSCCH communication, PSSCH communication, PSFCH communication and / or non-CLI SRS.
[0115] In one example, the first UE 715a may be configured to discard or prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUSCH with a priority index of 0. On the other hand, the first UE 715a may be configured to discard or prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUSCH with a priority index of 1. In some aspects, if the CLI-SRS resource is semi-persistent or periodic, the first UE 715a may be configured to prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUCCH carrying a channel state information (CSI) report, an RSRP report, and / or an SINR report. In some aspects, the first UE 715a may be configured to prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUCCH carrying HARQ-ACK information, a link recovery request, and / or a scheduling request. In some aspects, if the CLI-SRS resource is non-periodic, the first UE 715a may be configured to refrain from sending at least a portion of the PUCCH if the CLI-SRS collides with a PUCCH carrying a CSI report, an RSRP report, and / or an SINR report. On the other hand, the first UE 715a may be configured to refrain from sending at least a portion of the CLI-SRS if a periodic or semi-persistent CLI-SRS collides with an aperiodic non-CLI SRS. On the other hand, the first UE 715a may be configured to refrain from sending at least a portion of the non-CLI SRS if the CLI-SRS collides with a non-CLI SRS. On the other hand, the first UE 715a may be configured to refrain from sending at least a portion of the non-CLI SRS if the aperiodic CLI-SRS collides with a periodic or semi-persistent non-CLI SRS.
[0116] In some aspects, the first UE 715a may be configured to refrain from sending a dynamic PUSCH with a priority of 0 if the dynamic PUSCH will collide with the non-periodic CLI-SRS. On the other hand, the first UE 715a may be configured to refrain from sending an SPS PUSCH if the SPS PUSCH will collide with the non-periodic CLI-SRS. On the other hand, the first UE 715a may be configured to refrain from sending a CLI-SRS if the CLI-SRS will collide with a PUCCH carrying a scheduling request, a HARQ response, and / or a link recovery request. On the other hand, if the non-periodic CLI-SRS will collide with a configured grant (CG) PUSCH, the first UE 715a may be configured to discard the CG-PUSCH and send the CLI-SRS.
[0117] In other aspects, such as Fig.13 As shown in scenario 1300 of , the first UE 715a may be configured to discard one or more overlapping symbols of CLI-SRS or another UL / SL communication. For example, in some aspects, if PUSCH and / or PUCCH with a priority of 1 overlap with CLI-SRS resources, the first UE 715a may discard overlapping symbols of CLI-SRS. On the other hand, if the non-periodic CLI-SRS will conflict with a periodic or semi-persistent SRS, the UE may discard overlapping symbols of the periodic or semi-persistent SRS. On the other hand, if the non-periodic CLI-SRS will conflict with a periodic or semi-persistent CLI-SRS, the UE may discard overlapping symbols of the periodic or semi-persistent CLI-SRS. On the other hand, if the non-periodic SRS will conflict with a semi-persistent or periodic CLI-SRS, the first UE 715a may discard overlapping symbols of CLI-SRS. On the other hand, if the semi-persistent CLI-SRS will collide with the periodic SRS, the first UE 715a can be configured to discard the overlapping symbols of the periodic SRS. On the other hand, if the semi-persistent CLI-SRS will collide with the periodic CLI-SRS, the first UE 715a can be configured to discard the overlapping symbols of the periodic CLI-SRS.
[0118] In some aspects, the CLI-SRS priority configuration may indicate one or more of the rules described above. In other aspects, the CLI-SRS priority configuration may indicate the priority of the CLI-SRS relative to other CLI-SRS and / or other UL / SL communications. In other aspects, the CLI-SRS priority configuration may indicate a priority value or rank for each type of communication, including aperiodic CLI-SRS, semi-persistent CLI-SRS, periodic CLI-SRS, non-CLI SRS, PUCCH, PUSCH, PSSCH, PSCCH, PSFCH, and / or any other type of UL or SL communications.
[0119] At action 710, the first UE 715a transmits a CLI-SRS, and the second UE 715b receives the CLI-SRS. The transmission of the CLI-SRS may be based on the CLI-SRS priority configuration described above. In addition, the transmission of the CLI-SRS may be based on a CLI-SRS timing or time configuration. For example, the transmission of the CLI-SRS may be based on a CLI-SRS activation communicated at action 706. In other aspects, the CLI-SRS transmission may be based on a periodically configured CLI-SRS resource set. The CLI-SRS may be transmitted during a CLI-SRS measurement window configured for the second UE 715b.
[0120] At action 712, the first UE 715a sends at least one of UL communication or non-CLI SRS, and the BS 705 receives at least one of UL communication or non-CLI SRS. Similarly as described above, the transmission of UL communication and / or SRS can be based on the above-mentioned CLI-SRS priority configuration. In some aspects, action 712 includes the first UE 715a sending at least one of PUCCH or PUSCH to the BS 705. In some aspects, PUCCH and / or PUSCH can be associated with a priority of 0 or 1. In some aspects, action 712 can include sending PUCCH. For example, PUCCH can carry at least one of HARQ-ACK, scheduling request and / or link recovery request. In other aspects, action 712 can include sending non-CLI SRS. SRS can be periodic, aperiodic or semi-persistent.
[0121] Referring to actions 710 and 712, signaling arrows are shown as dashed lines, which may indicate an alternative scenario in which one communication is dropped in favor of another communication based on the conflict resolution of action 708. For example, in some aspects, action 710 is performed by the first UE 715a, but the UL communication or SRS of action 712 may be dropped and not sent. In another example, action 710 may not be performed, so that the CLI-SRS is dropped in favor of the UL communication or SRS. In other aspects, as explained above, the communication of both actions 710 and 712 may be performed with the overlapping symbols dropped. In yet another aspect, the method 700 may include the second UE 715b sending a CLI measurement report based on the CLI-SRS communicated at action 710, and the BS 705 receiving the CLI measurement report.
[0122] Prioritization of CLI-SRS relative to other UL communications as described above may be configured at the UE 715 and / or at the BS 705. For example, although aspects of the method 700 are described as resolving conflicts by the first UE 715a, it will be understood that the network including the BS 705 may be configured to prevent scheduling conflicts based on the CLI-SRS prioritization rules described above so that the first UE 715a does not expect to receive UL grants, SRS activations, and / or CLI-SRS activations that will cause conflicts. For example, the network may prioritize PUCCH, PUSCH, and / or aperiodic SRS by activating CLI-SRS resources that do not conflict or overlap with PUCCH, PUSCH, and / or aperiodic SRS resources. For example, the BS 705 may be configured to send CLI-SRS activations so that the CLI-SRS resources do not overlap with lower priority UL communications.
[0123] Figure 8is a signaling diagram illustrating a method 800 for power allocation for CLI-SRS and one or more other UL and / or SL communications scheduled for transmission in accordance with aspects of the present disclosure. Figure 8 The action of is performed by the first UE 815a, the second UE 815b and the BS 805. For example, the UE 815 may be Figure 1A or Figure 2 In some aspects, Figure 8 One or more actions may be performed by executing computer code to perform Figure 8 The functionalities shown in FIG. 8 are performed by a processor in the UE. One or more of the UEs 815 may be configured for carrier aggregation (CA), in which the UE 815 is configured with two or more serving cells.
[0124] At action 802, BS 805 sends the cell configuration of the first cell (CC1) and the second cell (CC2), and the first UE 815a receives the cell configuration of the first cell (CC1) and the second cell (CC2). In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. The cell configuration may be associated with Uu communication and / or SL communication. The cell configuration may indicate UL, DL and / or SL BWP configurations, measurement parameters, DL control channel monitoring configurations, timing advance parameters, beam management parameters and / or any other suitable parameters or configurations associated with CC1 and CC2. The first cell CC1 may be a Pcell, SpCell, Scell and / or any other type of cell. The second cell CC2 may be a Pcell, SpCell, Scell and / or any other type of cell.
[0125] The cell configurations may each be associated with a serving cell index. In some aspects, the first UE 815a may be configured with one or more CLI-SRS transmission resources and / or parameters. In this regard, multiple UEs operating in each cell CC1, CC2 may be configured with the same CLI-SRS transmission resources. Therefore, the CLI-SRS transmission resources or configurations may be referred to as cell-level resources or configurations.
[0126] At action 804, BS 805 sends at least one of a UL grant or an SRS activation signal associated with CC1, and the first UE 815a receives at least one of the UL grant or the SRS activation signal associated with CC1. The UL grant may indicate the time / frequency resources on CC1 for PUCCH and / or PUSCH. In other aspects, action 804 may include receiving a DL communication signal. The DL communication signal may include DCI and / or DL data. The first UE 815a may be configured to send ACK / NACK for DL data based on a HARQ protocol. In some aspects, SRS activation communication may include DCI communication to dynamically trigger one or more non-periodic SRS opportunities. In other aspects, SRS activation communication may include MAC-CE communication to activate a semi-persistent SRS resource set.
[0127] As discussed further below, the UL grant and / or SRS activation communicated at action 804 may trigger or indicate communication of the first UE 815a for a set of time / frequency resources on CC1 or on another cell. In some aspects, the set of time / frequency resources indicated in the UL grant and / or SRS activation may indicate one or more time windows for the first UE 815a to send UL communications and / or SRS. On the other hand, if the first UE 815a receives a DL signal at action 804, the UE 815a may be configured to send a response within the one or more time windows.
[0128] At action 806, BS 805 sends a CLI-SRS activation for one or more CLI-SRS resources on the second cell CC2, and the first UE 815a receives the CLI-SRS activation for one or more CLI-SRS resources on the second cell CC2. In some aspects, the CLI-SRS activation communication may include a DCI communication to dynamically trigger one or more non-periodic CLI-SRS opportunities. In other aspects, the CLI-SRS activation communication may include a MAC-CE communication to activate a semi-persistent CLI-SRS resource set. However, in some aspects, method 800 may not include receiving CLI-SRS activation. For example, the first UE 815a may be configured with a periodic CLI-SRS resource set that is activated based on the cell configuration for CC2 received at action 802. The CLI-SRS resource set may include periodic, semi-persistent and / or non-periodic CLI-SRS resource sets. Therefore, UE 815a can apply the CLI-SRS resource set indicated for CC2.
[0129] In some aspects, the CLI-SRS resource set for the serving cell may include one or more CLI-SRS opportunities that occupy the time resource set. In some instances, one or more of the CLI-SRS opportunities may at least partially overlap in time with UL communications or SL communications scheduled based on the UL grant, SRS activation, and / or DL communications received at action 806, although scheduled for different cells. Fig.15 An example of an overlapping timing configuration is illustrated in FIG. Fig.15 As shown in , the UE may receive PDCCH and PDSCH transmission 1502 on CC1. In some aspects, the PDCCH may include a DCI indicating a UL grant for PUSCH 1504 in a time window that occurs simultaneously with the CLI-SRS resource. In other aspects, the PDCCH and / or PDSCH may indicate or trigger a PUCCH that carries HARQ-ACK communications in the PUCCH / PUSCH resource 1504. In the illustrated example, the PUCCH / PUSCH transmission 1504 overlaps in time with the CLI-SRS resource 1506. Although scheduled for different cells, the UE 815a may be affected by a transmit power limit or rule for simultaneous transmission of CLI-SRS 1506 and PUCCH / PUSCH 1504. For example, for simultaneous transmission within a frequency range, the first UE 815a may be limited to a transmit power P_cmax. Therefore, the first UE 815a may be configured to allocate power to UL and / or SL transmissions based on power allocation prioritization.
[0130] At action 808, the first UE 815a determines the power allocation for CLI-SRS on CC2 and UL communications on CC1 based on the CLI-SRS power allocation priority configuration. According to aspects of the present disclosure, the first UE 815a may be configured with a CLI-SRS power allocation priority configuration. In some aspects, the CLI-SRS priority configuration may include or indicate the CLI-SRS power allocation priority configuration. For example, the CLI-SRS power allocation priority configuration may include or indicate the priority ranking of the CLI-SRS relative to other UL / SL communications. For example, the CLI-SRS power allocation priority configuration may indicate the power allocation priority of multiple UL communications (including CLI-SRS communications). In some aspects, the CLI-SRS power allocation priority configuration may indicate eight or more priority rankings according to the following table:
[0131]
[0132] On the other hand, the order of numbers 6 and 7 in the above table can be switched so that the CLI-SRS power allocation priority configuration follows the following table:
[0133]
[0134] As indicated above, CLI-SRS transmissions may be ordered relative to other UL communications. In addition, CLI-SRS transmissions of one timing type (e.g., aperiodic, semi-persistent) may be prioritized relative to other CLI-SRS transmissions of another timing type (e.g., semi-persistent, periodic). Non-CLI SRS transmissions may similarly be prioritized based on timing type.
[0135] In other aspects, the CLI-SRS may be ranked equally with the non-CLI SRS. In other aspects, the CLI-SRS may be ranked lower than the non-CLI SRS. In some aspects, the aperiodic CLI-SRS may have a different priority rank relative to other UL communications than the semi-persistent and / or periodic CLI-SRS. For example, in some aspects, the aperiodic CLI-SRS may have a higher power allocation priority ranking than the PUSCH that does not carry UCI and / or CSI.
[0136] At action 810, the first UE 815a sends a CLI-SRS on CC2 based on the priority allocation prioritization described above with respect to action 808. At action 812, based on the priority allocation prioritization discussed above, the first UE 815a sends UL communications on CC1, and the BS 805 receives the UL communications. In some aspects, the power allocation prioritization may result in more power being allocated to the CLI-SRS on CC2 or the UL communications on CC1.
[0137] Fig. 9 is a signaling diagram illustrating a method 900 for handling collisions between a CLI-SRS and one or more other UL and / or SL communications scheduled for transmission according to aspects of the present invention. Fig. 9 The action is performed by the first UE 915a, the second UE 915b and the BS 905. For example, the UE 915 may be Figure 1A or Figure 2 In some aspects, Fig. 9 One or more actions may be performed by executing computer code to perform Fig. 9 The functionality shown in FIG. 1 is performed by a processor in the UE. Fig. 9 In method 900, the first UE 915a can resolve conflicts between scheduled UL communications and conflicts between UL and SL communications.
[0138] At action 902, BS 905 sends a cell configuration of at least a first cell, and a first UE 915a receives the configuration. In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. The cell configuration may indicate a CC and / or a BWP or be associated with a CC and / or a BWP. In some aspects, the cell configuration indicates a Uu BWP and a SL BWP. In some aspects, the Uu BWP and the SL BWP are associated with the same cell or CC. In other aspects, the Uu BWP and the SL BWP are associated with different cells or CCs.
[0139] At action 904, the BS 905 sends at least one of a UL grant or an SRS activation signal associated with the Uu BWP, and the first UE 915a receives at least one of the UL grant or the SRS activation signal associated with the Uu BWP. The UL grant may indicate the time / frequency resources for PUCCH and / or PUSCH. In other aspects, action 904 may include receiving a DL communication signal. The DL communication signal may include DCI and / or DL data. The first UE 915a may be configured to send ACK / NACK for DL data based on a HARQ protocol. In some aspects, the SRS activation communication may include DCI communication to dynamically trigger one or more non-periodic SRS opportunities. In other aspects, the SRS activation communication may include MAC-CE communication to activate a semi-persistent SRS resource set.
[0140] As discussed further below, the UL grant and / or SRS activation communicated at action 904 may trigger or indicate communication by the first UE 915a for a set of time / frequency resources. In some aspects, the set of time / frequency resources indicated in the UL grant and / or SRS activation may indicate one or more time windows for the first UE 915a to send UL communications and / or SRS. On the other hand, if the first UE 915a receives a DL signal at action 904, the UE 915a may be configured to send a response within the one or more time windows.
[0141] At action 906, the BS 905 sends a CLI-SRS activation associated with the first cell, and the first UE 915a receives the CLI-SRS activation associated with the first cell. In some aspects, the CLI-SRS activation communication may include a DCI communication to dynamically trigger one or more non-periodic CLI-SRS opportunities. In other aspects, the CLI-SRS activation communication may include a MAC-CE communication to activate a semi-persistent CLI-SRS resource set. However, in some aspects, the method 900 may not include receiving a CLI-SRS activation. For example, the first UE 915a may be configured with a periodic CLI-SRS resource set that is activated based on the cell configuration received at action 902. The CLI-SRS resource set may include periodic, semi-persistent and / or non-periodic CLI-SRS resource sets. Therefore, the UE 915a can apply the CLI-SRS resource set indicated for the serving cell.
[0142] At action 908, the second UE 915b sends a SL communication, and the first UE 915a receives the SL communication. For example, the SL communication may include a PSSCH communication. In some aspects, the PSSCH may trigger the first UE 915a to send a SL feedback communication in a time window. For example, the PSSCH may trigger the first UE 915a to send a PSFCH communication in the time window.
[0143] In some aspects, the CLI-SRS resource set for the serving cell may include one or more CLI-SRS opportunities that occupy the time resource set. In some instances, one or more of the CLI-SRS opportunities may overlap at least partially in time with UL communications associated with the UL grant of action 904 and / or SL feedback communications associated with the SL communications of action 908. In some aspects, one or more of the CLI-SRS opportunities may also overlap at least partially in frequency with UL communications and / or SL communications. Therefore, the first UE 915a may experience a scheduling conflict or collision within at least one time window between Uu communications and SL communications.
[0144] At action 910, the first UE 915a resolves the scheduling conflict for the time window. In method 900, the first UE 915a can be configured to first resolve conflicts for Uu communications scheduled for the Uu BWP, and then resolve conflicts between Uu communications and any SL communications. Therefore, the CLI-SRS priority configuration may include or indicate the priority of the CLI-SRS relative to other Uu communications and SL communications. In some aspects, the first UE 915a can use one or more aspects of the conflict resolution of method 700 described above to determine the prioritization of Uu communications.
[0145] refer to Fig. 9 and Fig.14 , a conflict resolution may be used in a fourth full-duplex communication scenario 1400. In some aspects, the cell configuration may provide both Uu communications and SL communications. Thus, the UE may be configured to send and / or receive SL communications in at least a first portion of the CC and to send and / or receive Uu communications in at least a second portion of the CC. For purposes of this disclosure, Uu communications sent by the UE may be referred to as UL communications. Scenario 1400 may occur in at least a first carrier including a Uu bandwidth part (BWP) and a SL BWP.
[0146] For example, the first UE 715a may receive PSCCH and / or PSSCH communications 1402 on the SL BWP. In some aspects, the PSCCH / PSSCH may indicate or trigger sidelink feedback communications in the PSFCH resources 1408. The first UE 715a may also receive an activation signal 1404 on the Uu BWP that activates or indicates a CLI-SRS resource 1412. As explained above, receiving the activation signal 1404 may include receiving a MAC-CE that activates a semi-persistent CLI-SRS resource set. On the other hand, receiving the activation signal 1404 may include receiving a DCI that indicates an aperiodic CLI-SRS resource or resource set. The first UE 715a may also receive a non-CLI-SRS activation 1406 on the Uu BWP that activates or indicates a non-CLI SRS resource 1410. In some aspects, the SRS resource 1410 may be a semi-persistent SRS resource or an aperiodic SRS resource.
[0147] The CLI-SRS resource 1412 collides / conflicts with the scheduled SRS resource 1410 in the Uu BWP and with the scheduled PSFCH resource 1408 in the SL BWP. According to aspects of the present disclosure, action 910 may include resolving the Uu conflict and then resolving the SL conflict.
[0148] In some aspects, SL communications may be associated with a prioritization scheme. For example, SL communications may be prioritized from 1 to 8 based on the SL communication type. The priority of SL communications may be based on the data or logical channel carried by the SL communications. In other aspects, Uu communications may be associated with a priority index of 0 or 1, where 1 indicates the highest priority. To determine the prioritization of Uu communications relative to SL communications, the CLI-SRS priority configuration may include or indicate one or more SL priority rank thresholds associated with eight SL priority rank values to determine whether Uu communications have a higher or lower priority than SL communications.
[0149] For example, the CLI-SRS priority configuration may indicate a first threshold. The first threshold may correspond to one of the SL communication priority ranks in the SL communication priority rank. In some aspects, SL priority rank 1 may be the highest priority, while SL priority rank 8 may be the lowest priority. The first threshold may indicate that any SL communication above the threshold (i.e., a lower priority index such as priority index 1, 2, etc.) has a higher priority than any Uu / UL communication. For example, the first threshold may indicate that the corresponding SL communication has a higher priority than the URLLC Uu communication with a priority index of 1 and all other Uu communications with a priority index of 0. The CLI-SRS priority configuration may also indicate a second threshold. The second threshold may also correspond to one of the SL communication priority ranks in the SL communication priority rank. The second threshold may indicate that any SL communication above the second threshold has a higher priority than the Uu communication with a priority of 0, rather than the Uu communication with a priority of 1. For example, the second threshold may indicate that the SL communication between the first threshold and the second threshold has a higher priority than the Uu communication with a priority index of 0, rather than the URLLC Uu communication with a priority index of 1. Furthermore, SL communications having a priority lower than a second threshold (ie, a higher priority index value such as priority index 7, 8, etc.) may have a lower priority than Uu communications having a priority index of 0 or 1.
[0150] At action 912, the first UE 915a transmits at least one of the PSFCH communication or the CLI-SRS, and the second UE 915b receives at least one of the PSFCH communication or the CLI-SRS. At action 914, the first UE 915a transmits the UL communication or the non-CLI SRS associated with action 904, and the BS 905 receives the UL communication or the non-CLI SRS associated with action 904. In this regard, in some aspects, the first UE 915a may first resolve the conflict of the Uu communication. For example, referring to Fig.14, the first UE 915a may resolve the conflict between the SRS and the CLI-SRS. In one example, the CLI-SRS is an aperiodic CLI-SRS, and the first UE 915a prioritizes the aperiodic CLI-SRS over the aperiodic SRS 1410. Therefore, at action 914, the first UE 915a may discard or prohibit sending the non-CLI SRS 1410 in the scheduled time window. In another example, the first UE 915a may prioritize the non-CLI SRS or another UL communication over the CLI-SRS based on the CLI-SRS priority configuration.
[0151] Once the Uu prioritization is determined, the first UE 915a may determine the prioritization between any SL communications that conflict with the remaining Uu communications. Fig.14 In the example of FIG. 14 , if CLI-SRS 1412 takes precedence over non-CLI SRS 1412, the first UE 915a may determine the priority of PSFCH 1408 relative to CLI-SRS 1412. If CLI-SRS 1412 has a higher priority than PSFCH 1408, the first UE 915a may send CLI-SRS 1412 and discard PSFCH 1408. In another example, if PSFCH 1408 takes precedence over CLI-SRS 1412, the first UE 915a may send PSFCH 1408 and discard CLI-SRS 1412.
[0152] In some aspects, the Uu BWP and the SL BWP may be associated with different subcarrier spacings (SCS). In some aspects, the Uu BWP and the SL BWP may be associated with different SCSs even if associated with the same CC. For example, the Uu BWP may be associated with an SCS of 15kHz and the SL BWP may be associated with an SCS of 30kHz. In another example, the Uu BWP may be associated with an SCS of 60kHz and the SL BWP may be associated with an SCS of 30kHz. In another example, the Uu BWP may be associated with an SCS of 30kHz and the SL BWP may be associated with an SCS of 15kHz. In some aspects, the CLI-SRS may be sent based on the Uu BWP or the SLBWP. In one aspect of the present disclosure, if the SCS of the Uu BWP is different from the SCS of the SL BWP, a time gap may be defined for the transmission of the CLI-SRS on the SL BWP. Fig.14 The time interval 1414 between the transmission of the PSFCH 1408 and the transmission of the CLI-SRS on the SL BWP is illustrated.
[0153] As described above, in some aspects, the CLI-SRS may be communicated in a Uu BWP or on a SL BWP. According to one aspect of the present disclosure, if the CLI-SRS is communicated on a Uu BWP, the priority of the CLI-SRS may be determined as Uu communication. Therefore, the prioritization of the CLI-SRS may be first determined relative to other Uu communications using the techniques described above with respect to method 700, and then the priority of the CLI-SRS relative to any conflicting SL communications may be determined as described above. On the other hand, if the CLI-SRS is communicated on a SL BWP, the priority of the CLI-SRS may be determined as SL communication so that any Uu conflicts are resolved first, and then the priority of the CLI-SRS may be determined relative to the remaining Uu communications. On the other hand, the CLI-SRS priority may be considered as both Uu communication and SL communication. For example, in one aspect, the first UE 915a may determine the priority of the CLI-SRS based on whether the priority of the CLI-SRS would be higher if it were considered as Uu communication or SL communication.
[0154] Fig.10 is a signaling diagram illustrating a method 1000 for power allocation for CLI-SRS and one or more other UL and SL communications scheduled for transmission in accordance with aspects of the present disclosure. Fig.10 The action is performed by the first UE 1015a, the second UE 1015b and the BS 1005. For example, the UE 1015 may be Figure 1A or Figure 2 In some aspects, Fig.10 One or more actions may be performed by executing computer code to perform Fig.10 The functionalities shown in the method 1000 may be performed by a processor in a UE. One or more UEs in UE 1015 may be configured for carrier aggregation (CA), in which UE 1015 is configured with two or more serving cells. In addition, in method 1000, one or more UEs in UE may be configured to allocate power to Uu communication and SL communication transmitted simultaneously on different CCs.
[0155] At action 1002, BS1005 sends cell configurations for a first Uu cell (Uu CC1), a second Uu cell (Uu CC2), and a cell including at least one SL BWP (SL CC), and the first UE 1015a receives the cell configurations for the first Uu cell (Uu CC1), the second Uu cell (Uu CC2), and a cell including at least one SL BWP (SL CC). It will be understood that the SLCC may also include one or more Uu BWPs. In addition, in some aspects, Uu CC1 may include a Uu BWP and a SL BWP. In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. The cell configuration may be associated with Uu communication and / or SL communication. The cell configuration may indicate UL, DL, and / or SL BWP configurations, measurement parameters, DL control channel monitoring configurations, timing advance parameters, beam management parameters, and / or any other suitable parameters or configurations associated with Uu CC1 and Uu CC2. The cell may include a Pcell, a SpCell, a Scell, and / or any other type of cell.
[0156] The cell configurations may each be associated with a serving cell index. In some aspects, the first UE 1015a may be configured with one or more CLI-SRS transmission resources and / or parameters. In this regard, multiple UEs operating in each cell Uu CC1, Uu CC2, SL CC may be configured with the same CLI-SRS transmission resources. Therefore, the CLI-SRS transmission resources or configurations may be referred to as cell-level resources or configurations.
[0157] At action 1004, BS1005 sends at least one of a UL grant or an SRS activation signal associated with Uu CC1, and the first UE 1015a receives at least one of the UL grant or the SRS activation signal associated with Uu CC1. The UL grant may indicate the time / frequency resources on Uu CC1 for PUCCH and / or PUSCH. In other aspects, action 1004 may include receiving a DL communication signal. The DL communication signal may include DCI and / or DL data. The first UE 1015a may be configured to send ACK / NACK for DL data based on a HARQ protocol. In some aspects, the SRS activation communication may include DCI communication to dynamically trigger one or more non-periodic SRS opportunities. In other aspects, the SRS activation communication may include MAC-CE communication to activate a semi-persistent SRS resource set.
[0158] As discussed further below, the UL grant and / or SRS activation communicated at action 1004 may trigger or indicate communication by the first UE 1015a for a set of time / frequency resources on CC1 or on another cell. In some aspects, the set of time / frequency resources indicated in the UL grant and / or SRS activation may indicate one or more time windows for the first UE 1015a to send UL communications and / or SRS. On the other hand, if the first UE 1015a receives a DL signal at action 1004, the UE 1015a may be configured to send a response within the one or more time windows.
[0159] At action 1006, BS1005 sends a CLI-SRS activation for one or more CLI-SRS resources on the second cell Uu CC2, and the first UE 1015a receives the CLI-SRS activation for one or more CLI-SRS resources on the second cell Uu CC2. In some aspects, the CLI-SRS activation communication may include a DCI communication to dynamically trigger one or more non-periodic CLI-SRS opportunities. In other aspects, the CLI-SRS activation communication may include a MAC-CE communication to activate a semi-persistent CLI-SRS resource set. However, in some aspects, method 1000 may not include receiving CLI-SRS activation. For example, the first UE 1015a may be configured with a periodic CLI-SRS resource set that is activated based on the cell configuration for Uu CC2 received at action 1002. For example, the first UE 1015a may be configured with a lookup table of CLI-SRS resource sets associated with each of a plurality of serving cells. The CLI-SRS resource set may include periodic, semi-persistent and / or aperiodic CLI-SRS resource sets. Thus, the UE 1015a may apply the CLI-SRS resource set indicated for Uu CC2.
[0160] At action 1008, the second UE 1015b sends a SL communication on the SL CC, and the first UE 1015a receives the SL communication on the SL CC. In some aspects, the SL communication may include PSCCH and / or PSSCH communication. In some aspects, the SL communication may indicate or trigger feedback SL communication. For example, the SL communication may indicate or trigger PSFCH communication on the SL CC for a time window.
[0161] In some instances, despite being scheduled for different cells, one or more of the CLI-SRS opportunities may at least partially overlap in time with one or more other UL communications and / or SL communications. Fig.16 An example of an overlapping timing configuration is illustrated in FIG. Fig.16As shown in , the UE may be configured with periodic SRS resources 1602 on Uu CC1. In addition, the UE may receive a CLI-SRS activation 1606 on Uu CC2 that activates CLI-SRS resources for at least one CLI-SRS transmission 1608 on Uu CC2. In addition, the UE may have SL communications scheduled on the SL CC. In some aspects, the SL communications may include PSFCH communications 1604 in response to PSCCH and / or PSSCH communications. In the illustrated example, the CLI-SRS 1608 conflicts in time with the non-CLI SRS 1602 and the PSFCH 1604. However, the CLI-SRS 1608, SRS 1602, and PSFCH 1604 may be scheduled on different CCs or frequency resources so that they can be communicated simultaneously.
[0162] Although scheduled for different cells, the UE 1015a may be affected by the transmit power restrictions or rules for the simultaneous transmission of CLI-SRS 1608, non-CLISRS 1602, and PSFCH 1604. For example, for simultaneous transmission within the frequency range, the first UE 1015a may be limited to a transmit power of P_cmax. Therefore, the first UE 1015a may be configured to allocate power to UL and / or SL transmissions based on power allocation prioritization.
[0163] At action 1010, the first UE 1015a determines the power allocation for CLI-SRS on CC2, UL communication on CC1, and SL communication on SL CC based on the CLI-SRS power allocation priority configuration. According to various aspects of the present disclosure, the first UE 1015a may be configured with a CLI-SRS power allocation priority configuration. In some aspects, the CLI-SRS priority configuration may include or indicate the CLI-SRS power allocation priority configuration. For example, the CLI-SRS power allocation priority configuration may include or indicate the priority ranking of CLI-SRS relative to other UL / SL communications. For example, the CLI-SRS power allocation priority configuration may indicate the power allocation priority of multiple UL communications (including CLI-SRS communications). In some aspects, the CLI-SRS power allocation priority configuration may be similar or identical to the CLI-SRS power allocation priority configuration described above with respect to method 800.
[0164] In some aspects, the first UE 1015a can determine the power allocation prioritization of Uu and SL communications based on section 16.2.4 of 3GPP specification TS 38.213v16.8.0, the entire contents of which are incorporated herein by reference. As described above, in some aspects, the CLI-SRS can be communicated in the Uu BWP or on the SL BWP. According to one aspect of the present disclosure, if the CLI-SRS is communicated on the Uu BWP, the power allocation prioritization of the CLI-SRS can be determined as Uu communication. According to another aspect of the present disclosure, if the CLI-SRS is communicated on the SL BWP, the power allocation prioritization of the CLI-SRS can be determined as SL communication. On the other hand, the CLI-SRS power allocation prioritization can be regarded as both Uu and SL communications. For example, in one aspect, the first UE 915a can determine the power allocation prioritization of the CLI-SRS based on whether the power allocation prioritization of the CLI-SRS will be higher if it is regarded as Uu communication or SL communication.
[0165] Fig.17 is a block diagram of an exemplary BS 1700 according to some aspects of the present disclosure. BS 1700 may be as described above. Figure 1A The BS 105 in the network 100 discussed above and / or Figures 7 to 10 1005. As shown, BS 1700 may include a processor 1702, a memory 1704, a transceiver 1710 including a modem subsystem 1712 and an RF unit 1714, and one or more antennas 1716. These elements may communicate with each other directly or indirectly, for example, via one or more buses.
[0166] The processor 1702 may have various features as a particular type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1702 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0167] The memory 1704 may include cache memory (e.g., cache memory of the processor 1702), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid-state memory device, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 1704 may include a non-transitory computer-readable medium. The memory 1704 may store instructions 1706. The instructions 1706 may include instructions that, when executed by the processor 1702, cause the processor 1702 to cause other components of the base station 1700 to communicate with the UE 1800 (such as by sending a configuration, etc.), and instructions with respect to Figures 7 to 10 The instructions 1706 may also be referred to as code, which may be broadly interpreted as including the following with respect to Fig.19 Any type of computer-readable statement as described.
[0168] In some aspects, the CLI-SRS module 1708 may be configured to facilitate the measurement of the CLI. For example, the CLI-SRS module 1708 may be configured to cause the transceiver 1710 to send a CLI-SRS priority configuration to one or more UEs. In other aspects, the CLI-SRS module 1708 may be configured to activate CLI-SRS resources and / or other DL, UL and / or other communication resources for one or more UEs to prevent or resolve potential conflicts or scheduling conflicts between CLI-SRS resources and other UL / DL / SL resources. In some aspects, the CLI-SRS priority configuration may be based on or associated with a cell configuration. Therefore, in some aspects, the CLI-SRS may be associated with a CLI-SRS resource configured for multiple wireless communication devices in a cell. In some aspects, the CLI-SRS priority configuration may be associated with one or more CLI-SRS prioritization rules for conflict resolution and / or for allocating power for simultaneous Uu and / or SL communications, as described above with respect to methods 700 to 1000 and scenarios 1100 to 1600. In some aspects, the CLI-SRS module 1708 may be configured to perform Fig. 20 One or more steps, actions and / or other aspects of method 2000 shown in .
[0169] As shown, the transceiver 1710 may include a modem subsystem 1712 and an RF unit 1714. The transceiver 1710 may be configured to communicate bidirectionally with other devices, such as UE 115 and / or another core network element. The modem subsystem 1712 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 1714 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., SSB, RMSI, MIB, SIB, frame-based equipment—FBE configuration, PRACH configuration PDCCH, PDSCH) from the modem subsystem 1712 (for outbound transmission) or from another source (e.g., UE 115, node 315, and / or BS 1700). The RF unit 1714 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in the transceiver 1710, the modem subsystem 1712 and / or the RF unit 1714 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.
[0170] The RF unit 1714 may provide modulated and / or processed data, such as data packets (or more generally, data messages that may include one or more data packets and other information), to the antenna 1716 for transmission to one or more other devices. The antenna 1716 may be similar to the antenna of the BS 105 discussed above. This may include, for example, information transmission for completing attachment to the network and communication with the occupied UE 115 according to some aspects of the present disclosure. The antenna 1716 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 1710. The transceiver 1710 may provide the demodulated and decoded data (e.g., PUCCH control information, PRACH signals, PUSCH data) to the processor 1702 for processing. The antenna 1716 may include multiple antennas of similar or different designs to maintain multiple transmission links.
[0171] In one aspect, the BS 1700 may include multiple transceivers 1710 that implement different RATs (e.g., NR and LTE). In one aspect, the BS 1700 may include a single transceiver 1710 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1710 may include various components, where different combinations of components may implement different RATs.
[0172] Fig.181 is a block diagram of an exemplary UE 1800 according to some aspects of the present disclosure. The UE 1800 may be as described above. Figures 7 to 10 UE 115 or UE 215 in question. As shown, UE 1800 may include a processor 1802, a memory 1804, a CLI-SRS module 1808, a transceiver 1810 including a modem subsystem 1812 and a radio frequency (RF) unit 1814, and one or more antennas 1816. These elements may be coupled to each other. The term "coupled" may refer to being directly or indirectly coupled or connected to one or more intervening elements. For example, these elements may communicate directly or indirectly with each other, for example, via one or more buses.
[0173] The processor 1802 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1802 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. The processor 1802 may correspond to the application processor (AP) discussed above, on which the OS 311 (and HLOS 911) runs.
[0174] Memory 1804 may include cache memory (e.g., cache memory of processor 1802), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 1804 includes a non-transitory computer-readable medium. Memory 1804 may store or have recorded thereon instructions 1806. Instructions 1806 may include instructions that, when executed by processor 1802, cause processor 1802 to perform various aspects of the present disclosure described herein (e.g., Figures 7 to 10 Instructions 1806 may include instructions for the operations described with reference to UE 115. Instructions 1806 may also be referred to as code. Code may include any type of computer-readable statements.
[0175] The CLI-SRS module 1808 may be implemented via hardware, software, or a combination thereof. For example, the CLI-SRS module 1808 may be implemented as a processor, circuit, and / or instructions 1806 stored in the memory 1804 and executed by the processor 1802 .
[0176] In some aspects, the CLI-SRS module 1808 may be configured to send and / or receive SRS to facilitate measurement of CLI. For example, the CLI-SRS module 1808 may be configured to cause the transceiver 1810 to send CLI-SRS to one or more other UEs and / or to one or more BSs. In some aspects, the CLI-SRS may be similar or identical to a non-CLI SRS. In some aspects, the CLI-SRS may be based on or associated with a cell configuration. Therefore, in some aspects, the CLI-SRS may be associated with a CLI-SRS resource configured for multiple wireless communication devices in a cell.
[0177] In another aspect of the present disclosure, the CLI-SRS module 1808 may be configured to communicate the CLI-SRS based on the CLI-SRS timing or time configuration. In some aspects, the CLI-SRS time configuration may be periodic, semi-persistent, or aperiodic. In some aspects, the CLI-SRS module 1808 may be configured to communicate the CLI-SRS based on the CLI-SRS priority configuration. In some aspects, the CLI-SRS priority configuration may be statically configured or hard-coded at the UE 1800. In other aspects, the CLI-SRS priority configuration may be an RRC configuration. In some aspects, the CLI-SRS priority configuration may be associated with one or more CLI-SRS prioritization rules for conflict resolution and / or for allocating power for simultaneous Uu and / or SL communications, as described above with respect to methods 700 to 1000 and scenarios 1100 to 1600.
[0178] As shown, the transceiver 1810 may include a modem subsystem 1812 and an RF unit 1814. The transceiver 1810 may be configured to communicate bidirectionally with other devices (such as BSs 105 and 1700).
[0179] The modem subsystem 1812 may be configured to modulate and / or encode data from the memory 1804 and the CLI-SRS module 1808 according to a modulation and coding scheme (MCS) (e.g., a low density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 1814 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., PUSCH data, PUCCH UCI, MSG1, MSG3, etc.) or the modulated / encoded data transmitted from another source (e.g., UE 115, BS 185, or anchor). The RF unit 1814 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 1810, the modem subsystem 1812 and the RF unit 1814 may be separate devices that are coupled together at the UE 1800 to enable the UE 1800 to communicate with other devices.
[0180] The RF unit 1814 can provide modulated and / or processed data, such as data packets (or more generally, data messages that can include one or more data packets and other information) to the antenna 1816 for transmission to one or more other devices. The antenna 1816 can also receive data messages sent from other devices. The antenna 1816 can provide the received data message for processing and / or demodulation at the transceiver 1810. The transceiver 1810 can provide demodulated and decoded data (e.g., RRC configuration, MIB, PDSCH data and / or PDCCH DCI, etc.) to the CLI-SRS module 1808 for processing. The antenna 1816 may include multiple antennas of similar or different designs to maintain multiple transmission links.
[0181] In one aspect, the UE 1800 may include multiple transceivers 1810 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 1800 may include a single transceiver 1810 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 1810 may include various components, where different combinations of components may implement different RATs.
[0182] Fig.191 is a flow chart of a method 1900 for communicating a CLI-SRS based on a CLI-SRS priority configuration in accordance with aspects of the present disclosure. The steps, actions, or aspects of the method 1900 may be performed by a UE, such as the UE 1800 and / or one of the UEs 115 and / or 215 of the networks 100, 200, respectively. In some aspects, the UE 1800 may perform the actions of the method 1900 using one or more components, such as a processor 1802, a memory 1804, a CLI-SRS module 1808, a transceiver 1810, and / or one or more antennas 1816.
[0183] At action 1910, the UE receives a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing or time configuration. In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. For example, the cell configuration may include one or more RRC configurations. Thus, receiving the cell configuration may include receiving one or more RRC information elements (IEs). In some aspects, the cell configuration may indicate a CC and / or a BWP or be associated with a CC and / or a BWP. The cell configuration may include or indicate a Uu BWP and / or a SL BWP. The cell configuration may indicate UL, DL and / or SL BWP configurations, measurement parameters, DL control channel monitoring configurations, timing advance parameters, beam management parameters and / or any other suitable parameters or configurations associated with a first cell. The first cell may be a primary cell (Pcell), a special cell (SpCell), a secondary cell (Scell) and / or any suitable type of cell. In some aspects, receiving the cell configuration includes more than one cell configuration communications associated with more than one serving cell. For example, the UE may be configured to operate in a carrier aggregation (CA) mode in which the UE may communicate with more than one serving cell. For example, the UE may receive a cell configuration for a Pcell and at least one Scell. In some aspects, action 1910 includes receiving a first RRC IE indicating a Uu BWP configuration and a second RRC IE indicating a SL BWP or frequency resource configuration. In some aspects, the RRC IE may be associated with the same set of frequency resources. Thus, in some aspects, the RRC IE and therefore the Uu BWP and the SL BWP may be associated with the same CLI-SRS timing configuration and / or CLI-SRS priority configuration, as further explained below.
[0184] The cell configuration may be associated with a serving cell index. In some aspects, a UE may be configured with one or more CLI-SRS transmission resources and / or parameters. In this regard, multiple UEs operating in a cell may be configured with the same CLI-SRS transmission resources. Therefore, a CLI-SRS transmission resource or configuration may be referred to as a cell-level resource or configuration. Each CLI-SRS transmission resource may be associated with a serving cell index.
[0185] At action 1920, the UE sends a first communication in a first time period based on CLI-SRS timing and CLI-SRS priority configuration. In some aspects, a second communication is scheduled for at least a portion of the first time period. In some aspects, one of the first communication or the second communication includes a CLI-SRS. In some aspects, sending the first communication includes sending a CLI-SRS. In some aspects, the sending of the CLI-SRS may be based on CLI-SRS activation that activates semi-persistent or non-periodic resources. In other aspects, the CLI-SRS sending may be based on a periodically configured CLI-SRS resource set. The CLI-SRS may be sent during a CLI-SRS measurement window configured for one or more other UEs in the network.
[0186] In some aspects, the CLI-SRS priority configuration may indicate one or more of the rules described above. In other aspects, the CLI-SRS priority configuration may indicate the priority of the CLI-SRS relative to other CLI-SRS and / or other UL / SL communications. In other aspects, the CLI-SRS priority configuration may indicate a priority value or rank for each type of communication, including aperiodic CLI-SRS, semi-persistent CLI-SRS, periodic CLI-SRS, non-CLI SRS, PUCCH, PUSCH, PSSCH, PSCCH, PSFCH, and / or any other type of UL or SL communications.
[0187] In some aspects, action 1920 may include determining a priority for CLI-SRS transmission relative to one or more other UL and / or SL communications. For example, the UE may apply one or more CLI-SRS priority rules or configurations to resolve conflicts with CLI-SRS resources and other SL and / or UL resources or scheduled communications, as described above with respect to Figures 7 to 16 In some aspects, resolving conflicting (conflicting / colliding) resources may involve prohibiting the transmission of one communication and continuing to transmit another communication. In other aspects, resolving conflicting resources may involve discarding one or more overlapping symbols from at least one of the communications.
[0188] The CLI-SRS priority configuration may refer to one or more rules or protocols executed by the UE and / or BS to resolve and / or prevent a CLI-SRS resource from colliding with other UL / SL resources. In some aspects, the CLI-SRS priority configuration may be a static or hard-coded configuration. In addition, in some aspects, the CLI-SRS priority configuration may include a hard-coded BS configuration that may prevent activation or configuration of a UL / SL resource that will conflict with a CLI-SRS resource and / or may prevent activation or configuration of a CLI-SRS resource that will conflict with another UL / SL resource.
[0189] In some aspects, the UE may discard the CLI-SRS or one or more UL / SL scheduled resources. For example, the UE may determine which of the CLI-SRS or the simultaneous UL / SL communication is associated with a higher priority. Therefore, the UE may send the CLI-SRS or the simultaneous UL / SL communication based on a comparison of the priority of the CLI-SRS with the priority of the simultaneous UL / SL communication. In other aspects, the priority of the CLI-SRS relative to other UL / SL communications may depend on the time configuration and / or type of the UL / SL communication. In some aspects, the priority of the CLI-SRS may be based on the time configuration of the CLI-SRS. For example, the priority of the CLI-SRS relative to other UL / SL communications may be based on whether the CLI-SRS resource is periodic, semi-persistent or aperiodic. In some aspects, the priority of the CLI-SRS relative to another UL / SL communication may be based on whether the other UL / SL communication includes PUCCH communication, PUSCH communication, PSCCH communication, PSSCH communication, PSFCH communication and / or non-CLI SRS.
[0190] In one example, the UE may be configured to discard or prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUSCH with a priority index of 0. On the other hand, the UE may be configured to discard or prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUSCH with a priority index of 1. In some aspects, if the CLI-SRS resource is semi-persistent or periodic, the UE may be configured to prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUCCH carrying a channel state information (CSI) report, an RSRP report, and / or an SINR report. In some aspects, the UE may be configured to prohibit sending at least a portion of the CLI-SRS if the CLI-SRS collides with a PUCCH carrying HARQ-ACK information, a link recovery request, and / or a scheduling request. In some aspects, if the CLI-SRS resource is aperiodic, the UE may be configured to prohibit sending at least a portion of the PUCCH if the CLI-SRS collides with a PUCCH carrying a CSI report, an RSRP report, and / or an SINR report. In another aspect, the UE may be configured to refrain from sending at least a portion of the CLI-SRS if the periodic or semi-persistent CLI-SRS collides with the aperiodic non-CLI SRS. In another aspect, the UE may be configured to refrain from sending at least a portion of the non-CLI SRS if the CLI-SRS collides with the non-CLI SRS. In another aspect, the UE may be configured to refrain from sending at least a portion of the non-CLI SRS if the aperiodic CLI-SRS collides with the periodic or semi-persistent non-CLI SRS.
[0191] In some aspects, the UE may be configured to refrain from sending a dynamic PUSCH with priority 0 if the dynamic PUSCH will collide with a non-periodic CLI-SRS. On the other hand, the UE may be configured to refrain from sending an SPS PUSCH if the SPS PUSCH will collide with the non-periodic CLI-SRS. On the other hand, the UE may be configured to refrain from sending a CLI-SRS if the CLI-SRS will collide with a PUCCH carrying a scheduling request, a HARQ response, and / or a link recovery request. On the other hand, if the non-periodic CLI-SRS will collide with a configured grant (CG) PUSCH, the UE may be configured to discard the CG-PUSCH and send the CLI-SRS.
[0192] In other aspects, the UE may be configured to discard one or more overlapping symbols of the CLI-SRS or another UL / SL communication. For example, in some aspects, if the PUSCH and / or PUCCH with a priority of 1 overlaps with the CLI-SRS resource, the UE may discard the overlapping symbols of the CLI-SRS. On the other hand, if the non-periodic CLI-SRS will conflict with the periodic or semi-persistent SRS, the UE may discard the overlapping symbols of the periodic or semi-persistent SRS. On the other hand, if the non-periodic CLI-SRS will conflict with the periodic or semi-persistent CLI-SRS, the UE may discard the overlapping symbols of the periodic or semi-persistent CLI-SRS. On the other hand, if the non-periodic SRS will conflict with the semi-persistent or periodic CLI-SRS, the UE may discard the overlapping symbols of the CLI-SRS. On the other hand, if the semi-persistent CLI-SRS will conflict with the periodic SRS, the UE may be configured to discard the overlapping symbols of the periodic SRS. On the other hand, if the semi-persistent CLI-SRS would collide with the periodic CLI-SRS, the UE may be configured to drop the overlapping symbols of the periodic CLI-SRS.
[0193] In some aspects, the CLI-SRS priority configuration may indicate one or more of the rules described above. In other aspects, the CLI-SRS priority configuration may indicate the priority of the CLI-SRS relative to other CLI-SRS and / or other UL / SL communications. In other aspects, the CLI-SRS priority configuration may indicate a priority value or rank for each type of communication, including aperiodic CLI-SRS, semi-persistent CLI-SRS, periodic CLI-SRS, non-CLI SRS, PUCCH, PUSCH, PSSCH, PSCCH, PSFCH, and / or any other type of UL or SL communications.
[0194] In another aspect of the present disclosure, method 1900 may include simultaneously transmitting a second communication and / or a different communication based on a CLI-SRS power allocation priority configuration. For example, the UE may be configured with a CLI-SRS power allocation priority configuration. In some aspects, the CLI-SRS priority configuration may include or indicate a CLI-SRS power allocation priority configuration. For example, the CLI-SRS power allocation priority configuration may include or indicate a priority ranking of the CLI-SRS relative to other UL / SL communications. For example, the CLI-SRS power allocation priority configuration may indicate a power allocation priority for multiple UL communications (including CLI-SRS communications).
[0195] In some aspects, CLI-SRS transmissions may be ranked relative to other UL communications. In addition, CLI-SRS transmissions of one timing type (e.g., non-periodic, semi-persistent) may be prioritized relative to other CLI-SRS transmissions of another timing type (e.g., semi-persistent, periodic). Non-CLI SRS transmissions may be similarly prioritized based on timing type. In other aspects, CLI-SRS may be ranked equally with non-CLI SRS. In other aspects, CLI-SRS may be ranked lower than non-CLI SRS. In some aspects, non-periodic CLI-SRS may have a different priority rank relative to other UL communications than semi-persistent and / or periodic CLI-SRS. For example, in some aspects, non-periodic CLI-SRS may have a higher power allocation priority ranking than PUSCH that does not carry UCI and / or CSI.
[0196] Fig. 20 1 is a flow chart of a method 2000 for communicating a CLI-SRS based on a CLI-SRS priority configuration in accordance with aspects of the present disclosure. The steps, actions, or aspects of the method 2000 may be performed by a BS such as BS 1700 and / or one of BSs 105 and / or 205 of networks 100, 200, respectively. In some aspects, BS 1700 may use one or more components to perform the actions of the method 2000, such as processor 1702, memory 1704, CLI-SRS module 1708, transceiver 1710, and / or one or more antennas 1716.
[0197] At action 2010, the BS sends a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing or time configuration to the UE. In some aspects, the cell configuration may be referred to as a CC configuration and / or a BWP configuration. For example, the cell configuration may include one or more RRC configurations. Thus, receiving the cell configuration may include receiving one or more RRC information elements (IEs). In some aspects, the cell configuration may indicate a CC and / or a BWP or be associated with a CC and / or a BWP. The cell configuration may include or indicate a Uu BWP. In some aspects, the cell may also be associated with a SL BWP. In some aspects, action 2010 includes sending a first RRC IE including or indicating a CC configuration and a second RRC IE indicating a SL BWP configuration. The cell or frequency resource configuration may indicate UL, DL and / or SL BWP configurations, measurement parameters, DL control channel monitoring configurations, timing advance parameters, beam management parameters and / or any other suitable parameters or configurations associated with the first cell. The first cell may be a primary cell (Pcell), a special cell (SpCell), a secondary cell (Scell) and / or any suitable type of cell. In some aspects, receiving the cell configuration includes more than one cell configuration communication associated with more than one serving cell. For example, the UE may be configured to operate in a carrier aggregation (CA) mode in which the UE may communicate with more than one serving cell. For example, the UE may receive a cell configuration for a Pcell and at least one Scell.
[0198] The cell configuration may be associated with a serving cell index. In some aspects, a UE may be configured with one or more CLI-SRS transmission resources and / or parameters. In this regard, multiple UEs operating in a cell may be configured with the same CLI-SRS transmission resources. Therefore, a CLI-SRS transmission resource or configuration may be referred to as a cell-level resource or configuration. Each CLI-SRS transmission resource may be associated with a serving cell index.
[0199] At action 2020, the BS receives a first communication in a first time period based on CLI-SRS timing and CLI-SRS priority configuration. In some aspects, a second communication is scheduled for at least a portion of the first time period. In some aspects, one of the first communication or the second communication includes a CLI-SRS. In some aspects, receiving the first communication includes receiving a UL communication from a UE. In some aspects, method 2000 also includes sending a DL communication indicating a grant for the UL communication to the UE. In some aspects, the second indication may be a CLI-SRS. The CLI-SRS may be periodic, semi-persistent, or aperiodic. The CLI-SRS priority configuration may indicate that the first communication is associated with a higher priority than the second communication. For example, the CLI-SRS priority configuration may indicate that the scheduled UL communication has a higher priority than the overlapping CLI-SRS, so that the CLI-SRS is discarded by the UE. On the other hand, the UE may only truncate or discard overlapping symbols of the CLI-SRS.
[0200] In some aspects, the CLI-SRS priority configuration may indicate one or more of the rules described above. In other aspects, the CLI-SRS priority configuration may indicate the priority of the CLI-SRS relative to other CLI-SRS and / or other UL / SL communications. In other aspects, the CLI-SRS priority configuration may indicate a priority value or rank for each type of communication, including non-periodic CLI-SRS, semi-persistent CLI-SRS, periodic CLI-SRS, non-CLI SRS, PUCCH, PUSCH, PSSCH, PSCCH, PSFCH and / or any other type of UL or SL communication. In some aspects, at least one of the first communication or the second communication may include a CLI-SRS measurement report based on the CLI-SRS measured by the UE.
[0201] In some aspects, method 2000 may include steps, actions, and / or other aspects that correspond to the steps, actions, and / or other aspects of method 1900. For example, in some aspects, method 2000 may be complementary to method 1900.
[0202] The various illustrative blocks and modules described in conjunction with the present disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).
[0203] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software, hardware, firmware, hardware wiring, or any combination thereof executed by a processor. The features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), "or" as used in a list of items (e.g., "or" used in a list of items ending with "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).
[0204] As those skilled in the art will understand by now and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific implementations illustrated and described herein (as they are only some examples of the present disclosure), but should be fully equivalent to the attached claims and their functional equivalents.
[0205] Exemplary Aspects of the Disclosure
[0206] Specific implementation examples are described in the following numbered aspects:
[0207] Aspect 1. A wireless communication method performed by a user equipment (UE), the user equipment (UE) comprising: receiving a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, sending a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
[0208] Aspect 2. A method according to Aspect 1, wherein: the first communication is scheduled on a first frequency resource; the second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; and the method further includes: based on the CLI-SRS priority configuration, prohibiting the sending of the second communication in the first time period.
[0209] Aspect 3. A method according to Aspect 2, wherein: the first communication includes the CLI-SRS; the second communication includes at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission or a non-CLI SRS; the CLI-SRS is associated with a higher priority than the second communication; and prohibiting the transmission of the second communication is based on the CLI-SRS being associated with the higher priority than the second communication.
[0210] Aspect 4. A method according to Aspect 2, wherein: the first communication includes at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission or a non-CLI SRS; the second communication includes the CLI-SRS; the CLI-SRS is associated with a lower priority than the first communication; and prohibiting the transmission of the second communication includes prohibiting the transmission of the CLI-SRS based on the CLI-SRS being associated with the lower priority than the first communication.
[0211] Aspect 5. A method according to Aspect 1, wherein: the first communication is scheduled on a first frequency resource; the second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; the second communication is scheduled for a second time period that overlaps with the first time period by at least one overlapping symbol; the method also includes: based on the CLI-SRS priority configuration, discarding a portion of the second communication associated with the at least one overlapping symbol.
[0212] Aspect 6. A method according to any one of Aspects 1 or 5, wherein: the CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; sending the first communication includes sending the first communication on a first component carrier (CC) based on the CLI-SRS power allocation priority configuration; and the method also includes: sending the second communication on a second CC based on the CLI-SRS power allocation priority configuration and simultaneously with the first communication at the first time.
[0213] Aspect 7. A method according to Aspect 6, wherein: the first communication includes at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; the second communication includes the CLI-SRS; and the CLI-SRS is associated with a lower power allocation priority than the first communication.
[0214] Aspect 8. A method according to any one of Aspects 1 to 7, wherein: the cell configuration is associated with a component carrier (CC), the CC includes a Uu bandwidth part (BWP); the CLI-SRS configuration is associated with the Uu BWP and a side link (SL) BWP; and sending the first communication includes sending a first UL communication on the Uu BWP.
[0215] Aspect 9. A method according to Aspect 8, wherein: the Uu BWP is associated with a first subcarrier spacing (SCS), and the SL BWP is associated with a second SCS different from the first SCS; sending the first UL communication includes sending the CLI-SRS based on the first SCS; and the method further includes: sending SL communication on the SL BWP based on the second SCS after the gap duration after the sending of the first UL communication.
[0216] Aspect 10. A method according to aspect 8, wherein: the first UL communication includes the CLI-SRS scheduled for transmission on the UuBWP; the second communication includes a second UL communication scheduled for transmission on the Uu BWP; and transmitting the CLI-SRS is based on a first Uu priority of the CLI-SRS relative to a second Uu priority associated with the second UL communication.
[0217] Aspect 11. A method according to Aspect 8, wherein: the first UL communication includes the CLI-SRS scheduled for sending on the UuBWP; the second communication includes a first SL communication scheduled for sending on the SL BWP; and sending the CLI-SRS is based on a first SL priority associated with the CLI-SRS relative to a second SL priority associated with the first SL communication.
[0218] Aspect 12. A method according to Aspect 8, wherein: the first UL communication includes the CLI-SRS scheduled for sending on the UuBWP; the second communication includes a first SL communication scheduled for sending on the SL BWP; and sending the CLI-SRS is based on a first Uu priority associated with the CLI-SRS relative to a first SL priority associated with the first SL communication.
[0219] Aspect 13. A method according to Aspect 8, wherein: the CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; the first UL communication includes the CLI-SRS, and the CLI-SRS is scheduled for transmission on the UuBWP; the second communication includes a SL communication scheduled for transmission on the SL BWP; sending the first UL communication includes sending the CLI-SRS on the Uu BWP based on the CLI-SRS power allocation priority configuration and the Uu priority associated with the CLI-SRS; and the method also includes: sending the SL communication on the SL BWP based on the CLI-SRS power allocation priority configuration and simultaneously with the CLI-SRS in the first time period.
[0220] Aspect 14. A user equipment (UE), comprising: a processor; and a transceiver in communication with the processor, wherein the UE is configured to perform the actions according to any one of aspects 1 to 13.
[0221] Aspect 15. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a user equipment (UE) to cause the UE to perform actions according to any one of aspects 1 to 13.
[0222] Aspect 16. A user equipment (UE), comprising means for performing actions according to any one of aspects 1 to 13.
[0223] Aspect 27. A wireless communication method performed at a network device, the method comprising: sending a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, receiving a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
[0224] Aspect 28. A network device, comprising: a processor; and a transceiver communicating with the processor, wherein the network device is configured to: send a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and based on the CLI-SRS timing and the CLI-SRS priority configuration, receive a first communication in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
Claims
1. A wireless communication method performed at a user equipment (UE), the method comprising: receiving a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; as well as Based on the CLI-SRS timing and the CLI-SRS priority configuration, a first communication is sent in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
2. The method according to claim 1, wherein: The first communication is scheduled on a first frequency resource; The second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; and The method further comprises: Based on the CLI-SRS priority configuration, sending the second communication during the first time period is prohibited.
3. The method according to claim 2, wherein: The first communication includes the CLI-SRS; The second communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; the CLI-SRS is associated with a higher priority than the second communication; and The refraining from sending the second communication is based on the CLI-SRS being associated with the priority level higher than the second communication.
4. The method according to claim 2, wherein: The first communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; The second communication includes the CLI-SRS; The CLI-SRS is associated with a lower priority than the first communication; and Refraining from sending the second communication includes refraining from sending the CLI-SRS based on the CLI-SRS being associated with the lower priority than the first communication.
5. The method according to claim 1, wherein: The first communication is scheduled on a first frequency resource; The second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; scheduling the second communication for a second time period that overlaps with the first time period by at least one overlapping symbol; The method further comprises: Based on the CLI-SRS priority configuration, a portion of the second communication associated with the at least one overlapping symbol is discarded.
6. The method according to claim 1, wherein: The CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; Sending the first communication includes sending the first communication on a first component carrier (CC) based on the CLI-SRS power allocation priority configuration; and The method further comprises: The second communication is sent on a second CC based on the CLI-SRS power allocation priority configuration and simultaneously with the first communication at the first time.
7. The method according to claim 6, wherein: The first communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; the second communication comprises the CLI-SRS; and The CLI-SRS is associated with a lower power allocation priority than the first communication.
8. The method of claim 1, wherein: The cell configuration is associated with a component carrier (CC), the CC comprising a Uu bandwidth part (BWP); The CLI-SRS configuration is associated with the Uu BWP and a sidelink (SL) BWP; and Sending the first communication includes sending a first UL communication over the Uu BWP.
9. The method according to claim 8, wherein: The Uu BWP is associated with a first subcarrier spacing (SCS), and the SL BWP is associated with a second SCS different from the first SCS; Sending the first UL communication includes sending the CLI-SRS based on the first SCS; and The method further comprises: After a gap duration after the transmission of the first UL communication, a SL communication is transmitted on the SLBWP based on the second SCS.
10. The method according to claim 8, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a second UL communication scheduled for transmission on the Uu BWP; and Transmitting the CLI-SRS is based on a first Uu priority of the CLI-SRS relative to a second Uu priority associated with the second UL communication.
11. The method according to claim 8, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a first SL communication scheduled for transmission on the SL BWP; and Sending the CLI-SRS is based on a first SL priority level associated with the CLI-SRS relative to a second SL priority level associated with the first SL communication.
12. The method according to claim 8, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a first SL communication scheduled for transmission on the SL BWP; and Sending the CLI-SRS is based on a first Uu priority associated with the CLI-SRS relative to a first SL priority associated with the first SL communication.
13. The method according to claim 8, wherein: The CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; The first UL communication includes the CLI-SRS, the CLI-SRS being scheduled for transmission on the Uu BWP; The second communication comprises a SL communication scheduled for transmission on the SL BWP; Transmitting the first UL communication comprises transmitting the CLI-SRS on the Uu BWP based on the CLI-SRS power allocation priority configuration and a Uu priority associated with the CLI-SRS; and The method further comprises: The SL communication is transmitted on the SL BWP based on the CLI-SRS power allocation priority configuration and simultaneously with the CLI-SRS in the first time period.
14. A user equipment (UE), the user equipment (UE) comprising: processor; and a transceiver in communication with the processor, wherein the UE is configured to: receiving a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and Based on the CLI-SRS timing and the CLI-SRS priority configuration, a first communication is sent in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
15. The UE according to claim 14, wherein: The first communication is scheduled on a first frequency resource; The second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; and The UE is further configured to: Based on the CLI-SRS priority configuration, sending the second communication during the first time period is prohibited.
16. The UE according to claim 15, wherein: The first communication includes the CLI-SRS; The second communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; the CLI-SRS is associated with a higher priority than the second communication; and The UE is configured to refrain from sending the second communication based on the CLI-SRS being associated with the priority level higher than the second communication.
17. The UE according to claim 15, wherein: The first communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; The second communication includes the CLI-SRS; The CLI-SRS is associated with a lower priority than the first communication; and The UE is configured to refrain from sending the CLI-SRS based on the CLI-SRS being associated with the priority level lower than the first communication.
18. The UE according to claim 14, wherein: The first communication is scheduled on a first frequency resource; The second communication is scheduled on a second frequency resource that at least partially overlaps with the first frequency resource; scheduling the second communication for a second time period that overlaps with the first time period by at least one overlapping symbol; The UE is further configured to: Based on the CLI-SRS priority configuration, a portion of the second communication associated with the at least one overlapping symbol is discarded.
19. The UE according to claim 14, wherein: The CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; The UE is configured to send the first communication on a first component carrier (CC) based on the CLI-SRS power allocation priority configuration; and The UE is further configured to: The second communication is sent on a second CC based on the CLI-SRS power allocation priority configuration and simultaneously with the first communication at the first time.
20. The UE according to claim 19, wherein: The first communication comprises at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, or a non-CLI SRS; the second communication comprises the CLI-SRS; and The CLI-SRS is associated with a lower power allocation priority than the first communication.
21. The UE according to claim 14, wherein: The cell configuration is associated with a component carrier (CC), the CC comprising a Uu bandwidth part (BWP); The CLI-SRS configuration is associated with the Uu BWP and a sidelink (SL) BWP; and The UE being configured to send the first communication includes the UE being configured to send a first UL communication on the Uu BWP.
22. The UE according to claim 21, wherein: The Uu BWP is associated with a first subcarrier spacing (SCS), and the SL BWP is associated with a second SCS different from the first SCS; The UE being configured to send the first UL communication includes the UE being configured to send the CLI-SRS based on the first SCS; and The UE is further configured to: After a gap duration after the transmission of the first UL communication, a SL communication is transmitted on the SLBWP based on the second SCS.
23. The UE according to claim 21, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a second UL communication scheduled for transmission on the Uu BWP; and The UE is configured to send the CLI-SRS based on a first Uu priority of the CLI-SRS relative to a second Uu priority associated with the second UL communication.
24. The UE according to claim 21, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a first SL communication scheduled for transmission on the SL BWP; and The UE is configured to send the CLI-SRS based on a first SL priority level associated with the CLI-SRS relative to a second SL priority level associated with the first SL communication.
25. The UE according to claim 21, wherein: The first UL communication comprises the CLI-SRS scheduled for transmission on the Uu BWP; The second communication comprises a first SL communication scheduled for transmission on the SL BWP; and The UE is configured to send the CLI-SRS based on a first Uu priority associated with the CLI-SRS relative to a first SL priority associated with the first SL communication.
26. The UE according to claim 21, wherein: The CLI-SRS priority configuration includes a CLI-SRS power allocation priority configuration; The first UL communication includes the CLI-SRS, the CLI-SRS being scheduled for transmission on the Uu BWP; The second communication comprises a SL communication scheduled for transmission on the SL BWP; The UE being configured to transmit the first UL communication comprises the UE being configured to transmit the CLI-SRS on the Uu BWP based on the CLI-SRS power allocation priority configuration and a Uu priority associated with the CLI-SRS; and The UE is further configured to: The SL communication is transmitted on the SL BWP based on the CLI-SRS power allocation priority configuration and simultaneously with the CLI-SRS in the first time period.
27. A wireless communication method performed at a network device, the method comprising: transmitting a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; as well as Based on the CLI-SRS timing and the CLI-SRS priority configuration, a first communication is received in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
28. The method of claim 27, wherein: The method further includes sending a downlink (DL) communication indicating a grant for the first communication; The first communication comprises an uplink (UL) communication scheduled on a first frequency resource; The second communication comprises the CLI-SRS scheduled on a second frequency resource at least partially overlapping the first frequency resource; and The CLI-SRS priority configuration indicates that the CLI-SRS is associated with a lower priority than the first communication.
29. A network device, comprising: processor; and a transceiver in communication with the processor, wherein the network device is configured to: transmitting a cell configuration associated with a cross-link interference detection reference signal (CLI-SRS) timing; and Based on the CLI-SRS timing and the CLI-SRS priority configuration, a first communication is received in a first time period, wherein a second communication is scheduled for at least a portion of the first time period, and wherein one of the first communication or the second communication includes a CLI-SRS.
30. The network device according to claim 29, wherein: The network device is further configured to send a downlink (DL) communication indicating a grant for the first communication; The first communication comprises an uplink (UL) communication scheduled on a first frequency resource; The second communication includes the CLI-SRS scheduled on a second frequency resource at least partially overlapping the first frequency resource; and The CLI-SRS priority configuration indicates that the CLI-SRS is associated with a lower priority than the first communication.
Citation Information
Patent Citations
Systems and methods for managing uplink transmission and crosslink interference measurement
US20230318767A1
