Method and apparatus for mitigating crosslink interference - Patents.com

Abstract

The logic may decode information regarding a crosslink interference (CLI) measurement and reporting configuration received via a first downlink (DL) control information (DCI) from the first base station, the information including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink transmission should be measured and a definition for a CLI measurement report. The logic may measure the SRS or other uplink transmission based on the identification of the communication resource. The logic may generate a CLI measurement report based on the measurement of the SRS or other uplink transmission. The logic may transmit the CLI measurement report. The logic may generate the CLI measurement and reporting configuration to include an identification of a communication resource on which the SRS should be measured and a definition of the CLI measurement. The logic may also transmit the CLI measurement and reporting configuration to the first user equipment via the DCI transmission.

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to wireless communications, and in particular to measuring and mitigating cross-link interference. [Background technology]

[0002] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The next generation wireless communication system, the fifth generation technology (5G) for broadband cellular networks, or New Radio (NR), provides access to information and data sharing anytime and anywhere by various users and applications. NR is expected to be an integrated network / system that aims to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse and multi-dimensional requirements are driven by various services and applications. In general, NR evolves based on 3GPP LTE-Advanced, adding new radio access technologies (RATs) to enrich people's lives with better, simpler and seamless wireless connectivity solutions. NR will connect everything wirelessly, providing high speed and richer content and services.

[0003] Currently, time division duplexing (TDD) is widely used in commercial NR deployments, where the time domain resource is divided between downlink and uplink symbols. In NR, the TDD uplink / downlink (UL / DL) configuration can be semi-statically configured by the next generation NodeB (gNB) via tdd-UL-DLConfigurationCommon or tdd-UL-DLConfigurationDedicated. Dynamic TDD has also been introduced in NR. In this case, the gNB can dynamically allocate UL and DL resources to match the instantaneous traffic conditions for UL and DL transmissions, respectively. This can maximize resource utilization and improve the throughput of the user equipment (UE). [Brief description of the drawings]

[0004] [Figure 1A] 1 illustrates an embodiment of a system including base stations and user equipment interconnected by a communication network. [Figure 1B] 1 illustrates an embodiment of a system including a base station and user equipment interconnected by a communication network, such as the user equipment and base station shown in FIG. 1A, to illustrate cross-link interference. [Diagram 2] 1A and 1B illustrate an embodiment of a base station and a user equipment, such as those illustrated in FIGS. [Figure 3A] 1A, 1B, and 2 for measuring and reporting crosslink interference between cells. [Figure 3B] 1A, 1B, and 2 for measuring and reporting crosslink interference between cells. [Figure 3C] 1A, 1B, 2, 3A and 3B illustrate embodiments of crosslink interference (CLI) measurement reports of Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP) and / or CLI-Received Signal Strength Indicator (RSSI) in channel state information (CSI) reports by user equipment to a base station, such as the user equipment and base stations shown in FIG. 1A, FIG. 1B, FIG. 2, FIG. 3A and FIG. 3B. [Figure 3D] 1A, 1B, 2, 3A and 3B, depict an embodiment of a CLI measurement report of SRS-RSRP and / or CLI-RSSI in an uplink control information format by a user equipment to a base station, such as the user equipment and base station shown in FIG. 1A, FIG. 1B, FIG. 2, FIG. 3A and FIG. 3B. [Figure 3E] 1A, 1B, 2, 3A and 3B, depict another embodiment of a CLI measurement report of SRS-RSRP and / or CLI-RSSI in an uplink control information format by a user equipment to a base station, such as the user equipment and base station shown in FIG. 1A, FIG. 1B, FIG. 2, FIG. 3A and FIG. 3B. [Figure 4]1A, 1B, 2, 3A and 3B depict embodiments of communication between user equipment and base stations, including non-overlapping sub-band full duplex (SBFD). [Figure 5A] 1A, 1B, and 2 that transmits sounding or other frames for measurement by nearby user equipment to mitigate cross-link interference. [Figure 5B] 1A, 1B, 2 and 5 depict an alternative embodiment of a victim user equipment, such as the user equipment depicted in FIGS. 1A, 1B, 2 and 5, measuring sounding frames or other frames from an aggressor user equipment to mitigate cross-link interference. [Figure 5C] 1A, 1B, 2 and 5 depict an alternative embodiment of a victim user equipment, such as the user equipment depicted in FIGS. 1A, 1B, 2 and 5, measuring sounding frames or other frames from an aggressor user equipment to mitigate cross-link interference. [Figure 5D] 1A, 1B, 2 and 5 depict an alternative embodiment of a victim user equipment, such as the user equipment depicted in FIGS. 1A, 1B, 2 and 5, measuring sounding frames or other frames from an aggressor user equipment to mitigate cross-link interference. [Figure 5E] 1A, 1B, 2 and 5 depict an alternative embodiment of a victim user equipment, such as the user equipment depicted in FIGS. 1A, 1B, 2 and 5, measuring sounding frames or other frames from an aggressor user equipment to mitigate cross-link interference. [Figure 6] 1A, 1B, 2, 3A-3E, 4, and 5A-5E illustrate flow charts of embodiments for measuring and mitigating cross-link interference, such as those described in connection with FIGS. [Figure 7] 1A, 1B, 2, 3A-3E, 4, 5A-5E, and 6, illustrates a flowchart of an alternative embodiment for measuring and mitigating cross-link interference. [Figure 8]1 illustrates an embodiment of protocol entities within a wireless communication device, such as a base station and a user equipment, illustrated in FIGS. 1A, 1B, and 2. FIG. [Figure 9] 3 illustrates an embodiment of a format for a physical layer data unit (PDU) formed by a baseband circuitry and an RF transceiver, such as the baseband circuitry and RF transceiver illustrated in FIG. 2. [Figure 10A] 3 illustrates an embodiment of communications circuitry, such as components and modules shown in the user equipment and base station shown in FIG. 2. [Figure 10B] 3 illustrates an embodiment of communications circuitry, such as components and modules shown in the user equipment and base station shown in FIG. 2. [Figure 11] 1 illustrates an embodiment of a storage medium as described herein. [Figure 12] 1 illustrates an embodiment of a system architecture for a network such as the communication network of FIGS. 1A and 1B. [Figure 13] 1A, 1B, and 2 illustrate an embodiment of a device such as a base station or a user equipment. [Figure 14] 3 illustrates an embodiment of an interface for a baseband circuit such as the baseband circuit shown in FIG. 2. [Figure 15] 1A, 1B, 2-4, 5A-5C, 6A-6B, 7A-7B, 8-9, 10A-10B, and 11-14 illustrate block diagram embodiments of components that perform functions described herein, such as the functions described in connection with the embodiments described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] The following is a detailed description of the embodiments illustrated in the drawings, which covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.

[0006] To improve the performance of uplink transmission in a dynamic time division duplex (TDD) system, simultaneous downlink (DL) and uplink (UL) transmission and reception on the same frequency resources (subcarriers of the carrier bandwidth) can be considered. For example, dynamic TDD includes flexible symbols or slots that a base station can dynamically allocate or assign to downlink (DL) or uplink (UL) communications based on traffic load conditions, while static TDD includes a set of symbols that remain assigned to either DL or UL communications.

[0007] Dynamic TDD may further include non-overlapping subband full duplex (SBFD, or NO SBFD) where the channel bandwidth of a communication may include one or more UL and one or more DL communications on different sets of subcarriers, also referred to as subbands or bandwidth parts (BWPs). For example, within a symbol, a base station, such as a next-generation NodeB or gNodeB (gNB), may transmit DL on one subband and receive UL from a user equipment (UE) on another subband that does not overlap during SBFD operation. A subband corresponds to a number of contiguous frequency resources (e.g., Physical Resource Blocks (PRBs) on a Common Resource Block (CRB) grid) within a carrier. A communication resource as discussed herein refers to a frequency resource at a particular time within a communication. For example, a reference to two UEs transmitting or receiving on the same communication resource indicates simultaneous communication within the same frequency resource. Dynamic TDD as described herein may also include dynamic configuration of SBFD.

[0008] Without coordination between nearby or adjacent UEs, a certain type of cross link interference (CLI) can occur in dynamic TDD systems, especially when considering that two UEs from different operators may transmit DL and UL communications simultaneously within the same frequency band or bandwidth. For example, cross link interference in dynamic TDD systems can occur between UL and DL communications of nearby UEs due to different transmission directions (UL and DL) between nearby UEs at a given time on the same carrier frequency and within the same frequency bandwidth, especially when the UL communication of the first UE is pointed in the general direction of the receiving antenna of the second UE. It should be noted that CLI can also occur when the UL communication is omnidirectional, but the UE can use beamforming to point the UL communication in the direction of the base station that is the intended recipient of the UL. If the base station is in the general direction of the receiver of the second UE, the first UE may transmit UL in the general direction of the receiver of the second UE while the second UE is receiving DL.

[0009] Two types of CLI may be observed under dynamic TDD operation: User Equipment (UE)-to-User Equipment (UE) interference and inter-gNB interference. In the case of UE-to-UE interference, CLI occurs when a first UE's UL transmission interferes with a DL transmission from a gNB in ​​a serving cell to a neighboring UE. A "serving" cell, base station, or gNB generally refers to the base station of a cell of a cellular system that is transmitting DL communications to a UE. Furthermore, in the case of inter-gNB interference, inter-gNB CLI occurs when a neighboring gNB's DL transmission interferes with the serving cell gNB's reception of the UE's UL transmission.

[0010] At the UE, CLI may manifest as communication errors such as high error rates, dropped packets, and / or repeated DL transmissions of the same packets from the base station to the UE. Without coordination and synchronization between base stations, dynamic TDD may result in overlapping UL and DL transmissions. Thus, a UE may transmit UL close to a second UE when the second UE is attempting to receive a transmission from the base station on the same carrier, causing adjacent channel or co-channel CLI from the first UE's transmission to the second UE's reception of the base station's DL transmission.

[0011] During SBFD operation, a dynamic TDD UL transmission from a first UE may cause CLI not only in DL transmissions received by a second UE in the same (or overlapping) subbands of a carrier (co-channel CLI), but also in subbands adjacent to the DL transmission at the second UE (adjacent channel CLI). For example, SBFD operation may or may not include a guard band (a set of unused subcarriers) between UL and DL communications in the same symbol or slot, and neighboring UEs may have different configurations of SBFD symbols, especially if those UEs are in cells of different operators.

[0012] During SBFD communications, UL subbands may exist between DL subbands. Although guard bands, if used, can mitigate interference between UL and DL subbands, UL signals from an "aggressor" UE may cause inter-subband CLI to the DL subbands of nearby (or "victim") UEs. In such a situation, the victim UE (and / or the UE serving cell) may recognize the affected link based on communication errors, communication loss, etc. associated with the UE's DL communications.

[0013] Embodiments may define methods and apparatuses for measuring cross-link interference (CLI) during dynamic TDD communications to mitigate CLI and / or facilitate mitigation measures. For example, if a victim UE repeatedly detects errors in DL communications from a base station, the victim UE or base station may trigger periodic, semi-persistent, or aperiodic measurements of CLI of UL communications from aggressor UEs to determine parameters of the CLI, such as CLI-Received Signal Strength Indicator (CLI-RSSI) or Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP). In some embodiments, the victim UE may measure CLI from the aggressor UE when the aggressor UE transmits an UL communication to a base station associated with the aggressor UE. In some embodiments, the victim UE's base station may communicate with the aggressor base station, e.g., by backhaul signaling, to trigger periodic, semi-persistent, or aperiodic UL reference signal transmission from the aggressor UE to facilitate measurements of CLI-RSSI and / or SRS-RSRP. In some embodiments, the reference signal may include a sounding reference signal (SRS).

[0014] During preparation for UL transmission of the SRS, a first base station in the victim UE's serving cell may transmit or share, e.g., by backhaul signaling, a request for the aggressor UE to transmit the SRS periodically, semi-persistently, or aperiodically to a second base station in the aggressor UE's serving cell. The second base station may DL transmit an SRS resource configuration in DL control information (DCI) to the aggressor UE to schedule the transmission of the SRS periodically, semi-persistently, or aperiodically according to the SRS resource configuration. In some embodiments, the second base station may inform the first base station of the communication resources on which the aggressor UE may transmit the SRS in UL.

[0015] A first base station in a serving cell of the victim UE may send a DCI including a CLI measurement and reporting configuration to the victim UE to schedule measurements and directions by the victim UE. The CLI measurement and reporting configuration in the DCI may inform the victim UE of communication resources for SRS and / or measurement resources on which to measure SRS, and may define reporting information for generation of a CLI measurement report, such as a Layer 1 (L1) CLI-RSSI and / or an L1 SRS-RSRP.

[0016] After the victim UE successfully detects the DCI, the victim UE may measure the SRS by the SRS-RSRP or the CLI-RSSI and generate an L1 CLI measurement report. In some embodiments, the victim UE may send periodic, semi-persistent, or aperiodic L1 CLI measurement reports on a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH). In other embodiments, the victim UE may send periodic, semi-persistent, or aperiodic L1 CLI measurement reports on a medium access control-control element (MAC-CE).

[0017] In some embodiments, the aggressor UEs may be part of the same cell connected to the same base station. In such embodiments, the base station may send a first DCI to the aggressor UE to schedule UL SRS and a second DCI to the victim UE to schedule CLI measurement and reporting. After the aggressor UE detects the first DCI, the aggressor UE may send a periodic, semi-persistent, or aperiodic SRS in the UL to the base station. After the victim UE detects the second DCI, the victim UE may measure the SRS on the communication resource identified for the SRS UL and generate a CLI measurement report according to the CLI measurement and reporting configuration for transmission to the base station. The victim UE may send the CLI measurement report to the base station. The base station may then mitigate the CLI by moving the aggressor UE or victim UE to a different communication resource, communicating with the aggressor UE to adjust or limit the transmit power of UL communication in the communication resource, etc.

[0018] In some embodiments, the base station may schedule CLI measurements and reporting during SBFD operation. In such embodiments, the SRS resource configuration may define subbands on which the aggressor UE may transmit the SRS. In some embodiments, the CLI resource measurement and reporting configuration may define UL subbands within the communication resources of the SRS and / or one or more DL subbands on which the victim UE may measure the SRS, and / or one or more subband measurements within one or more or each of the DL subbands to increase the granularity of the subband measurements.

[0019] In some embodiments, the victim UE's base station may transmit or share CLI measurement and reporting configurations to other neighboring base stations over a backhaul, such as an Xn interface, so that the neighboring base stations can transmit periodic, semi-persistent, or aperiodic CLI measurement reports. In some embodiments, the victim UE's base station may transmit or share a PDU with one or more bits over the backhaul to trigger CLI measurement reports from neighboring cells.

[0020] In some embodiments, the victim UE's base station may transmit or share CLI resources and measurement report configurations including muting patterns to other neighboring base stations over a backhaul such as an Xn interface to mute one or more neighboring base stations during the measurement of the SRS. For example, the victim UE's base station may transmit CLI resources and measurement report configurations to schedule zero power (ZP) CLI-RS transmissions to neighboring base stations to instruct or force other base stations to mute the channel during the measurement.

[0021] An embodiment may define CLI measurements for an evolved NodeB (eNB) for a Radio Access Network (RAN), such as RAN1, and a NodeB, such as gNB. RAN may be an abbreviation for Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and the numbers, such as 1 and 2, may represent release numbers of the 3rd Generation Partnership Project (3GPP) E-UTRAN standard. NR may coexist with 3GPP Long Term Evolution (LTE) radio and may include beamforming for higher frequencies, such as frequencies above 6 gigahertz (GHz).

[0022] In some embodiments, the victim UE's base station may exchange information for the configuration of the SBFD symbol or slot. The base station may share the SBFD configuration with neighboring base stations, including one or more configurations of intended DL sub-bands and / or UL sub-bands within the SBFD symbol, which may include at least an identification of frequency resources that may be used for DL ​​reception at the victim UE, the overall frequency resources including both UL and DL, which may be identified by signaling similar to an indication of the location of the BWP and bandwidth (BW) configuration, one or more guard bands, if any, within the SBFD symbol and their location in frequency, the time domain location of the SBFD symbol, etc.

[0023] In the case of the RAN, the base station may execute E-UTRAN codes and protocols that are used for the base station's air interface and for interaction with other devices in the E-UTRAN, such as UEs, and may include radio resource management (RRM) in the radio resource control (RRC) layer.

[0024] Various embodiments may be designed to address various technical challenges associated with crosslink interference, such as measuring CLI, communicating with neighboring base stations, transmitting or sharing CLI resources and measurement report configurations, transmitting or sharing CLI assumptions and report configurations, scheduling SRS for measurements, identifying Layer 1 measurement reports for measurements, determining parameters related to measurements, determining communication configurations for measurements, synchronizing SBFD communications for measurements, muting neighboring base stations during measurements, determining CLI measurement report configurations or definitions, and sharing or transmitting measurement reports.

[0025] Various technical problems as described above may be addressed by one or more different embodiments. An embodiment may address one or more of these problems related to crosslink interference. For example, some embodiments addressing problems related to crosslink interference may do so by one or more different technical means, such as scheduling measurement of CLI, scheduling transmission of SRS by an aggressor UE for measurement, determining a muting pattern during measurement, sharing a muting pattern for measurement by a first base station with a nearby or neighboring base station, determining parameters of CLI resources and measurement configuration, determining parameters of CLI measurement and reporting configuration, identifying Layer 1 measurement reports for CLI measurements, identifying point A as a reference point for communication resources, repeatedly transmitting SRS for measurement and reporting, repeatedly measuring SRS for CLI measurement reports, sharing CLI measurement reports, performing measurements of SRS for SBFD communication, etc.

[0026] Some embodiments include systems with multiple processor cores, such as central servers, access points, and stations (STAs), such as modems, routers, switches, servers, workstations, netbooks, mobile devices (e.g., laptops, smartphones, tablets), sensors, meters, controls, appliances, monitors, home or office equipment, Internet of Things (IoT) gear (e.g., watches, glasses, headphones, cameras, etc.). Some embodiments may provide, for example, indoor and / or outdoor "smart" grid and sensor services. In various embodiments, these devices are associated with specific applications, such as healthcare, home, commercial office and retail, security, industrial automation and surveillance applications, and vehicle applications (cars, autonomous vehicles, airplanes, drones, etc.).

[0027] The techniques disclosed herein may include transmission of data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may include transmission over one or more wireless connections according to one or more 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), 3GPP LTE-Advanced (LTE-A), 4G LTE, and / or 5G New Radio (NR) technologies and / or protocols, modifications, progenies, and variations thereof. Various embodiments may additionally or alternatively include transmission according to one or more Global System for Mobile Communications (GSM) / Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS) / High Speed ​​Packet Access (HSPA), and / or GSM with General Packet Radio Service (GPRS) (GSM / GPRS) technologies and / or standards, modifications, progenies, and variations thereof.

[0028] Examples of wireless mobile broadband technologies and / or standards include, without limitation, the Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standard, such as IEEE 802.16m and / or 802.16p, International Mobile Telecommunications Advanced (IMT-ADV), Worldwide Interoperability for Microwave Access (WiMAX) and / or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), High Performance Radio Metropolitan Area Network (HIPERMAN), wireless broadband (WiBro), High Speed ​​Downlink Packet Access (HSDPA), Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA), High-Speed ​​Uplink Packet Access (HSUPA), and the like. Access) technology and / or standards, and any modifications, progeny, and variations thereof.

[0029] Some embodiments may also perform wireless communications according to other wireless communication technologies and / or standards. Examples of other wireless communication technologies and / or standards that may be used in various embodiments include, without limitation, other IEEE wireless communication standards, such as IEEE 802.11-2020, IEEE 802.11ax-2021, IEEE 802.11ay-2021, IEEE 802.11ba-2021, and / or other specifications and standards, such as the Wi-Fi Alliance (WFA) Neighbor Awareness Networking (NAN) Task Group, Machine Type Communication (MTC) standards, such as 3GPP Technical Report (TR) 23.887, 3GPP Technical Specification (TS) 22.368, 3GPP TS23.682, 3GPP TS36.133, 3GPP TS36.306, 3GPP TS36.321, 3GPP TS36.331, 3GPP TS38.133, 3GPP TS38.306, 3GPP TS38.321, 3GPP TS38.214, and / or 3GPP TS38.331, and / or Near Field Communication (NFC) standards, such as standards produced by the NFC Forum, and any modifications, progenies, and / or variations of any of these.

[0030] 1A shows a communication network 100 for cross-link interference measurement and mitigation. The communication network 100 is an Orthogonal Frequency Division Multiplexing (OFDM) network including a primary base station 101, a first user equipment UE-1, a second user equipment UE-2, a third user equipment UE-3, and a secondary base station 102. In a 3GPP system based on Orthogonal Frequency Division Multiple Access (OFDMA) downlink, radio resources are divided into subframes in the time domain, and each subframe consists of two slots. Each OFDMA symbol further consists of a number of OFDMA subcarriers in the frequency domain depending on the system (or carrier) bandwidth. The basic unit of the resource grid is called a Resource Element (RE), where the OFDMA subcarriers are arranged over one OFDMA symbol. A Resource Block (RB) includes a group of REs, and each RB may have, for example, 12 consecutive subcarriers in one slot.

[0031] Some physical downlink channels and reference signals use a set of resource elements carrying information originating from higher layers of codes. For downlink channels, the physical downlink shared channel (PDSCH) is the main data-carrying downlink channel, while the physical downlink control channel (PDCCH) may carry downlink control information (DCI). The control information may include information on scheduling decisions, reference signal information, rules for forming the corresponding transport blocks (TBs) carried by the PDSCH, and power control commands. The UE may use cell-specific reference signals (CRS) for demodulating the control / data channels in non-precoded or codebook-based precoded transmission modes, monitoring the radio link, and measuring channel state information (CSI) feedback. The UE may use UE-specific reference signals (DM-RS) for demodulating the control / data channels in non-codebook-based precoded transmission modes.

[0032] The communication network 100 may have cells, such as microcells or macrocells, and the base station 101 may provide wireless service to UEs in the cells. The base station 102 may provide wireless service to UEs in other cells that are adjacent to or overlapping the cells. In other embodiments, the communication network 100 may have microcells, and the base station 102 may operate smaller cells within the macrocells, such as microcells or picocells. Other examples of small cells include, without limitation, microcells, femtocells, or other types of smaller sized cells.

[0033] In various embodiments, base station 101 and base station 102 may communicate over a backhaul. In some embodiments, the backhaul may include a wired backhaul. In various other embodiments, the backhaul may include a wireless backhaul. In some embodiments, the backhaul may include an interface defined between RAN nodes or base stations, for example, an Xn interface or an F1 interface, which is the backhaul between base station 101 and base station 102. The Xn interface is an interface for a gNB, and the F1 interface is an interface for a gNB-distributed unit (DU) when the architecture of communication network 100 is a central unit / distributed unit (CU / DU) architecture.

[0034] Base stations 101 and 102 may exchange protocol data units (PDUs) over the backhaul. As an example, for an Xn interface, base station 101 may transmit or share control plane PDUs over the Xn-C interface and may transmit or share data PDUs over the Xn-U interface. For an F1 interface, base station 101 may transmit or share control plane PDUs over the F1-C interface and may transmit or share data PDUs over the F1-U interface. Discussions herein regarding signaling, sharing, receiving, or transmitting over the Xn interface may refer to signaling, sharing, receiving, or transmitting over the Xn interface, the Xn-U interface, or a combination thereof. Similarly, discussions herein regarding signaling, sharing, receiving, or transmitting over the F1 interface may refer to signaling, sharing, receiving, or transmitting over the F1-C interface, the F1-U interface, or a combination thereof.

[0035] In some embodiments, the base stations 101 and 102 may have CLI logic that cooperates over the backhaul or by other communication methods to schedule periodic, semi-persistent, and / or aperiodic CLI-reference signal (CLI-RS) transmissions, such as SRS, by the aggressor UE. The CLI logic may schedule CLI measurements and reports based on the victim UE and possibly other base stations and other UEs connected to the other base stations through the backhaul. The resource signal and measurement process may measure CLI with dynamic TDD using flexible symbols in addition to dynamic TDD including SBFD operation, and trigger the generation of CLI measurement reports, such as L1 CLI measurement reports, that are transmitted to the victim UE's base station and possibly nearby base stations so that the base station can take mitigation measures or actions to reduce or eliminate the CLI.

[0036] The CLI resource and measurement reporting configuration may include an SRS configuration and a CLI measurement and reporting configuration. The SRS configuration may include communication resources for transmission of the SRS. The CLI measurement and reporting configuration may include communication resources for measurement of the SRS or other UL communications, such as communication resources on which the SRS or other UL may transmit and communication resources for measuring the SRS or other UL communications. The CLI measurement and reporting configuration may also include definitions for CLI measurement reports.

[0037] It should be noted that in some embodiments, the CLI resource and measurement reporting configuration and / or the CLI measurement and reporting configuration may include CLI measurements and reports that have not yet been transmitted to the UE and / or other base stations, CLI measurements and reports that are not yet known by the UE and / or other base stations, or one or more parameters of the CLI measurements and reports that have changed from one or more parameters that are already known or previously transmitted. For example, the definition of the CLI measurement reports may be specified by use or set as a default configuration and may not be part of the CLI measurement and reporting configuration.

[0038] In some embodiments, the aggressor UE-1 from the first cell transmits a sounding reference signal (SRS) or other uplink channel / signal in the UL subband for SBFD operation. The victim UE-3 from the second cell measures the inter-subband CLI on configured or indicated resources in the DL subband. The victim UE-3 may then report the CLI measurement report (result) to the base station 102 in the second cell, which in some embodiments may transmit the CLI measurement report to one or more neighboring base stations, such as the base station 101 in the first cell, or share the CLI measurement report with one or more neighboring base stations via backhaul signaling, e.g., an Xn interface or an F1 interface for a central unit / distributed unit architecture.

[0039] In some embodiments, base station 101 coordinates with base station 102 for CLI measurement and reporting over the backhaul. Base station 101 schedules SRS transmission for CLI measurement and reporting by UE-1 via transmission of a first DCI. After UE-1 successfully detects the first DCI, UE-1 transmits SRS for CLI measurement according to the SRS resource configuration indicated in the first DCI. Base station 102 schedules CLI measurement and reporting configuration for UE-3 via transmission of a second DCI. After UE-3 successfully detects the second DCI, UE-3 measures SRS-RSRP on the time and frequency resources (communication resources) indicated by the second DCI, and reports the measured SRS-RSRP in a CLI measurement report via a scheduled PUSCH or PUCCH also indicated in the second DCI. It should be noted that if the SRS-RSRP is included in the MAC-CE, the PUSCH carrying the SRS-RSRP may be the first available PUSCH slot after the generation of the CLI measurement report by UE-3.

[0040] In some embodiments, CLI logic circuitry in UE-3 or base station 102 may determine the presence of CLI in UE-3 and determine to mitigate the CLI if it exceeds a threshold, such as an energy threshold, a noise threshold, or an error threshold, that causes errors in the process of capturing the DL transmission. In some embodiments discussed herein, a UE that experiences a CLI is referred to as a victim UE, and a UE that is causing the CLI is referred to as an aggressor UE. It should be noted that any UE can be an aggressor, a victim, or both an aggressor and a victim, depending on the circumstances.

[0041] In some embodiments, the CLI logic of base station 101 may decide to communicate with base station 102 to address the CLI. In such embodiments, the CLI logic of base station 101 may send or share a PDU that includes a source address, a destination address, a source tunnel endpoint identifier (TEID), a destination TEID, etc., and an instruction to trigger or request base station 102 to adjust measurements of the CLI for mitigation.

[0042] In some embodiments, if base station 101 identifies a CLI in an SBFD communication, base station 101 may generate and send an SRS configuration to UE-1 to schedule periodic, semi-persistent, or aperiodic SRS transmissions by UE-1 on the UL subbands of SBFD, and generate a CLI resource measurement and reporting configuration for SBFD operation. The CLI resource measurement and reporting configuration for SBFD operation may include one or more parameters of the SBFD configuration that include an identification of one or more DL bands of SBFD in the measurement configuration for victim UE-2 to measure the CLI and generate a CLI measurement report.

[0043] After measuring the SRS in SBFD, the victim UE-2 may generate an L1 CLI measurement report as indicated in the CLI measurement and reporting configuration. The CLI measurement and reporting configuration may identify the CLI measurement report as SRS-RSRP or CLI-Received Signal Strength Indicator (CLI-RSSI). The L1 CLI measurement report may include a signal measurement of SRS-Reference Signal Received Power (SRS-RSRP) or CLI-Received Signal Strength Indicator (CLI-RSSI), or may include an average (or other combination) of two or more measurements of periodic, semi-persistent, or aperiodic SRS transmissions by the aggressor UE-1 for generation of the L1 CLI measurement report. In some embodiments, the L1 CLI measurement report may include an algorithm that determines an average, mean value, or other combination of multiple measurements.

[0044] After the CLI logic of victim UE-2 and optionally nearby stations may generate the CLI measurement report, the CLI logic of victim UE-2 and optionally nearby stations may transmit or share the CLI measurement report to base station 101. In some embodiments, victim UE-2 may generate multiple CLI measurement reports, such as one per DL in SBFD operation, and share the multiple CLI measurement reports with base station 101, which may share the multiple CLI measurement reports with nearby base stations.

[0045] Once base stations 101 and 102 have one or more CLI measurement reports, base station 101 and / or base station 102 may mitigate the CLI by one or more mitigation actions, such as moving one or more UEs to other communications resources, reducing or limiting the transmission power by aggressor UEs to the communications resources experiencing the CLI, etc.

[0046] FIG. 1B illustrates an embodiment of a dynamic TDD system including base stations, gNBs 152 and 162, and user equipments 156 and 166 associated with gNBs 152 and 162, respectively, such as the user equipment and base station illustrated in FIG. 1A, to illustrate crosslink interference 170 and 172, respectively. In this example, due to different transmission directions between neighboring gNBs at a given time, two types of CLI may be observed under dynamic TDD operation: UE-to-UE interference 172 and gNB-to-gNB interference 170. In the case of UE-to-UE interference 172, CLI occurs when a UE transmission 164 from a UE 166 to a nearby base station gNB 162 interferes with the reception of a DL transmission 154 from a serving base station gNB 152 by the UE 156. Furthermore, in the case of gNB-to-gNB interference 170, CLI occurs when a DL transmission 154 of a nearby base station gNB 152 interferes with the reception of a UL transmission 164 from a UE 166 by the serving base station gNB 162. In other words, DL transmission 154 creates gNB-to-gNB interference 170 when energy from DL transmission 154 is detected at the receiver antenna of gNB 162 when gNB 162 is attempting to receive UL transmission 164. Similarly, UL transmission 164 creates UE-to-UE interference 172 when energy from UE transmission 164 is detected at the receiver antenna of UE 156 when UE 156 is attempting to receive DL transmission 154. In static TDD, this situation does not typically occur since nearby gNBs transmit DL and UL at the same time (during the same communication resource).

[0047] 2 is a simplified block diagram 200 of a base station 201 and a user equipment (UE) 211 that may implement certain embodiments of the present invention in a communication network, such as the base station 101, UE, and communication network 100 shown in FIG. 1. For the base station 201, an antenna 221 transmits and receives radio signals. An RF circuit 208, which is coupled to the antenna 221 and is a physical layer of the base station 201, receives the RF signals from the antenna 221, converts the signals into digital baseband signals or uplink data, and sends them to a processor 203, also called a processing circuit or a baseband processing circuit, of the baseband circuit 251 through an interface of the baseband circuit 251. The RF circuit 208 also converts digital baseband signals or downlink data received from the processor 203 through an interface of the baseband circuit 251, converts them into RF signals, and sends the RF signals to the antenna 221.

[0048] The processor 203 decodes and processes digital baseband signals or uplink signals and invokes different functional modules to perform functions within the base station 201. The memory 202 stores program instructions or code and data 209 for controlling the operation of the base station 201. The processor 203 may also execute code, such as RRC layer code, from the code and data 209 to implement RRC layer functions.

[0049] A similar configuration exists in the UE 211, where an antenna 231 transmits and receives RF signals. An RF circuit 218 coupled to the antenna receives the RF signals from the antenna 231, converts them to baseband signals or downlink data, and sends them to the processor 213 of the baseband circuit 261 via the interface of the baseband circuit 261. The RF circuit 218 also converts digital baseband signals or uplink data from the processor 213 to RF signals, and sends the RF signals to the antenna 231.

[0050] The RF circuitry 218 implements multiple RF chains. Although the RF circuitry 218 represents five RF chains, each UE may have a different number of RF chains, and each of the illustrated RF chains may represent multiple time domain receive (RX) and transmit (TX) chains. The RX and TX chains include circuitry that may operate on or modify a time domain signal transmitted through a time domain chain, such as circuitry for inserting a guard interval in the TX chain and circuitry for deleting a guard interval in the RX chain. For example, the RF circuitry 218 may include transmitter and receiver circuitry, which may be referred to as transceiver circuitry. The transmitter circuitry may prepare digital data from the processor 213 for transmission by the antenna 231. To prepare for transmission, the transmitter may encode data, modulate the encoded data, and form the modulated encoded data into Orthogonal Frequency Division Multiplexing (OFDM) and / or Orthogonal Frequency Division Multiple Access (OFDMA) symbols. The transmitter may then convert the symbols from the frequency domain to the time domain for input to the TX chain. The TX chain may include a chain for each subcarrier of the RF chain's bandwidth and may operate on time domain signals within the TX chain to prepare them for transmission on the component subcarriers of the RF chain. For wide bandwidth communications, more than one RF chain may simultaneously process symbols representing data from the baseband processor.

[0051] The processor 213 decodes and processes digital baseband or downlink signals and invokes different functional modules to perform functions within the UE 211. The memory 212 stores program instructions or code and data 219 for controlling the operation of the UE 211. The processor 213 may also execute Medium Access Control (MAC) layer code of the code and data 219 for the RUE 211. For example, the MAC layer code may be executed by the processor 213 such that UE communications are transmitted to the base station 201 over one or more RF channels of a physical layer (PHY). The PHY is RF circuitry 218 and associated logic, such as some or all of the functional modules.

[0052] The base station 201 and the UE 211 may include several functional modules and circuits for performing several embodiments. Different functional modules may include circuits or circuit configurations that may be configured and implemented by code, hardware, or any combination thereof. Each functional module may implement the function as circuit configurations or as code and processing circuitry configured to perform the function, and may also be referred to as a functional block. For example, the processor 203 (e.g., by executing the program code 209) is a functional block that configures and implements the circuits of the functional modules so that the base station 201 can schedule (via the scheduler 204), encode or decode (via the codec 205), modulate or demodulate (via the modulator 206), and transmit data to or receive data from the UE 211 via the RF circuitry 208 and the antenna 221.

[0053] The processor 213 (e.g., by executing program code in code and data 219) may be a functional block that configures and implements circuitry of functional modules such that the UE 211 can receive or transmit data appropriately via the RF circuitry 218 and antenna 231, demodulate or modulate (via demodulator 216), and decode or encode (via codec 215).

[0054] Both the UE 211 and the base station 201 may include CLI logic 240 and 235, which are functional modules, respectively. The CLI logic 235 of the base station 201 may include some code and data 209 in the memory 202 in some embodiments and may cause the processor 203 to perform operations to measure and mitigate CLI associated with dynamic TDD operations including flexible symbols and / or SBFD symbols. For example, the processor 203 may cause the base station 201 to transmit an SRS resource configuration or trigger PDU to the second base station via backhaul signaling or other communication medium. The SRS configuration may transmit the trigger PDU to trigger the second base station to transmit the SRS configuration to the aggressor UE for CLI measurement. In some embodiments, the processor 203 of the base station 101 may transmit the SRS configuration to the connected aggressor UE to schedule transmission of the SRS according to the SRS configuration.

[0055] The base station 201 may send a CLI resource measurement and reporting configuration to the victim UE to schedule CLI measurements and reports based on the SRS. The CLI resource measurement and reporting configuration may include an identification of communication resources on which the SRS should be measured and a definition of the CLI measurement report. The communication resources on which the SRS should be measured may include communication resources on which the victim UE can measure the SRS or communication resources on which the aggressor UE transmits the SRS. In some embodiments, the CLI measurement report may include the L1 CLI-RSSI or the L1 SRS-RSRP.

[0056] After transmitting the CLI measurement and reporting configuration to the victim UE (UE 211), the CLI logic 240 of the UE 211 may cause the processor 213 to measure one or more periodic, semi-persistent, and / or aperiodic transmissions of the SRS and generate a CLI measurement report defined in the CLI measurement and reporting configuration. The CLI logic of the UE 211 may transmit a CLI measurement report back to the base station 201 in response to measuring the one or more periodic, semi-persistent, and / or aperiodic transmissions of the SRS. In some embodiments, the CLI logic of the UE 211 may transmit a CLI measurement report for each SRS transmission in accordance with the CLI measurement and reporting configuration. In some embodiments, the CLI logic of the UE 211 may transmit a CLI measurement report, such as an L1 CLI-RSSI measurement report or an L1 SRS-RSRP measurement report, for each SRS transmission in accordance with the CLI measurement and reporting configuration.

[0057] The CLI logic 235 of the base station 201 may receive the CLI measurement report and determine, depending on the contents of the CLI measurement report, what mitigation action, if any, to take. For example, the CLI logic 235 of the base station 201 may determine that the mitigation action to beneficially mitigate CLI between UEs is to reduce the transmit power of DL transmissions on the communication resources experiencing the CLI indicated by the aggressor UE in the CLI measurement report or to move the victim UE DL to an alternative communication resource.

[0058] 3A illustrates an embodiment of communication 300 between user equipment and base stations, such as the user equipment and base stations illustrated in FIG. 1A, FIG. 1B, and FIG. 2, for inter-cell cross-link interference measurement and reporting. More specifically, this embodiment illustrates an example of an L1 CLI measurement and reporting procedure for UE-to-UE CLI mitigation with aperiodic SRS transmission. In such an embodiment, one base station may transmit one or both of DCI#1 and DCI#2, or a first base station may transmit DCI#1 to the aggressor UE#1, and a second base station may transmit DCI#2 to the victim UE#2 in backhaul coordination with the first base station.

[0059] Based on the SRS configuration in DCI#1 for scheduling SRS transmission sent by the base station to UE#1, UE#1 may transmit SRS for CLI measurement in slot#1. Based on the CLI measurement and reporting configuration in DCI#2 for scheduling measurement and reporting by UE#2, UE#2 may measure SRS to generate SRS-RSRP in slot#1 and report the measured SRS-RSRP by PUSCH in slot#3. It should be noted that DCI#1 for UE#1 and DCI#2 for UE#2 may be transmitted at different times depending on scheduler decisions from different base stations.

[0060] In another embodiment, when UE#2 includes the SRS-RSRP in the MAC-CE, the PUSCH carrying the SRS-RSRP may be the first available PUSCH after the generation of the SRS-RSRP. In yet another embodiment, DCI#2 may indicate the CLI-RSSI for measurement reporting, and UE#2 may measure the SRS to generate the CLI-RSSI and transmit the CLI-RSSI to the base station connected to UE#2.

[0061] FIG. 3B illustrates another embodiment of communication between user equipment and base station, such as the user equipment and base station illustrated in FIG. 1A, FIG. 1B, and FIG. 2, for measuring and reporting inter-cell cross-link interference. More specifically, this embodiment illustrates an example of an L1 CLI measurement and reporting procedure for mitigating inter-UE CLI by periodic SRS transmission. For example, the base station transmits DCI (not shown) including an SRS configuration defining periodic transmission of SRS to UE#1. UE#1 may transmit an SRS for CLI measurement in slot#1 based on the periodic configuration. Also, based on the CLI measurement and reporting configuration indicated in DCI#1 and transmitted to UE#2, UE#2 may measure SRS in slot#1 and generate SRS-RSRP, and report the SRS-RSRP to the base station by PUSCH in slot#3. In other embodiments, if DCI#1 defines an SRS-RSRP for CLI measurement reporting, the SRS-RSRP may be included in the MAC-CE, and the PUSCH may carry the SRS-RSRP, for example, on the first available PUSCH after generation of the RSR-.

[0062] In another embodiment, DCI#1 may indicate L1-RSSI for CLI measurement report in CLI measurement and reporting configuration for UE-UE CLI mitigation. Furthermore, in the case of L1 CLI-RSSI, the base station does not need to trigger SRS transmission. The base station may schedule PUSCH / PUCCH transmission for UE#1 in slot#1, and the base station may instruct UE#2 in DCI#1 to perform CLI-RSSI measurement in the same symbol or slot as the PUSCH / PUCCH transmission.

[0063] In some embodiments, the base station may schedule the SRS transmission from UE#1 using an existing DCI format, e.g., DCI format 0_1 ​​or 1_1. In some embodiments, the base station may use a new DCI format defined to schedule one or more SRS transmissions to one or more UEs. For example, a new group-wide DCI format may be defined to schedule one or more SRS transmissions from a group of UEs. The CLI logic of the base station may determine or configure a mapping of UE index to corresponding SRS resources, and the transmission of an L1 trigger by the base station may determine a reference time, e.g., a starting symbol for one or more of the SRS resources in time-frequency. In other words, the CLI logic may map SRS configurations for a plurality of UEs and determine the timing of SRS transmission for each of the plurality of UEs based on the transmission of an L1 trigger in the DCI to each UE among the plurality of UEs or to each group of one or more UEs.

[0064] In some embodiments, the CLI logic of the base station may transmit the DCI with a new field, and the value of one or more bits of the new field may be set to trigger CLI measurements and reporting from the UE on the PUSCH or PUCCH. In some embodiments, the CLI logic of the base station may transmit the DCI with a new DCI format that may be defined to trigger one or more CLI measurements for a UE. The UE may report measurement results of all triggered SRSs on the PUSCH or PUCCH.

[0065] In another embodiment, the CLI logic of the base station may transmit the DCI in a new group common DCI format defined to direct CLI measurements and reports for a group of UEs based on a mapping of UE index to PUSCH resource. The CLI logic of the base station may determine or configure a mapping of UE index to PUSCH resource to carry the measurement report, and the CLI logic of the base station may transmit an L1 trigger in the DCI to each UE to determine a reference time, e.g., the starting symbol of the PUSCH or PUCCH at which the UE transmits the CLI measurement report to the base station.

[0066] In some embodiments, for Layer 1 triggering of measurements on CLI resources, e.g., measurements on SRS resources, the minimum processing time between the L1 trigger and the CLI resource occasion will be equal to that for the L1 trigger for transmission of A-SRS as defined in the Rel-15 NR specifications as found in 3GPP TS38.214.

[0067] In some embodiments, for Layer 1 reporting of CLI measurements (as UL control information "UCI"), the minimum processing time between a CLI resource and a PUSCH or PUCCH transmission including a measurement corresponding to the CLI resource is the same as the minimum processing time defined between a channel state information resource (CSI-RS) and a corresponding aperiodic CSI report in the PUSCH as defined in the Rel-15 NR specifications. In some embodiments, the minimum processing time between a CLI resource and a PUSCH or PUCCH transmission including a measurement corresponding to the CLI resource is less than the minimum processing time defined between a CSI-RS resource and a corresponding aperiodic CSI report in the PUSCH. In some embodiments, basic and advanced features regarding the minimum processing time for reporting of CLI measurements may be defined to be applied based on the UE's support for mandatory and advanced processing times of CSI feedback. In some embodiments, the minimum processing time between a CLI resource and a PUSCH / PUCCH may be different for different CLI resources. For example, the minimum processing time is different for CLI resources for SRS-RSRP measurements and for RSSI measurements.

[0068] FIG. 3C illustrates an embodiment of a crosslink interference (CLI) measurement report of Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP) and / or Crosslink Interference-Received Signal Strength Indicator (CSI-RSSI) in a channel state information (CSI) report by a user equipment to a base station, such as the user equipment and base stations illustrated in FIGS. 1A, 1B, 2, and 3A-3B. In this embodiment, the UE may report the SRS-RSRP and / or CSI-RSSI as part of the CSI report. In such an embodiment, the UE may include the SRS-RSRP and / or CLI-RSSI in a CSI reporting configuration as reportQuantity 320. The reportQuantity 320 in the CSI report may include the SRS-RSRP 322 and / or CLI-RSSI 324 for L1 CLI measurement and reporting.

[0069] Note that for this embodiment, the UE may include the SRS-RSRP and / or CLI-RSSI in CSI part 1. This indicates that the SRS-RSRP and / or CLI-RSSI have the same priority as CSI part 1 for handling CSI drops on the PUSCH and / or PUCCH.

[0070] In other embodiments, the UE may include the SRS-RSRP and / or CLI-RSSI in CSI part 2. In this case, the SRS-RSRP and / or CLI-RSSI have the same priority as CSI part 2 to handle CSI drops on the PUSCH and / or PUCCH.

[0071] As an example, for CSI part 2, SRS-RSRP and / or CLI-RSSI may have lower priority than other CSI reports. In such an embodiment, if there are not enough REs for CSI part 2, the UE may drop SRS-RSRP and / or CLI-RSSI first. As another example, SRS-RSRP and / or CLI-RSSI may have higher priority than other CSI reports. In such an embodiment, if there are not enough REs for CSI part 2, the UE may drop other CSI reports first.

[0072] FIG. 3D illustrates an embodiment of a CLI measurement report of SRS-RSRP and / or CSI-RSSI in an uplink control information (UCI) format by a user equipment, such as the user equipment and base stations illustrated in FIG. 1A, FIG. 1B, FIG. 2, and FIG. 3A-3B, to a base station. In this embodiment, the SRS-RSRP and / or CLI-RSSI may be considered as separate UCI types 330. FIG. 3D illustrates an example of a bit ordering of UCI types 330 including hybrid automatic repeat-request acknowledgement (HARQ-ACK) feedback, scheduling request (SR), CSI part 1, SRS-RSRP and / or CLI-RSSI 332, and CSI part 2. The UE may transmit the UCI type 330 including the SRS-RSRP and / or CLI-RSSI 332 to the base station. In such an embodiment, multiple UCI types may be multiplexed on the PUSCH and / or PUCCH to add SRS-RSRP and / or CLI-RSSI 332 before CSI Part 1 and after CSI Part 2.

[0073] FIG. 3E illustrates another embodiment of CLI measurement reporting of SRS-RSRP and / or CSI-RSSI in an uplink control information (UCI) format by a user equipment, such as the user equipment and base station illustrated in FIG. 1A, FIG. 1B, FIG. 2, and FIG. 3A-3B, to a base station. In this embodiment, the SRS-RSRP and / or CLI-RSSI may be considered as separate UCI types 340. FIG. 3E illustrates another example of bit ordering of UCI types 340 including HARQ-ACK feedback, SR, CSI part 1, CSI part 2, and SRS-RSRP and / or CLI-RSSI 342. The CLI logic of the UE may transmit the UCI type 340 including the SRS-RSRP and / or CLI-RSSI 342 to the base station. In such an embodiment, multiple UCI types may be multiplexed on the PUSCH and / or PUCCH to add the SRS-RSRP and / or CLI-RSSI 342 after the CSI part 2.

[0074] In some embodiments, the CLI logic of the UE may support up to two separate encodings for multiple UCI types when multiple UCI types are multiplexed in PUCCH formats 3 and 4. In some embodiments, the CLI logic of the UE may separately encode the SRS-RSRP and / or CLI-RSSI 342 along with CSI part 1 and CSI part 2. In such embodiments, the UE may transmit only two of the SRS-RSRP and / or CLI-RSSI 342, CSI part 1, and CSI part 2. For example, the UE may transmit only the SRS-RSRP and / or CLI-RSSI and CSI part 1.

[0075] In some embodiments, when multiple UCI types are multiplexed in PUCCH formats 3 and 4, the CLI logic circuitry of the UE may jointly encode the SRS-RSRP and / or CLI-RSSI 342 with CSI part 1 and jointly encode the SRS-RSRP and / or CLI-RSSI 342 with CSI part 2. In some embodiments, when multiple UCI types are multiplexed in PUCCH formats 3 and 4, the CLI logic circuitry of the UE may jointly encode the SRS-RSRP and / or CLI-RSSI 342 with CSI part 2.

[0076] In some embodiments, the UE may support up to three separate encodings for multiple UCI types when multiple UCI types are multiplexed on the PUSCH. In some embodiments, the CLI logic of the UE may separately encode the SRS-RSRP and / or CLI-RSSI 342 along with CSI Part 1 and CSI Part 2. In such embodiments, the UE may transmit only two of the SRS-RSRP and / or CLI-RSSI, CSI Part 1, and CSI Part 2. For example, the UE may transmit only the SRS-RSRP and / or CLI-RSSI and CSI Part 1.

[0077] In some embodiments, the CLI logic of the UE may jointly encode the SRS-RSRP and / or CSI-RSSI with CSI Part 1. In further embodiments, when multiple UCI types are multiplexed on the PUSCH, the SRS-RSRP and / or CLI-RSSI 342 may be jointly encoded with CSI Part 2. Additionally, the base station may set beta_offset for the SRS-RSRP and / or CLI-RSSI separately. In some embodiments, the CLI logic of the UE and / or base station may define a metric such as a channel quality indicator (CQI) that is derived based on measurements on configured and / or indicated SRS resources for reporting Layer 1 reports (as UCI) of SRS measurements of the CLI instead of the SRS-RSRP. In further embodiments, a 4-bit CQI Table 1 (defined in Table 5.2.2.1-2 of 3GPP TS38.214) may be used for reporting SRS-CQI by CQI index values, each CQI index value being associated with a modulation, code rate, and efficiency value.

[0078] In some embodiments, for Layer 1 reporting of SRS measurements (as UCI) of the CLI, the CLI logic of the base station and / or UE may define a one-shot SRS-RSRP or CLI-RSSI without application of L3 filtering. In further embodiments, for Layer 1 reporting of SRS measurements (as UCI) of the CLI, the CLI logic of the base station and / or UE may define an instantaneous SRS-RSRP or CLI-RSSI without application of L3 filtering such that the measurements are averaged over a configured or specified number of SRS transmissions for the determination of the instantaneous SRS-RSRP or averaged over a configured or specified number of OFDM symbols for the determination of the instantaneous CLI-RSSI.

[0079] FIG. 4 illustrates an embodiment of communication 400 between more than one UE and a base station, such as the user equipment and base station illustrated in FIG. 1A, FIG. 1B, and FIG. 2, including non-overlapping sub-band full duplex (SBFD) communication 410. FIG. 4 illustrates the base station communication 400 in a frequency bandwidth versus time graph, starting with DL 402. DL 402 is the first communication covering the entire channel bandwidth of the channel of communication 400. The second communication is “F” 404, which is a flexible symbol. Flexible symbols refer to symbols that have dynamic allocation under dynamic TDD, i.e., the base station can dynamically choose to use flexible symbols for DL ​​or for UL to dynamically manage UL / DL traffic conditions. If a first UE transmits UL to a first base station with flexible symbol F 404, while a second neighboring UE receives DL with a flexible symbol corresponding to the same communication resource as F 404, CLI may be caused in the second neighboring UE by the first UE's UL with F 404.

[0080] To achieve efficient scheduling of UEs in the DL and UL portions of a symbol or slot with SBFD operation, the base station may identify CLI due to power leakage from transmissions in the UL subband into resources in symbols or slots that do not overlap with the UL subband (referred to as UE-to-UE inter-subband CLI).

[0081] SBFD 410 includes three parallel communications DL 412, UL 414, and DL 416, for example. SBFD communications may include multiple DL subbands and multiple UL subbands, or one DL subband and one UL subband. For SBFD communications, overlapping communications by nearby UEs may cause CLI if the overlapping communications are in different directions (UE and DL). In other words, SBFD operation may cause UE-to-UE inter-subband CLI and UE-to-UE intra-subband CLI. DL and UL overlap may occur, for example, when communications are not precisely synchronized between a first UE and a second UE, when SBFD communications 410 are allocated differently than SBFD communications on the same communications resources of a nearby base station, or when a first UE transmits UL for SBFD operation and a second nearby UE does not implement SBFD operation, etc. Additionally, UL 414 may trigger intra-band CLI in DL 412 and / or DL ​​416 of SBFD 410 to other UEs using the same communication resources as DL 412 and / or DL ​​416.

[0082] Inter-UE intra-subband CLI may be defined as the interference caused by transmission from one UE (which may be called the "aggressor") on a set of consecutive RBs in a carrier to reception by another UE (which may be called the "victim") on the same set of consecutive RBs in the same carrier at the same time.

[0083] Similarly, UE-to-UE inter-subband CLI may be defined as the interference caused by transmission from one UE (which may be called the "aggressor") on a first set of consecutive RBs in a carrier to reception by another UE (which may be called the "victim") on a second set of consecutive RBs in the same carrier, where the two sets of consecutive RBs do not overlap in frequency.

[0084] For SBFD operation, the CLI measurement and reporting configuration may include identification of multiple communication resources (RBs) for measurement, and the aggressor UE may transmit an SRS in a UL sub-band (or BWP) of SBFD communication, such as in UL 414. The victim base station may perform one or more measurements of the CLI triggered by the SRS transmission by the aggressor UE in response to the CLI measurement and reporting configuration. For example, the victim UE may perform measurements on one or more or each DL sub-band of SBFD in the SBFD of the base station connected to the victim UE according to the CLI measurement and reporting configuration. In some embodiments, the victim UE may transmit a separate measurement report for each measurement in SBFD, and in other embodiments, the victim base station may transmit a single CLI measurement report that includes a compilation of all measurements performed for SBFD operation.

[0085] F 420 may comprise another set of flexible symbols of communication resources across the entire channel bandwidth, and UL 422 may comprise a set of symbols designated for UL transmission across the entire channel bandwidth.

[0086] 5A-5C illustrate an embodiment of measurements in SBFD operation of an aggressor base station and a victim base station. FIG. 5A and FIG. 5B illustrate an example of CLI measurement and reporting in SBFD operation for mitigating inter-subband CLI between UEs. In this embodiment, an aggressor UE 500 from a first cell is scheduled or configured to transmit an SRS 512 in a UL subband of an SBFD symbol or slot 510. Furthermore, a victim UE 530 (FIG. 5B) from a second cell performs CLI measurements on assigned resources (CL measurement resources) in DL subbands 532 and 536 (FIG. 5B), and then reports the measurement results to the network via a gNB to which the victim UE 530 is connected.

[0087] FIG. 5A illustrates an embodiment of an aggressor UE 500 that transmits a sounding frame, such as an SRS 512 or other frame, for measurement by a victim UE 530 (shown in FIG. 5B), such as the UEs shown in FIGS. 1A, 1B, and 2, to mitigate cross-link interference (CLI). FIG. 5A illustrates an SBFD symbol 510 in a graph of carrier bandwidth (frequency bandwidth) versus time. The SBFD operation includes a DL subband 502, a guard band 504 for a UL subband 514, and a DL subband 506. The guard band 504 may not have sufficient bandwidth to prevent inter-band CLI from the UL subband 512 to the DL subband of the victim UE 530 on the same communication resources (including carrier frequency and timing) as the DL subbands 502 and 506. It should be noted that the aggressor UE 500 may have sufficient shielding and / or filtering to avoid inter-subband interference in the DL subbands 502 and 506.

[0088] In this embodiment, the CLI logic circuitry of the aggressor UE 500 may cause transmission of the SRS 512 on the UL sub-band 512 for the measurements. In some embodiments, the gNB connected to the victim UE 530 may synchronize SBFD operations with the gNB connected to the aggressor UE 500, at least for purposes of performing measurements. In other embodiments, the gNB connected to the aggressor UE 500 may synchronize SBFD operations of the gNB connected to the victim UE 530, at least for purposes of performing measurements.

[0089] FIG. 5B illustrates an embodiment of a victim UE 530 measuring a sounding frame, such as an SRS 512 or other frame, from an aggressor UE 500, such as the UEs illustrated in FIGS. 1A, 1B, 2, and 5A, to mitigate cross-link interference (CLI). FIG. 5B illustrates an SBFD symbol 540 in a graph of carrier bandwidth (frequency bandwidth) versus time. The SBFD operation includes a DL subband 532, a guard band 534 for a UL subband 542, and a DL subband 536. The guard band 534 may not have sufficient bandwidth to prevent inter-band CLI to the victim UE 530's DL subbands 532 and 536 from the aggressor UE 500's UL subband 514 (see FIG. 5A), which is on the same communication resource (including carrier frequency and timing) as the victim UE 530's UL subband 542.

[0090] The CLI measurements 544 may correspond to communication resources for the measurements in a CLI measurement and reporting configuration received at a gNB connected to the victim UE 530.

[0091] FIG. 5C illustrates another embodiment of a SBFD symbol 560 of a victim UE 530 for measurement of an SRS 512 from an aggressor UE 500, such as the UEs illustrated in FIG. 1A, FIG. 1B, FIG. 2, and FIG. 5A-5B, to mitigate crosslink interference. FIG. 5C illustrates an example of a CLI measurement resource configuration including non-contiguous frequency resources. In this example, two DL subbands 532 and 536 are configured within a carrier bandwidth (BW). Furthermore, two measurement resources (CLI resource measurements 0, 1, 2, and 3) are configured within each DL subband (532 and 536). The frequency resources within one CLI measurement resource (CLI resource measurements 0, 1, 2, or 3) are contiguous. In this case, four CLI measurement resources (CLI resource measurements 0, 1, 2, and 3) are configured for SBFD operation, and each CLI measurement resource (CLI resource measurements 0, 1, 2, and 3) is associated with one measurement report, respectively. Alternatively, one or more CLI measurement resources (CLI resource measurements 0, 1, 2, 3 or a combination thereof) are associated with one measurement report. Note that in this example, the length of the PRB of each CLI measurement resource (CLI resource measurements 0, 1, 2, and 3) in the frequency may be the same or different.

[0092] FIG. 5D illustrates another embodiment of a SBFD symbol 570 of a victim UE 530 for measurement of an SRS 512 from an aggressor UE 500 of FIG. 5A, such as the UEs illustrated in FIG. 1A, FIG. 1B, FIG. 2, and FIG. 5A-5C, to mitigate crosslink interference. FIG. 5D illustrates another example of a CLI measurement resource configuration including non-contiguous frequency resources. In this example, two measurement resources (CLI resource measurement 0 and 1) may be configured in two DL subbands 532 and 536, respectively. Furthermore, the CLI measurement resources for CLI resource measurement 0 and CLI resource measurement 1 span two DL subbands, respectively, and are non-contiguous in frequency. In other words, the CLI measurement report 0 is based on two non-contiguous frequency ranges of the carrier bandwidth, since a single measurement resource, i.e., CLI resource measurement 0, is a measurement of non-contiguous subbands of DL subband 532 and DL subband 536. Similarly, since a single measurement resource, namely CLI resource measurement 1, is a measurement of non-contiguous subbands of DL subband 532 and DL subband 536, CLI measurement report 1 is based on two non-contiguous frequency ranges of the carrier bandwidth.

[0093] FIG. 5E illustrates another embodiment of a SBFD symbol 570 of a victim UE 530 for measurement of an SRS 512 from an aggressor UE 500 of FIG. 5A, such as the UEs illustrated in FIG. 1A, FIG. 1B, FIG. 2, and FIG. 5A-5D, to mitigate crosslink interference. FIG. 5E illustrates another example of a CLI measurement resource configuration including non-contiguous frequency resources. In this example, one DL sub-band 532 is configured within the carrier bandwidth. Furthermore, four CLI measurement resources (CLI measurement resources 0, 1, 2, and 3) are configured within the DL sub-band 532 for SBFD operation. It should be noted that in this example, the length of the PRB for each CLI measurement resource in frequency may be the same or different.

[0094] FIG. 6 illustrates a flowchart 6000 of an embodiment for measuring and mitigating crosslink interference, such as the embodiments described in connection with FIGS. 1A-1B, 2, 3A-3E, 4, and 5A-5E. At the beginning of the flowchart 6000, an aggressor UE from a first cell transmits a sounding reference signal (SRS) or other uplink channel / signal in an UL subband for dynamic TDD, such as SBFD operation (element 6005). For example, the CLI logic of the aggressor UE may receive a DCI from a first base station of the first cell indicating an SRS configuration for transmission of the SRS on communication resources. In response to receiving the DCI, the CLI logic of the aggressor UE may transmit an SRS for measurement and mitigation of the CLI. In some embodiments, the UE may transmit an SRS during SBFD operation.

[0095] In some embodiments for SBFD including dynamic TDD operation, the CLI logic of the first base station (or a second base station from a second cell) can share a CLI measurement and reporting configuration with nearby base stations, the CLI measurement and reporting configuration comprising: the intended DL and / or UL sub-band configuration in the SBFD symbol, which may include an identification of frequency resources of the communications resources that may be used for UL reception at the victim UE; The entire communication resource, both UL and DL, which can be identified by signaling similar to indicate the location of the BWP and the bandwidth (BW) settings; One or more guard bands in the frequency resource and their locations, if any, within the SBFD symbol; and / or Time domain position of SBFD symbols may include one or more of:

[0096] Note that the SBFD configuration may be presumed to be valid until a new configuration is received. The SBFD configuration may be replaced along with the intended UL / DL configuration in the CLI measurement and reporting configuration.

[0097] In some embodiments of SBFD operation, base stations may exchange muting patterns that indicate symbols and frequency resources (sub-bands) within a carrier bandwidth.

[0098] For the processes described in the examples above or below, it should be noted that a "base station" or "gNB" may generally be replaced with a transmit and receive point (TRP), and a cellular network may configure CLI measurement and reporting settings for more than one TRP. A TRP may transmit and measure SRS according to SRS settings and CLI measurement and reporting settings, respectively. Furthermore, while many of the backhauls above and below describe an Xn interface, the embodiments may alternatively be applied to a central unit-distributed unit (CU-DU) gNB with a split architecture (e.g., a CU-DU split where a distributed unit (DU) may correspond to a TRP). In such embodiments, coordination / information exchange between different DUs may be realized over an F1 interface or other communication channels.

[0099] Furthermore, the CLI measurement and reporting configuration may be used for inter-subband and / or intra-subband CLI processing, which may depend on the DL / UL subband configuration in the serving cell and between the serving cell and neighboring cells. For example, the base station may configure the UE to measure CLI in a subband, and the UE may not be aware that the measured CLI pertains to only inter-subband CLI, only intra-subband CLI, or both.

[0100] After the aggressor UE transmits the SRS, the CLI logic of the first base station and optionally the nearby base stations may mute the DL channel (subband) for transmission and measurement of the SRS according to the CLI measurement and reporting configuration. In some embodiments, the first base station or the second base station from the second cell may share information about the resource muting pattern with one or more nearby base stations via backhaul signaling, e.g., the Xn interface. For example, such information may include the configuration of the zero-power CSI-RS (ZP-CSI-RS). The CLI logic of the first base station (or the second base station) may use the ZP-CSI-RS for the muting pattern when the (non-zero-power) CSI-RS is used as the CLI-RS. In other embodiments, the logic of the first base station (or the second base station) may use the zero-power SRS (ZP-SRS) to define the muting pattern, where the ZP-SRS corresponds to the resource pattern used for mapping the SRS to physical (time-frequency) resources. In other embodiments, the muting pattern may only include the identification of the OFDM symbol. In yet another embodiment, the OFDM symbols may not be limited to symbols designated as flexible symbols or DL ​​in an RDD configuration provided by the first base station or a second base station from the second cell to one or more neighboring base stations.

[0101] After the aggressor UE transmits the SRS, the CLI logic of the victim UE from the second cell measures the inter-subband CLI on resources configured or indicated in the DL subband by the CLI measurement and reporting configuration (element 6010). The victim UE can receive the CLI measurement and reporting configuration in the DCI from the second base station to schedule measurements of the SRS transmission from the aggressor UE on communication resources identified to the aggressor UE by the first base station in the SRS resource configuration. In such an embodiment, the first and second base stations can coordinate the SRS configuration and / or CLI measurements over the backhaul or other communication resources.

[0102] After receiving information regarding the SRS and generating a CLI measurement report based on the CLI measurement and reporting configuration, the CLI logic of the victim UE may report the CLI measurement report (result) to the second base station in the second cell (element 6015). For example, in SBFD operation, the UE-to-UE inter-subband CLI measurement report may include an L1 CLI measurement report or an L3 CLI measurement report.

[0103] After receiving the CLI measurement report, one or more neighboring base stations in the other cell may share the CLI measurement report with the second base station in the second cell via backhaul signaling, e.g., the Xn interface (element 6020). In some embodiments, the CLI logic of the second base station may share CLI measurement and reporting configuration with nearby base stations so that the nearby base stations may also measure the CLI or may command or request one or more UEs to measure the CLI based on the SRS transmission from the aggressor UE. The other base stations may then share their CLI measurement reports with nearby base stations, or vice versa. The CLI measurement report enables the CLI logic of the base station to determine actions to mitigate the CLI experienced from the SRS transmission by the aggressor UE.

[0104] FIG. 7 illustrates a flowchart 7000 of an alternative embodiment for measuring and mitigating crosslink interference, such as the embodiments described in connection with FIGS. 1A-1B, 2, 3A-3E, 4, 5A-5E, and 6. More specifically, flowchart 7000 may illustrate a process of inter-subband CLI measurement and reporting in a cell for SBFD operation. At the beginning of flowchart 7000, the CLI logic of a first UE from a cell transmits a sounding reference signal (SRS) or other uplink channel / signal in a UL subband for SBFD operation (element 7005). In some embodiments, the CLI logic of the first UE may receive a first DCI from a first gNB in ​​the cell to schedule or instruct SRS resource configuration to transmit the SRS. In other embodiments, the first DCI may include a trigger, such as an index from a mapping of SRS resources to the UE, and the timing of the SRS or starting PRB may be based on the timing of receipt of the first DCI including the trigger. In such an embodiment, the trigger may include one or more bits, for example, to indicate an index number of the mapping or to indicate the mapping of an SRS resource.

[0105] After transmitting the SRS, a second UE from that cell may measure inter-subband CLI on configured or indicated resources in the DL subband in the second DCI received from the first gNB. The second UE may measure the SRS transmission from the first UE on one or more DL subbands of the SBFD symbol. In some embodiments, the second UE may measure the SRS transmission on two or more subbands of each of the DL subbands of the SBFD symbol to increase the granularity of the measurement of the SRS transmission.

[0106] The second UE may then report CLI measurement results to the first gNB according to the CLI measurement and reporting configuration included in the second DCI (element 7015). In some embodiments, the second UE may use the CLI-RSSI to define a CLI measurement report that may be shared between the first gNB in ​​the first cell and one or more gNBs in the second cell. Additionally, the first gNB may trigger or cause transmission of periodic, semi-persistent, or aperiodic CLI measurement reports from gNBs in neighboring cells. L1 or L3 CLI-RSSI measurement reports may be exchanged from neighboring cells to the first gNB in ​​the first cell.

[0107] In some embodiments, the second UE may use L1 or L3 CLI-SINR or CLI-RSRP for CLI measurements and reporting, which may be shared among neighboring gNBs by the first gNB via backhaul and / or reported from the second UE.

[0108] In some embodiments, one or more of the following parameters may be configured as part of the CLI measurement and reporting configuration: Reference subcarrier spacing and cyclic prefix (CP) length, Point A as the common reference point of the reference block grid, Channel bandwidth, DL / UL sub-band and / or guard band configuration for SBFD, Time and frequency resources for CLI-RSSI measurement and reporting. The time and frequency resources may include the starting Physical Resource Block (PRB) or Common Resource Block (CRB) grid, which may be indicated for the BWP configuration or DL / UL subband, as well as the PRB length, periodicity and offset, symbol position within the slot (e.g. starting symbol and number of symbols), etc. · System Frame Number (SFN) of the serving cell, · Quasi co-location (QCL) assumption for transmission of corresponding uplink channels / signals from aggressor UEs.

[0109] The channel bandwidth may include the bandwidth of the channel for SRS US transmission. The time and frequency resources for SRS-RSRP transmission or for SRS CLI-RSSI measurement may include a starting physical resource block (PRB). The starting PRB may be indicated with respect to a BWP setting or based on a common resource block (CRB) grid, a PRB length, a PRB periodicity and offset, a symbol position within a slot, etc. The symbol position within a slot may include, for example, a starting symbol and a number of symbols. A slot may be a communication resource for SRS transmission or a communication resource for SRS CLI-RSSI measurement. A BWP may be a portion of the channel bandwidth to which an SRS is mapped. In some embodiments, for example, a BWP may not be included if the time and frequency resources for SRS transmission or for SRS CLI-RSSI measurement are directly mapped to a CRB grid.

[0110] The SFN may be included to adjust the indexing in the time domain of slots, subframes, and system frames. A 5G system may have a system (or radio) frame of 10 milliseconds (ms) in length divided into 10 subframes, with each subframe having a 1 ms duration. Each subframe may have 2 microslots, with each slot having, for example, 14 OFDM symbols. The slot length may vary based on the subcarrier spacing and the number of slots per subframe. For example, a slot may have a 1 ms duration for a 15 kilohertz (KHz) subcarrier spacing, a 500 microsecond (μs) duration for a 30 KHz subcarrier spacing, etc. A 15 KHz subcarrier spacing would occupy one slot per subframe, a 30 KHz subcarrier spacing would occupy two slots per subframe, etc. Furthermore, each slot would occupy 14 OFDM symbols for normal CP or 12 OFDM symbols for extended CP.

[0111] In some embodiments, the communication resources for CLI-RSSI measurements may correspond to a zero-power channel state information (CSI)-RS (ZP-CSI-RS) resource configuration. Such resource configuration may help improve the accuracy of inter-subband CLI measurements by avoiding DL transmissions on the measurement resources. For example, the first gNB may share a CLI measurement and reporting configuration with nearby gNBs, and the ZP-CSI-RS may cause the nearby gNBs to mute DL transmissions on the communication resources being measured according to the CLI measurement and reporting configuration. Muting the nearby gNBs' DL transmissions may eliminate other sources of CLI on the CLI measurement resources when the victim UE is measuring SRS from the aggressor UE on the CLI measurement resources according to the CLI measurement and reporting configuration.

[0112] In some embodiments, the communication resources for CLI-RSSI measurements may correspond to the RB symbol granularity of the resource configuration, similar to that used to indicate PDSCH rate matching.

[0113] It should be noted that the set of time and frequency resources for CLI-RSSI measurement and reporting can be configured for the UE. The set of frequency resources may be contiguous or non-contiguous. Furthermore, the CLI measurement resource may be located within a DL subband to measure inter-subband CLI. In some embodiments, the CLI measurement resource may span more than one DL subband. If more than one DL subband is not contiguous in frequency, the CLI measurement resource may also be non-contiguous in frequency.

[0114] Additionally, in some embodiments, a victim UE may generate one CLI measurement, e.g., CLI-RSSI, for a single CLI measurement resource. In some embodiments, a victim UE may generate more than one CLI measurement, e.g., multiple CLI-RSSI, for inclusion in a CLI measurement report. The number of CLI measurement resources in a CLI measurement and reporting configuration may determine the number of CLI-RSSI values ​​in a CLI measurement report.

[0115] In some embodiments, the victim UE may include the QCL assumptions used for the CLI measurements in the CLI measurement report.

[0116] FIG. 8 illustrates an embodiment of a protocol entity 8000 that may be implemented in a wireless communication device including one or more of a user equipment (UE) 8060, a base station 8080, which may be an evolved NodeB (eNB) or a new radio next generation NodeB (gNB), and a network function 8094, which may be a mobility management entity (MME) or an access and mobility management function (AMF), in accordance with some aspects.

[0117] According to some aspects, the gNB8080 may be implemented as one or more dedicated physical devices, such as a macrocell, femtocell, or other suitable device, or in alternative aspects, as one or more software entities executing on a server computer as part of a virtual network referred to as a Cloud Radio Access Network (CRAN).

[0118] In accordance with some aspects, one or more protocol entities that may be implemented in one or more of the UE 8060, gNB 8080, and AMF 8094 may be described as implementing all or a portion of a protocol stack, where the layers are considered to be ordered from bottom to top in the following order: physical layer (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), non-access stratum (NAS). In accordance with some aspects, one or more protocol entities that may be implemented in one or more of the UE 8060, gNB 8080, and AMF 8094 may communicate with respective peer protocol entities that may be implemented in other devices, using the services of the respective lower layer protocol entities to perform such communications.

[0119] In accordance with some aspects, the UE PHY layer 8072 and the peer entity gNB PHY layer 8090 may communicate using signals transmitted and received over a wireless medium. In accordance with some aspects, the UE MAC layer 8070 and the peer entity gNB MAC layer 8088 may communicate using services provided by the UE PHY layer 8072 and the gNB PHY layer 8090, respectively. In accordance with some aspects, the UE RLC layer 8068 and the peer entity gNB RLC layer 8086 may communicate using services provided by the UE MAC layer 8070 and the peer entity gNB MAC layer 8088, respectively. In accordance with some aspects, the UE PDCP layer 8066 and the peer entity gNB PDCP layer 8084 may communicate using services provided by the UE RLC layer 8068 and the 5GNB RLC layer 8086, respectively. In accordance with some aspects, the UE RRC layer 8064 and the gNB RRC layer 8082 can communicate using services provided by the UE PDCP layer 8066 and the gNB PDCP layer 8084, respectively. In accordance with some aspects, the UE NAC 8062 and the AMF NAS 8092 can communicate using services provided by the UE RRC layer 8064 and the gNB RRC layer 8082, respectively.

[0120] The PHY layers 8072 and 8090 may transmit or receive information used by the MAC layers 8070 and 8088 over one or more air interfaces. The PHY layers 8072 and 8090 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover), and other measurements used by higher layers, such as the RRC layers 8064 and 8082. The PHY layers 8072 and 8090 may also perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0121] The MAC layers 8070 and 8088 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units from one or more logical channels into transport blocks (TBs) delivered to the PHY via the transport channels, demultiplexing of MAC SDUs from the transport blocks (TBs) delivered from the PHY via the transport channels into one or more logical channels, multiplexing of MAC SDUs into TBs, scheduling of information reports, error correction via hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0122] The RLC layers 8068 and 8086 may operate in multiple operating modes, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layers 8068 and 8086 may perform upper layer protocol data unit (PDU) transfer, error correction with automatic repeat request (ARQ) for AM data transfer, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transfer. The RLC layers 8068 and 8086 may also perform re-segmentation of RLC data PDUs for AM data transfer, reordering of RLC data PDUs for UM and AM data, detection of duplicate data for UM and AM data, discarding of RLC SDUs for UM and AM data, detection of protocol errors for AM data transfer, and performing RLC re-establishment.

[0123] The PDCP layers 8066 and 8084 may perform header compression and decompression of Internet Protocol (IP) data, maintain the PDCP sequence number (SN), ensure in-order delivery of upper layer PDUs upon re-establishment of lower layers, eliminate duplicate lower layer SDUs upon re-establishment of lower layers of radio bearers mapped over the RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of the control plane data, control timer-based discarding of data, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0124] The main services and functions of the RRC layers 8064 and 8082 may include broadcasting of system information (e.g., contained in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the Non-Access Stratum (NAS)), broadcasting of system information related to the Access Stratum (AS), establishment, maintenance, and release of RRC connections between the UE and the E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting. The above MIBs and SIBs may include one or more Information Elements (IEs), each of which may have individual data fields or data structures.

[0125] The UE 8060 and the RAN node gNB 8080 may exchange control plane data using a Uu interface (e.g., an LTE-Uu interface) via a protocol stack including PHY layers 8072 and 8090, MAC layers 8070 and 8088, RLC layers 8068 and 8086, PDCP layers 8066 and 8084, and RRC layers 8064 and 8082.

[0126] The Non-Access Stratum (NAS) protocol 8092 forms the highest layer of the control plane between the UE 8060 and the AMF 8005. The NAS protocol 8092 supports the mobility and session management procedures of the UE 8060 to establish and maintain IP connectivity between the UE 8060 and a Packet Data Network (PDN) Gateway (P-GW).

[0127] 9 illustrates an embodiment of a format of a PHY data unit (PDU) that may be transmitted by a PHY device over one or more antennas and encoded and decoded by a MAC entity, such as processors 203 and 213 of FIG. 2 or baseband circuitry 1304 of FIG. 13 and FIG. 14, in accordance with some aspects. In some embodiments, an upper layer frame, such as a frame containing RRC layer information elements, may be transmitted from a base station to a UE or from a UE to a base station as one or more MAC service data units (MSDUs) in the payload of one or more PDUs in one or more subframes of a radio frame.

[0128] According to some aspects, the MAC PDU 9000 may comprise a MAC header 9005 and a MAC payload 9010, where the MAC payload comprises zero or more MAC control elements 9030, zero or more MAC service data unit (SDU) portions 9035, and zero or more padding portions 9040. According to some aspects, the MAC header 9005 may comprise one or more MAC subheaders, where each of the MAC subheaders corresponds to a MAC payload portion and may appear in a corresponding order. According to some aspects, each of the zero or more MAC control elements 9030 included in the MAC payload 9010 may correspond to a fixed length subheader 9015 included in the MAC header 9005. According to some aspects, each of the zero or more MAC SDU portions 9035 included in the MAC payload 9010 may correspond to a variable probe portion header 9020 included in the MAC header 9005. According to some aspects, the padding portion 9040 included in the MAC payload 9110 may correspond to a padding subheader 9025 included in the MAC header 9005.

[0129] Figure 10A illustrates an embodiment of communications circuitry 1000, such as the circuitry in base station 201 and user equipment 211 shown in Figure 2. Communications circuitry 1000 may alternatively be grouped according to functionality. The components shown in communications circuitry 1000 are shown here for illustrative purposes and may include other components not shown in Figure 10A.

[0130] The communications circuitry 1000 may include a protocol processing circuitry 1005 that may implement one or more of a medium access control (MAC) function, a radio link control (RLC) function, a packet data convergence protocol (PDCP) function, a radio resource control (RRC) function, and a non-access stratum (NAC) function. The protocol processing circuitry 1005 may include one or more processing cores (not shown) for executing instructions and one or more memory structures (not shown) for storing program (code) and data information.

[0131] The communications circuitry 1000 may further include digital baseband circuitry 1010 that may implement a physical layer (PHY) including one or more of hybrid automatic repeat request (HARQ) functionality, scrambling and / or descrambling, encoding and / or decoding, layer mapping and / or demapping, modulation symbol mapping, received symbol and / or bit metric determination, multi-antenna port precoding and / or decoding that may include one or more of space-time, space-frequency, or spatial coding, reference signal generation and / or detection, preamble sequence generation and / or detection, synchronization sequence generation and / or detection, control channel signal brand decoding, and other related functions.

[0132] The communications circuit 1000 may further include a transmitting circuit 1015, a receiving circuit 1020, and / or an antenna array circuit 1030.

[0133] The communications circuitry 1000 may further include radio frequency (RF) circuitry 1025, such as RF circuitry 208 and 218 of Figure 2. In some aspects of the embodiment, the RF circuitry 1025 may include multiple parallel RF chains for one or more of the receive or transmit functions, each connected to one or more antennas of the antenna array circuitry 1030.

[0134] In an aspect of the present disclosure, the protocol processing circuit 1005 may include one or more instances of control circuitry (not shown) that provides control functions for one or more of the digital baseband circuit 1010, the transmit circuit 1015, the receive circuit 1020, and / or the radio frequency circuit 1025.

[0135] Figure 10B illustrates an embodiment of the radio frequency circuitry 1025 of Figure 10A according to some aspects, such as the RF circuitry 208 and 218 illustrated in Figure 2. The radio frequency circuitry 1025 may include one or more instances of radio chain circuitry 1072, which in some aspects may include one or more filters, power amplifiers, low noise amplifiers, programmable phase shifters, and power supplies (not shown).

[0136] The radio frequency circuitry 1025 may include a power combining and splitting circuitry 1074. In some aspects, the power combining and splitting circuitry 1074 may operate bidirectionally such that the same physical circuitry may be configured to operate as a power splitter when the device is transmitting and as a power combiner when the device is receiving. In some aspects, the power combining and splitting circuitry 1074 may include separate circuits, in whole or in part, to perform power splitting when the device is transmitting and power combining when the device is receiving. In some aspects, the power combining and splitting circuitry 1074 may include passive circuitry including one or more bidirectional power splitters / combiners arranged in a tree. In some aspects, the power combining and splitting circuitry 1074 may include active circuitry including amplifier circuitry.

[0137] In some aspects, the radio frequency circuitry 1025 may connect to the transmit circuitry 1015 and the receive circuitry 1020 of FIG. 10A via one or more radio chain interfaces 1076 or a combined radio chain interface 1078. The combined radio chain interface 1078 may provide a wideband or ultra-wideband bandwidth.

[0138] In some aspects, the one or more radio chain interfaces 1076 may provide one or more interfaces to one or more receive or transmit signals each associated with a single antenna structure that may include one or more antennas.

[0139] In some aspects, the combined radio chain interface 1078 may provide a single interface to one or more receive or transmit signals each associated with a group of antenna structures combining one or more antennas.

[0140] FIG. 11 illustrates an example of a storage medium 1100 that stores code and data executed by any one or more of the processors and / or processing circuits described herein. The storage medium 1100 may include an article of manufacture. In some examples, the storage medium 1100 may include any non-transitory computer-readable or machine-readable medium, such as optical, magnetic, or semiconductor storage. The storage medium 1100 may store various types of computer-executable instructions, such as instructions for implementing the logic flows and / or techniques described herein. Examples of computer-readable or machine-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or rewriteable memory, and the like. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like.

[0141] Figure 12 illustrates an architecture of a network system 1200 according to some embodiments. System 1200 is shown to include user equipment (UE) 1201 and UE 1202, such as the UEs illustrated in Figures 1A, 1B, and 2. UEs 1201 and 1202 are illustrated as smartphones (e.g., handheld touchscreen mobile computing systems capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communications interface.

[0142] In some embodiments, either of the UEs 1201 and 1202 may comprise an Internet of Things (IoT) UE that may have network access designed for low-power IoT applications using short-lived UE connections. The IoT UE may utilize technologies such as public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communications, sensor networks, or machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over the IoT network. The M2M or MTC exchange of data may be a machine-initiated exchange of data. The IoT network represents the interconnection of IoT UEs that may include uniquely identifiable embedded computing devices (within the Internet infrastructure) through short-lived connections. The IoT UE may run background applications (keep-alive messages, status updates, etc.) to aid in the connectivity of the IoT network.

[0143] The UEs 1201 and 1202 can connect to, e.g., be communicatively coupled to, a radio access network (RAN), such as a base station shown in Figures 1A, 1B, and 2, in this embodiment, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (EUTRAN) 1210. UEs 1201 and 1202 utilize connections 1203 and 1204, respectively, each having a physical communication interface or layer (described in further detail below), which in this example are represented as air interfaces enabling a communicative coupling and may follow cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5th generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0144] In this embodiment, the UEs 1201 and 1202 may further directly exchange communication data via a ProSe interface 1205. The ProSe interface 1205 may alternatively be referred to as a sidelink interface that includes one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0145] The UE 1202 is shown configured to access an access point (AP) 1206 via a connection 1207. The connection 1207 may comprise a local wireless connection, such as a connection following the IEEE 802.11 protocol, and the AP 1206 comprises a Wireless Fidelity (Wi-Fi) router. In this example, the AP 1206 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below). The E-UTRAN 1210 may include one or more access nodes that enable the connections 1203 and 1204. These access nodes (AN) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may comprise terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The E-UTRAN 1210 may include one or more RAN nodes providing macro cells, e.g., macro RAN node 1211, and one or more RAN nodes providing femto cells or pico cells (e.g., cells having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macro cell), e.g., low power (LP) RAN node 1212.

[0146] Either of the RAN nodes 1211 and 1212 may terminate air interface protocols and may be the first point of contact for the UEs 1201 and 1202. In some embodiments, either of the RAN nodes 1211 and 1212 may fulfill various logical functions of the E-UTRAN 1210, including, but not limited to, Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0147] According to some embodiments, the UEs 1201 and 1202 may be configured to communicate with either the RAN nodes 1211 and 1212 or with each other over a multi-carrier communication channel using Orthogonal Frequency Division Multiplexing (PFDM) communications according to various communication techniques, such as, but not limited to, an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications). Note that the scope of the embodiments is not limited in this respect. An OFDM signal may have multiple orthogonal subcarriers.

[0148] In some embodiments, a downlink resource grid can be used for downlink transmissions from either of the RAN nodes 1211 and 1212 to the UEs 1201 and 1202, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or a time-frequency resource grid, which is the physical resources in the downlink in each slot. Such a time-frequency plane representation is common in OFDM systems and allows for intuitive allocation of radio resources. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid contains a number of resource blocks, which represents the mapping of a particular physical channel to the resource elements. Each resource block contains a set of resource frequencies, which in the frequency domain may represent the smallest number of resources that can currently be allocated. There are several different physical downlink (DL) channels carried using such resource blocks.

[0149] A physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to the UEs 1201 and 1202. A physical downlink control channel (PDCCH) may carry information regarding transport formats and resource allocations related to the PDSCH channel, among others. It may also inform the UEs 1201 and 1202 of transport formats, resource allocations, and Hybrid Automatic Repeat Request (HARQ) information regarding the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to the UEs 102 in a cell) may be performed by either of the RAN nodes 1211 and 1212 based on channel quality information fed back from either of the UEs 1201 and 1202. Downlink resource allocation information may be transmitted on a PDCCH used by (e.g., assigned to) each of the UEs 1201 and 1202.

[0150] The PDCCH may carry the control channel using control channel elements (CCEs). Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets and then reordered using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, and each CCE may correspond to nine sets of four physical resource elements known as a resource element group (REG). Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs depending on the size of the downlink control information (DCI) and the channel conditions. There may be four or more different PDCCH formats defined in the LLE with different numbers of CCEs (e.g., aggregation levels L=1, 2, 4, or 8).

[0151] Some embodiments may use a concept of resource allocation for control channel information that is an extension of the concept above. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). As above, each ECCE may correspond to nine sets of four physical resource elements known as an extended resource element group (EREG). An ECCE may have other numbers of EREGs in some circumstances.

[0152] The RAN nodes 1211 and 1212 may communicate with each other and / or other access nodes in the E-UTRAN 1210 and / or other RANs via the X2 interface, which is a signaling interface for exchanging data packets between ANs. Other suitable interfaces for exchanging data packets directly between ANs may also be used.

[0153] The E-UTRAN 1210 is shown communicatively coupled to a core network, in this embodiment an Evolved Packet Core (EPC) network 1220, via an SI interface 1213. In this embodiment, the SI interface 1213 is divided into two parts: an SI-U interface 1214, which carries traffic data between the RAN nodes 1211 and 1212 and a Serving Gateway (S-GW) 1222, and an SI-Mobility Management Entity (MME) interface 1215, which is a signaling interface between the RAN nodes 1211 and 1212 and the MME 1221.

[0154] In this embodiment, the EPC network 1220 includes an MME 1221, an S-GW 1222, a Packet Data Network (PDN) Gateway (P-GW) 1223, and a Home Subscriber Server (HSS) 1224. The MME 1221 is similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 1221 may manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 1224 may have a database for network users, including subscription-related information to support the handling of communication sessions by network entities. The EPC network 1220 may include one or more HSSs 1224, depending on the number of mobile subscribers, device capabilities, network configuration, etc. For example, the HSS 1224 may support routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0155] The S-GW 1222 terminates the SI interface 1213 to the E-UTRAN 1210 and may route data packets between the E-UTRAN 1210 and the EPC network 1220. The S-GW 1222 may also be a local mobility anchor point for handovers between RAN nodes and provide an anchor for inter-3GPP mobility. Other roles it may play include lawful interception, charging, and some policy enforcement.

[0156] The P-GW 1223 may terminate the SGi interface to the PDN. The P-GW 1223 routes data packets between the EPC network 1220 and an external network, such as a network including an application server 1230 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 1225. In general, the application server 1230 may be an element that provides applications that use IP bearer resources in a core network (e.g., UMTS packet service (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 1223 is shown communicatively coupled to the application server 1230 via the IP interface 1225. The application server 1230 may also be configured to support one or more services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1201 and 1202 via the EPC network 1220.

[0157] The P-GW 1223 may further be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 1226 is the policy and charging control element of the EPC network 1220. In a non-roaming scenario, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited Public Land Mobile Network (V-PCRF) in the VPLMN. The PCRF 1226 may be communicatively coupled to the application server 1230 via the P-GW 1223. The application server 1230 may signal the PCRF 1226 to indicate the new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 1226 provisions this rule with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI) to the Policy and Charging Enforcement Function (PCEF) (not shown) and initiates the QoS and charging specified by the application server 1230.

[0158] FIG. 13 illustrates components of a device 1300 according to some embodiments, such as the base station and UE shown in FIGS. 1A, 1B, 2, and 12. In some embodiments, the device 1300 may include an application circuit 1302, a baseband circuit 1304, a radio frequency (RF) circuit 1306, a front-end module (FEM) circuit 1308, one or more antennas 1310, and a power management circuit (PMC) 1312, coupled at least as shown. The depicted components of the device 1300 may be included in a RAN node, such as a base station or gNB, or a UE. In some embodiments, the device 1300 may include fewer elements (e.g., a RAN node may not utilize the application circuit 1302 and may instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 1300 may include additional elements, such as, for example, memory / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the above circuitry may be included separately in more than one device for a Cloud RAN (C-RAN) implementation).

[0159] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose and special-purpose processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 1300. In some embodiments, the processors of the application circuit 1302 may process IP data packets received from an EPC.

[0160] The baseband circuitry 1304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1304 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1306 and generate baseband signals for a transmit signal path of the RF circuitry 1306. The baseband circuitry 1304 may interface with the application circuitry 1302 for generating and processing baseband signals and for controlling the operation of the RF circuitry 1306. For example, in some embodiments, the baseband circuitry 1304 may include a third generation (3G) baseband processor 1304A, a fourth generation (4G) baseband processor 1304B, a fifth generation (5G) baseband processor 1304C, or other baseband processors 1304D for other existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). In many embodiments, the fourth generation (4G) baseband processor may include capabilities for generating and processing baseband signals for LTE radio, and the fifth generation (5G) baseband circuitry 1304C may include capabilities for generating and processing baseband signals for NR.

[0161] The baseband circuitry 1304 (e.g., one or more of the baseband circuits 1304A-D) may handle various radio control functions that enable communication with one or more wireless networks via the RF circuitry 1306. In other embodiments, some or all of the functionality of the baseband processors 1304A-D may be included in modules stored in the memory 1304G and executed via a central processing unit (CPU) 1304E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc.

[0162] In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1304 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder / decoder functionality. The embodiments of the modulation and / or demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0163] In some embodiments, the baseband circuitry 1304 may include one or more audio digital signal processors (DSPs) 1304F. The audio DSPs 1304F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. The components of the baseband circuitry may be suitably integrated into a single chip or a single chipset, or may be located on the same circuit in some embodiments. In some embodiments, some or all of the components of the baseband circuitry 1304 and the application circuitry 1302 may be implemented together, such as, for example, a system on chip (SoC). In some embodiments, the baseband circuitry 1304 may provide communication according to one or more wireless technologies. For example, in some embodiments, the baseband circuitry 1304 may support communication with an evolved universal terrestrial radio access network (E-UTRAN), other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), or wireless personal area networks (WPANs). An embodiment in which the baseband circuitry 1304 is configured to support wireless communication of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

[0164] The RF circuitry 1306 may enable communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, the RF circuitry 1306 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. The RF circuitry 1306 may include a receive signal path that may include circuitry to downconvert RF signals received from the FEM circuitry 1308 and provide a baseband signal to the baseband circuitry 1304. The RF circuitry 1306 may also include a transmit signal path that may include circuitry to upconvert baseband signals provided by the baseband circuitry 1304 and provide an RF output signal to the FEM circuitry 1308 for transmission.

[0165] In some embodiments, the receive signal path of the RF circuitry 1306 may include a mixer circuit 1306a, an amplifier circuit 1306b, and a filter circuit 1306c. In some embodiments, the transmit signal path of the RF circuitry 1306 may include a filter circuit 1306c and a mixer circuit 1306a. The RF circuitry 1306 may also include a synthesizer circuit 1306d that synthesizes frequencies or component carriers for use by the mixer circuitry 1306a of the receive and transmit signal paths. In some embodiments, the mixer circuitry 1306a of the receive signal path may downconvert the RF signal received from the FEM circuitry 1308 based on a synthesis frequency provided by the synthesizer circuitry 1306d. The amplifier circuitry 1306b may amplify the downconverted signal, and the filter circuitry 1306c may be a low pass filter (LPF) or a band pass filter (BPF) that removes unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1304 for further processing.

[0166] In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not a requirement. In some embodiments, the mixer circuit 1306a in the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0167] In some embodiments, the mixer circuit 1306a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesis frequency provided by the synthesizer circuit 1306d to generate an RF output signal for the FEM circuit 1308. The baseband signal may be provided by the baseband circuit 1304 and may be filtered by the filter circuit 1306c.

[0168] In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and quadrature upconversion, respectively. In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may be configured for superheterodyne operation.

[0169] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuitry 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuitry 1304 may include a digital baseband interface to communicate with the RF circuitry 1306.

[0170] In some dual-mode embodiments, separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0171] In some embodiments, the synthesizer circuit 1306d may be a fractional-N synthesizer or a fractional NIN+I synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer having a phase-locked loop including a divider.

[0172] The synthesizer circuit 1306d may synthesize an output frequency for use by the mixer circuit 1306a of the RF circuit 1306 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuit 1306d may be a fractional NIN+I type synthesizer.

[0173] In some embodiments, the frequency input may be the output of a voltage controlled oscillator (VCO), although this is not a requirement. The divider control input may be the output of either the application processor of the application circuit 1302 or the baseband circuit 1304, depending on the desired output frequency. Some embodiments may determine the divider control input (e.g., N) from a lookup table based on the channel indicated by the application circuit 1302.

[0174] The synthesizer circuit 1306d of the RF circuit 1306 may include a divider, a delay-locked loop (DLL), a multiplier, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry-out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded adjustable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In such an embodiment, the delay elements may divide the VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to ensure that the total delay through the delay line is one VCO cycle.

[0175] In some embodiments, the synthesizer circuit 1306d may generate the carrier frequency (or component carrier) as an output frequency, while in other embodiments the output frequency is a multiple of the carrier frequency (such as twice the carrier frequency or four times the carrier frequency) and may be used in conjunction with a quadrature generator and divider circuit to generate signals at the carrier frequency with different phases. In some embodiments, the output frequency may be the local oscillator (LO) frequency (fLO). In some embodiments, the RF circuit 1306 may include an IQ to polarity converter.

[0176] The FEM circuitry 1308 may include a receive signal path, which may include circuitry for operating on RF signals received from one or more antennas 1310 to amplify the received signals and provide an amplified version of the received signals to the RF circuitry 1306 for further processing. The FEM circuitry 1308 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1306 for transmission by one or more of the one or more antennas 1310. In various embodiments, amplification via the transmit signal path or the receive signal path may occur only in the RF circuitry 1306, only in the FEM circuitry 1308, or in both the RF circuitry 1306 and the FEM circuitry 1308.

[0177] In some embodiments, the FEM circuitry 1308 may include a TX / RX switch to switch between a transmit mode and a receive mode of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low noise amplifier (LNA) that amplifies a received RF signal and provides the amplified received RF signal as an output (e.g., to the RF circuitry 1306). The transmit signal path of the FEM circuitry 1308 may include a power amplifier (PA) that amplifies an input RF signal (e.g., provided by the RF circuitry 1306) and one or more filters that generate an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1310).

[0178] In this embodiment, radio refers to the combination of RF circuitry 1306 and FEM circuitry 1308. Radio refers to the parts of the circuitry that generate, transmit or receive, and process radio signals. RF circuitry 1306 includes a transmitter that generates a time domain radio signal containing data from a baseband signal and applies the radio signal to subcarriers of a carrier frequency that form the bandwidth of a channel. The PA of FEM circuitry 1308 amplifies the tones for transmission and amplifies the tones received from one or more antennas 1310 by the LAN to increase the signal-to-noise ratio (SNR) for interpretation. In wireless communication, FEM circuitry 1308 may also look for detectable patterns that appear to be wireless communication. The receiver of RF circuitry 1306 then converts the time domain radio signal to a baseband signal by one or more functional modules, such as those shown in base station 201 and user device 211 depicted in FIG. 2.

[0179] In some embodiments, the PMC 1312 may manage the power provided to the baseband circuitry 1304. In particular, the PMC 1312 may control power source selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1312 may be included when the device 1300 can be powered by a battery, such as when the device is included in a UE. The PMC 1312 may increase power conversion efficiency while providing a desired packaging size and heat dissipation characteristics.

[0180] Although FIG. 13 shows the PMC 1312 coupled only to the baseband circuitry 1304, in other embodiments, the PMC 1312 can additionally or alternatively be coupled to and perform similar power management operations for other components, such as, but not limited to, the application circuitry 1302, the RF circuitry 1306, or the FEM circuitry 1308.

[0181] In some embodiments, the PMC 1312 may control or otherwise be a part of various power saving mechanisms of the device 1300. For example, if the device 1300 is in an RRC_Connected state, in which the device 1300 is still connected to a RAN node in that it expects to receive traffic shortly, then the device 1300 enters a state known as a discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 1300 may power down for a short period of time to conserve power.

[0182] If there is no data traffic activity for an extended period of time, the device 1300 transitions to an RRC Idle state, in which the device 1300 is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1300 goes into a very low power state, performs paging, wakes up periodically to listen to the network, and then powers down again. The device 1300 cannot receive data in this state, so it must return to the RRC_Connected state to receive data.

[0183] Additional power saving modes may cause the device to be unavailable on the network for periods longer than the paging interval (from a few seconds to a few hours). During this time the device may not have any network access and may even be completely powered down. Any data sent during this time will experience significant delays, but these delays are assumed to be tolerable.

[0184] The processors of the application circuitry 1302 and the baseband circuitry 1304 may be used to execute elements of one or more instances of a protocol stack. For example, the processors of the baseband circuitry 1304 may be used to execute layer 3, layer 2, or layer 1 functions, either alone or in combination, while the processors of the application circuitry 1302 may utilize data (e.g., packet data) received from these layers and further execute layer 4 functions (e.g., Transmission Communication Protocol (TCP) layer and User Datagram Protocol (UDP) layer). As referred to herein, layer 3 may include a Radio Resource Control (RRC) layer, which is described in more detail below. As referred to herein, layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in more detail below. As referred to herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which is described in more detail below.

[0185] Figure 14 illustrates an interface of a baseband circuit according to some embodiments, such as the baseband circuits shown in Figures 1A, 2, and 13. As described above, the baseband circuit 1304 of Figure 13 may include processors 1304A-1304E and memory 1304G utilized by the processors. Each of the processors 1304A-1304E may include a memory interface 1404A-1404E, respectively, to transmit data to and receive data from the memory 1304G.

[0186] The baseband circuit 1304 may further include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1412 (e.g., an interface for transmitting data to and receiving data from a memory external to the baseband circuit 1304), an application circuit interface 1414 (e.g., an interface for transmitting data to and receiving data from the application circuit 1302 of FIG. 13), an RF circuit interface 1416 (e.g., an interface for transmitting data to and receiving data from the RF circuit 1306 of FIG. 13), a wireless hardware connectivity interface 1418 (e.g., an interface for transmitting data to and receiving data from a near field communication (NFC) component, a Bluetooth® component (e.g., Bluetooth Low Energy), a Wi-Fi component, and other communication components), and a power management interface 1420 (e.g., an interface for transmitting power or control signals to and receiving power or control signals from the PMC 1312).

[0187] 15 is a block diagram representing components according to some example embodiments that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and execute any one or more of the methodologies discussed herein. Specifically, FIG. 15 illustrates a diagrammatic representation of hardware resources including one or more processors (or processor cores) 1510, one or more memory / storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540. For embodiments in which node visualization (e.g., NFV) is utilized, a hypervisor 1520 may execute to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1500.

[0188] Processor 1510 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a multiple instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), such as a baseband processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof) may include, for example, processor 1512 and processor 1514.

[0189] The memory / storage device 1520 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1520 may include, but is not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc. Communications resources 1530 may include interconnection or network interface components or other suitable devices for communicating with one or more peripherals 1504 or one or more databases 1506 over network 1508. For example, communications resources 1530 may include wired communications components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communications components, NFC components, Bluetooth components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communications components.

[0190] The instructions 1550 may include software, programs, applications, applets, apps, or other executable code that causes at least one of the processors 1510 to execute any one or more of the methodologies discussed herein. The instructions 1550 may reside completely or partially within the processor 1510 (e.g., a cache memory of the processor), the memory / storage device 1520, or any suitable combination thereof. Furthermore, any portion of the instructions 1550 may be transferred to the hardware resources 1500 from any combination of the peripherals 1504 or the database 1506. Thus, the memory of the processor 1510, the memory / storage device 1520, the peripherals 1504, and the database 1506 are examples of computer-readable and machine-readable media.

[0191] In embodiments, one or more elements of Figures 12, 13, 14, and / or 15 may be configured to perform one or more processes, techniques, or methods, or portions thereof, described herein. In embodiments, one or more elements of Figures 12, 13, 14, and / or 15 may be configured to perform one or more processes, techniques, or methods, or portions thereof, described in the examples below.

[0192] As used herein, the term "circuitry" may refer to, be part of, or include application specific integrated circuits (ASICs), electronic circuits, processors (shared, dedicated, or groups), and / or memories (shared, dedicated, or groups) that execute one or more software or firmware programs, combinatorial logic circuits, and / or other suitable hardware components that provide the described functionality.

[0193] Various examples may be implemented using hardware elements, software elements, or a combination of both. In some examples, hardware elements may include devices, components, processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. In some examples, software elements may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. The decision whether an example is implemented using hardware and / or software elements may vary according to any number of factors, such as desired computation rates, power levels, thermal budget, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints desired for a given implementation.

[0194] Some examples may be described using the terms "coupled" and "connected," along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, descriptions using the terms "connected" and / or "coupled" may indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

[0195] Moreover, in the above Detailed Description, it can be seen that various features are grouped together in a single example to streamline the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed example. Accordingly, the following claims are incorporated into the Detailed Description, with each claim standing on its own as a separate example. In the appended claims, the terms "including" and "in which" are used as the plain English equivalents of the terms "comprising" and "wherein," respectively. Furthermore, the terms "first," "second," "third," etc. are used merely as labels and do not impose numerical requirements on their subject matter.

[0196] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features or acts described above are disclosed as example forms of implementing the claims.

[0197] A data processing system suitable for storing and / or executing program code includes at least one processor coupled indirectly or directly to memory elements through a system bus. The memory elements can include local memory used during the actual execution of the program code, bulk storage, and cache memory that provides temporary storage of at least some of the program code to reduce the number of times the code must be retrieved from bulk storage during execution. The term "code" encompasses a broad range of software components and configurations, including applications, drivers, processes, routines, methods, modules, firmware, microcode, and subprograms. Thus, the term "code" can be used to refer to any collection of instructions that, when executed by a processing system, performs a desired operation(s).

[0198] The processing circuits, logic circuits, devices, and interfaces described herein may be implemented in hardware and perform functions that are also implemented by code executed by one or more processors. A processing circuit or logic circuit refers to hardware or hardware and code that implements one or more logical functions. A circuit is hardware and can refer to one or more circuits. Each circuit can perform a particular function. Circuits in a circuit configuration can have discrete electrical components interconnected with one or more conductors, integrated circuits, chip packages, chip sets, memory, etc. Integrated circuits include circuits and can have components fabricated on a substrate such as a silicon wafer. Integrated circuits, processor packages, chip packages, and chip sets can also have one or more processors.

[0199] A processor may receive signals, such as instructions and / or data, at inputs and process the signals to generate at least one output. During execution of the code, the code changes the physical states and properties of the transistors that form the processor pipeline. The physical states of the transistors are transformed into logical bits of 1 and 0 that are stored in registers within the processor. The processor may transfer the physical states of the transistors to the registers and may transfer the physical states of the transistors to other storage media.

[0200] A processor may have a circuit or circuit configuration that performs one or more sub-functions implemented to perform the overall functionality of the "processor." Note that a "processor" may have one or more processors, and each processor may have one or more processor cores that process code and / or data independently or dependently. Each of the processor cores is also a "processor" and is distinguished from the processor only to describe the physical arrangement or architecture of a processor that includes multiple processor cores on one or more dies and / or in one or more chip packages. Depending on the design of the processor, a processor core may have a general-purpose processing core or may have a processor core that is configured to perform a specific task. A processor core may be a processor that includes one or more processor cores. As discussed and claimed herein, when discussing functions performed by a processor, processing circuit, etc., a processor, processing circuit, etc. may have one or more processors, each processor may include one or more processor cores, and any one or more of the processors and / or processor cores may be present on one or more dies and / or in one or more chip packages, and may perform all or a portion of the processing required to perform the function.

[0201] One example of a processor is a state machine or application specific integrated circuit (ASIC) that includes at least one input and at least one output. The state machine may operate on the at least one input to generate at least one output by performing a predetermined series of serial and / or parallel operations or transformations on the at least one input.

[0202] Some embodiments have one or more potentially advantageous effects. For example, triggering a measurement of the CLI can advantageously provide measurements to identify the CLI. Triggering an SRS of an aggressor UE can advantageously provide measurements of the CLI. Triggering a periodic, semi-persistent, or aperiodic SRS can advantageously facilitate dynamic L1 and / or L3 measurements of the CLI to identify mitigation schemes. Sending a CLI measurement and reporting configuration can advantageously facilitate measurements of the CLI by the victim UE and multiple neighbor base stations or UEs of neighbor base stations. Identifying an SRS or communication resource reference point A for measurements can advantageously facilitate generation of an L1 or L3 SRS-RSRP or CLI-RSSI CLI measurement report. Sending an SRS measurement report as part of a CSI-RS Part 1 or CSI Part 2 can advantageously send a CLI measurement report during a PUUCH or PUSCH. Sending an SRS measurement report as part of a MAC-CE can advantageously send a CLI measurement report during a PUSCH. Identifying a CLI-RSSI measurement of the CLI-RS can advantageously identify the RSSI of the CLI to aid in mitigation. Sharing or transmitting a muting pattern can advantageously aid in improved measurement and report generation by the victim UE and other base stations to improve measurement of the CLI for mitigation. Transmitting a CLI measurement report by one or more nearby base stations can advantageously facilitate mitigation of the CLI. Moving the UE to another communication resource in response to the SRS measurement report can advantageously mitigate the CLI and improve the efficiency of communication between the UE and the base station. Repeatedly measuring the SRS can advantageously monitor communication of the CLI. Measuring the L1 SRS-RSRP or CLI-RSSI can advantageously determine a dynamic CLI for dynamic TDD. Measuring the L3 CLI-RSRP or CLI-RSSI can advantageously determine a longer term dynamic CLI. Reporting one CLI measurement can advantageously be generated based on a single CLI measurement report. Reporting multiple CLI measurements can advantageously be shared or transmitted in a single CLI measurement report.

[0203] Further embodiment examples The following examples relate to further embodiments. Details of the examples may be used anywhere in one or more of the embodiments.

[0204] Example 1. An apparatus for reporting crosslink interference in a mobile user equipment (UE), comprising: Memory, a processing circuit coupled to the memory; The processing circuit includes: Decoding a first downlink (DL) control information (DCI) or higher layer signaling from a first base station, the DCI including a crosslink interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink (UL) transmission should be measured; measuring the SRS or other UL transmission based on the identification of the communications resource; generating said CLI measurement report based on measurements of said SRS or other UL transmissions and based on a definition of a CLI measurement report; encoding a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) for the first base station, the physical uplink shared channel (PUSCH) including the CLI measurement report; Device.

[0205] Example 2. the processing circuitry includes a processor and a memory coupled to the processor, a radio frequency circuit coupled to the processor, and one or more antennas coupled to the radio frequency circuitry; The apparatus described in Example 1.

[0206] Example 3. The CLI measurement and reporting configuration defines a periodic, semi-persistent, or aperiodic SRS to generate an SRS-Reference Signal Received Power (SRS-RSRP) for the CLI measurement report. The apparatus described in Example 1.

[0207] Example 4. The CLI measurement and reporting configuration defines that Layer 1 CLI measurements and reporting can be used for CLI mitigation between UEs. The apparatus described in Example 1.

[0208] Example 5. The CLI measurement and reporting configuration defines periodic, semi-persistent, or aperiodic reporting of SRS-Reference Signal Received Power (SRS-RSRP) or CLI-Received Signal Strength Indicator (CLI-RSSI) to be transmitted via the PUSCH or the PUCCH. The apparatus described in Example 1.

[0209] Example 6. the processing circuitry encodes a medium access control-control element (MAC-CE) including the CLI measurement report. The apparatus described in Example 1.

[0210] Example 7. The processing circuitry further transmits a second DCI to the second UE to schedule the SRS transmission from the second UE; The second DCI includes DCI format 0_1 ​​or DCI format 1_1; 7. A device according to any one of Examples 1 to 6.

[0211] Example 8. A method for mobile user equipment (UE) for reporting crosslink interference, comprising: receiving information regarding a crosslink interference (CLI) measurement and reporting configuration received from a first base station via a first downlink (DL) control information (DCI) or higher layer signaling, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink (UL) transmission should be measured; measuring, by a processing circuit, the SRS or other UL transmission based on the identification of the communications resource; generating, by the processing circuitry, the CLI measurement report based on measurements of the SRS or other UL transmissions and based on a definition of a CLI measurement report; transmitting the CLI measurement report to the first base station via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH); The method according to claim 1,

[0212] Example 9. the first DCI triggering an SRS measurement on the communications resource in response to decoding the first DCI; The method described in Example 8.

[0213] Example 10. transmitting the CLI measurement report includes transmitting an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both in CSI Part 1 or CSI Part 2 as part of a Channel State Information (CSI) report. The method described in Example 8.

[0214] Example 11. transmitting the CLI measurement report includes transmitting an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both as an uplink control information (UCI) type portion. The method described in Example 8.

[0215] Example 12. A machine-readable medium containing instructions for a mobile user equipment (UE), comprising: The instructions, when executed by a processor, cause the processor to perform an operation for reporting crosslink interference, the operation comprising: receiving information regarding a crosslink interference (CLI) measurement and reporting configuration received from a first base station via a downlink (DL) control information transmission or higher layer signaling, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink (UL) transmission should be measured; measuring the SRS or other UL transmission based on the identification of the communications resource; generating said CLI measurement report based on measurements of said SRS or other UL transmissions and based on a definition of a CLI measurement report; transmitting the CLI measurement report to the first base station via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH); 13. A machine-readable medium having:

[0216] Example 13. The operations further include multiplexing a plurality of uplink control information (UCI) types to transmit the CLI measurement report on the PUSCH, the PUCCH, or both; The CLI measurement report includes an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both, appended in a UCI type after Control State Information (CSI) Part 1 and before CSI Part 2 or after CSI Part 2; The machine-readable medium of Example 12.

[0217] Example 14. The operations include multiplexing a plurality of uplink control information (UCI) types and reporting the CLI measurement report on the PUSCH in a PUSCH format 3 or a PUSCH format 4 to support up to two separate encodings for the plurality of UCI types. The machine-readable medium of Example 12.

[0218] Example 15. The operations further include multiplexing a plurality of uplink control information (UCI) types for transmitting the CLI measurements on the PUCCH to support up to three separate encodings for the plurality of UCI types. The program described in Example 12.

[0219] Example 16. An apparatus for reporting cross-link interference in a mobile communication base station, comprising: an interface for backhaul signaling; a processing circuit coupled to the interface; The processing circuit includes: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; Sending the CLI measurement and reporting configuration to a first user equipment (UE) via downlink (DL) control information or higher layer signaling transmission; Device.

[0220] Example 17. the processing circuitry includes a processor and a memory coupled to the processor, a radio frequency circuit coupled to the processor, and one or more antennas coupled to the radio frequency circuitry; The device described in Example 16.

[0221] Example 18. The CLI measurement and reporting configuration defines a CLI-received signal strength indicator (CLI-RSSI) for measuring inter-subband CLI, intra-subband CLI, or both. The device described in Example 16.

[0222] Example 19. The CLI measurement and reporting configuration includes a configuration for SBFD operation including time and frequency resources for CLI-RSSI measurement reporting in one or more subbands for SBFD operation and UL quasi-co-location (QCL) assumptions from a second user equipment (UE); 19. A device according to any of Examples 16 to 18.

[0223] Example 20. 1. A method for a mobile communications base station for reporting cross-link interference, comprising: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; Sending the CLI measurement and reporting configuration to a first user equipment (UE) via downlink (DL) control information or higher layer signaling transmission; The method according to claim 1,

[0224] Example 21. and sharing the CLI measurement and reporting configuration with one or more neighboring base stations in a PDU via a backhaul interface. The method of Example 20.

[0225] Example 22. The CLI measurement and reporting configuration defines that the first UE generates a CLI measurement to include an SRS-Reference Signal Received Power (SRS-RSRP) or a CLI-Received Signal Strength Indicator (CLI-RSSI); The identification of the communication resource includes a reference subcarrier spacing and a cyclic prefix (CP) length, point A as a common reference point of a reference block grid, a channel bandwidth, time and frequency resources for measurement, a bandwidth portion (BWP) for transmission of the SRS, a system frame number (SFN) for the SRS, or a combination thereof; The method according to any of Examples 20 to 21.

[0226] Example 23. 1. A machine-readable medium containing instructions for a mobile communications base station, comprising: The instructions, when executed by a processor, cause the processor to perform an operation for reporting crosslink interference, the operation comprising: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; Sending the CLI measurement and reporting configuration to a first user equipment (UE) via downlink (DL) control information or higher layer signaling transmission; 13. A machine-readable medium having:

[0227] Example 24. The communications resource is located within a downlink (DL) subband in a non-overlapping subband full duplex (SBFD) symbol or slot, or the communications resource spans more than one DL subband of the SBFD, or both. The machine-readable medium of Example 23.

[0228] Example 25. The CLI measurement and reporting configuration defines the first UE to generate CLI measurements to include one or more CLI measurements. 25. The machine-readable medium of any of Examples 23-24.

[0229] Example 26. An apparatus comprising the means according to any one of Examples 8 to 11.

[0230] Example 27. An apparatus comprising the means according to any one of Examples 20 to 22.

[0231] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority under 35 U.S.C. § 119 to U.S. Provisional Patent Application No. 63 / 334,934, filed April 26, 2022, entitled "SYSTEMS AND METHODS FOR HANDLING UE CROSS LINK INTERFERENCE," which is incorporated herein by reference in its entirety. This application also claims priority under 35 U.S.C. § 119 to U.S. Provisional Patent Application No. 63 / 347,480, filed May 31, 2022, entitled "SYSTEMS AND METHODS FOR HANDLING UE CROSS LINK INTERFERENCE," which is incorporated herein by reference in its entirety.

Claims

1. An apparatus for reporting crosslink interference in a mobile user equipment (UE), comprising: Memory, a processing circuit coupled to the memory; The processing circuit includes: Decode a first downlink (DL) control information (DCI) or higher layer signaling from a first base station, the DCI including a crosslink interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which to measure a sounding reference signal (SRS) or other uplink (UL) transmission; measuring the SRS or other UL transmission based on the identification of the communications resource; generating said CLI measurement report based on measurements of said SRS or other UL transmissions and based on a definition of a CLI measurement report; encoding a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) for the first base station, the physical uplink shared channel (PUSCH) including the CLI measurement report; Device.

2. the processing circuitry includes a processor and a memory coupled to the processor, a radio frequency circuit coupled to the processor, and one or more antennas coupled to the radio frequency circuitry; 2. The apparatus of claim 1.

3. The CLI measurement and reporting configuration defines periodic, semi-persistent, or aperiodic SRS to generate SRS-Reference Signal Received Power (SRS-RSRP) for the CLI measurement report.

3. Apparatus according to claim 1 or 2.

4. The CLI measurement and reporting configuration defines that Layer 1 CLI measurement and reporting can be used for UE-to-UE CLI mitigation.

3. Apparatus according to claim 1 or 2.

5. The CLI measurement and reporting configuration defines periodic, semi-persistent, or aperiodic reporting of SRS-Reference Signal Received Power (SRS-RSRP) or CLI-Received Signal Strength Indicator (CLI-RSSI) to be transmitted via the PUSCH or the PUCCH.

3. Apparatus according to claim 1 or 2.

6. the processing circuitry encodes a medium access control-control element (MAC-CE) including the CLI measurement report; 3. Apparatus according to claim 1 or 2.

7. The processing circuit further transmits a second DCI to the second UE to schedule the SRS transmission from the second UE; The second DCI includes DCI format 0_1 ​​or DCI format 1_1; 3. Apparatus according to claim 1 or 2.

8. 1. A mobile user equipment (UE) method for reporting crosslink interference, comprising: receiving information regarding a crosslink interference (CLI) measurement and reporting configuration received via a first downlink (DL) control information (DCI) or higher layer signaling from a first base station, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink (UL) transmission should be measured; measuring, by a processing circuit, the SRS or other UL transmission based on the identification of the communications resource; generating, by the processing circuitry, the CLI measurement report based on measurements of the SRS or other UL transmissions and based on a CLI measurement report definition; transmitting the CLI measurement report to the first base station via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH); The method according to claim 1,

9. the first DCI triggering an SRS measurement on the communications resource in response to decoding the first DCI. The method according to claim 8.

10. transmitting the CLI measurement report comprises transmitting an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both as part of a Channel State Information (CSI) report in CSI Part 1 or CSI Part 2.

10. The method according to claim 8 or 9.

11. The transmitting the CLI measurement report includes transmitting an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both as an uplink control information (UCI) type part.

10. The method according to claim 8 or 9.

12. A program including instructions for a mobile user equipment (UE), comprising: The instructions, when executed by a processor, cause the processor to perform an operation for reporting crosslink interference, the operation comprising: receiving information regarding a cross-link interference (CLI) measurement and reporting configuration received from a first base station via a downlink (DL) control information transmission or higher layer signaling, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) or other uplink (UL) transmission should be measured; measuring the SRS or other UL transmission based on the identification of the communications resource; generating said CLI measurement report based on measurements of said SRS or other UL transmissions and based on a definition of a CLI measurement report; transmitting the CLI measurement report to the first base station via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH); A program having

13. The operations further include multiplexing a plurality of uplink control information (UCI) types to transmit the CLI measurement report on the PUSCH, the PUCCH, or both; The CLI measurement report includes an SRS-Reference Signal Received Power (SRS-RSRP), a CLI-Received Signal Strength Indicator (CLI-RSSI), or both, appended in a UCI type after Control State Information (CSI) Part 1 and before CSI Part 2 or after CSI Part 2. The program according to claim 12.

14. The operations include multiplexing a plurality of uplink control information (UCI) types and reporting the CLI measurement report on the PUSCH in a PUSCH format 3 or a PUSCH format 4 to support up to two separate encodings for the plurality of UCI types.

14. The program according to claim 12 or 13.

15. The operations further include multiplexing a plurality of uplink control information (UCI) types for transmitting the CLI measurements on the PUCCH to support up to three separate encodings for the plurality of UCI types.

14. The program according to claim 12 or 13.

16. An apparatus for reporting cross-link interference in a mobile communication base station, comprising: an interface for backhaul signaling; a processing circuit coupled to the interface; The processing circuit includes: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; sending the CLI measurement and reporting configuration to a first user equipment (UE) via a downlink (DL) control information or higher layer signaling transmission; Device.

17. the processing circuitry includes a processor and a memory coupled to the processor, a radio frequency circuit coupled to the processor, and one or more antennas coupled to the radio frequency circuitry; 17. The apparatus of claim 16.

18. The CLI measurement and reporting configuration defines a CLI-Received Signal Strength Indicator (CLI-RSSI) for measuring inter-subband CLI, intra-subband CLI, or both; 18. Apparatus according to claim 16 or 17.

19. The CLI measurement and reporting configuration includes a configuration for SBFD operation including time and frequency resources for CLI-RSSI measurement reporting in one or more subbands for SBFD operation and UL quasi-co-location (QCL) assumptions from a second user equipment (UE).

18. Apparatus according to claim 16 or 17.

20. 1. A method for a mobile communications base station for reporting cross-link interference, comprising: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; Sending the CLI measurement and reporting configuration to a first user equipment (UE) via a downlink (DL) control information or higher layer signaling transmission. The method according to claim 1,

21. and sharing the CLI measurement and reporting configuration with one or more neighboring base stations in a PDU over a backhaul interface.

21. The method of claim 20.

22. The CLI measurement and reporting configuration defines that the first UE generates a CLI measurement to include an SRS-reference signal received power (SRS-RSRP) or a CLI-received signal strength indicator (CLI-RSSI); The identification of the communication resource includes a reference subcarrier spacing and a cyclic prefix (CP) length, point A as a common reference point of a reference block grid, a channel bandwidth, time and frequency resources for measurements, a bandwidth portion (BWP) for transmission of the SRS, a system frame number (SFN) for the SRS, or a combination thereof.

22. The method according to claim 20 or 21.

23. A program including instructions for a mobile communications base station, comprising: The instructions, when executed by a processor, cause the processor to perform an operation for reporting crosslink interference, the operation comprising: generating a cross-link interference (CLI) measurement and reporting configuration, the CLI measurement and reporting configuration including an identification of a communication resource on which a sounding reference signal (SRS) is to be measured; Sending the CLI measurement and reporting configuration to a first user equipment (UE) via a downlink (DL) control information or higher layer signaling transmission. A program having

24. the communications resource is located within a downlink (DL) subband in a non-overlapping subband full duplex (SBFD) symbol or slot, the communications resource spans more than one DL subband of the SBFD, or both; 24. The program of claim 23.

25. The CLI measurement and reporting configuration defines the first UE to generate CLI measurements to include one or more CLI measurements.

25. A program according to claim 23 or 24.

Images