# US 12,004,088 B2 · Network coordination for crosslink interference mitigation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,004,088 B2 - Document ID: US12004088B2 - Status: Granted - Kind: B2 - Application number: 17/421,786 - Filed: 2020-01-11 - Published: 2022-03-24 - Granted: 2024-06-04 - Earliest claimed: 2019-01-11 - Assignees: Apple Inc. - Applicants: Apple Inc. - Inventors: Dawei Ying; Hassan Ghozlan; Qian Li; Geng Wu - Web page: https://patentgrep.com/patent/US12004088B2 ## CPC - H04L 5/005: {of common pilots, i.e. pilots destined for multiple users or terminals} - H04W 52/243: {taking into account interferences} - H04B 17/336: Signal-to-interference ratio [SIR] or carrier-to-interference ratio [CIR] - H04L 5/0073: {Allocation arrangements that take into account other cell interferences} - H04W 24/10: Scheduling measurement reports {; Arrangements for measurement reports} - H04W 52/146: {Uplink power control} - H04W 52/367: {Power values between minimum and maximum limits, e.g. dynamic range} - H04W 12/06: Authentication - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04B: TRANSMISSION ## Abstract Disclosed herein are system, method, and computer program product embodiments for identifying an aggressor device or an aggressor beam of an aggressor device. The embodiments further mitigate the impact of the identified aggressor device or the identified aggressor beam of the aggressor device. ## Claims ### Claim 1 A method of mitigating an aggressor device, comprising: identifying the aggressor device based at least in part on an original crosslink interference (CLI) measurement report from a victim device; transmitting a CLI Reference Signal (CLI-RS) refinement request message to the aggressor device, wherein the CLI-RS refinement request message comprises an identifier for the aggressor device; receiving a CLI-RS refinement response message from the aggressor device, wherein the CLI-RS refinement response message comprises an indication that the CLI-RS refinement request message was accepted by the aggressor device; and transmitting an updated CLI measurement configuration to the victim device based at least in part on the CLI-RS refinement response message. ### Claim 2 (depends on 1) The method of claim 1, further comprising: transmitting an original CLI measurement configuration to the victim device; and receiving the original CLI measurement report from the victim device. ### Claim 3 (depends on 1) The method of claim 1, further comprising: receiving an updated CLI measurement report from the victim device; and identifying an aggressor beam of the aggressor device based at least in part on the updated CLI measurement report. ### Claim 4 (depends on 1) The method of claim 1, wherein the CLI-RS refinement response message comprises a CLI-RS transmission configuration for the aggressor device. ### Claim 5 (depends on 1) The method of claim 1, wherein the aggressor device is a user equipment (UE) or a Next Generation NodeB (gNB). ### Claim 6 (depends on 1) The method of claim 1, wherein the victim device is a user equipment (UE) or a Next Generation NodeB (gNB). ### Claim 7 (depends on 1) The method of claim 1, wherein the CLI-RS refinement request message comprises a transmission information type for the aggressor device. ### Claim 8 A base station, comprising: radio front end circuitry; and processing circuitry coupled to the radio front end circuitry and configured to: identify an aggressor device based at least in part on an original crosslink interference (CLI) measurement report from a victim device; transmit, via the radio front end circuitry, a CLI Reference Signal (CLI-RS) refinement request message to the aggressor device, wherein the CLI-RS refinement request message comprises an identifier for the aggressor device; receive, via the radio front end circuitry, a CLI-RS refinement response message from the aggressor device, wherein the CLI-RS refinement response message comprises an indication that the CLI-RS refinement request message was accepted by the aggressor device; and transmit, via the radio front end circuitry, an updated CLI measurement configuration to the victim device based at least in part on the CLI-RS refinement response message. ### Claim 9 (depends on 8) The base station of claim 8, wherein the processing circuitry is further configured to: transmit, via the radio front end circuitry, an original CLI measurement configuration to the victim device; and receive, via the radio front end circuitry, the original CLI measurement report from the victim device. ### Claim 10 (depends on 8) The base station of claim 8, wherein the processing circuitry is further configured to: receive, via the radio front end circuitry, an updated CLI measurement report from the victim device; and identify an aggressor beam associated with the aggressor device based at least in part on the updated CLI measurement report. ### Claim 11 (depends on 8) The base station of claim 8, wherein the CLI-RS refinement response message comprises a CLI-RS transmission configuration for the aggressor device. ### Claim 12 (depends on 8) The base station of claim 8, wherein the aggressor device is a user equipment (UE) or a Next Generation NodeB (gNB). ### Claim 13 (depends on 8) The base station of claim 8, wherein the victim device is a user equipment (UE) or a Next Generation NodeB (gNB). ### Claim 14 (depends on 8) The base station of claim 8, wherein the CLI-RS refinement request message comprises a transmission information type for the aggressor device. ### Claim 15 A non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising: identifying an aggressor device based at least in part on an original crosslink interference (CLI) measurement report from a victim device; transmitting a CLI Reference Signal (CLI-RS) refinement request message to the aggressor device, wherein the CLI-RS refinement request message comprises an identifier for the aggressor device; receiving a CLI-RS refinement response message from the aggressor device, wherein the CLI-RS refinement response message comprises an indication that the CLI-RS refinement request message was accepted by the aggressor device; and transmitting an updated CLI measurement configuration to the victim device based at least in part on the CLI-RS refinement response message. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the operations further comprise: transmitting an original CLI measurement configuration to the victim device; and receiving the original CLI measurement report from the victim device. ### Claim 17 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the operations further comprise: receiving an updated CLI measurement report from the victim device; and identifying an aggressor beam of the aggressor device based at least in part on the updated CLI measurement report. ### Claim 18 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the CLI-RS refinement response message comprises a CLI-RS transmission configuration for the aggressor device. ### Claim 19 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the aggressor device is a user equipment (UE) or a Next Generation NodeB (gNB), and the victim device is a user equipment (UE) or a Next Generation NodeB (gNB). ### Claim 20 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the CLI-RS refinement request message comprises a transmission information type for the aggressor device.