Triggering of reporting indicating interference and / or integrity of downlink data related to cross-link interference

Abstract

A method of operating a communication device with a wireless communication network includes receiving downlink data transmitted over a wireless access interface provided by the wireless communication network. Downlink data is transmitted in a downlink channel that forms part of the wireless access interface. The method includes generating a metric indicating integrity of downlink data received over a downlink channel. A downlink channel carrying downlink data may be referred to as a target channel. The method further includes generating, from the measurement resource, a metric indicating cross-link interference (CLI) coexisting with downlink data received over the target downlink channel, the CLI measured from the measurement resource for the target downlink channel, and determine whether to trigger a reporting event based on the metric indicative of the integrity of the cross-link interference and / or the downlink data to report the metric indicative of the integrity of the cross-link interference and / or the downlink data. In accordance with an exemplary embodiment, a decision made by a UE to transmit an indication of a cross-link interference metric is based on the integrity of downlink data (e.g., bit error rate), or the number of consecutive similar HARQ-ACKs, and / or the measured CLI, to more efficiently respond to CLI by adjusting transmission of downlink data or avoiding CLI.

Description

Technical Field

[0001] This disclosure relates to communication apparatus, infrastructure equipment, and methods of operating communication apparatus and infrastructure equipment with wireless communication networks. This disclosure is entitled to priority under the Paris Convention for European patent application filed on April 18, 2023 (application number: EP23168602.3), the entire contents of which are incorporated herein by reference. Background Technology

[0002] The “background” description provided herein is for the purpose of generally presenting the context of this disclosure. To the extent described in this background section, the work of the currently designated inventors and aspects of the description that may not be considered prior art at the time of filing are neither expressly nor implied to be considered prior art to this technology.

[0003] Previous-generation mobile telecommunications systems, such as those based on the UMTS and LTE architectures defined by 3GPP, can support a wider range of services than the simple voice and messaging services offered by earlier generations. For example, with the improved radio interface and increased data rates provided by LTE systems, users can enjoy high-data-rate applications, such as mobile video streaming and mobile video conferencing, which were previously only available through fixed-line data connections. Therefore, there is a strong demand for deploying such networks, and a faster expectation that the coverage areas of these networks (i.e., the geographical locations where the network can be accessed) will expand more rapidly.

[0004] Current and future wireless communication networks are expected to routinely and efficiently support communication with an increasingly diverse range of devices, whose associated data traffic characteristics and types are broader than those optimized for by existing systems. For example, future wireless communication networks are expected to efficiently support communication with various types of devices, including low-complexity devices, machine-type communication (MTC) devices, high-resolution video displays, virtual reality headsets, and extended reality (XR) devices. Some of these different device types can be deployed in large numbers, such as low-complexity devices supporting the Internet of Things (IoT), and are typically associated with relatively small data transmissions and relatively high latency tolerance. Other types of devices (such as devices supporting high-definition video streaming) may be associated with relatively large data transmissions and relatively low latency tolerance. Other types of devices (such as devices used for autonomous vehicle communication and other critical applications) may be characterized by low-latency, high-reliability data transmission over the network. Depending on the application being operated, individual device types may also be associated with different traffic characteristics / features. For example, when a smartphone is used for video streaming applications (high downlink data), the factors that need to be considered to efficiently support its data exchange may be different compared to when it is used for internet browsing applications (indirect uplink and downlink data) or for voice communication by emergency responders in emergency scenarios (where data must meet strict reliability and latency requirements).

[0005] In light of this, it is expected that current wireless communication networks, such as what may be called 5G or New Radio (NR) systems / New Radio Access Technology (RAT) systems, or future 6G wireless communication and subsequent iterations / versions of existing systems, will be able to effectively support the connectivity of a wide range of devices associated with different applications and the data traffic characteristics and demands with different features.

[0006] One example of the new service is called Ultra Reliable Low Latency Communication (URLLC), which, as the name suggests, requires data units or packets to be transmitted with high reliability and low communication latency. Another example of the new service is Enhanced Mobile Broadband (eMBB), characterized by high capacity, requiring support up to 20 Gb / s. Therefore, URLLC and eMBB type services are challenging examples for both LTE and 5G / NR communication systems.

[0007] 5G NR continues to evolve, and current work plans have incorporated 5G-NR-Advanced, with further enhancements expected, particularly to support new use cases and scenarios with higher demands. The expectation of supporting these new use cases and scenarios presents new challenges, requiring solutions for effectively handling communications within wireless communication systems. Summary of the Invention

[0008] This disclosure can help resolve or mitigate at least some of the aforementioned problems.

[0009] Implementations of this technology provide a method for operating a communication device with a wireless communication network. The method includes receiving downlink data transmitted via a wireless access interface provided by the wireless communication network. The downlink data is transmitted in a downlink channel forming part of the wireless access interface. The method further includes generating a metric indicating the integrity of the downlink data received via the downlink channel. The method also includes generating a metric from measurement resources indicating cross-link interference (CLI) that coexists with the downlink data received via the target downlink channel, and determining whether to trigger a reporting event based on the metric indicating integrity and / or the metric indicating cross-link interference to report the metric indicating the integrity of the downlink data and / or the metric indicating cross-link interference.

[0010] According to an exemplary implementation, the decision made by the communication device to transmit a cross-link interference indication is based on a relative metric used to assess the integrity of the target downlink channel carrying downlink data, such as the bit error rate, or the number of HARQ-ACKs and / or CLIs. Therefore, the UE determines whether to transmit a report of experienced cross-link interference based on a measurement or estimate of the integrity of the target downlink channel. The report may be a Layer 1 (L1) report. Thus, improvements can be provided in more efficient and effective downlink data transmission by mitigating CLIs or more accurately controlling link adjustments based on the cross-link interference experienced by the communication device while receiving downlink data.

[0011] Implementations of this technology may also provide methods for operating infrastructure equipment, communication devices, infrastructure equipment, circuits for communication devices, circuits for infrastructure equipment, computer programs, and computer-readable storage media.

[0012] The appended claims define various aspects and features of this disclosure.

[0013] It should be understood that the foregoing general description and the following detailed description are exemplary and not intended to limit the technology. A better understanding of the described embodiments and their additional advantages will be achieved by reading the following detailed description in conjunction with the accompanying drawings. Attached Figure Description

[0014] This disclosure will become more readily understood by referring to the following detailed description and taking into consideration the accompanying drawings, in which the same reference numerals indicate the same or corresponding parts in multiple views, and wherein:

[0015] Figure 1Some aspects of an LTE-type wireless telecommunications system that can be configured to operate according to some embodiments of this disclosure are illustrated schematically;

[0016] Figure 2 Some aspects of a novel radio access technology (RAT) wireless telecommunication system that can be configured to operate according to some embodiments of this disclosure are illustrated schematically;

[0017] Figure 3 This is a schematic block diagram of exemplary infrastructure equipment and communication apparatus that can be configured to operate according to some embodiments of this disclosure;

[0018] Figure 4 An example of inter-cell cross-link interference is illustrated schematically;

[0019] Figure 5 An exemplary method for resolving inter-cell cross-link interference is shown;

[0020] Figure 6 An example of non-overlapping subbands used for uplink and downlink transmission is illustrated schematically;

[0021] Figure 7 An example of non-overlapping subbands used for uplink and downlink transmission is illustrated schematically;

[0022] Figure 8 An example of cross-link interference within a cell is illustrated schematically;

[0023] Figure 9 An example of inter-subband interference is illustrated schematically;

[0024] Figure 10 An example of interference within a subband is illustrated schematically;

[0025] Figure 11 The diagram illustrates CSI-RS resources and CSI reports.

[0026] Figure 12 The diagram schematically illustrates a CSI-RS arranged close to the PDSCH according to an exemplary embodiment; and

[0027] Figure 13 This is a flowchart illustrating an exemplary implementation of triggering a CLI report based on one or both of the integrity of the received downlink data and the measured CLI, according to an exemplary implementation. Detailed Implementation

[0028] Advanced Long Term Evolution (4G) radio access technology

[0029] Figure 1A schematic diagram is provided illustrating some basic functions of a mobile telecommunications network / system 6 that typically operates according to LTE principles, but it may also support other radio access technologies and can be adapted to implement embodiments of this disclosure as described herein. Figure 1 The various components and certain aspects of their respective operating modes are well known and defined in the relevant standards managed by the 3GPP (RTM) organization, as well as described in numerous books on the subject (e.g., Holma H. ​​and Toskala A [1]). It should be understood that aspects of telecommunications network operation not specifically described herein (e.g., those related to specific communication protocols and physical channels used for communication between different components) can be implemented according to any known technology, such as in accordance with relevant standards, and proposed modifications and additions to the relevant standards known thereto.

[0030] Network 6 includes multiple base stations 1 connected to core network 2. Each base station provides coverage area 3 (i.e., a cell) within which it can transmit data to and receive data from communication device 4. Although each base station 1... Figure 1 While shown as a single entity, those skilled in the art will understand that some functions of a base station may be performed by different interconnecting elements, such as antennas (antenna assemblies), remote radio heads, amplifiers, etc. Overall, one or more base stations may form a radio access network.

[0031] Data is transmitted from base station 1 to communication device 4 within its respective coverage area 3 via a radio downlink. Data is transmitted from communication device 4 to base station 1 via a radio uplink. Core network 2 routes data to and from communication device 4 through each base station 1, and provides functions such as authentication, mobility management, and billing. Terminal devices may also be referred to as mobile stations, user equipment (UE), user terminals, mobile radio stations, communication devices, etc. Services provided by core network 2 may include connectivity to the Internet or external telephone services. Core network 2 may further track the location of communication device 4 to efficiently contact (i.e., call) communication device 4, thereby sending downlink data to communication device 4.

[0032] A base station (as an example of network infrastructure equipment) may also be referred to as a transceiver station, nodeB, e-nodeB, eNB, g-nodeB, gNB, etc. In this respect, different generations of wireless telecommunication systems are typically associated with different terms for components providing substantially equivalent functionality. However, some embodiments of this disclosure can be implemented equivalently in different generations of wireless telecommunication systems, and for the sake of brevity, specific terms may be used without being limited to the underlying network architecture. That is, the use of specific terms in some exemplary implementations is not intended to indicate that these implementations are limited to the generation of networks most closely associated with that specific term.

[0033] New radio access technology (5G)

[0034] Systems incorporating NR technology are expected to support different services (or service types) characterized by varying requirements for latency, data rate, and / or reliability. For example, enhanced mobile broadband (eMBB) service is characterized by high capacity, requiring support up to 20 Gb / s. Ultra-reliable low-latency communication (URLLC) service requires latency of 1– ms when transmitting 32-byte data packets in a single transmission. "(99.999%) or higher (99.9999%) [2] reliability, from the radio protocol layer 2 / 3 SDU entry point to the radio protocol layer 2 / 3 SDU exit point of the radio interface."

[0035] Massive Machine Type Communication (mMTC) is another example of a service that can be supported by NR-based communication networks. Furthermore, the system is expected to support further enhancements related to the Industrial Internet of Things (IIoT) to support services with new requirements for high availability, high reliability, low latency, and, in some cases, high-precision positioning.

[0036] Figure 2 An exemplary configuration of a wireless communication network is shown, which uses some of the terminology proposed and used for NR and 5G. Figure 2 In this configuration, multiple transmission and reception points (TRPs) 10 are connected to distributed control units (DUs) 41, 42 via a connection interface represented by line 16. Each TRP 10 is arranged to transmit and receive signals within the available radio frequency bandwidth of the wireless communication network via a wireless access interface. Thus, within the range of radio communication via the wireless access interface, each TRP 10 forms a cell of the wireless communication network, as indicated by circle 12. Therefore, wireless communication devices 14 within the wireless communication range provided by cell 12 can transmit and receive signals with TRPs 10 via the wireless access interface. Each of the distributed units 41, 42 is connected to a central unit (CU) 40 (which may be referred to as a control node) via interface 46. The central unit 40 is then connected to a core network 20, which may contain all other functions required for data transmission during bidirectional communication with wireless communication devices, and the core network 20 may be connected to other networks 60.

[0037] Figure 2 The components of the wireless access network shown can be configured according to the relevant provisions. Figure 1 The example describes a similar operation to the corresponding components of an LTE network. It should be understood that, in Figure 2The operational aspects of the telecommunications network represented, and the operational aspects of other networks according to embodiments of this disclosure discussed herein, wherein the parts not specifically described (e.g., regarding specific communication protocols and physical channels for communication between different components) may be implemented according to any known technology, such as methods currently used for implementing such operations of wireless telecommunications systems, for example, according to relevant standards.

[0038] Figure 2 The TRP 10 in the new RAT network may partially possess functions corresponding to a base station or eNodeB in an LTE network. Similarly, the communication device 14 may possess functions corresponding to a UE device 4 known for operation with an LTE network. Therefore, it should be understood that operational aspects of the new RAT network (e.g., specific communication protocols and physical channels for communication between different components) may differ from known operations in LTE or other known mobile telecommunications standards. However, it should also be understood that each of the core network components, base stations, and communication devices in the new RAT network will functionally resemble, respectively, the core network components, base stations, and communication devices of an LTE wireless communication network.

[0039] In terms of a wide range of high-level functions, connecting to Figure 2 The core network 20 of the new RAT telecommunications system can be roughly considered to be... Figure 1 Corresponding to the core network 2 represented, and each central unit 40 and its associated distributed unit / TRP 10 can be considered to provide a similar service to... Figure 1 The functions corresponding to base station 1. The term "network infrastructure equipment / access node" can be used to encompass these elements as well as more traditional base station types in wireless telecommunications systems. Depending on the specific application, the responsibility for scheduling transmissions arranged at the radio interfaces between the distributed units and communication devices may be borne by the control node / central unit and / or the distributed unit / TRP. Figure 2 In this context, communication device 14 is indicated within the coverage area of ​​the first communication cell 12. Therefore, communication device 14 can exchange signaling with the first central unit 40 within the first communication cell 12 via one of the distributed units / TRP 10 associated with the first communication cell 12.

[0040] It should also be understood that Figure 2 This is merely an example of the proposed architecture for a telecommunications system based on the new RAT, in which the methods described herein can be employed, and the functionality disclosed herein can also be applied to wireless telecommunications systems with different architectures.

[0041] Therefore, some embodiments of this disclosure discussed herein can be implemented according to various different architectures (such as, Figure 1 and Figure 2The exemplary architecture shown is implemented in a wireless telecommunications system / network. Therefore, it should be understood that the specific wireless telecommunications architecture is not of primary significance to the principles described herein in any particular implementation. In this regard, some embodiments of this disclosure are generally described in the context of communication between network infrastructure equipment / access nodes and communication devices, wherein the specific form of the network infrastructure equipment / access nodes and communication devices will depend on the network infrastructure in the specific implementation scenario. For example, in some scenarios, the network infrastructure equipment / access node may include a base station (such as...) suitable for providing functions consistent with the principles described herein. Figure 1 The LTE-type base station 1 shown, in other examples, network infrastructure equipment may include a central unit / control node 40 and / or a central unit / control node 40 adapted to provide functions consistent with the principles described herein. Figure 2 The TRP10 shown is of the type shown.

[0042] Figure 3 Provided Figure 2 A more detailed illustration of some components of the network is shown. Figure 3 In, such as Figure 2 The TRP 10 shown (in simplified form) includes a wireless transmitter 30, a wireless receiver 32, and a controller or control processor 34 operable to control the transmitter 30 and the wireless receiver 32 to transmit and receive radio signals to one or more UEs 14 within the cell 12 formed by the TRP 10. Figure 3 As shown, the exemplary UE 14 is shown to include a corresponding transmitter 49, receiver 48, and controller 44, which is configured to control the transmitter 49 and receiver 48 to transmit signals representing uplink data to the wireless communication network through the wireless access interface formed by TRP 10, and to receive downlink data (such as signals transmitted by transmitter 30 and received by receiver 48) in normal operation.

[0043] Transmitters 30, 49 and receivers 32, 48 (and other transmitters, receivers, and transceivers described in connection with the examples and embodiments of this disclosure) may include radio frequency filters, amplifiers, and signal processing components and devices for transmitting and receiving radio signals, for example, according to 5G / NR standards. Controllers 34, 44 (and other controllers described in connection with the examples and embodiments of this disclosure) may be, for example, microprocessors, CPUs, or dedicated chipsets, configured to execute instructions stored on a computer-readable medium, such as non-volatile memory. The processing steps described herein may be executed, for example, by a microprocessor in conjunction with random access memory, and the microprocessor operates according to instructions stored on a computer-readable medium. For ease of illustration, the transmitters, receivers, and controllers are shown in... Figure 3These are schematically shown as independent components. However, it should be understood that the functions of these components can be implemented in a variety of different ways, such as using one or more appropriately programmed programmable computers, or one or more appropriately configured application-specific integrated circuits / circuit systems / chips / chipsets. It should be understood that network infrastructure equipment / TRP / base stations and UE / communication devices typically include a variety of other components related to their operational functions.

[0044] like Figure 3 As shown, TRP 10 also includes a network interface 50, which is connected to DU 42 via physical interface 16. Therefore, network interface 50 provides a communication link for transmitting data and signaling from TRP 10 to core network 20 via DU 42 and CU 40.

[0045] The interface 46 between DU 42 and CU 40 is referred to as the F1 interface, which can be a physical interface or a logical interface. The F1 interface 46 between the CU and DU can operate according to the 3GPP TS 38.470 and 3GPP TS 38.473 specifications and can be formed by fiber optic or other wired or wireless high-bandwidth connections. In one example, the connection 16 from TRP 10 to DU 42 is implemented via fiber optic. The connection between TRP 10 and the core network 20 is typically referred to as the backhaul, which includes the interface 16 from the network interface 50 of TRP 10 to DU 42, and the F1 interface 46 from DU 42 to CU 40.

[0046] Full-duplex time-division duplex (FD-TDD)

[0047] NR / 5G networks can use time division duplex (TDD) operation, in which the entire frequency band or carrier will switch to downlink or uplink transmission for a period of time, and then switch to another downlink or uplink transmission in subsequent periods. Currently, TDD operates in half-duplex mode (HD-TDD), in which gNB or UE can send or receive data packets at a given time, but cannot send and receive simultaneously. As wireless networks evolve from NR to 5G-Advanced networks, a new feature of such networks is proposed: to enhance the duplex operation capability of time division duplex (TDD) by implementing full-duplex operation (FD-TDD) in TDD [3], [4].

[0048] In FD-TDD, the gNB can simultaneously send and receive data from the UE on the same frequency band. Furthermore, depending on the UE's capabilities, the UE can operate in either HD-TDD or FD-TDD mode. For example, when the UE only supports HD-TDD, FD-TDD can be implemented at the gNB by scheduling downlink transmissions to the first UE and uplink transmissions from the second UE within the same Orthogonal Frequency Division Multiplexing (OFDM) symbol (i.e., simultaneously). Conversely, when the UE supports FD-TDD, FD-TDD is implemented at both the gNB and the UE; the gNB can simultaneously schedule DL and UL transmissions for the UE within the same OFDM symbol by arranging DL and UL transmissions on different frequencies within the system bandwidth (e.g., different Physical Resource Blocks, PRBs). The hardware required for a UE supporting FD-TDD is more complex than that for a UE supporting only HD-TDD. Current 5G network development primarily focuses on enabling FD-TDD at the gNB, while the UE operates in HD-TDD mode.

[0049] Motivations for enhancing TDD duplex operation include increasing system capacity, reducing latency, and improving uplink coverage. For example, in current HD-TDD systems, OFDM symbols are allocated semi-statically only in the DL or UL direction. Therefore, if there is little or no data in one direction, idle resources cannot be used in the other direction, or their utilization is low. However, if resources can be used for both DL and UL data simultaneously (as in FD-TDD), resource utilization in the system can be improved. Furthermore, in current HD-TDD systems, UEs can receive DL data but cannot simultaneously transmit UL data, resulting in latency. Allowing the gNB or UE to transmit and receive data simultaneously (as in FD-TDD) would improve data transmission latency. Additionally, UL transmission is often coverage-limited when a UE is near the cell edge. While allocating more time-domain resources to UL transmission (e.g., retransmission) can improve coverage for UEs at the cell edge, allocating more time resources to the UL direction reduces the time resources allocated to the DL direction, leading to system imbalance. Enabling FD-TDD allows for the allocation of more UL time resources to the UE when needed, without sacrificing DL time resources.

[0050] Inter-cell cross-link interference (CLI)

[0051] In NR systems, the slot format (i.e., the allocation of DL and UL OFDM symbols within a slot) can be semi-static or dynamically configured, where each OFDM symbol (OS) in a slot can be configured as downlink (DL), uplink (UL), or flexible mode (F). OFDM symbols semi-statically configured as flexible mode can be dynamically indicated as DL, UL, or remain flexible by a dynamic slot format indicator (SFI) transmitted using Group Common (GC) DCI of DCI format 2_0, where the CRC of the GC-DCI is masked by the SFI-RNTI. Flexible OFDM symbols that remain flexible mode after indication from the SFI can be changed to DL or UL symbols respectively via downlink grant (DL Grant) or uplink grant (UL Grant). That is, a downlink grant for a PDSCH that overlaps with a flexible OFDM symbol will convert those flexible OFDM symbols to DL, and similarly, an uplink grant for a PUSCH that overlaps with a flexible OFDM symbol will convert those flexible OFDM symbols to UL.

[0052] Because each gNB in ​​the network can independently change the configuration of each OFDM symbol in a semi-static or dynamic manner, it is possible that in a given OFDM symbol, one gNB is configured for UL while an adjacent gNB is configured for DL. This can cause inter-cell cross-link interference (CLI) between conflicting gNBs (due to UL / DL symbol conflicts in one or more symbols). Inter-cell CLI occurs when a UE's UL transmission interferes with the DL reception of another UE in another cell, or when a gNB's DL transmission interferes with the UL reception of another gNB. In other words, inter-cell CLI is caused by inconsistent (conflicting) time slot formats between adjacent cells. Figure 4 An example is shown where gNB1 411 and gNB2 412 have synchronized time slots. At a given time slot, the format of gNB1's 411 time slot is {D, D, D, D, D, D, D, D, D, D, U, U, U, U}, while the format of gNB2's 412 time slot is {D, D, D, D, D, D, D, D, D, D, D, U, U, U}, where D indicates DL and U indicates UL. Inter-cell CLI occurs during the 11th OFDM symbol of the time slot, where gNB1 411 is performing UL while gNB2 412 is performing DL. Specifically, inter-cell CLI 441 occurs between gNB1 411 and gNB2 412, where gNB2 412's DL transmission 431 interferes with gNB1 411's UL reception 432. CLI 442 also occurs between UE1 421 and UE2 422, where UL transmission 432 of UE1 421 interferes with DL reception 431 of UE2 422.

[0053] Rel-16 CLI Measurement

[0054] Some traditional implementations attempt to reduce inter-cell CLI caused by flexible and dynamic time slot format configurations in TDD networks. Two CLI measurement reports used to manage and coordinate scheduling between neighboring gNBs include: Reference Signal Received Power (RSRP) for Sounding Reference Signals (SRS) and CLI Received Signal Strength Indication (RSSI). In SRS-RSRP, the power contribution of the SRS transmitted by the UE is measured as a linear average by the UE in neighboring cells. This measurement is performed on the configured resource elements within the considered measurement frequency bandwidth and at the configured measurement timing. In CLI-RSSI, the linear average of the observed total received power is measured only at a specific OFDM symbol of the measurement timing resource, and this measurement is performed on the measurement resource elements configured by the UE within the measurement bandwidth.

[0055] Both SRS-RSRP and CLI-RSSI are RRC measurements performed by the UE to mitigate inter-cell CLI between UEs. For SRS-RSRP, the interfering UE (i.e., the UE whose UL transmission interferes with another UE in a neighboring cell) sends SRS in the uplink, while the victim UE in the neighboring cell (i.e., the UE that is interfered with by the UL transmission of the UE in the neighboring cell) is configured with a measurement configuration that includes the SRS parameters of the interfering UE, enabling the measurement of interference from the interfering UE. Figure 5 An example is shown where, in a specific time slot, the 11th OS (OFDM symbol) of gNB1 511 and gNB2 512 causes an inter-cell CLI. Here, gNB1 511 has configured UE1 521 (the interfering UE) to transmit SRS 540, and gNB2 512 has configured UE2 522 (the victim UE) to measure SRS 540. UE2 522 is provided with the SRS configuration parameters of UE1 521, such as the RS sequence used, frequency resources, frequency transport comb structure, and time resources, enabling UE2 522 to measure SRS 540. Typically, the UE can be configured to monitor 32 different SRSs, with a maximum rate of 8 SRSs per time slot.

[0056] For CLI-RSSI measurements, the UE measures the total received power (i.e., signal and interference) according to the configured period, the start and end OFDM symbols of the time slot, and a set of frequency resource blocks (RBs). Since SRS-RSRP is measured against a specific UE's transmission, the network can target specific interfering UEs to reduce their transmission power, and in some cases, the interfering UE is not scheduled at the same time as a victim UE reporting high SRS-RSRP measurements. In contrast, CLI-RSSI cannot be used to identify the transmissions of specific interfering UEs, but it does provide an overall estimate of the inter-cell CLI experienced by the victim UE.

[0057] However, both SRS-RSRP and CLI-RSSI are Layer 3 measurements, which typically take longer to perform than measurements at lower layers (such as Layer 1).

[0058] Sub-band Full-Duplex (SBFD)

[0059] In SBFD, the frequency resources of the TDD system bandwidth or bandwidth portion (BWP) (i.e., at the UE / gNB) are divided into two or more non-overlapping subbands, each of which can be DL or UL[5]. Guard subbands can be used between DL and UL subbands to reduce inter-subband interference.

[0060] Figure 6 An example is shown where DL and UL transmissions can be performed simultaneously in different non-overlapping subbands 401 to 403, i.e., in different sets of frequency resource blocks (RBs): subband #1 401, subband #2 402, and subband #3 403, where subband #1 401 and subband #3 403 are used for DL ​​transmissions, while subband #2 402 is used for UL transmissions.

[0061] Although Figure 6 The diagram shows the system bandwidth divided into three subbands, but any number of subbands can be used. For example, the system bandwidth can be divided into four subbands, which may include two downlink subbands 401 and 403, an uplink subband 402, and another uplink subband, although other subband configurations are contemplated. To reduce leakage from one subband to another from subbands 401 to 403, a protection subband 410 can be configured between the UL and DL subbands 401 to 403. Protection subband 410 is configured between downlink subband #3 403 and uplink subband #2 402, and between uplink subband #2 402 and downlink subband #1 401.

[0062] Figure 6The arrangement of sub-bands 401 to 403 shown is only one possible arrangement of sub-bands. Other arrangements may also be used, and guard sub-bands can be used in almost any sub-band arrangement.

[0063] Figure 7 Two other examples are shown, where the DL sub-band and UL sub-band are separated by a protective sub-band. For example, in Figure 7 On the left, UL subband #1 501 and DL subband #2 503 are separated by guard subband 502. In this case, DL subband #2 503 occupies a higher frequency portion of the system bandwidth compared to UL subband #1 501. Figure 7 On the right side, DL subband #1 504 is separated from UL subband #2 506 by guard subband 505. In this case, UL subband #2 506 occupies a higher frequency portion of the system bandwidth compared to DL subband #1 504.

[0064] Intra-cell cross-link interference

[0065] In addition to inter-cell CLI, FD-TDD will also suffer intra-cell CLI at gNB and UE. Figure 8 An example is shown where gNB 610 has FD-TDD capability and simultaneously receives UL transmission 631 from UE1 621 and sends DL transmission 642 to UE2 622. At gNB 610, the intra-cell CLI is caused by self-interference 641 generated by the downlink transmission 642 performed by the gNB's transmitter on its own receiver, which is attempting to decode the UL signal 631. At UE2 622, the intra-cell CLI 632 is caused by an interfering UE (e.g., UE1 621) transmitting in UL 631, while the victim UE (e.g., UE2 622) is receiving the DL signal 642.

[0066] Self-interference can cause significant intra-cell interference (CLI) at the gNB, as in some cases, the DL transmission can exceed the UL reception power by more than 100 dB. Therefore, sophisticated RF hardware and interference cancellation measures are required to isolate this self-interference.

[0067] Subband Interference

[0068] However, SBFD can suffer from inter-subband interference caused by transmission leakage and receiver selectivity. Although transmissions are typically scheduled within a specific frequency subband (i.e., a specific set of RBs), transmission power can still leak into other subbands. This occurs because the subband filters are not ideal, and the filter roll-off causes power leakage into subbands adjacent to the intended specific frequency subband.

[0069] Figure 9An example is shown where an interferer transmits a signal in an adjacent subband 1010 at a frequency lower than that of the victim's receiving subband 1020. Due to the roll-off of the transmission filter and the nonlinear effects of the transmitter components, some transmitted power leaks into the victim's receiving subband 1020. Similarly, the receiver's filter is not ideal and receives unwanted power from subband 1010. Therefore, the receiver suffers interference 1050.

[0070] Subband interference

[0071] When the subband configurations between gNBs are inconsistent (misaligned) in the frequency domain, intra-subband interference (CLI) may occur. In this case, CLI will occur at the overlapping frequencies of the subbands between the two subbands. Figure 10 An example is shown where the system bandwidth of gNB1 1111 is divided into a UL subband UL-SB#1 1152 occupying f0 to f2 and a DL subband DL-SB#1 1115 occupying f2 to f3, while the system bandwidth of gNB2 1112 is divided into a UL subband UL-SB#2 1154 occupying f0 to f1 and a DL subband DL-SB#2 1153 occupying f1 to f3. This inconsistent subband configuration 1150 causes UL-SB#1 1152 and DL-SB#2 1153 to overlap, resulting in intra-subband CLIs at the overlapping frequencies f1 to f2. In this example, because the DL transmission 1132 performed by gNB2 1112 within the range f1 to f2 of DL-SB#2 1153 interferes with the UL reception 1131 performed by gNB1 1111 from UE1 1121 within the range f1 to f2 of UL-SB#1 1152, an in-subband CLI 1141 occurs at gNB1 1111. Furthermore, because the UL transmission 1131 performed by UE1 1121 within the range f1 to f2 of UL-SB#1 1152 interferes with the DL reception 1132 performed by UE2 1122 within the range f1 to f2 of DL-SB#2 1153, an in-subband CLI 1142 occurs at UE2 1122.

[0072] One of the enhancements proposed for the Release-18 duplex evolution is the introduction of CLI measurements and the reporting of these measurements at Layer 1 and Layer 2. That is, instead of performing CLI measurements and reporting at Layer 3 (which is usually slow), these CLI measurements and reports are performed at Layer 1 and / or Layer 2, which is faster, especially at Layer 1, and is more advantageous for dynamically changing CLI environments. There is a consensus to consider using the traditional CSI framework for new Layer 1 CLI measurement reporting. That is, similar to CSI reporting, new Layer 1 CLI measurements can be reported in a periodic, semi-persistent, or aperiodic (triggered by DCI) manner [6]. In addition to periodic, semi-persistent, and aperiodic CLI reporting, the introduction of event-triggered CLI reporting has also been proposed. In [7], event triggering was proposed, in which if the UE has K consecutive NACKs and the CLI is higher than a threshold, the UE sends a CLI report.

[0073] In traditional systems, CSI measurements are performed on CSI resources (typically CSI-RS), and the gNB can be configured with multiple CSI resources, with the UE reporting CSI data for each resource. For example, in... Figure 11 In this configuration, the UE is equipped with two CSI-RS resources, labeled CSI-RS#1 and CSI-RS#2 respectively. Here, the UE needs to send a CSI report based on CSI Report#1's CSI-RS#1 in the PUCCH of time slot n+4, and send another CSI report based on CSI Report#2's CSI-RS#2 in another PUCCH of time slot n+9, as indicated by arrows 1101 and 1102.

[0074] In traditional systems, non-periodic CSI reports can be triggered by UL grants.

[0075] Link adaptation is a technique in which modulation and error correction coding for downlink data transmission in mobile communication networks are adjusted according to current radio channel conditions, including radio link quality and co-channel interference. If the radio link quality is good and interference is low, the modulation scheme can be set to a higher order, with a higher number of bits per symbol, thus enabling the transmission of a larger amount of data within available communication resources. Similarly, the error correction coding scheme can be set to a high code rate, containing less redundancy in the transmitted data, thereby reusing available capacity to transmit downlink data. Conversely, under conditions of high interference or poor radio conditions, the link adaptation process reduces the order of the modulation scheme to a smaller number of bits per symbol and lowers the coding rate to enhance error protection of the transmitted data, resulting in a smaller amount of data that can be transmitted within available communication resources.

[0076] An exemplary embodiment provides a method for operating a communication device with a wireless communication network. The method includes receiving downlink data transmitted via a radio access interface provided by the wireless communication network. The downlink data is transmitted in a downlink channel forming part of the radio access interface. The method also includes generating a metric indicating the integrity of the downlink data received via the downlink channel. The downlink channel carrying the downlink data may be referred to as a target channel. The method further includes generating a metric from measurement resources indicating cross-link interference (CLI) present simultaneously with the downlink data received via the target downlink channel, the CLI being measured from the measurement resources for the target downlink channel, and determining whether to trigger a reporting event to report the metric indicating cross-link interference and / or the integrity of the downlink data based on the metric indicating cross-link interference and / or the integrity of the downlink data. According to the exemplary embodiment, the UE makes a decision to send a cross-link interference metric indication based on the integrity of the downlink data, such as bit error rate, or the number of consecutive similar HARQ-ACKs and / or the measured CLI. Therefore, the UE determines whether to send a cross-link interference report based on the measurement or estimation of the integrity of the downlink data and / or the CLI. Therefore, the UE does not always send a metric indicating cross-link interference, but rather determines whether to send a report based on an assessment of the integrity of the target downlink channel. Thus, the UE can send a report indicating a metric of cross-link interference in the uplink channel. The uplink channel can be associated with measurements of generated cross-link interference and / or the target downlink channel. CLI and / or data integrity reports can be transmitted via Layer 1 (L1) messages / signaling.

[0077] According to an exemplary implementation, Layer 1 CLI reports are based on the decoding of the target channel. In other words, the event triggering of the CLI report is based on the decoding of the target channel. Therefore, the CLI report is associated with the target channel.

[0078] Unlike existing techniques [7] that only report CLI when decoding performance is poor, this technique can report CLI even when decoding performance is good, although the UE is operating in a CLI scenario. This is advantageous for gNB link adaptation because gNB scheduling under CLI does not need to be overly conservative if the UE is robust enough to decode the channel or if the UE experiences a sudden change in CLI. gNB performs link adaptation when CLI weakens and the NACK rate decreases accordingly. This technique also recognizes that the UE is affected by CLI in addition to errors caused by radio propagation channel conditions (NACK), and therefore gNB needs to take this additional factor into account when selecting a suitable MCS for the UE in link adaptation. gNB can also use CLI reporting to determine whether to implement some CLI mitigation measures, such as power-up downlink transmission or coordination with other gNBs to manage their respective resources. It should be noted that gNB can of course use other CLI mitigation techniques.

[0079] In the prior art [7], it is proposed that if the UE sends a CLI report if it responds with NACK to PDSCH K times consecutively and the CLI is high. This only provides the CLI level to the gNB in ​​the case of decoding failure, which may lead to overly conservative link adaptation. In contrast, the implementation can provide CLI measurement to the gNB in ​​a variety of situations: when decoding performance is poor, when CLI exists (especially when CLI is high) but decoding still performs well, and during the transition from high CLI operation to low CLI operation. This will avoid the gNB scheduling an overly conservative MCS for the UE, thus enabling the gNB to utilize resources more efficiently.

[0080] PDSCH

[0081] In some implementations, the target channel is the PDSCH. In other words, CLI transmission is based on the decoding of data transmitted and received in the PDSCH.

[0082] In some implementations, a CLI report is triggered when the UE sends a HARQ-ACK feedback in a PUCCH or PUSCH. In other words, a CLI report is associated with one or more PDSCHs. For example, after decoding one or more PDSCHs, the UE may send a PUCCH to indicate that the one or more PDSCHs have been successfully decoded (i.e., ACK) or have not been successfully decoded (i.e., NACK). In such cases, the UE may send a CLI report along with the HARQ-ACK feedback. For example, a CLI report may be appended to the HARQ-ACK feedback. It should be understood that a PUCCH may carry HARQ-ACKs for multiple PDSCHs. A CLI report may report the average CLI (i.e., a single CLI value) of the CLI measurement resources associated with a PDSCH or the CLI measurement for each of the one or more PDSCHs (i.e., multiple CLI values ​​in the report).

[0083] In some implementations, CLI reports in a multi-level HARQ-ACK format used for PDSCH. For example, a 4-level HARQ-ACK can be reported using 2 bits, as follows:

[0084] NACK under severe CLI

[0085] NACK under mild CLI

[0086] · ACK under mild CLI

[0087] ·ACK under heavy CLI

[0088] The UE can measure CLI simultaneously with PDSCH decoding, or measure CLI based on predefined CLI resources (e.g., the CSI-RS or DMRS of the PDSCH described in the section titled "CLI Measurement Resources" below). The UE then reports a multi-level HARQ-ACK to indicate to the gNB the impact of CLI on PDSCH decoding. For example, if the UE sends an ACK under heavy CLI, the gNB can schedule more optimistically and schedule the UE with a higher MCS. If the UE still sends a NACK under heavy CLI, the gNB can begin to be more conservative in scheduling, for example, using a lower MCS compared to a NACK under light CLI. While an exemplary implementation has been discussed above with reference to four HARQ-ACK levels, it should be understood that the number of HARQ-ACK levels can be less than or greater than four.

[0089] Heavy CLI is defined as a CLI value exceeding a specific threshold, while mild CLI is defined as a CLI value not exceeding a specific threshold. This specific threshold is predefined by the specification or configured via higher-level signaling.

[0090] In some implementations, CLI reports in units of RSRP, RSRQ, SINR, or RSSI.

[0091] In some implementations, CLI is reported based on quantization levels, similar to a Channel Quality Indicator (CQI). For example, CLI can be reported using 5 bits, which represent 32 CLI levels {0, ..., 31}, where 0 indicates no CLI detected and 31 indicates extremely high CLI.

[0092] In some implementations, during decoding N ReTx A CLI report is triggered after the next PDSCH retransmission. In such an implementation, the UE can report the CLI for both the initial PDSCH decoding and the retransmission PDSCH decoding. Since the initial PDSCH and subsequent retransmissions may experience different levels of CLI, it is beneficial for the gNB to know the CLI level the UE is experiencing. In some implementations, N ReTx It can be indicated in the Radio Resource Control (RRC) signal, dynamically indicated in the DL license, or predefined in the specification, for example, N. ReTx =1.

[0093] In some implementations, CLI reporting is triggered by DL authorization. Using DL authorization to trigger CLI reporting is particularly advantageous because CLI measurements can be based on a target PDSCH. For example, after receiving DL authorization, the UE can prepare to measure the CLI on the target PDSCH that will be received later. In these implementations, DL authorization may include an indication of a PUCCH or PUSCH resource for reporting the CLI. It should be understood that the CLI can be transmitted via a PUCCH or PUSCH indicated by a DCI other than the DL authorization.

[0094] In some implementations, CLI reporting is triggered by the activation DCI of the SPS (Semi-persistent Scheduling Resource). In such implementations, the target channel is the PDSCH of the SPS. In these implementations, the activation DCI may indicate the semi-persistent PUCCH resource used for CLI reporting.

[0095] In some implementations, a CLI report is triggered if multiple ACKs associated with a mild CLI occur after a period of severe CLI. ACKs associated with mild CLI indicate that CLI conditions have become more favorable after a period of unfavorable CLI. This allows the gNB to adjust the link to account for CLI improvements, for example, by increasing the scheduled MCS. Alternatively, the gNB can switch between two link adaptive control procedures: a mild CLI control procedure and a severe CLI control procedure.

[0096] In some implementations, if multiple ACKs associated with mild CLI occur after a period of decoding multiple NACKs, CLI is reported. After a period of unfavorable CLI caused by multiple NACKs, an ACK associated with mild CLI will indicate more favorable CLI conditions. This allows the gNB to adjust the link to account for CLI improvements, for example, by increasing the scheduled MCS. Alternatively, the gNB can switch between two link adaptive control procedures: a mild CLI control procedure and a severe CLI control procedure.

[0097] Therefore, metrics indicating the integrity of the target downlink channel can be based on a variety of measurements, including the number of retransmissions and the number of received ACKs or NACKs, as described above. Metrics indicating downlink channel integrity can also, or alternatively, be derived from parameters in the error correction decoding function of the UE receiver. Example parameters in the error correction decoding function include statistics on the LLR (log-likelihood ratio) within the decoder, estimates of the intermediate bit error rate within the decoder, and the number of decoding iterations required to correctly decode a transport block.

[0098] In some implementations, there may be multiple potential triggers for CLI reporting, and the gNB may configure the UE to apply which trigger. For example, the gNB may configure the UE to report CLI based on either of the following: (1) a period of heavy CLI followed by a mild CLI; or (2) a period of time followed by multiple NACKs after decoding.

[0099] Alternatively or additionally, the gNB may be configured with multiple triggers, and the UE (e.g., in the form of an ID) indicates the event that triggers the CLI report.

[0100] PDCCH

[0101] In some implementations, the target channel is the PDCCH. In other words, CLI transmission is based on the decoding of the detected PDCCH.

[0102] In some implementations, CLI reports are triggered based on the PDCCH aggregation level (AL). In other implementations, the UE sends a CLI report if the AL is above a threshold. This implementation is particularly advantageous when a high AL indicates poor channel conditions (in which case the gNB needs to carefully manage CLI). In some implementations, the UE sends a CLI report if the AL is below a threshold. This implementation is particularly advantageous because PDCCHs transmitted at low ALs are less robust and therefore more susceptible to CLI: in this case, CLI conditions should be reported to improve PDCCH robustness. The threshold can be configured by RRC or predefined in the specification.

[0103] In some implementations, CLI reports are triggered based on the Radio Network Temporary Identifier (RNTI) used by the PDCCH. For example, if the PDCCH uses C-RNTI or CS-RNTI, the UE sends a CLI report; otherwise, the UE does not send any CLI report. Such implementations recognize that some PDCCHs (e.g., PDCCHs using C-RNTI) are associated with channels that apply link adaptation, while channels associated with PDCCHs using other RNTIs may not apply link adaptation.

[0104] CLI Measurement Resources

[0105] Similar to CSI measurement resources, gNB can configure CLI measurement resources for UE, and UE can send CLI reports based on one or more CLI measurement resources.

[0106] In some implementations, CLI measurement resources are configured sets of CSI-RS or reference signals (RS). The gNB can configure CSI-RS / RS sets and require the UE to measure CLI on these resources. CSI-RS can be zero-power (ZP-CSI) resources or non-zero-power CSI (NZP-CSI) resources. ZP-CSI does not contain any signals from the serving gNB and can be used to measure CLI from other cells.

[0107] In some implementations, the CLI measurement resource is the DMRS of the target channel. That is, the measurement is based on the CLI experienced on the DMRS of the channel. For example, if the channel is a PDSCH, then the CLI is based on the DMRS of the PDSCH.

[0108] In some implementations, CLI measurement resources are CSI-RS located near the target channel. That is, the CLI measurement resources are within a predefined time window of the target channel. For example, in... Figure 12 In this context, the target channel is the PDSCH in time slot n, and the CSI-RS near the PDSCH is CSI-RS#1 in time slot n.

[0109] In some implementations, CLI measurements are CSI-RS that are in the same time slot as the target channel. For example, if the channel is PDSCH, then the CSI-RS in the same time slot as PDSCH are the measurement resources reported by CLI.

[0110] In some implementations, CLI measurements are CSI-RS that overlap with the target channel in time. For example, if the channel is PDSCH, then the CSI-RS in the same OFDM symbol as PDSCH is used as the CLI measurement resource. Figure 12For example, in the example above, the target channel is the PDSCH within time slot n. The CLI measurement resource is CSI-RS#1 in the 5th OFDM symbol of time slot n, because it overlaps with the PDSCH. CSI-RS#1 in the 9th OFDM symbol is not used for CLI reporting.

[0111] In some implementations, CLI resources are the portion of the CSI-RS that is frequency-proximity to the target channel. For example, CLI resources could be N at the edge of the target channel. CLI_PRB CSI-RS resources within.

[0112] In some implementations, the CLI measurement resource is the SRS of the interfering UE. In this implementation, the SRS is transmitted near the target channel (e.g., in the same time slot as the target channel).

[0113] Exemplary Operation

[0114] Based on the above explanation, Figure 13 The flowchart shown illustrates an exemplary implementation of the operation of the gNB and UE according to this technology. Figure 13 The operations of the presented UE and gNB can be summarized as follows:

[0115] S1: In the first step, the gNB sends the configuration of cross-link interference (CLI) measurement resources (such as CSI-RS) so that the UE can measure cross-link interference.

[0116] S2: Then, the gNB can send the conditions for triggering a reporting event to the UE. The reporting event can be one or both of reporting the integrity of downlink data received by the communication device and indicating a CLI metric.

[0117] S3: The gNB then transmits downlink data or control signaling / information (also known as downlink data) to the UE through the radio access interface provided by the wireless communication network. Downlink data is transmitted in a downlink channel (e.g., PDSCH) that forms part of the radio access interface, or downlink control information or signaling can be transmitted via, for example, PDCCH, which may be subject to CLI.

[0118] S4: The UE receives downlink data transmitted in the downlink channel. According to some examples, the downlink data is transmitted according to the HARQ-ACK procedure. Therefore, the UE generates either an ACK or a NACK, depending on whether each transport block or code block carrying the downlink data is correctly received.

[0119] S5: The UE generates a metric indicating the integrity of downlink data received via the downlink channel. This can be based on the number of ACKs or NACKs generated in the HARQ-ACK report, or on a metric generated as part of the error correction decoding scheme. As will be understood, ACK indicates successful PDSCH decoding, while NACK indicates PDSCH decoding failure. The UE uses measurement resources transmitted by the gNB to generate a metric indicating the cross-link interference (CLI) present simultaneously with the received downlink data. This metric can be generated from measurement resources used to measure the CLI of the downlink channel as the measurement target.

[0120] S6: Then, based on the conditions received in S2, the UE determines whether the conditions for triggering a measurement report are met, based on one or more of the metrics indicating cross-link interference and the metrics indicating the integrity of the received downlink data.

[0121] S7: If the conditions for triggering a reporting event are met, the UE sends a CLI report, which includes one or both of the integrity of the received downlink data and CLI measurements. This report can be sent via the associated uplink channel (e.g., PUCCH). At this time, the UE may also send an ACK or NACK for each transport block to the gNB (this ACK / NACK forms part of the same report), or if the reporting event is not triggered in step S6, the UE may send only an ACK or NACK without a CLI report.

[0122] S8: The gNB then evaluates the received report to determine whether an action should be taken to reduce CLI and improve downlink data integrity upon reception, or both, and may send control information as part of that action. An example aimed at improving downlink data integrity is performing link adaptation on the downlink channel by adjusting the modulation and coding scheme (MCS). Examples aimed at mitigating CLI include controlling the transmission of interfering UEs and / or using different DL beams or frequency / time resources.

[0123] S9: In one example, where the gNB sends control information to improve the integrity of downlink data, as part of the link adaptation technique, the gNB sends a new MCS value via a downlink control information message (DCI).

[0124] The following numbered paragraphs provide further exemplary aspects and features of this technology:

[0125] Paragraph 1. A method of operating a communication device with a wireless communication network, the method comprising:

[0126] Receive downlink data transmitted via a wireless access interface provided by a wireless communication network, the downlink data being transmitted in a downlink channel forming part of the wireless access interface.

[0127] Generate a metric indicating the integrity of downlink data received through the downlink channel, which serves as the target channel.

[0128] Generate a metric indicating the cross-link interference (CLI) that coexists with downlink data received via the downlink channel. This metric is generated based on the measurement resources used to measure the CLI.

[0129] Based on one or more of the metrics indicating CLI and the metrics indicating downlink data integrity, determine whether to trigger a reporting event to report one or more of the metrics indicating cross-link interference and / or the metrics indicating downlink data integrity.

[0130] Paragraph 2. According to the method described in paragraph 1, including

[0131] Based on the triggering of the determined reporting event, a report is sent in the uplink channel of one or more of the metrics indicating CLI and the metrics indicating the integrity of the received downlink data.

[0132] Paragraph 3. The method described in paragraph 1 or 2, wherein the uplink channel is associated with a measurement of the generated cross-link interference.

[0133] Paragraph 4. The method according to paragraphs 1, 2, or 3, wherein, in accordance with a Hybrid Automatic Repeat Request (HARQ) scheme, downlink data is transmitted as one or more transport blocks, in which, for each transport block, an ACK or NACK is generated to report to the wireless communication network; if it is determined that the transport block carrying the downlink data has been correctly received, an ACK is generated; if it has not been correctly received, a NACK is generated; and a metric indicating the integrity of the received downlink data is determined based on the number of ACKs or NACKs generated for the received downlink data.

[0134] Paragraph 5. The method according to any one of paragraphs 1 to 3, wherein downlink data is encoded using error correction codes, and the measure indicating the integrity of the received downlink data is determined based on parameters derived when decoding the error correction codes.

[0135] Paragraph 6. The method according to any one of paragraphs 1 to 5, wherein triggering the reporting event includes:

[0136] Based on a combination of the determined metric indicating cross-link interference and the determined metric indicating downlink data integrity, it is determined whether to trigger a reporting event.

[0137] Paragraph 7. The method according to any one of paragraphs 1 to 6 includes generating a report for the reported event, the report indicating a determined measure of cross-link interference and a determined measure of downlink data integrity.

[0138] Paragraph 8. According to the method described in paragraph 7, the event for generating a report includes...

[0139] A value is generated, which represents one of several levels, whereby the level represents a combination of a determined metric indicating downlink data integrity and a determined metric indicating cross-link interference.

[0140] Paragraph 9. According to the method described in paragraph 8, the event for generating a report includes

[0141] Generate a report value to indicate one of the following conditions: NACK under severe cross-link interference, NACK under mild cross-link interference, ACK under mild cross-link interference, and ACK under severe cross-link interference.

[0142] Paragraph 10. The method according to any one of paragraphs 1 to 9, wherein the target downlink channel is the Physical Downlink Shared Channel (PDSCH).

[0143] Paragraph 11. The method according to any one of paragraphs 1 to 9, wherein the target downlink channel is one or more PDSCH channels, and a metric indicating cross-link interference is generated based on a reference symbol transmitted in association with one or more PDSCH channels.

[0144] Paragraph 12. The method according to any one of paragraphs 4 to 11, wherein determining whether to trigger a reporting event to report one or more of a metric indicating cross-link interference and a metric indicating the integrity of downlink data comprises:

[0145] Determine the number of NACKs generated based on multiple transport blocks of downlink data within a predetermined time period, and

[0146] If the number of NACKs exceeds the predetermined number Nretx, a report event is triggered.

[0147] Paragraph 13. The method according to any one of paragraphs 4 to 11, wherein determining whether to trigger a reporting event to report one or more of a metric indicating cross-link interference and a metric indicating the integrity of downlink data comprises:

[0148] Determine the first level of CLI within the first time period, and

[0149] Following the first time period, the CLI is determined to be at the second level in the second time period. During the second time period, multiple ACKs are generated based on multiple transport blocks of downlink data.

[0150] If the CLI's first level is greater than the CLI's second level, a report event is triggered.

[0151] Paragraph 14. The method according to any one of paragraphs 4 to 11, wherein determining whether to trigger a reporting event to report one or more of a metric indicating cross-link interference and a metric indicating the integrity of downlink data comprises:

[0152] It was determined that multiple NACKs had been generated based on multiple transport blocks of downlink data during the first time period, and

[0153] It was determined that multiple ACKs were generated based on multiple transport blocks of downlink data during the second time period, and

[0154] If the CLI in the second time period is lower than the CLI in the first time period, a report event is triggered.

[0155] Paragraph 15. The method according to any one of paragraphs 1 to 14, wherein the target downlink channel is the physical downlink control channel (PDCCH).

[0156] Paragraph 16. According to the method described in paragraph 15, determining whether a reporting event is triggered includes:

[0157] Determine the polymerization grade AL of PDCCH, and

[0158] Based on AL, a report event is triggered.

[0159] Paragraph 17. According to the method described in paragraph 16, the triggering of the reporting event includes:

[0160] Compare AL with a predetermined threshold, and

[0161] If AL is higher than a predetermined threshold, a report event is triggered.

[0162] Paragraph 18. According to the method described in paragraph 16, the triggering of the reporting event includes:

[0163] Compare AL with a predetermined threshold, and

[0164] If AL falls below a predetermined threshold, a report event is triggered.

[0165] Paragraph 19. According to the method described in paragraph 15, determining whether a reporting event is triggered includes:

[0166] The reporting event is triggered based on the temporary identifier of the wireless network used by the PDCCH.

[0167] Paragraph 20. The method according to any one of paragraphs 1 to 19, comprising:

[0168] The system receives a configuration of measurement resources from a wireless communication network, which includes cross-link interference (CLI) measurement resources. Based on the CLI measurement resources, it generates a metric indicating cross-link interference, and the generated metric, indicating the presence of cross-link interference (CLI) simultaneously with downlink data, includes:

[0169] Generate a metric for cross-link interference that indicates the presence of downlink data, based on one or more CLI measurement resources.

[0170] Paragraph 21. According to the method described in paragraph 20, wherein the CLI measurement resources include a set of one or more Channel State Information Reference Symbols (CSI-RS) or a set of one or more Reference Symbols (RS).

[0171] Paragraph 22. According to the method described in paragraph 21, wherein the configuration of receiving measurement resources from the wireless communication network includes a receiving configuration indicating which set of CSI-RS sets or RS sets should be used to generate the metric indicating cross-link interference.

[0172] Paragraph 23. The method according to paragraph 21 or 22, wherein one or more of the CSI-RS are zero-power channel state information reference symbols.

[0173] Paragraph 24. The method according to paragraph 21 or 22, wherein one or more of the CSI-RS are non-zero power channel state information reference symbols.

[0174] Paragraph 25. The method according to paragraph 21 or 22, wherein one or more CSI-RS are channel state information reference symbols within a predefined time window of the target downlink channel.

[0175] Paragraph 26. According to the method described in paragraph 25, one or more CSI-RS are channel state information reference symbols in the radio access interface that are in the same time slot as the target downlink channel.

[0176] Paragraph 27. According to the method described in paragraph 25, wherein the CSI-RS is a channel state information reference symbol that overlaps with the target downlink channel in time, forming part of the same orthogonal frequency division multiplexing (OFDM) symbol of the radio access interface.

[0177] Paragraph 28. According to the method described in paragraph 20, wherein the CLI measurement resources include demodulation reference symbols of the target downlink channel.

[0178] Paragraph 29. The method according to paragraph 21 or 22, wherein the CSI-RS is within a predefined frequency range of the target downlink channel.

[0179] Paragraph 30. The method according to paragraph 20, wherein the CLI measurement resources include synchronization reference symbols SRS transmitted by the interfering communication device that generates cross-link interference.

[0180] Paragraph 31. The method according to any one of paragraphs 1 to 30 includes receiving a condition for triggering a reporting event, and determining whether a reporting event is triggered includes determining whether the received condition has been met to trigger a reporting event.

[0181] Paragraph 32. A method of operating infrastructure equipment, the infrastructure equipment forming part of a wireless communication network, the method comprising:

[0182] The configuration of the CLI measurement resources for cross-link interference is transmitted, and the receiving communication device can generate a metric indicating cross-link interference based on this configuration.

[0183] Downlink data is transmitted via a radio access interface provided by a wireless communication network to a receiving communication device within the serving cell formed by infrastructure equipment. The downlink data is transmitted in a target downlink channel that forms part of the radio access interface, and the target downlink channel may be affected by CLI.

[0184] The reception report includes one or both of a metric indicating the integrity of downlink data received by the communication device through the target downlink channel and a metric indicating CLI determined by the receiving communication device.

[0185] Control information is transmitted via a wireless communication network. This control information is used to reduce CLI and improve the integrity of downlink data received by the communication device, or both.

[0186] Paragraph 33. According to the method described in paragraph 32, sending the control information includes:

[0187] In response to the received report, downlink control information is sent, which instructs the receiving communication device to adapt the modulation or coding scheme of the downlink data in response to one or both of the following two measures: a measure indicating the integrity of the downlink data received by the communication device through the target downlink channel, and a measure indicating the cross-link interference (CLI) determined by the receiving communication in the received measurement report.

[0188] Paragraph 34. According to the method described in paragraph 32 or 33, sending control information includes:

[0189] Send control information to the interfering communication device so that the interfering communication device can adapt the uplink transmission to reduce CLI, or

[0190] Send control information to the receiving communication device to use different receiving beams or frequencies, or

[0191] Reduce CLI by sending control information to another infrastructure device that forms part of the wireless communication network.

[0192] Paragraph 35. The method according to paragraph 32 or 34 includes sending to the receiving communication device a condition for triggering a reporting event, the reporting event reporting one or both of the integrity of downlink data received by the communication device and a metric indicating cross-link interference (CLI).

[0193] Paragraph 36. The method according to any one of paragraphs 32 to 35, wherein transmitting downlink data includes:

[0194] According to the Hybrid Automatic Repeat Request (HARQ) scheme, the downlink data is transmitted in one or more transport blocks. In this HARQ scheme, for each transport block, an ACK or NACK is generated, and the method includes:

[0195] Receive ACK or NACK for each transport block, wherein a metric indicating the integrity of the received downlink data is determined based on the number of ACKs or NACKs generated for the received downlink data.

[0196] Paragraph 37. The method according to any one of paragraphs 32 to 35, wherein transmitting downlink data includes:

[0197] Error correction codes are used to encode downlink data, and the metrics in the received reports that indicate the integrity of the received downlink data include parameters derived by the communication device when decoding the downlink data.

[0198] Paragraph 38. The method according to any one of paragraphs 32 to 37, wherein the report includes a determined metric indicating cross-link interference and a determined metric indicating the integrity of the downlink data.

[0199] Paragraph 39. The method according to paragraph 38, wherein the report includes a value representing one of a plurality of levels, the level representing a combination of a determined metric indicating the integrity of downlink data and a determined metric indicating cross-link interference.

[0200] Paragraph 40. The method according to paragraph 39, wherein the report includes a value representing one of the following: NACK under severe cross-link interference, NACK under mild cross-link interference, ACK under mild cross-link interference, and ACK under severe cross-link interference.

[0201] Paragraph 41. The method according to any one of paragraphs 32 to 40, wherein the target downlink channel is the Physical Downlink Shared Channel (PDSCH).

[0202] Paragraph 42. The method according to any one of paragraphs 32 to 40, wherein the target downlink channel is one or more PDSCH channels, and a metric indicating cross-link interference is generated based on reference symbols transmitted in association with one or more PDSCH channels.

[0203] Paragraph 43. The method according to any one of paragraphs 32 to 40, wherein the target downlink channel is the physical downlink control channel (PDCCH).

[0204] Paragraph 44. According to the method described in paragraph 32, wherein the CLI measurement resources include a set of one or more Channel State Information Reference Symbols (CSI-RS) or a set of one or more Reference Symbols (RS).

[0205] Paragraph 45. According to the method described in paragraph 44, one or more of the CSI-RS are zero-power channel state information reference symbols.

[0206] Paragraph 46. The method according to paragraph 44 or 45, wherein one or more CSI-RS are non-zero power channel state information reference symbols.

[0207] Paragraph 47. The method according to paragraphs 43, 44 or 45, wherein one or more CSI-RS are channel state information reference symbols within a predefined time window of the target downlink channel.

[0208] Paragraph 48. According to the method described in paragraph 47, one or more CSI-RS are channel state information reference symbols in the radio access interface that are in the same time slot as the target downlink channel.

[0209] Paragraph 49. The method according to paragraph 47, wherein the CSI-RS is a channel state information reference symbol that overlaps with the target downlink channel in time, forming part of the same orthogonal frequency division multiplexing (OFDM) symbol of the radio access interface.

[0210] Paragraph 50. The method according to any one of paragraphs 32 to 43, wherein the CLI measurement resources include demodulation reference symbols of the target downlink channel.

[0211] Paragraph 51. The method according to any one of paragraphs 44 to 50, wherein the CSI-RS is within a predefined frequency range of the target downlink channel.

[0212] Paragraph 52. The method according to any one of paragraphs 32 to 43, wherein the CLI measurement resource includes a synchronization reference symbol SRS transmitted by the interfering communication device that generates cross-link interference.

[0213] Paragraph 53. A communication device operating on a wireless communication network, the communication device comprising:

[0214] The transceiver circuit is configured to transmit data via a wireless access interface provided by a wireless communication network, and to receive data transmitted via the wireless access interface.

[0215] The controller circuit is configured to control the transceiver circuit to receive downlink data transmitted via a wireless access interface provided by a wireless communication network, the downlink data being transmitted in a downlink channel forming part of the wireless access interface, and the controller circuit is configured to...

[0216] Generate a metric indicating the integrity of downlink data received through the downlink channel, which serves as the target channel;

[0217] Generate a metric indicating the cross-link interference (CLI) that coexists with downlink data received via the downlink channel. This metric is generated based on the measurement resources used to measure the CLI.

[0218] Based on one or more of the metrics indicating CLI and the metrics indicating downlink data integrity, determine whether to trigger a reporting event to report one or more of the metrics indicating cross-link interference and / or the metrics indicating downlink data integrity.

[0219] Paragraph 54. An infrastructure device forming part of a wireless communication network, said infrastructure device comprising:

[0220] A transceiver circuit is configured to transmit data to one or more communication devices via a wireless access interface provided by a wireless communication network, and to receive data transmitted from one or more communication devices via the wireless access interface.

[0221] The controller circuit is configured to control the transceiver circuit, wherein the controller circuit and the transceiver circuit are configured together.

[0222] The configuration of cross-link interference CLI measurement resources is sent to the communication device, which can then generate a metric indicating cross-link interference based on this configuration when receiving downlink data.

[0223] The conditions for triggering a reporting event are sent to the receiving communication device. The reporting event reports one or both of the following: the integrity of the downlink data received by the communication device and a metric indicating cross-link interference (CLI).

[0224] Downlink data is transmitted via the radio access interface to the receiving communication device within the serving cell formed by infrastructure equipment. The downlink data is transmitted in the target downlink channel, which is part of the radio access interface and may be affected by CLI.

[0225] A reception report, comprising one or both of a metric indicating the integrity of downlink data received by the receiving communication device via the target downlink channel and a metric indicating CLI determined by the receiving communication device, and

[0226] Control information is transmitted via a wireless communication network. This control information is used to reduce CLI when receiving downlink data and to improve the integrity of downlink data received by the communication device, or both.

[0227] Paragraph 55. The infrastructure device according to paragraph 54, wherein the controller circuitry is configured to control the transceiver circuitry to transmit downlink channel information in response to a received report, the downlink channel information informing the receiving communication device to adapt the modulation or coding scheme of the downlink data, wherein the report is received after triggering the transmission of the report based on a metric indicating cross-link interference generated according to CLI measurement resources, the report including one or both of a metric indicating the integrity of the downlink data and a metric indicating the CLI determined by the receiving communication device.

[0228] Paragraph 56. The infrastructure equipment according to paragraph 54 or 55, wherein the controller circuitry is configured to control the transceiver circuitry to send control information to the interfering communication device to adapt the uplink transmission by the interfering communication device to reduce CLI, or to send control information to the receiving communication device to use a different receiving beam or frequency, or to send control information to another infrastructure equipment forming part of the wireless communication network to reduce CLI.

[0229] Paragraph 57. The infrastructure equipment according to paragraph 54 or 55, wherein the controller circuitry is configured to control the transceiver circuitry to send a condition to the receiving communication device for triggering a reporting event, which reports one or both of the integrity of downlink data received by the communication device and a metric indicating cross-link interference (CLI).

[0230] It should be understood that, for clarity, the above description has referenced different functional units, circuit systems, and / or processors in describing the implementation. However, it will be apparent that any suitable allocation of functions among the different functional units, circuit systems, and / or processors can be used without departing from the implementation.

[0231] The described embodiments can be implemented in any suitable form, including hardware, software, firmware, or any combination thereof. The described embodiments can optionally be implemented, at least in part, as computer software operating on one or more data processors and / or digital signal processors. Elements and components of any embodiment can be implemented physically, functionally, and logically in any suitable manner. In practice, functionality can be implemented in a single unit, in multiple units, or as part of other functional units. Therefore, the disclosed embodiments can be implemented in a single unit or can be physically and functionally distributed among different units, circuit systems, and / or processors.

[0232] Although this disclosure has been described in conjunction with some embodiments, it is not intended to limit it to the specific forms set forth herein. Furthermore, while features may appear to be described in conjunction with particular embodiments, those skilled in the art will recognize that the different features of the described embodiments can be combined in any manner suitable for implementing the technology.

[0233] References

[0234] [1] Holma H. ​​and Toskala A, "LTE for UMTS OFDMA and SC-FDMA basedradio access", John Wiley and Sons, 2009.

[0235] [2] TR 38.913, “Study on Scenarios and Requirements for NextGeneration Access Technologies (Release 14)”, 3rd Generation PartnershipProject, v14.3.0, August 2017.

[0236] [3] RP-213591, “New SI: Study on evolution of NR duplex operation,”CMCC, RAN#94e, December 2021.

[0237] [4] RP-220633, “Revised SID: Study on evolution of NR duplexoperation,” CMCC, RAN#95e, March 2022.

[0238] [5] European Patent No. 3545716

[0239] [6] R1-2301978, “Summary #3 of potential enhancement on dynamic / flexible TDD,” Moderator (LG Electronics), RAN1#112.

[0240] [7] R1-2300332, “Potential enhancements on dynamic / flexible TDDoperation,” InterDigital, Inc., RAN1#112。

Claims

1. A method for operating a communication device with a wireless communication network, the method comprising: Receive downlink data transmitted via a wireless access interface provided by a wireless communication network, the downlink data being transmitted in a downlink channel forming part of the wireless access interface. Generate a metric indicating the integrity of the downlink data received via the downlink channel, which serves as the target channel. Generate a metric indicating the simultaneous presence of cross-link interference (CLI) with the downlink data received via the downlink channel, the metric being generated from measurement resources used to measure the CLI. Based on one or more of the metrics indicating the CLI and the metrics indicating the integrity of the downlink data, determine whether to trigger a reporting event to report one or more of the metrics indicating the cross-link interference and the metrics indicating the integrity of the downlink data.

2. The method according to claim 1, comprising: Based on the determined triggering of the reporting event, a report is sent in the uplink channel of one or more of the metrics indicating the CLI and the metrics indicating the integrity of the received downlink data.

3. The method according to claim 1, wherein, The uplink channel is associated with the measurement of the generation of the cross-link interference.

4. The method according to claim 1, wherein, According to the Hybrid Automatic Repeat Request (HARQ) scheme, the downlink data is transmitted as one or more transport blocks or code blocks. In the HARQ scheme, for each transport block, an ACK or NACK is generated to report to the wireless communication network. If it is determined that the transport block carrying the downlink data has been correctly received, an ACK is generated; if it is determined that the transport block carrying the downlink data has not been correctly received, a NACK is generated. And based on the number of ACKs or NACKs generated for the received downlink data, a metric indicating the integrity of the received downlink data is determined.

5. The method according to claim 1, wherein, The downlink data is encoded using error correction codes, and the measure indicating the integrity of the received downlink data is determined based on parameters derived when decoding the error correction codes.

6. The method according to claim 1, wherein, The triggering of the reporting event includes: Whether to trigger the reporting event is determined based on a combination of a defined metric indicating cross-link interference and a defined metric indicating the integrity of the downlink data.

7. The method of claim 1, further comprising generating a report for the reported event, the report indicating a determined metric of the cross-link interference and a determined metric of the integrity of the downlink data.

8. The method according to claim 7, wherein, The events that generate the report include Generate a value, which represents one of a plurality of levels, the level representing a combination of a definite metric indicating the integrity of the downlink data and a definite metric indicating cross-link interference.

9. The method according to claim 8, wherein, The events that generate the report include: The report generates a value indicating one of the following: NACK under severe cross-link interference, NACK under mild cross-link interference, ACK under mild cross-link interference, and ACK under severe cross-link interference.

10. The method according to claim 1, wherein, The target downlink channel is the Physical Downlink Shared Channel (PDSCH).

11. The method according to claim 1, wherein, The target downlink channel is one or more PDSCH channels, and a metric indicating the cross-link interference is generated based on the reference symbols transmitted in association with the one or more PDSCH channels.

12. The method according to claim 4, wherein, Determining whether to trigger a reporting event to report one or more of a metric indicating the cross-link interference and a metric indicating the integrity of the downlink data includes: Determine the number of NACKs generated from multiple transport blocks of the downlink data within a predetermined time period, and If the number of NACKs exceeds a predetermined number Nretx, a report event is triggered.

13. The method according to claim 4, wherein, Determining whether to trigger a reporting event to report one or more of a metric indicating the cross-link interference and a metric indicating the integrity of the downlink data includes: Determine the first level of the CLI during the first time period, and Following the first time period, multiple ACKs are determined to be generated from multiple transport blocks of the downlink data within a second time period of the second level of the CLI, and If the first level of the CLI is greater than the second level of the CLI, a report event is triggered.

14. The method according to claim 4, wherein, Determining whether to trigger a reporting event to report one or more of a metric indicating the cross-link interference and a metric indicating the integrity of the downlink data includes: Determine that multiple NACKs are generated from multiple transport blocks of the downlink data within the first time period, and Determine that multiple ACKs are generated from multiple transport blocks of the downlink data during the second time period, and If the CLI in the second time period is lower than the CLI in the first time period, a report event is triggered.

15. The method according to claim 1, wherein, The target downlink channel is the Physical Downlink Control Channel (PDCCH).

16. The method according to claim 15, wherein, Determining whether a reporting event is triggered includes: Determine the polymerization level AL of the PDCCH, and Based on the aforementioned AL, a report event is triggered.

17. The method according to claim 16, wherein, Events that trigger reporting include: The AL is compared with a predetermined threshold, and If the AL is higher than the predetermined threshold, a report event is triggered.

18. The method according to claim 16, wherein, Events that trigger reporting include: The AL is compared with a predetermined threshold, and If the AL is lower than the predetermined threshold, a report event is triggered.

19. The method according to claim 15, wherein, Determining whether a reporting event is triggered includes: The reporting event is triggered based on the temporary radio network identifier used by the PDCCH.

20. The method of claim 1, comprising: The configuration of the measurement resources, including cross-link interference (CLI) measurement resources, is received from the wireless communication network. A metric indicating the cross-link interference is generated based on the CLI measurement resources. The metrics for generating a cross-link interference CLI that indicates the presence of the downlink data simultaneously include: Generate a metric indicating the cross-link interference that coexists with the downlink data based on one or more of the CLI measurement resources.

21. The method according to claim 20, wherein, The CLI measurement resources include a set of one or more Channel State Information Reference Symbols (CSI-RS) or a set of one or more Reference Symbols (RS).

22. The method according to claim 21, wherein, The configuration for receiving the measurement resources from the wireless communication network includes a configuration indicating which set of CSI-RS sets or RS sets should be used to generate the metric indicating the cross-link interference.

23. The method according to claim 21, wherein, One or more of the CSI-RS are zero-power channel state information reference symbols.

24. The method according to claim 21, wherein, One or more of the CSI-RS are non-zero power channel state information reference symbols.

25. The method according to claim 21 or 22, wherein, The one or more CSI-RS are channel state information reference symbols within a predefined time window of the target downlink channel.

26. The method of claim 25, wherein, The one or more CSI-RS are channel state information reference symbols in the radio access interface that are in the same time slot as the target downlink channel.

27. The method according to claim 25, wherein, The CSI-RS is a channel state information reference symbol, which overlaps with the target downlink channel in time, forming part of the same orthogonal frequency division multiplexing (OFDM) symbol of the radio access interface.

28. The method according to claim 20, wherein, The CLI measurement resources include the demodulation reference symbols of the target downlink channel.

29. The method according to claim 21, wherein, The CSI-RS is located within a predefined frequency range of the target downlink channel.

30. The method of claim 20, wherein, The CLI measurement resources include the Synchronization Reference Symbol (SRS) sent by the interfering communication device that generated the cross-link interference.

31. The method of claim 1, further comprising receiving a condition for triggering a reporting event, and determining whether to trigger the reporting event comprising determining whether the received condition has been satisfied to trigger a reporting event.

32. A method of operating infrastructure equipment, said infrastructure equipment forming part of a wireless communication network, the method comprising: The configuration of the CLI measurement resources for cross-link interference is transmitted, and the receiving communication device can generate a metric indicating cross-link interference based on the configuration. Downlink data is transmitted via a wireless access interface provided by the wireless communication network to a receiving communication device within a serving cell formed by the infrastructure equipment. The downlink data is transmitted in a target downlink channel that forms part of the wireless access interface, and this target downlink channel may be affected by the CLI. A reception report, the report including one or both of a metric indicating the integrity of the downlink data received by the communication device through the target downlink channel and a metric indicating the CLI determined by the receiving communication device, and Control information is transmitted through the wireless communication network, the control information being used to reduce the CLI when receiving downlink data and to improve the integrity of the downlink data received by the communication device, or both.

33. The method according to claim 32, wherein, Sending the control information includes: In response to the received report, downlink control information is sent, which instructs the receiving communication device to adjust the modulation or coding of the downlink data in response to one or both of the following two metrics: a metric indicating the integrity of the downlink data received by the communication device through the target downlink channel and a metric indicating cross-link interference (CLI) determined by the receiving communication in the received measurement report.

34. The method according to claim 32, wherein, Sending the control information includes: Send control information to the interfering communication device to adjust the uplink transmission performed by the interfering communication device to reduce the CLI, or Send control information to the receiving communication device to use different receiving beams or frequencies, or Sending control information to another infrastructure device that forms part of the wireless communication network to reduce the CLI.

35. The method of claim 32, further comprising sending to the receiving communication device a condition for triggering a reporting event, the reporting event reporting one or both of the integrity of downlink data received by the communication device and a metric indicating cross-link interference (CLI).

36. The method according to claim 32, wherein, Sending the downlink data includes: According to the Hybrid Automatic Repeat Request (HARQ) scheme, the downlink data is transmitted as one or more transport blocks. In the HARQ scheme, for each transport block, an ACK or NACK response is generated, and the method includes: Receive ACK or NACK for each transport block, wherein a metric indicating the integrity of the received downlink data is determined based on the number of ACKs or NACKs generated for the received downlink data.

37. The method according to claim 32, wherein, Sending the downlink data includes: The downlink data is encoded using error correction codes, and the received report includes a metric indicating the integrity of the received downlink data, comprising parameters derived by the communication device when decoding the downlink data.

38. The method according to claim 32, wherein, The report includes determined metrics indicating the cross-link interference and determined metrics indicating the integrity of the downlink data.

39. The method according to claim 38, wherein, The report includes values ​​representing one of a plurality of levels, which represent a combination of a determined metric indicating the integrity of the downlink data and a determined metric indicating cross-link interference.

40. The method according to claim 39, wherein, The report includes values ​​representing one of the following: NACK under severe cross-link interference, NACK under mild cross-link interference, ACK under mild cross-link interference, and ACK under severe cross-link interference.

41. The method according to claim 32, wherein, The target downlink channel is the Physical Downlink Shared Channel (PDSCH).

42. The method according to claim 32, wherein, The target downlink channel is one or more PDSCH channels, and a metric indicating the cross-link interference is generated based on reference symbols transmitted in association with the one or more PDSCH channels.

43. The method according to claim 32, wherein, The target downlink channel is the Physical Downlink Control Channel (PDCCH).

44. The method according to claim 32, wherein, The CLI measurement resources include a set of one or more Channel State Information Reference Symbols (CSI-RS) or a set of one or more Reference Symbols (RS).

45. The method according to claim 44, wherein, One or more of the CSI-RS are zero-power channel state information reference symbols.

46. ​​The method of claim 44, wherein, One or more of the CSI-RS are non-zero power channel state information reference symbols.

47. The method according to claim 43, wherein, The one or more CSI-RS are channel state information reference symbols within a predefined time window of the target downlink channel.

48. The method according to claim 47, wherein, The one or more CSI-RS are channel state information reference symbols in the radio access interface that are in the same time slot as the target downlink channel.

49. The method according to claim 47, wherein, The CSI-RS is a channel state information reference symbol, which overlaps with the target downlink channel in time. The target downlink channel forms part of the same orthogonal frequency division multiplexing (OFDM) symbol of the radio access interface.

50. The method according to claim 32, wherein, The CLI measurement resources include the demodulation reference symbols of the target downlink channel.

51. The method according to claim 44, wherein, The CSI-RS is located within a predefined frequency range of the target downlink channel.

52. The method according to claim 32, wherein, The CLI measurement resources include the Synchronization Reference Symbol (SRS) sent by the interfering communication device that generated the cross-link interference.

53. A communication device operating via a wireless communication network, the communication device comprising: The transceiver circuit is configured to transmit data via a wireless access interface provided by the wireless communication network, and to receive data transmitted via the wireless access interface. A controller circuit is configured to control the transceiver circuit to receive downlink data transmitted via a wireless access interface provided by the wireless communication network, the downlink data being transmitted in a downlink channel forming part of the wireless access interface, and the controller circuit is configured to... Generate a metric indicating the integrity of the downlink data received via the downlink channel, which is the target channel; Generate a metric indicating the simultaneous presence of cross-link interference (CLI) with the downlink data received via the downlink channel, the metric being generated based on measurement resources used to measure the CLI, and Based on one or more of a metric indicating the CLI and a metric indicating the integrity of the downlink data, determine whether to trigger a reporting event to report one or more of the metric indicating the cross-link interference and the metric indicating the integrity of the downlink data.

54. An infrastructure device forming part of a wireless communication network, said infrastructure device comprising: A transceiver circuit is configured to transmit data to one or more communication devices via a wireless access interface provided by the wireless communication network, and to receive data transmitted from the one or more communication devices via the wireless access interface. A controller circuit is configured to control the transceiver circuit, wherein the controller circuit and the transceiver circuit are configured together for: The configuration of cross-link interference CLI measurement resources is sent to a communication device, which is capable of generating a metric indicating cross-link interference based on the configuration when receiving downlink data. A condition for triggering a reporting event is sent to the receiving communication device, the reporting event reporting one or both of the integrity of the downlink data received by the communication device and a metric indicating cross-link interference (CLI). Downlink data is transmitted via the radio access interface to the receiving communication device within the serving cell formed by the infrastructure equipment. The downlink data is transmitted in a target downlink channel that forms part of the radio access interface, and this target downlink channel may be affected by the CLI. A reception report, the report including one or both of a metric indicating the integrity of the downlink data received by the receiving communication device via the target downlink channel and a metric indicating the CLI determined by the receiving communication device, and Control information is transmitted through the wireless communication network, the control information being used to reduce the CLI when receiving downlink data and to improve the integrity of the downlink data received by the communication device, or both.

55. The infrastructure equipment according to claim 54, wherein, The controller circuit is configured to control the transceiver circuit to transmit downlink channel information in response to a received report, the downlink channel information notifying the receiving communication device to adjust the modulation or coding of the downlink data, wherein the report is received after being triggered based on a metric indicating cross-link interference generated according to the CLI measurement resource, the report including one or both of a metric indicating the integrity of the downlink data and a metric indicating the CLI determined by the receiving communication device.

56. The infrastructure equipment according to claim 54, wherein, The controller circuit is configured to control the transceiver circuit to send control information to the interfering communication device to adjust the uplink transmission by the interfering communication device to reduce the CLI, or to send control information to the receiving communication device to use a different receiving beam or frequency, or to send control information to another infrastructure device forming part of the wireless communication network to reduce the CLI.

57. The infrastructure equipment according to claim 54, wherein, The controller circuit is configured to control the transceiver circuit to send conditions to the receiving communication device for triggering a reporting event, the reporting event reporting one or both of the integrity of downlink data received by the communication device and a metric indicating cross-link interference (CLI).

Images