Interference mitigation scheme for asynchronous time division duplex

Abstract

To provide methods for reducing user equipment (UE)-to-UE cross-link interference.SOLUTION: In a wireless communication system, a user equipment (UE) may receive from a base station (BS), a time-division-duplexing (TDD) pattern, and may establish a guard band on uplink resources from resources specified in the TDD pattern. Alternatively, the UE may reduce power to uplink resources from the resources specified in the TDD pattern. The UE transmits the resources on a carrier that carries the uplink resources, as specified in the TDD pattern.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] Cross - reference to Related Applications

[0001] This application claims the benefit and priority of U.S. Patent Application No. 17 / 115,779, filed on December 8, 2020, and U.S. Provisional Patent Application No. 62 / 947,963, filed on December 13, 2019, which are hereby incorporated by reference in their entirety.

[0002]

[0002] This application relates to wireless communication systems, and more particularly to mitigating cross - link interference in asynchronous time - division duplex (TDD) wireless communication.

Background Art

[0003]

[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 can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multi - access communication system may include several base stations (BS) that each support communication for multiple communication devices, which may sometimes be known as user equipment (UE) simultaneously.

[0004]

[0004] To meet the increasing demand for extended mobile broadband connections, wireless communication technology is evolving from Long Term Evolution (LTE (registered trademark)) technology to the next-generation New Radio (NR) technology, sometimes referred to as the fifth generation (5G). For example, NR is designed to achieve lower latency, higher bandwidth, or higher throughput, and higher reliability than LTE. NR is designed to operate over a wide range of spectral bands, from low-frequency bands below about 1 gigahertz (GHz) and intermediate-frequency bands from about 1 GHz to about 6 GHz to high-frequency bands such as the millimeter wave (mmWave) band. NR is also designed to operate over different spectral types, from licensed spectrum to unlicensed spectrum and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0005]

[0005] A UE 115 associated with a different network, such as a TDD network, may experience cross-link interference. Cross-link interference can occur when the UE 115 is transmitting on adjacent carriers and using different TDD patterns. This mis-aligns different types of resources specified in the TDD pattern and causes cross-link interference.

Summary of the Invention

[0006]

[0006] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology being discussed. The summary of the invention is not an extensive overview of all contemplated features of the present disclosure, nor does it identify the main or critical elements of all aspects of the present disclosure, nor does it delimit the scope of any or all aspects of the present disclosure. Its sole purpose is to present, in summary form, some concepts of one or more aspects of the present disclosure as a prelude to the more detailed description that is presented later.

[0007]

[0007] A method for avoiding cross-link interference in wireless communication, comprising receiving, by a first user equipment (UE) from a base station (BS), a second time-division-duplexing (TDD) pattern associated with a second UE, wherein the second TDD pattern specifies a second resource on a carrier adjacent to a carrier of the first UE; establishing, by the first UE, a guard band on an edge of a carrier including at least one uplink resource when there is a resource type mismatch between at least one uplink resource from a first resource specified in a first TDD pattern associated with the first UE and at least one resource in the second resource; and transmitting, by the first UE to the BS, the first resource on the carrier and in the first TDD pattern as specified, including the at least one uplink resource together with the guard band on the edge of the carrier carrying the at least one uplink resource.

[0008] Aspect further relates to establishing, by a first UE, a second guard band on a portion of a specific resource from a first resource specified in a first TDD pattern, where transmitting further comprises transmitting the portion of the specific resource together with the second guard band.

[0009] Aspect further relates to monitoring, by a first UE, an indicator including a second TDD pattern used by a second UE to transmit a second resource on a carrier adjacent to a carrier transmitting a first resource.

[0010] Aspect further relates to determining, by a first UE, that at least one uplink resource from a first resource specified in a first TDD pattern is aligned with at least one uplink resource from a second resource specified in a second TDD pattern, and transmitting at least one uplink resource without a guard band when there is an alignment between at least one uplink resource specified in the first TDD pattern and at least one uplink resource specified in the second TDD pattern.

[0011] Aspect further relates to the first TDD pattern including locations of at least one uplink resource, at least one downlink resource, and at least one special resource in the first resource during a time period.

[0012]

[0012] In one aspect of the present disclosure, a user equipment (UE) receives from a base station (BS) a second time-division duplexing (TDD) pattern associated with a second UE, where the second TDD pattern includes at least one uplink resource that specifies a second resource on a carrier adjacent to the UE's carrier, and transmits the first resource on the UE's carrier and in the first TDD pattern as specified, including the at least one uplink resource and a guard band on the edge of the carrier carrying the at least one uplink resource to the BS. A transceiver configured to do so, and when there is a resource type mismatch between at least one uplink resource from the first resource specified in the first TDD pattern and at least one resource of the second resource, a processor configured to establish a guard band on the edge of the carrier carrying the at least one uplink resource.

[0013]

[0013] The aspect further targets that the processor is further configured to establish a second guard band on a portion of a specific resource from the first resource specified in the first TDD pattern, and for transmitting the first resource, the transceiver is further configured to transmit the portion of the specific resource together with the second guard band.

[0014]

[0014] The aspect further targets that the processor is further configured to monitor an indicator including a second TDD pattern used by a second UE for transmitting a second resource on a carrier adjacent to the carrier transmitting the first resource.

[0015] Aspect is further configured such that a processor determines that at least one uplink resource from a first resource specified in a first TDD pattern is aligned with at least one uplink resource from a second resource specified in a second TDD pattern, and in order to transmit the first resource, a transceiver is configured to transmit at least one uplink resource without a guard band when there is an alignment between at least one uplink resource specified in the first TDD pattern and at least one uplink resource specified in the second TDD pattern.

[0016] Aspect is further directed to reducing cross-link interference caused by resource type mismatches using a guard band.

[0017] In one aspect of the present disclosure, there is provided a non-transitory computer-readable medium having program code recorded thereon, the program code including code for a first user equipment (UE) to receive from a base station (BS) a second time division duplex (TDD) pattern associated with a second UE, where the second TDD pattern specifies a second resource on a carrier adjacent to a carrier of the first UE, code for the first UE to establish a guard band on an edge of a carrier including at least one uplink resource when there is a resource type mismatch between at least one uplink resource from a first resource specified in a first TDD pattern associated with the first UE and at least one resource in the second resource, and code for the first UE to transmit the first resource on the carrier and in the first TDD pattern as specified, including at least one uplink resource together with the guard band on the edge of the carrier carrying the at least one uplink resource, to the BS.

[0018]

[0018] Aspect further targets code for establishing a second guard band on a portion of a specific resource from a first resource specified in a first TDD pattern by a first UE, where the code for transmission further comprises code for transmitting the portion of the specific resource together with the second guard band.

[0019]

[0019] Aspect further targets code for monitoring an indicator including a second TDD pattern used by a second UE to transmit a second resource on a carrier adjacent to a carrier transmitting a first resource in a first UE.

[0020]

[0020] Aspect further targets code for determining that at least one uplink resource from a first resource specified in a first TDD pattern is aligned with at least one uplink resource from a second resource specified in a second TDD pattern in a first UE, and code for transmitting at least one uplink resource without a guard band when there is an alignment between at least one uplink resource specified in the first TDD pattern and at least one uplink resource specified in the second TDD pattern.

[0021]

[0021] Aspect further targets that a first TDD pattern includes locations of at least one uplink resource, at least one downlink resource, and at least one special resource in a first resource during a time period.

[0022]

[0022] In one aspect of the present disclosure, a user equipment (UE) includes means for receiving, from a base station (BS), a second time division duplex (TDD) pattern associated with a second UE, where the second TDD pattern designates a second resource on a carrier adjacent to the UE's carrier, and when there is a resource type mismatch between at least one uplink resource from a first resource designated in a first TDD pattern associated with the first UE and at least one resource in the second resource, means for the first UE to establish a guard band on an edge of a carrier including the at least one uplink resource, and means for transmitting, to the BS, the at least one uplink resource together with the guard band on an edge of the at least one uplink resource and the first resource as designated on the carrier and in the first TDD pattern.

[0023]

[0023] The aspect further targets means for establishing a second guard band on a portion of a specific resource from a first resource designated in the first TDD pattern, where the means for transmitting further includes means for transmitting the portion of the specific resource together with the second guard band.

[0024]

[0024] The aspect further targets means for monitoring a second TDD pattern used by a second UE to transmit a second resource on a carrier adjacent to a carrier transmitting the first resource.

[0025] Aspect further targets means for determining that at least one uplink resource from a first resource specified in a first TDD pattern is aligned with at least one uplink resource from a second resource specified in a second TDD pattern, and means for transmitting at least one uplink resource without a guard band when there is an alignment between at least one uplink resource specified in the first TDD pattern and at least one uplink resource specified in the second TDD pattern.

[0026] Aspect further targets that a guard band reduces cross-link interference caused by a resource type mismatch.

[0027] Upon consideration of the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying figures, other aspects, features, and embodiments of the present invention will become apparent to those skilled in the art. The features of the present invention may be described with respect to some embodiments and the following drawings, but all embodiments of the present invention may include one or more of the advantageous features described herein. In other words, one or more embodiments may be described as having certain advantageous features, but one or more of such features may also be used in accordance with various embodiments of the invention described herein. Similarly, although exemplary embodiments may be described below as device embodiments, system embodiments, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods.

Brief Description of the Drawings

[0028]

Figure 1

[0028] A diagram showing a wireless communication network according to some aspects of the present disclosure.

Figure 2A

[0029] A diagram showing a time-division duplex (TDD) pattern according to some aspects of the present disclosure.

Figure 2B

Figure 2C

[0030] A diagram showing cross-link interference between user equipment (UEs) according to some aspects of the present disclosure.

Figure 3A

[0031] A diagram for reducing cross-link interference between user equipment according to some aspects of the present disclosure.

Figure 3B

Figure 3C

Figure 4

[0032] A block diagram of a user equipment according to some aspects of the present disclosure.

Figure 5

[0033] A block diagram of a base station according to some aspects of the present disclosure.

Figure 6

[0034] A flowchart of a communication method according to some aspects of the present disclosure.

Figure 7

[0035] A flowchart of a communication method according to some aspects of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0029]

[0036] The following description of the embodiments for carrying out the invention with reference to the accompanying drawings describes various configurations, and does not represent only the configurations in which the concepts described in this specification can be implemented. The embodiments for carrying out the invention include specific details for providing a complete understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some examples, well-known structures and components are shown in the form of block diagrams so as not to obscure such concepts.

[0030]

[0037] The present disclosure relates generally to a wireless communication system, also referred to as a wireless communication network. In various embodiments, the techniques and apparatus 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 systems for mobile communications (GSM®) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. The terms "network" and "system" as described herein can be used interchangeably.

[0031]

[0038] OFDMA networks can implement wireless technologies 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 the Universal Mobile Telecommunications System (UMTS). In particular, Long-Term Evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by a group called the "3rd Generation Partnership Project" (3GPP®), and cdma2000 is described in documents from a group called the "3rd Generation Partnership Project 2" (3GPP2). These various wireless technologies and standards are known or developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration among groups of the telecommunications society aimed at defining globally applicable 3rd generation (3G) mobile phone specifications. 3GPP Long-Term Evolution (LTE) is a 3GPP project aimed at improving UMTS mobile phone specifications. 3GPP can define specifications for next-generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the development of wireless technologies from LTE, 4G, 5G, NR, and beyond, involving shared access to the wireless spectrum between networks using a set of new and different wireless access technologies or wireless air interfaces.

[0032]

[0039] In particular, 5G networks can be implemented using an OFDM-based integrated air interface, contemplating various deployments, various spectrums, and various services and devices. To achieve these goals, in addition to the development of new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are considered. 5G NR is characterized by (1) ultra-high density (e.g., about 1 million nodes / km 2) coverage for large-scale Internet of Things (IoT) devices with ultra-low complexity (e.g., about dozens of bits per second), ultra-low energy (e.g., about battery life of over 10 years), and deep coverage with the ability to reach difficult locations, (2) strong security to protect highly confidential personal information, financial information, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 ms), and mission-critical control with or without a wide range of mobility of users, and (3) extremely high capacity (e.g., about 10 Tbps / km 2 ) along with extended mobile broadband including extremely high data rates (e.g., multi-Gbps rates, user experience rates of 100 Mbps or more), and deep awareness for advanced discovery and optimization, is scalable to provide.

[0033]

[0040] 5G NR has a common flexible framework with scalable numerology and transmission time intervals (TTIs) to efficiently multiplex services and features with a dynamic low-latency time-division duplexing (TDD) / frequency-division duplexing (FDD) design, and can be implemented to use an optimized OFDM-based waveform with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter-wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of numerology in 5G NR with subcarrier spacing (SCS) scaling can efficiently address operating various services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments of FDD / TDD implementations below 3 GHz, the SCS can occur at 15 kHz across bandwidths (BW) such as, for example, 5, 10, 20 MHz. In various other outdoor and small cell coverage deployments of TDD greater than 3 GHz, the SCS can occur at 30 kHz across 80 / 100 MHz BW. In various other indoor broadband implementation forms using TDD on the unlicensed portion of the 5 GHz band, the SCS can occur at 60 kHz across 160 MHz BW. Finally, in various deployments transmitting using mmWave components in 28 GHz TDD, the SCS can occur at 120 kHz across 500 MHz BW.

[0034]

[0041] The scalable numerology of 5G NR enables scalable TTIs for diverse 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 and short TTIs that enables transmissions to start on symbol boundaries. 5G NR also contemplates a self - contained integrated sub - frame design with UL / downlink scheduling information, data, and acknowledgments in the same sub - frame. The self - contained integrated sub - frame supports communication in adaptive UL / downlink that can be flexibly configured per cell to dynamically switch between UL and downlink to satisfy unlicensed or contention - based shared spectrum and current traffic needs.

[0035]

[0042] Various other aspects and features of the present disclosure are further described below. It will be apparent that the teachings of this specification can be implemented in a variety of forms, and that the specific structures, functions, or both disclosed herein are merely representative and not limiting. Based on the teachings of this specification, those skilled in the art should understand that the aspects disclosed herein can be implemented independently of other aspects, and that two or more of these aspects can be combined in various ways. For example, an apparatus can be implemented using any number of the aspects described herein, or a method can be practiced. Further, in addition to, or instead of, one or more of the aspects described herein, such an apparatus can be implemented using other structures, functions, or both structures and functions. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer - readable medium for execution on a processor or computer. Further, one aspect can comprise at least one element of one claim.

[0036]

[0043] In this application, a mechanism for identification is described.

[0037]

[0044] Aspects of the present disclosure can provide several benefits.

[0038]

[0045] FIG. 1 shows a wireless communication network 100 according to some aspects of the present disclosure. Network 100 may be a 5G network. Network 100 includes several base stations (BSs) 105 (individually labeled 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. BS 105 can be a station that communicates with 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 can provide communication coverage to a specific geographic area. In 3GPP, the term "cell" can refer to this specific geographic coverage area of the BS 105 and / or the BS subsystem that serves the coverage area, depending on the context in which the term is used.

[0039]

[0046] BS105 can provide communication coverage to macro cells, or small cells such as picocells or femtocells, and / or other types of cells. Macro cells generally cover a relatively large geographical area (e.g., several kilometers in radius) and can enable unrestricted access by UEs subscribed to the services of a network provider. Small cells such as picocells generally cover a relatively small geographical area and can enable unrestricted access by UEs subscribed to the services of a network provider. Also, small cells such as femtocells generally cover a relatively small geographical area (e.g., a home) and, in addition to unrestricted access, can also provide restricted access by UEs associated with the femtocell (e.g., UEs in a closed subscriber group (CSG), UEs for users within a home, etc.). The BS for a macro cell may be called a macro BS. The BS for a small cell may be called a small cell BS, pico BS, femto BS, or home BS. In the example shown in FIG. 1, BS105d and 105e can be normal macro BSs, but BS105a - 105c can be macro BSs capable of one of 3 - dimensional (3D) MIMO, full - dimension (FD) MIMO, or massive MIMO. BS105a - 105c can utilize their higher - dimensional MIMO capabilities to employ 3D beamforming in beamforming for both elevation and azimuth angles to increase coverage and capacity. BS105f can be a small cell BS that can be a home node or a portable access point. BS105 can support one or more (e.g., two, three, four, etc.) cells.

[0040]

[0047] Network 100 may support synchronous operation or asynchronous operation. In the case of synchronous operation, the BSs may have similar frame timings, and transmissions from different BSs may be approximately time-aligned. In the case of asynchronous operation, the BSs may have different frame timings, and transmissions from different BSs may not be time-aligned.

[0041]

[0048] UEs 115 are distributed throughout the wireless network 100, and each UE 115 can be fixed or mobile. UEs 115 may also be referred to as terminals, mobile stations, subscriber units, stations, etc. UEs 115 can be mobile phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, tablet computers, laptop computers, cordless phones, wireless local loop (WLL) stations, etc. In one aspect, a UE 115 can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, a UE 115 that does not include a UICC may also be referred to as an Internet of Things (IoT) device or an Internet of Everything (IoE) device. UEs 115a - 115d are examples of mobile smartphone - type devices that access the network 100. UEs 115 can also be machines specially configured for connected communication, including machine - type communication (MTC), enhanced MTC (eMTC), narrow - band IoT (NB - IoT), etc. UEs 115e - 115h are examples of various machines configured for communication that access the network 100. UEs 115i - 115k are examples of vehicles equipped with wireless communication devices configured for communication that access the network 100. UEs 115 can potentially communicate with any type of base station (BS), regardless of whether it is a macro BS, a small cell, etc. In FIG. 1, lightning bolts (e.g., communication links) indicate wireless transmissions between a UE 115 and a serving BS 105, which is the BS designated to serve the UE 115 on the downlink (DL) and / or uplink (UL), desired transmissions between BSs, backhaul transmissions between BSs, or sidelink transmissions between UEs 115.

[0042]

[0049] In operation, BS105a to 105c can serve UE115a and 115b using 3D beamforming and cooperative spatial techniques such as coordinated multi-point (CoMP) or multi-connectivity. Macro BS105d can perform backhaul communication with BS105a to 105c and small cell BS105f. Macro BS105d can also be registered with and transmit multicast services received by UE115c and 115d. Such multicast services can include mobile television or streamed video, or other services for providing community information such as weather emergencies or alerts such as amber alerts or gray alerts.

[0043]

[0050] BS105 can also communicate with the core network. The core network can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of BS105 (which can be an example of a gNB or access node controller (ANC)) can interface with the core network through a backhaul link (such as NG-C, NG-U, etc.) and perform radio configuration and scheduling for communication with UE115. In various examples, BS105 can communicate directly or indirectly with each other (such as through the core network) via a backhaul link (such as X1, X2, etc.) that can be a wired or wireless communication link.

[0044]

[0051] Network 100 may also support mission-critical communication using ultra-reliable links and redundant links for mission-critical devices such as UE115e, which may be a drone. The redundant communication link with UE115e may include links from macro BSs 105d and 105e, as well as a link from small cell BS 105f. Other machine type devices such as UE115f (e.g., a thermometer), UE115g (e.g., a smart meter), and UE115h (e.g., a wearable device) may communicate directly with BSs such as small cell BS 105f and macro BS 105e via Network 100, or communicate the temperature measurement information to smart meter UE115g, and the temperature measurement information is then reported to the network via small cell BS 105f, etc., communicate in a multi-step size configuration by communicating with another user device that relays the information to the network. Network 100 may also provide additional network efficiency through dynamic low-latency TDD / FDD communication such as vehicle-to-vehicle (V2V) communication between UE115i - 115k, vehicle-to-everything (V2X) communication between UE115i, 115j, or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communication between UE115i, 115j, or 115k and BS105. Network 100 that provides TDD communication may sometimes be referred to as a TDD network.

[0045]

[0052] In some implementations, Network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system may divide the system BW into a plurality (K) of orthogonal subcarriers, also commonly referred to as subcarriers, tones, bins, etc. Each subcarrier may be modulated with data. In some cases, the subcarrier spacing (SCS) between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system BW. The system BW may be partitioned into sub-bands. In other cases, the SCS and / or the duration of the transmission time interval (TTI) may be scalable.

[0046]

[0053] In some aspects, BS105 can allocate or schedule transmission resources for downlink (DL) and uplink (UL) transmissions in network 100 (e.g., in the form of time-frequency resource blocks (RBs)). DL refers to the transmission direction from BS105 to UE115, while UL refers to the transmission direction from UE115 to BS105. The communication can be in the form of radio frames. The radio frames can be divided into a plurality of subframes or slots, e.g., about 20 subframes or slots. Each slot can be further divided into minislots. In FDD mode, simultaneous UL transmission and DL reception can be performed in paired spectra. For example, each slot includes a UL subframe in the UL frequency band and a DL subframe in the DL frequency band. Subframes are sometimes also called slots. In TDD mode, UL transmission and DL reception are performed in different time periods using the same frequency (also called unpaired spectra). For example, a subset of slots in a radio frame (e.g., DL slots) can be used for DL transmission, and another subset of slots in the radio frame (e.g., UL slots) can be used for UL transmission. In TDD mode, there is one or more slots that include a period that can be used to switch from the resources used for DL reception to the resources used for UL transmission. The resources that can be used for the switch from DL reception to UL transmission are sometimes called special or flexible resources.

[0047]

[0054] The DL slot and the UL slot can be further divided into several regions. For example, each DL or UL slot may have a pre-defined region for the transmission of reference signals, control information, and data. A reference signal is a pre-determined signal that facilitates communication between the BS105 and the UE115. For example, the reference signal may have a specific pilot pattern or structure, and the pilot tones may spread across the operable BW or frequency band, each being arranged at a pre-determined time and a pre-determined frequency. For example, the BS105 may transmit a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable the UE115 to estimate the DL channel. Similarly, the UE115 may transmit a sounding reference signal (SRS) to enable the BS105 to estimate the UL channel. The control information may include resource allocation and protocol control. The data may include protocol data and / or operation data. In some aspects, the BS105 and the UE115 may communicate using self-contained slots. A self-contained subframe may include a portion for DL communication and a portion for UL communication. A self-contained slot may be DL-centric or UL-centric. A DL-centric subframe may include a duration for DL communication that is longer than the duration for UL communication. A UL-centric subframe may include a duration for UL communication that is longer than the duration for DL communication.

[0048]

[0055] In some aspects, network 100 can be an NR network deployed on an authorized spectrum. BS105 can transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS105 can broadcast system information related to 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 cases, BS105 can broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) via a physical broadcast channel (PBCH), and can broadcast RMSI and / or OSI via a physical downlink shared channel (PDSCH).

[0049]

[0056] In some aspects, a UE115 attempting to access network 100 can perform initial cell search by detecting a PSS from BS105. The PSS can enable period timing synchronization and can indicate a physical layer identification information value. UE115 can then receive the SSS. The SSS can enable radio frame synchronization and can provide a cell identification information value that can be combined with a physical layer identification information value for identifying the cell. The PSS and SSS can be located at the center portion of the carrier or any suitable frequency within the carrier.

[0050]

[0057] After receiving the PSS and SSS, the UE 115 may receive the MIB, which may be transmitted within the Physical Broadcast Channel (PBCH). The MIB may include system information for initial network access and scheduling information for the RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI, OSI, and / or one or more System Information Blocks (SIBs). The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESETs) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, and sounding reference signal (SRS). In some aspects, SIB1 may include cell access parameters and scheduling information for other SIBs.

[0051]

[0058] After obtaining the MIB, RMSI, and / or OSI, UE115 can execute a random access procedure to establish a connection with BS105. In some examples, the random access procedure can be a 4-step random access procedure. For example, UE115 can send a random access preamble, and BS105 can respond with a random access response. The random access response (RAR) can include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. When UE115 receives the random access response, it can send a connection request to BS105, and BS105 can respond with a connection response. The connection response can indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response can 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 can be a 2-step random access procedure, where UE115 can send a random access preamble and a connection request in a single transmission, and BS105 can respond by sending a random access response and a connection response in a single transmission.

[0052]

[0059] After establishing the connection, UE115 and BS105 can enter the normal operation phase, where operation data can be exchanged. For example, BS105 can schedule UE115 for UL and / or DL communication. BS105 can send UL and / or DL scheduling grants to UE115 via PDCCH. The scheduling grant can be sent in the form of downlink control information (DCI). BS105 can send a DL communication signal (e.g., carrying data) to UE115 via PDSCH according to the DL scheduling grant. UE115 can send a UL communication signal to BS105 via PUSCH and / or PUCCH according to the UL scheduling grant.

[0053]

[0060] In some aspects, BS105 may communicate with UE115 using HARQ techniques, for example, to provide URLLC services, to improve communication reliability. BS105 may schedule UE115 for PDSCH communication by transmitting DL grants in the PDCCH. BS105 may transmit DL data packets to UE115 according to the schedule in the PDSCH. The DL data packets may be transmitted in the form of transport blocks (TBs). If UE115 successfully receives the DL data packet, UE115 may transmit a HARQ ACK to BS105. Conversely, if UE115 fails to successfully receive the DL transmission, UE115 may transmit a HARQ NACK to BS105. When BS105 receives a HARQ NACK from UE115, BS105 may retransmit the DL data packet to UE115. The retransmission may include the same coded version of the DL data as the initial transmission. Alternatively, the retransmission may include a different coded version of the DL data from the first transmission. UE115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. BS105 and UE115 may also apply HARQ for UL communication using a mechanism substantially similar to DL HARQ.

[0054]

[0061] In some aspects, network 100 may operate via a system bandwidth (BW) or a component carrier (CC) BW. Network 100 may divide the system BW into multiple BWPs (e.g., parts). BS105 may dynamically allocate UE115 to operate via a certain BWP (e.g., a certain part of the system BW). The allocated BWP may be referred to as an active BWP. UE115 may monitor the active BWP for signaling information from BS105. BS105 may schedule UE115 for UL or DL communication in the active BWP. In some aspects, BS105 may allocate a pair of BWPs within a CC to UE115 for UL and DL communication. For example, the BWP pair may include one BWP for UL communication and one BWP for DL communication.

[0055]

[0062] In some aspects, network 100 may operate on a shared channel, which may include shared spectrum or unlicensed spectrum. For example, network 100 may be a New Radio Unlicensed (NR-U) network operating on unlicensed spectrum. In such aspects, BS105 and UE115 may be operated by multiple network operation entities. To avoid collisions, BS105 and UE115 may adopt a Listen Before Talk (LBT) procedure to monitor the transmission opportunity (TXOP) in the shared channel. For example, a transmitting node (e.g., BS105 or UE115) may perform LBT before transmitting in the channel. If the LBT is successful, the transmitting node may proceed with the transmission. If the LBT fails, the transmitting node may refrain from transmitting in the channel. In one example, the LBT may be based on energy detection. For example, the LBT results in a pass when the signal energy measured from the channel is less than a threshold. Conversely, the LBT results in a failure when the signal energy measured from the channel exceeds the threshold. In another example, the LBT may be based on signal detection. For example, the LBT results in a pass when a channel reservation signal (e.g., a predetermined preamble signal) is not detected in the channel.

[0056]

[0063] In some cases, in network 100 which is a TDD network, UE 115 may encounter cross-link interference between UEs. This is associated with different TDD networks and can occur when UEs 115 transmitting using adjacent carriers or the same carrier are adjacent to each other or within a specified distance of each other. When interference between UEs occurs, the quality of service provided by UE 115 deteriorates. In the following aspects, techniques for reducing cross-link interference between UEs will be described.

[0057]

[0064] In some aspects, UEs 115 within a TDD network may transmit resources using a TDD pattern. FIGS. 2A and 2B show exemplary TDD patterns 200A and 200B according to some aspects of the present disclosure. TDD patterns 200A and 200B may be adopted by a BS such as BS 105 and a UE 115 within a network such as network 100 which is a TDD network. In FIGS. 2A and 2B, the x-axis represents time in some arbitrary unit and the y-axis represents frequency in some arbitrary unit. TDD pattern 200A may be transmitted using the same or different carriers.

[0058]

[0065] BS 105 may configure UE 115 with resources within frequency band 202 during time period 204. Time period 204 may refer to the periods of TDD patterns 200A and 200B specified in the TDD pattern. The resources may be downlink (D) resources 206 used for downlink communication, uplink (U) resources 208 used for uplink communication, and special (S) resources 210 used for guard times between two D resources 206, between two U resources 208, or between a D resource 206 and a U resource 208. S resource 210 may include an uplink portion and a downlink portion. Resources 206, 208, and 210 are also known as slots.

[0059]

[0066] In some aspects, TDD patterns such as TDD patterns 200A and 200B can be specified using a TDD configuration that indicates, for each TDD pattern, a pool of frequency bands (e.g., frequency band 202) and resources (e.g., UL slots, DL slots, special S slots) within a time period 204. In particular, the aspects described herein are not limited to TDD patterns 200A and 200B and may be applicable to other TDD patterns. The TDD configuration may also specify the number of D resources 206, the number of U resources 208, and the number of S resources 210 within the time period 204 and the frequency band 202.

[0060]

[0067] In some aspects, TDD patterns, such as TDD patterns 200A and 200B, can be configured for different types of traffic. For example, TDD pattern 200A can be configured for heavy DL delay-tolerant traffic, such as traffic associated with Internet services. In another example, TDD pattern 200B can be configured for heavy UL traffic and delay-sensitive traffic, such as traffic associated with industrial Internet of Things (IoT) traffic.

[0061]

[0068] In some aspects, a network 100 that is a TDD network can transmit TDD patterns, such as TDD patterns 200A and 200B, in an asynchronous manner that leads to cross-link interference. Since the placement of different BSs 105 is static, cross-link interference caused by BSs 105 in different TDD networks can be controlled to some extent by the operators and suppliers of the BSs 105. However, the UEs 115 are mobile and move around in coverage areas covered by BSs 105 in different TDD networks. Thus, UEs 115 associated with different TDD networks can operate at distances close enough to each other to cause cross-link interference between the UEs.

[0062]

[0069] Cross-link interference between UEs can occur when different UEs 115 transmit data using adjacent carriers with different TDD patterns. Cross-link interference between UEs can occur on both uplink and downlink transmissions. In the following embodiments, uplink cross-link interference between UEs will be described, although it may be equally applicable to downlink interference. FIG. 2C is a block diagram showing cross-link interference between UEs according to some aspects of the present disclosure. FIG. 2C shows two TDD patterns 200, namely a TDD pattern 200A that can be used by carrier #1 and a TDD pattern 200B that can be used by carrier #2. Both the TDD pattern 200A and the TDD pattern 200B have a time period 204. Carrier #1 and carrier #2 can be adjacent carriers within the frequency spectrum.

[0063]

[0070] In some cases, a first UE 115 from a first TDD network may use carrier #1 to transmit resources as specified by the TDD pattern 200A, and a second UE 115 from a second TDD network may use carrier #2 to transmit resources as specified by the TDD pattern 200B. The TDD pattern 200A can be transmitted using carriers within a frequency period 202A, and the TDD pattern 200B can be transmitted using carriers within a frequency period 202B.

[0064]

[0071] In some cases, cross-link interference 212 may occur when there is a mismatch between the resource types of TDD patterns 200A and 200B transmitted on adjacent carriers simultaneously or during the same time period 204. In the following aspects, examples that can cause uplink cross-link interference 212 are given. An example of cross-link interference 212A can occur when carrier #1 conveys the D resource 206 specified in TDD pattern 200A (i.e., BS105 in the TDD network for carrier #1 transmits the D resource 206 and UE115 in the same TDD network for carrier #1 receives the D resource 206), and at the same time, carrier #2 conveys the U resource 208 specified in TDD pattern 200A (i.e., UE115 in the TDD network for carrier #2 transmits the U resource 208 and BS105 in the same TDD network for carrier #2 receives the U resource 208). Another example of cross-link interference 212B can occur when carrier #1 conveys the D resource 206 specified in TDD pattern 200A and at the same time, carrier #2 conveys the S resource 210 specified in TDD pattern 200B. Another example of cross-link interference 212C can occur when carrier #1 conveys the U resource 208 specified in TDD pattern 200A and at the same time, carrier #2 conveys the D resource 206 specified in TDD pattern 200B. Another example of cross-link interference 212D can occur when TDD pattern 200A transmits the U resource 208 and at the same time, TDD pattern 200B transmits the S resource 210.

[0065]

[0072] In the following aspects, various techniques for avoiding or reducing the cross-link interference 212 discussed above will be described. In one aspect, BS105 or UE115 or another component in the TDD network can avoid or reduce cross-link interference by avoiding UL transmission over a set of resource blocks (RBs) at the edge of a carrier including the TDD pattern 200A and / or 200B. FIG. 3A is a block diagram including a guard band in a TDD pattern according to some aspects. As shown in FIG. 3A, the guard band 302 can be incorporated into each U resource 208 included in the TDD pattern 200A and each U resource 208 included in the TDD pattern 200B. The size of the guard band 302 can be configured by UE115 or BS105. For example, BS105 or UE115 can configure the number of RBs corresponding to the size of the guard band 302. Further, assume that carrier #1 uses the TDD pattern 200A and carrier #2 uses the TDD pattern 200B. The guard band 302 is included in the U resources 208 on the adjacent edges of carriers #1 and #2. This effectively creates a buffer between carrier #1 and carrier #2.

[0066]

[0073] In some aspects, a portion of the S resource 210 associated with the uplink transmission may also include the guard band 302.

[0067]

[0074] In some aspects, the guard band 302 can be incorporated into the U resources 208 (and also the uplink portion of the S resources 210) specified in the TDD patterns 200A, 200B in several ways. In one aspect, the BS105 or the UE115 can configure the UL bandwidth part (BWP) to exclude a set of RBs on the edge of the carrier. In another example, the network 100 or the BS105 can avoid scheduling or configuring UL transmissions that overlap with a set of RBs on the edge of the carrier. In another example, when the UL transmissions scheduled, indicated, or configured by the BS105 overlap with a set of RBs on the edge of the carrier, the UE115 can drop all or part of the UL transmissions.

[0068]

[0075] In some aspects, the network 100 can use various techniques to determine when UL cross-link interference 212 can occur. In one aspect, the TDD network 100 can store each TDD pattern 200 associated with the TDD network on a server accessible to multiple TDD networks. The stored information can also include frame timing information of the TDD carriers in the TDD network. Other networks 100 can then access the server and obtain the TDD pattern 200. In this way, multiple networks 100 can share their respective TDD patterns 200.

[0069]

[0076] In another aspect, the network 100 can use a backhaul to exchange the TDD pattern 200 and the time period 204 of the TDD pattern 200. The backhaul can be an alternative communication channel, such as the Internet, 3G communication, etc., that can be used for the network 100 and / or components within the network 100 to share information.

[0070]

[0077] In another aspect, one TDD network may monitor or listen to the carriers of another TDD network. For example, a TDD network measures the strength of received signals in carriers that may be used by another TDD network when it has no signals or channels to transmit. The first TDD network 100 may then identify a TDD pattern, e.g., the TDD pattern 200A used by the second TDD network, and then identify U resources 208 from the identified TDD pattern 200A. In some aspects, the BS 105 included in the first network 100 may listen or monitor the carriers of other TDD networks 100.

[0071]

[0078] In another aspect, UE 115 associated with the first TDD network may listen or monitor for interference caused by mismatching resources 206, 208, 210 on an adjacent carrier used by the second TDD network. Listening or monitoring for such interference by UE 115 is possible when the UE does not have a transmission on its own carrier. In this way, the first TDD network may become aware of the presence of an adjacent carrier associated with the second TDD network. In one example, UE 115 within the first TDD network may monitor for interference from an adjacent carrier and may estimate the TDD pattern 200 of the adjacent carrier used by the second TDD network, such as TDD patterns 200A, 200B. UE 115 may then report the estimated TDD pattern 200 to BS 105 or another component within the first TDD network. In another example, UE 115 may monitor for interference from an adjacent carrier and may report interference fluctuations to BS 105 or another component associated with the first TDD network for analysis and identification of the TDD pattern 200 associated with the adjacent carrier within the second TDD network, such as TDD patterns 200A, 200B. The report may include one or more received signal strength indicator (RSSI), reference signal received power (RSRP), reference signal received quality (RSRQ), or signal-to-interference plus noise ratio (SINR) values over time that provide information regarding interference fluctuations over time and that represent resources that are colliding during downlink transmission and resources that are colliding during uplink transmission.

[0072]

[0079] Figure 3B is another block diagram including a guard band in a TDD pattern according to some aspects of the present disclosure. Similar to FIG. 3A, FIG. 3B shows a guard band 302 incorporated in each U resource 208 and the uplink portion of the S resource 210 included in the TDD patterns 200A and 200B. Different from FIG. 3A, in FIG. 3B, the guard band 302 can be created when the TDD patterns 200A and 200B of adjacent carriers #1 and #2 can cause UL cross-link interference 212. The UL cross-link interference 212 can occur when there is a mismatch between the resource types of the coherent resources transmitted on adjacent carriers #1 and #2, such as, for example, the D resource 206 and the U resource 208, or the S resource 210 and the U resource 208. FIG. 3B shows that the guard band 302 is not created on the edge of the U resource 208 transmitted using the coherent carriers #1 and #2. For example, assume that carrier #1 uses the TDD pattern 200A, carrier #2 uses the TDD pattern 200B, and carriers #1 and #2 are adjacent. FIG. 3B shows two U resources 208 (shown as 304) specified in the coherent TDD patterns 200A and 200B. When the two UL resources 208 are coherent, there is no (or minimal) UL cross-link interference 212, and the guard band 302 is not included for the coherent UL resources 208.

[0073]

[0080] In some aspects, UE 115 and BS 105 may be able to determine whether there is potential UL cross-link interference 212 using the timing of adjacent carriers and higher-level parameters. Exemplary parameters may be TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated provided by a radio resource configuration (RRC) parameter set. In one aspect, UE 115 may obtain these parameters using RRC signaling in the received downlink data channel (e.g., system information). In another aspect, UE 115 may monitor the downlink data channel (e.g., system information) of an adjacent carrier and identify these parameters using the system information. In yet another aspect, a DCI format, such as DCI format 2_0, may indicate the TDD pattern 200 to UE 115. The DCI format may be shared via backhaul signaling as discussed above or may be identified using TDD pattern 200 detection used by BS 105 or UE 115. In this way, UE 115 associated with different TDD networks may determine the TDD pattern 200 of an adjacent TDD network. In some aspects, UE 115 may be notified of the TDD pattern 200 used by an adjacent TDD network by monitoring the carrier used by UE 115 or an adjacent carrier used by an adjacent TDD network. For example, UE 115 may be notified of the TDD pattern 200 of an adjacent carrier by DCI format 2_0 received by UE 115 on its own carrier. In another example, UE 115 may be notified of the TDD pattern 200 of an adjacent carrier by monitoring the DCI format 2_0 of the adjacent carrier.

[0074]

[0081] Figure 3C is a block diagram showing techniques for reducing UL cross-link interference according to some aspects of the present disclosure. Unlike the aspects of FIGS. 3A - 3B where guard band 302 is incorporated at the edges of UL resources 208 in adjacent carriers #1 and #2, the aspect of FIG. 3C reduces the power for UL resources 208 in adjacent carriers. For example, UE115 may reduce the maximum transmit power used to transmit UL resource 208, thereby reducing or eliminating UL cross-link interference. Assume that two UE115s associated with different TDD networks are transmitting on adjacent carriers #1 and #2, where carrier #1 uses TDD pattern 200A and carrier #2 uses TDD pattern 200B. UE115 may transmit D resource 206 and S resource 210 (or the downlink portion of S resource 210) using maximum or full power and then reduce the power for transmitting U resource 208.

[0075]

[0082] In some aspects, UE115 may not reduce the power of U resources 208 aligned within an adjacent carrier (shown as 304). As discussed above, the aligned U resources 208 do not cause UL cross-link interference. In this case, UE115 may transmit the U resources 208 in TDD pattern 200A that are aligned with the U resources 208 in TDD pattern 200B using maximum or full power and transmit the U resources 208 in TDD pattern 200A that are not aligned with the U resources 208 in TDD pattern 200B using reduced power.

[0076]

[0083] UE115 associated with a first TDD network may determine or receive the TDD pattern 200 of an adjacent carrier used by a second TDD network, as discussed above.

[0077]

[0084] In some aspects, the amount of power that UE 115 may use to transmit U resource 208 may be configured by UE 115 or by a configuration transmitted from BS 105. For example, a TDD network may use a transmit power control (TPC) parameter indicating the power for transmitting U resource 208. Typically, the amount of power indicated by TPC is less than the maximum power that UE 115 may use to transmit a resource. BS 105 may transmit the TPC parameter to UE 115 using a TPC command field within a DCI format, such as DCI format 0_0, 0_1, 1_0, or 1_1, or DCI format 2_2. In another example, network 100 may configure an upper layer parameter for TPC. An exemplary upper layer parameter for TPC may be PUSCH, such as P0_PUSCH. BS 104 may then transmit P0_PUSCH to UE 115. In some aspects, UE 115 may receive the TPC parameter using, for example, a DCI format or PUSCH, and transmit U resource 208 using the power indicated by the TPC parameter.

[0078]

[0085] FIG. 4 is a block diagram of UE 400 according to some aspects of the present disclosure. UE 400 may be the UE 115 described above in FIG. 1. As shown, UE 400 may include a processor 402, a memory 404, a TDD module 408, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0079]

[0086] Processor 402 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. Processor 402 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors and DSP cores, or any other such configuration.

[0080]

[0087] Memory 404 may include a cache memory (e.g., the cache memory of processor 402), 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 (registered trademark)), flash memory, solid-state memory devices, hard disk drives, other forms of volatile and non-volatile memory, or combinations of different types of memory. In one aspect, memory 404 includes a non-transitory computer-readable medium. Memory 404 may store or record instructions 406. When executed by processor 402, instructions 406 may include instructions that cause processor 402 to perform the operations described herein with respect to UE 115 in accordance with aspects of the present disclosure, such as the aspects of FIGS. 6-7. Instructions 406 may also be referred to as program code. The program code is for causing these operations to be performed on a wireless communication device, and may be, for example, by controlling or instructing the wireless communication device, such as one or more processors (such as processor 402), to do so. The terms "instructions" and "code" should be construed broadly to include any type of computer-readable statement. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0081]

[0088] The TDD module 408 may determine a TDD pattern that the UE 400 can use to transmit and receive information using carrier #1 in the TDD network associated with the UE 400, and also a TDD pattern that the UE 115 in a different TDD network can use to transmit and receive information using carrier #2, where carrier #1 and carrier #2 are adjacent carriers. Based on the determination, the TDD module 408 may cause the UE 400 to transmit information using U resources including a guard band. In some cases, the TDD module 408 may be activated when the UE 115 from a different TDD network is within a configurable distance from the UE 400. Alternatively, the TDD module 408 may cause the UE 400 to transmit information using the U resource 208 using a reduced power specified in the TPC parameter.

[0082]

[0089] The TDD module 408 may also use various techniques to identify the TDD patterns used by adjacent carriers in different TDD networks. The TDD module 408 may obtain the TDD pattern by monitoring the TDD network associated with the UE 400 or the BS 105, or adjacent carriers associated with a different TDD network for the TDD pattern. The TDD module 408 may be used for various aspects of the present disclosure, for example, the aspects of FIGS. 1-3 and FIGS. 6-7.

[0083]

[0090] As shown, transceiver 410 may include a modem subsystem 412 and an RF unit 414. Transceiver 410 may be configured to communicate bidirectionally with other devices such as BS105. Modem subsystem 412 may be configured to modulate and / or encode data from memory 404. RF unit 414 may process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from modem subsystem 412 (e.g., PSSCH data and / or PSCCH control information during outbound transmission), or the modulated / encoded data of a transmission generated from another source such as UE115 or BS105. RF unit 414 may be further configured to perform analog beamforming along with digital beamforming. Modem subsystem 412 and RF unit 414 are shown to be integrated with each other within transceiver 410, but may be separate devices coupled to each other in UE115 to enable UE115 to communicate with other devices.

[0084]

[0091] RF unit 414 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 antenna 416 for transmission to one or more other devices. Antenna 416 may further receive data messages transmitted from other devices. Antenna 416 may provide the received data messages for processing and / or demodulation in transceiver 410. Antenna 416 may include multiple antennas of the same or different designs to maintain multiple transmission links. RF unit 414 may constitute antenna 416.

[0085]

[0092] In some aspects, transceiver 410 is configured to receive from another UE115 the TDD pattern or TPC parameters from BS105.

[0086]

[0093] In some aspects, the UE 400 can include a plurality of transceivers 410 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 400 can include a single transceiver 410 that implements a plurality of RATs (e.g., NR and LTE). In one aspect, the transceiver 410 can include various components, where different combinations of components can implement different RATs.

[0087]

[0094] FIG. 5 is a block diagram of a BS 500 according to some aspects of the present disclosure. The BS 500 can be the BS 105 described above in FIG. 1. As shown, the BS 500 can include a processor 502, a memory 504, a TDD module 508, a transceiver 510 including a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements can communicate directly or indirectly with each other, for example, via one or more buses.

[0088]

[0095] The processor 502 can have various characteristics as a particular type of processor. For example, these can 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 502 can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors and DSP cores, or any other such configuration.

[0089]

[0096] Memory 504 can include cache memory (e.g., the cache memory of processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid state memory devices, one or more hard disk drives, memory - based arrays, other forms of volatile and non - volatile memory, or combinations of different types of memory. In some embodiments, memory 504 can include a non - transitory computer - readable medium. Memory 504 can store instructions 506. When executed by processor 502, instructions 506 can include instructions that cause processor 502 to perform the operations described herein, such as the operations of the embodiments of FIGS. 6 - 7. Instructions 506 may also be referred to as code, and as discussed above in connection with FIG. 4, code can be broadly interpreted to include any type of computer - readable statement.

[0090]

[0097] TDD module 508 can be implemented via hardware, software, or a combination thereof. TDD module 508 can be implemented as instructions 506 stored in processor, circuitry, and / or memory 504 and executed by processor 502. In some cases, TDD module 508 can be incorporated within modem subsystem 512. TDD module 508 can be implemented by a combination of software components (e.g., executed by a DSP or a general - purpose processor) and hardware components (e.g., logic gates and circuitry) within modem subsystem 512.

[0091]

[0098] The TDD module 508 can be used for various aspects of the present disclosure, such as the aspects of FIGS. 1-3 and FIGS. 6-7. The TDD module 508 is configured to transmit a TDD pattern that the UE 115, 400 can use to transmit resources, and also to determine the TDD pattern of the UE 115 associated with different TDD networks that transmit resources on adjacent carriers. The TDD module 508 can cause the BS 105 to transmit TDD patterns, such as the TDD pattern used by the TDD network associated with the UE 115 and the TDD pattern used by the UE 115 in the second TDD network. The TDD module 508 can format parameters that may include the TDD pattern. The TDD module 508 can also transmit to the UE 115, 400 a TPC parameter indicating the power that the UE 115 can use to transmit information using uplink resources in order to reduce uplink cross-link interference.

[0092]

[0099] As shown in the figure, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as the UE 115 and / or 400, and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS, such as an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc. The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion) the modulated / coded data from the modem subsystem 512 (during outbound transmission), such as permitted, resource allocation, or the modulated / coded data of a transmission originated from another source such as the UE 115 and / or the UE 400. The RF unit 514 may be further configured to perform analog beamforming together with digital beamforming. The modem subsystem 512 and / or the RF unit 514 are shown to be integrated with each other within the transceiver 510, but may be separate devices coupled to each other in the BS 105 to enable the BS 105 to communicate with other devices.

[0093]

[0100] The RF unit 514 may provide the 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 516 for transmission to one or more other devices. This may include, for example, the transmission of information to complete the connection to the network and the communication with the staying UE 115 or 400, according to some aspects of the present disclosure. The antenna 516 may further receive the data messages transmitted from other devices and provide the received data messages for processing and / or demodulation in the transceiver 510. The antenna 516 may include a plurality of antennas of the same or different designs to maintain a plurality of transmission links.

[0094]

[0101] In one example, the transceiver 510 is configured to transmit a TDD configuration by cooperating with the TDD module 508. In one aspect, the BS 500 can include a plurality of transceivers 510 implementing different RATs (e.g., NR and LTE). In one aspect, the BS 500 can include a single transceiver 510 implementing a plurality of RATs (e.g., NR and LTE). In one aspect, the transceiver 510 can include various components, where different combinations of components can implement different RATs.

[0095]

[0102] FIG. 6 is a flowchart of a communication method 600 according to some aspects of the present disclosure. The steps of method 600 can be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device, or by other suitable means for performing the steps. For example, a wireless communication device such as UE 115 or UE 400 can utilize one or more components such as a processor 402, a memory 404, a TDD module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of method 600. As illustrated, method 600 includes some of the recited steps, but aspects of method 600 can include additional steps before, after, and in between the recited steps. In some aspects, one or more of the recited steps can be omitted or performed in a different order.

[0096]

[0103] In step 610, method 600 includes receiving, by a first UE from a BS, a TDD pattern. The TDD pattern 200 can be a pattern that specifies resources for a second UE 115, such as a D resource 206, a U resource 208, and an S resource 210, a time period 204, and a frequency band 202. The D resource 206 can transmit data and information from the BS 105 to the UE 115, the U resource 208 can transmit data and information from the UE 115 to the BS 105, and the S resource 210 can guard the time between the D resource 206 and the U resource 208. A carrier can be used to carry the resources 206, 208, 210 in the pattern included in the TDD pattern 200. The TDD pattern 200 received in step 610 can be a TDD pattern 200 associated with a second UE 115 transmitting on a carrier adjacent to the carrier used by the first UE 115.

[0097]

[0104] In step 620, method 600 includes establishing a guard band by a first UE. The guard band 302 may include RBs at the edge of a carrier using the TDD pattern 200 of the first UE 115. Further, the guard band 302 may be included in the U resource 208 specified by the TDD pattern 200 and the uplink portion of the S resource 210. The first UE 115 or the BS 105 may specify the size of the guard band 302 by configuring the number of RBs that may be included in the guard band 302. When the first UE 115 is transmitting on an adjacent carrier and identifies a second UE 115 from a different TDD network using the TDD pattern 200 received in step 610, the first UE 115 may establish the guard band 302. The UE 115 may establish the guard band 302 by excluding scheduling or configuring information on the portion of the U resource 208 covered by the guard band 302. When there is a resource type mismatch between the aligned resources within the TDD pattern 200 of the first UE 115 and the second UE 115, the guard band 302 may reduce the UL cross-link interference 212 between adjacent carriers. For example, when the first UE 115 identifies a U resource 208 within the TDD pattern 200 used by the first UE 115 that is aligned with a D resource 306 or an S resource 210 within the TDD pattern 200 used by the second UE 115, the first UE 115 may establish the guard band 302. In some cases, the first UE 115 may not establish the guard band 302 in the U resource 208. This may occur when the first UE 115 identifies the TDD pattern used by the second UE 115 and the U resources 208 specified by the TDD patterns 200 associated with the first and second UEs 115 are aligned.

[0098]

[0105] In step 630, method 600 includes the first UE transmitting resources to BS105 using a carrier and a pattern specified by TDD pattern 200 associated with the first UE115. The first UE115 may transmit resources that include U resources 208 and, in some cases, S resources 210, along with a guard band. In some cases, when there is a match between the U resources 208 of the TDD pattern 200 of the first UE115 and the second UE115, the first UE115 may not include a guard band on the U resources 208.

[0099]

[0106] FIG. 7 is a flowchart of a communication method 700 according to some aspects of the present disclosure. The steps of method 700 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device, or by other suitable means for performing the steps. For example, a wireless communication device such as UE115 or UE400 may utilize one or more components such as processor 402, memory 404, TDD module 408, transceiver 410, modem 412, and one or more antennas 416 to perform the steps of method 700. As illustrated, method 700 includes some enumerated steps, but aspects of method 700 may include additional steps before, after, and in between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0100]

[0107] In step 710, method 700 includes receiving, by a first UE from a BS, a TDD pattern. The TDD pattern 200 can be a pattern that specifies resources of a second UE 115 transmitting on a carrier adjacent to a carrier of the first UE 115, such as D resources 206, U resources 208, and S resources 210, a time period 204, and a frequency band 202. The D resource 206 can transmit data and information from the BS 105 to the UE 115, the U resource 208 can transmit data and information from the UE 115 to the BS 105, and the S resource 210 can guard the time between the D resource 206 and the U resource 208. The carrier can be used to carry the resources 206, 208, 210 in the pattern included in the TDD pattern 200.

[0101]

[0108] In step 720, method 700 includes receiving, by a first UE from a BS, a transmit power command (TPC). The TPC indicates the amount of power that the first UE 115 can use to transmit information using the U resource 208. The TPC command can be included in a TPC command field within DCI format 0_0, 0_1, 1_0, or 1_1, or DCI format 2_2. The TPC command can also be included in a higher level parameter, such as P0_PUSCH.

[0102]

[0109] In step 730, method 700 includes reducing the power for the uplink resource by the first UE. The location of the uplink resource 208 may be specified during the TDD pattern 200 of the first UE. The first UE 115 may identify a second UE 115 from a different TDD network transmitting on an adjacent carrier, and when the TDD pattern 200 indicates a resource type mismatch, the first UE 115 may reduce the power. For example, when there is a match between the U resource 208 of the first UE 115 and the D resource 206 or S resource 210 of the second UE 115, the first UE 115 may reduce the power. The power may be reduced from the total power or maximum power to the power specified in the TPC. In some cases, when the first UE 115 identifies the TDD pattern used by a second UE 115 within a different TDD network and the U resources 208 within the TDD patterns associated with the first UE 115 and the second UE 115 are aligned, the first UE 115 may not reduce the power.

[0103]

[0110] In step 740, method 700 includes transmitting resources to BS 105 by the first UE using a carrier and as specified in the TDD pattern. The first UE 115 may transmit resources to BS 105 using a carrier and as specified in the TDD pattern 200. Further, the U resources 208 may be transmitted using the power specified in the TPC.

[0104]

[0111] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0105]

[0112] With respect to the disclosure of this specification, the various exemplary blocks and modules described can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in the 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, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration).

[0106]

[0113] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on a computer-readable medium or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementation forms are within the scope of this disclosure and within the scope of the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically arranged in various positions, including being distributed such that portions of the functions are implemented in different physical locations. Also, as used herein, including in the claims, the "or" used in a list of items (e.g., a list of items followed by phrases such as "at least one of" or "one or more of") indicates an inclusive list, and thus, for example, the list [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).

[0107]

[0114] As will be appreciated by those skilled in the art, many modifications, alternatives, and variations can be made in the materials, devices, configurations, and methods of use of the devices of the present disclosure, as well as thereto, without departing from the spirit and scope of the present disclosure, in accordance with the particular applications at hand. In light of this, the scope of the present disclosure should not be limited to the scope of those particular embodiments, which are merely examples by several examples of the present disclosure illustrated and described herein, but rather should fully correspond to the scope of the appended claims below and the scope of their functional equivalents.

Claims

1. A method for avoiding cross-link interference in wireless communication, comprising: receiving, by a first user equipment (UE), from a base station (BS), a second time-division duplex (TDD) pattern associated with a second UE, wherein the second TDD pattern designates a second resource on a carrier adjacent to a carrier of the first UE; when there is a resource type mismatch between at least one uplink resource from a first resource designated in a first TDD pattern associated with the first UE that is aligned with at least one second resource in the second resource, establishing, by the first UE, a guard band on an edge of the carrier including the at least one uplink resource; transmitting, by the first UE to the BS, on the carrier and in the first TDD pattern as designated, the first resource, together with the at least one uplink resource and the guard band on the edge of the carrier carrying the at least one uplink resource.

2. further comprising establishing, by the first UE, a second guard band on a portion of a specific resource from the first resource designated in the first TDD pattern; wherein the transmitting further comprises transmitting the portion of the specific resource together with the second guard band, according to the method of Claim 1.

3. further comprising monitoring, by the first UE, an indicator including the second TDD pattern used by the second UE to transmit the second resource on a carrier adjacent to the carrier on which the first resource is transmitted, according to the method of Claim 1.

4. The establishing comprises: determining, by the first UE, that at least one uplink resource from the first resource designated in the first TDD pattern is aligned with at least one uplink resource from the second resource designated in the second TDD pattern; The method according to claim 1, further comprising transmitting the at least one uplink resource without the guard band when there is an alignment between the at least one uplink resource specified in the first TDD pattern and the at least one uplink resource specified in the second TDD pattern.

5. The method according to claim 1, wherein the first TDD pattern includes the locations of the at least one uplink resource, at least one downlink resource, and at least one special resource in the first resource during a time period.

6. A user equipment (UE), receiving from a base station (BS) a second time-division duplexing (TDD) pattern associated with a second UE, wherein the second TDD pattern specifies a second resource on a carrier adjacent to the carrier of the UE; transmitting, to the BS, the first resource on the carrier of the UE and as specified in a first TDD pattern, including the at least one uplink resource together with a guard band on an edge of the carrier carrying the at least one uplink resource; a transceiver configured to perform; establishing the guard band on the edge of the carrier carrying the at least one uplink resource when there is a resource type mismatch between at least one resource of the at least one uplink resource from the first resource specified in the first TDD pattern associated with the UE and at least one resource of the second resource; a UE comprising a processor configured to perform.

7. The processor is further configured to establish a second guard band on a portion of a specific resource from the first resource specified in the first TDD pattern, The UE according to claim 6, wherein the transceiver is further configured to transmit the portion of the specific resource together with the second guard band for transmitting the first resource.

8. The processor is The UE according to claim 6, further configured to monitor an indicator including the second TDD pattern used by the second UE to transmit the second resource on the carrier adjacent to the carrier transmitting the first resource.

9. The processor is further configured to determine that at least one uplink resource from the first resource specified in the first TDD pattern is aligned with at least one uplink resource from the second resource specified in the second TDD pattern. The UE according to claim 6, wherein, to transmit the first resource, the transceiver is further configured to transmit the at least one uplink resource without a guard band when there is an alignment between the at least one uplink resource specified in the first TDD pattern and the at least one uplink resource specified in the second TDD pattern.

10. The UE according to claim 6, wherein the guard band reduces cross-link interference caused by the resource type mismatch.

11. A non-transitory computer-readable medium recording program code, the program code including code for receiving, by a first user equipment (UE) from a base station (BS), a second time division duplexing (TDD) pattern associated with a second UE, wherein the second TDD pattern designates a second resource on a carrier adjacent to the carrier of the first UE. code for establishing a guard band on an edge of the carrier including the at least one uplink resource by the first UE when there is a resource type mismatch between at least one uplink resource from the first resource specified in the first TDD pattern associated with the first UE and at least one resource in the second resource. A non - transitory computer - readable medium comprising code for transmitting the first resource by the first UE to the BS on the carrier and within the first TDD pattern, including the at least one uplink resource together with the guard band on the edge of the carrier for carrying the at least one uplink resource as specified. **Claim 12** Further comprising code for the first UE to establish a second guard band on a portion of a specific resource from the first resource specified in the first TDD pattern, wherein the code for transmission further comprises code for transmitting the portion of the specific resource together with the second guard band. The non - transitory computer - readable medium according to claim 11. **Claim 13** Further comprising code for the first UE to monitor an indicator including the second TDD pattern used by the second UE to transmit a second resource on a carrier adjacent to the carrier for transmitting the first resource. The non - transitory computer - readable medium according to claim 11. **Claim 14** Code for the first UE to determine that at least one uplink resource from the first resource specified in the first TDD pattern is aligned with at least one uplink resource from the second resource specified in the second TDD pattern, and code for transmitting the at least one uplink resource without a guard band when there is an alignment between the at least one uplink resource specified in the first TDD pattern and the at least one uplink resource specified in the second TDD pattern. The non - transitory computer - readable medium according to claim 11. **Claim 15** The non - transitory computer - readable medium according to claim 11, wherein the first TDD pattern includes the locations of the at least one uplink resource, at least one downlink resource, and at least one special resource within the first resource during a time period. **Claim 16** A user equipment (UE), means for receiving, from a base station (BS), a second time division duplexing (TDD) pattern associated with a second UE, wherein the second TDD pattern designates a second resource on a carrier adjacent to a carrier of the UE; means, when there is a resource type mismatch between at least one uplink resource from a first resource designated in a first TDD pattern associated with the first UE and at least one resource in the second resource, for establishing a guard band on an edge of the carrier including the at least one uplink resource by the first UE; a UE comprising: means for transmitting the first resource on the carrier and in the first TDD pattern as designated, including the at least one uplink resource together with the guard band on the edge of the at least one uplink resource, to the BS;

17. further comprising means for establishing a second guard band on a portion of a specific resource from the first resource designated in the first TDD pattern; the UE according to claim 16, wherein the means for transmitting further comprises means for transmitting the portion of the specific resource together with the second guard band;

18. the UE according to claim 16, further comprising means for monitoring the second TDD pattern used by the second UE for transmitting the second resource on a carrier adjacent to the carrier transmitting the first resource;

19. means for determining that at least one uplink resource from the first resource designated in the first TDD pattern is aligned with at least one uplink resource from the second resource designated in the second TDD pattern; the UE according to claim 16, further comprising means for transmitting the at least one uplink resource without a guard band when there is an alignment between the at least one uplink resource designated in the first TDD pattern and the at least one uplink resource designated in the second TDD pattern;

20. The UE according to claim 16, wherein the guard band reduces cross-link interference caused by the resource type mismatch.

Images