Techniques for rank-aware interference suppression based on neighboring cell layer notifications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment may send, to a serving network entity, a message requesting a number of transmit layers scheduled to be used by one or more neighboring network entities for communication within a communication resource. In response, the user equipment may receive, from the serving network entity, an indication of the number of transmit layers scheduled by one or more neighboring network entities for communication within the communication resource. A user equipment may apply the number of transmit layers for communication resources to a rank aware interference suppression algorithm, and may use the rank aware interference suppression algorithm to improve noise covariance matrix estimation. An improved noise covariance matrix estimate may be used to mitigate interference at a communication resource when receiving a downlink message from a serving network entity via the communication resource.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 501,829, filed November 3, 2023, entitled “TECHNIQUES FORRANK-AWARE INTERFERENCE REJECTION BASED ON NEIGHBOR CELL LAYER NOTIFICATION”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including techniques for rank-aware interference suppression based on neighboring cell layer notifications. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] In some cases, to avoid interference between downlink transmissions from the same base station, a base station may allocate unique resources to each UE served by the base station. However, in other cases, a base station may allocate resources to its users that are also allocated to users served by another base station within the wireless communication system. In such cases, different base stations may simultaneously use the same resources for downlink communication, potentially leading to downlink signal interference at one or more UEs. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting rank-aware interference suppression based on neighboring cell layer notifications. According to various aspects, the described technology can provide a method for a UE to determine whether an interference level within a communication resource (such as a resource for downlink communication from a serving network entity, e.g., a base station) meets an interference threshold. Based on the determination that the interference level meets the interference threshold, the UE can send a message to the serving network entity requesting notification of the number of transmission layers scheduled for communication within the communication resource by one or more neighboring network entities. The serving network can deliver the request from the UE to a core network entity, and the core network entity can identify one or more network entities (such as those approaching the serving network entity or requesting the UE or a combination thereof) as one or more neighboring network entities that are potential sources of interference to the serving network entity.

[0007] A core network entity may request each of its neighboring network entities to notify the core network entity of the number of transmission layers scheduled for use by that neighboring network entity within the communication resource. One or more neighboring network entities may notify the core network entity of the number of transmission layers scheduled for use by that neighboring network entity within the communication resource. The core network entity may receive one or more responses from one or more identified neighboring network entities and may aggregate (e.g., sum) the indicated number of transmission layers scheduled for use within the communication resource. The core network entity may send an indication to the serving network entity of the aggregated number of transmission layers scheduled for use by one or more identified neighboring network entities within the communication resource, and the serving network entity may send this indication to the UE.

[0008] To mitigate interference from one or more identified neighboring network entities, the UE can apply the aggregated number of transmit layers scheduled for communication within the communication resources by one or more identified neighboring network entities to the rank-aware channel estimation algorithm, and subsequently use the updated rank-aware channel estimation algorithm when receiving downlink messages via the communication resources. Using the updated rank-aware channel estimation algorithm improves the accuracy of the estimated interference and noise covariance matrix associated with the communication resources, thereby enhancing communication reliability within the wireless communication system.

[0009] A method for wireless communication by a user equipment (UE) is described. The method may include: sending a first message to a first network entity serving the UE, including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; receiving from the first network entity an indication of the number of transmission layers for the communication resource; and receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0010] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the UE: sends a first message to a first network entity serving the UE, including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; receives from the first network entity an indication of the number of transmission layers for the communication resource; and receives downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0011] Another UE for wireless communication is described. The UE may include: components for sending a first message to a first network entity serving the UE, including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; components for receiving from the first network entity an indication of the number of transmission layers for the communication resource; and components for receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0012] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send a first message to a first network entity serving the UE, including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; receive from the first network entity an indication of the number of transmission layers for the communication resource; and receive downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0013] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first message may be sent based on an estimate of the noise covariance matrix for the communication resource to satisfy an interference threshold.

[0014] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information from the first network entity, including instructions to perform the noise covariance matrix estimation within the communication resource.

[0015] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first message includes an indication of the granularity associated with the number of transmission layers, and the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0016] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the indication of the number of transmission layers includes the sum of the number of transmission layers associated with the one or more adjacent network entities.

[0017] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the indication of the number of transmission layers for the communication resource may be received via control signaling, and the control signaling may also include scheduling permission to allocate the communication resource to the UE.

[0018] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first message may be transmitted via a first media access control-control element (MAC-CE) or a physical uplink control channel (PUCCH), and the indication of the number of transmission layers for the communication resource may be received via a second media access control-control element (MAC-CE) or a physical downlink control channel (PDCCH).

[0019] A method for wireless communication performed by a first network entity is described. The method may include: receiving from a UE served by the first network entity a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; sending to a second network entity a second message including the request for the number of transmission layers for the communication resource; receiving from the second network entity a third message including an indication of the number of transmission layers for the communication resource; and sending to the UE the indication of the number of transmission layers for the communication resource.

[0020] A first network entity for wireless communication is described. The first network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the first network entity: receives from a UE served by the first network entity a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; sends to a second network entity a second message including the request for the number of transmission layers for the communication resource; receives from the second network entity a third message including an indication of the number of transmission layers for the communication resource; and sends to the UE the indication of the number of transmission layers for the communication resource.

[0021] Another first network entity for wireless communication is described. The first network entity may include: means for receiving from a UE served by the first network entity a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; means for sending to a second network entity a second message including the request for the number of transmission layers for the communication resource; means for receiving from the second network entity a third message including an indication of the number of transmission layers for the communication resource; and means for sending to the UE the indication of the number of transmission layers for the communication resource.

[0022] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor for: receiving from a UE served by a first network entity a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; sending to a second network entity a second message including the request for the number of transmission layers for the communication resource; receiving from the second network entity a third message including an indication of the number of transmission layers for the communication resource; and sending to the UE the indication of the number of transmission layers for the communication resource.

[0023] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first message includes an indication of granularity associated with the number of transmission layers, and the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0024] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, this indication of the number of transmission layers may be based on the indicated granularity.

[0025] The methods described herein, examples of the first network entity, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for sending control information to the UE including an instruction to perform the noise covariance matrix estimation within the communication resource.

[0026] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the indication of the number of transmission layers for the communication resource may be sent to the UE via control signaling, and the control signaling may also include scheduling permission to allocate the communication resource to the UE.

[0027] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first network entity includes a serving gNodeB (gNB) serving the UE, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a set of multiple gNBs, the set of multiple gNBs including the serving gNB and the one or more interference source gNBs.

[0028] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first message includes information indicating the estimated geographic location of the UE.

[0029] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first message may be received via a first media access control-control element (MAC-CE) or PUCCH, and the indication of the number of transmission layers for the communication resource may be sent via a second media access control-control element (MAC-CE) or PDCCH.

[0030] A method for wireless communication by a second network entity is described. The method may include: receiving from a first network entity a message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities; requesting from at least one of the one or more neighboring network entities a number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity; and sending to the first network entity an indication of the number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity.

[0031] A second network entity for wireless communication is described. The second network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the second network entity to: receive from a first network entity a message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities; request from at least one of the one or more neighboring network entities a number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity; and send to the first network entity an indication of the number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity.

[0032] Another second network entity for wireless communication is described. The second network entity may include: components for receiving from a first network entity a message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities; components for requesting from at least one of the one or more neighboring network entities a number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity; and components for sending to the first network entity an indication of the number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity.

[0033] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor for: receiving from a first network entity a message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities; requesting from at least one of the one or more neighboring network entities a number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity; and sending to the first network entity an indication of the number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity.

[0034] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the message includes information indicating the estimated geographic location of the UE served by the first network entity.

[0035] The methods described herein, examples of second network entities, and nontransitory computer-readable media may also include operations, features, components, or instructions for identifying one or more adjacent network entities based on the determination of one or more candidate network entities that have the potential to interfere with the first network entity.

[0036] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the determination of the one or more candidate network entities may be based on the estimated geographic location of the UE requesting the number of transmission layers.

[0037] In some examples of the methods, second network entities, and nontransitory computer-readable media described herein, the first network entity includes a serving gNodeB (gNB) serving a UE requesting the number of transmission layers, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a set of multiple gNBs, the set of multiple gNBs including the serving gNB and the one or more interference source gNBs. Attached Figure Description

[0038] Figure 1 Examples of wireless communication systems supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, are shown.

[0039] Figure 2 An example of a wireless communication system environment supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0040] Figure 3 An example of a wireless communication system environment supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0041] Figure 4 An example of a process flow supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0042] Figure 5 and Figure 6 A block diagram of an apparatus supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0043] Figure 7 A block diagram of a communication manager supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0044] Figure 8 A diagram is shown of a system including an apparatus for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure.

[0045] Figure 9 and Figure 10A block diagram of an apparatus supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0046] Figure 11 A block diagram of a communication manager supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0047] Figure 12 A diagram is shown of a system including an apparatus for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure.

[0048] Figure 13 and Figure 14 A block diagram of an apparatus supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0049] Figure 15 A block diagram of a communication manager supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0050] Figure 16 A diagram is shown of a system including an apparatus for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure.

[0051] Figures 17 to 19 A flowchart illustrating a method for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0052] Various aspects of this disclosure relate to techniques for rank-aware interference suppression based on neighboring cell layer notifications in wireless communication systems. In some wireless communication systems, multiple network entities may each serve one or more UEs. In some cases, to avoid interference during downlink communication from the network entity to the served UEs, the network entity may allocate a unique set of communication resources to each of the UEs served by the network entity. However, while the intra-resource allocation by the network entity may be unique among the served UEs, there may be situations where a network entity allocates communication resources to one or more of the UEs it serves, and these communication resources are also allocated to one or more UEs served by another network entity within the wireless communication system. In some cases, simultaneous use of such shared communication resources by multiple UEs across different network entities may cause interference at one or more UEs during downlink communication.

[0053] According to the various techniques described herein, improved techniques can enable improvements in the accuracy of estimated interference and noise covariance matrix estimation associated with communication resources. For example, based on the UE determining that the interference level within the communication resource meets an interference threshold, the UE can send a message to its serving network entity requesting notification of the number of transmission layers scheduled for communication within the communication resource by one or more adjacent network entities. In response, the serving network entity can identify the number of transmission layers scheduled for communication within the communication resource by one or more adjacent network entities and send that number of transmission layers to the UE. To mitigate interference at the communication resource, the UE can apply the number of transmission layers to a rank-aware channel estimation algorithm, and subsequently use an updated rank-aware channel estimation algorithm to receive downlink messages via the communication resource. Using an updated rank-aware channel estimation algorithm improves the accuracy of estimated interference and noise covariance matrix estimation associated with communication resources.

[0054] The aspects of this disclosure are first described in the context of wireless communication systems. These aspects are further illustrated and described by way of process flow diagrams, apparatus diagrams, system diagrams, and flowcharts relating to techniques for rank-aware interference suppression based on neighboring cell layer notifications.

[0055] Figure 1 Examples of wireless communication systems 100 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, are shown. Wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0056] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0057] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0058] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0059] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0060] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0061] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0062] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0063] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0064] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support techniques for rank-aware interference suppression based on neighboring cell layer notifications, as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0065] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0066] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0067] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0068] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0069] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0071] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0072] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0073] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0074] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and can operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 can support one or more cells and can also use one or more component carriers to support communication via one or more cells.

[0075] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0076] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0077] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0078] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0079] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0080] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0081] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0082] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna port.

[0083] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0084] In some implementations, UE 115 may determine that the interference level within the communication resource meets an interference threshold. In response, UE 115 may send a message to its serving network entity 105-a requesting notification of the number of transmission layers scheduled for communication within the communication resource by one or more neighboring network entities 105-b. UE 115 may receive from serving network entity 105-a an indication of the number of transmission layers scheduled for communication within the communication resource by one or more neighboring network entities 105-b. To mitigate potential interference within the communication resource, UE 115 may apply this number of transmission layers to a rank-aware channel estimation algorithm, and may use an updated rank-aware channel estimation algorithm to receive downlink messages from serving network entity 105-a via the communication resource. Using an updated rank-aware channel estimation algorithm (which considers the number of transmission layers scheduled for communication within the communication resource by potentially interfering neighboring network entities 105-b) improves the accuracy of the estimated interference and noise covariance matrix estimates associated with the communication resource. The improved accuracy associated with interference estimation enables more precise interference mitigation, thereby enhancing performance at UE 115 and overall communication reliability at the wireless communication system.

[0085] Figure 2 An example of a wireless communication system environment 200 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. In the example environment 200, the wireless system may consist of multiple network entities 205 (e.g., Figure 1 The network entity 205 consists of network entities 105. Each network entity 205 (e.g., gNodeB (gNB)) can provide communication coverage via one or more cells. In some cases, a cell may refer to a coverage area, such as coverage area 210 (e.g., Figure 1The coverage area 210), and the corresponding network entity 205 provides communication coverage in the coverage area. Each of the multiple network entities 205 can serve one or more UEs 215 within the corresponding coverage area 210 (e.g., Figure 1 (UE 115). For example, each network entity 205 may serve those UEs 215 closest to network entity 205. For example, network entity 205-a may serve UE 215-a within coverage area 210-a; network entity 205-b may serve UE 215-b within coverage area 210-b; and network entity 205-c may serve UE 215-c within coverage area 210-c. As described herein, the network entity 205 serving a particular UE 215 may be referred to as the serving network entity 205 of that UE 215.

[0086] In some cases, each network entity 205 may allocate a unique set of communication resources to each UE 215 served by the network entity 205. For example, the serving network entity 205 may allocate a unique frequency band and a unique time slot to each UE 215 served by the serving network entity 205. By allocating a unique set of communication resources to each UE 215, interference between downlink communications from the serving network entity 205 can be mitigated or reduced. However, in some cases, one or more network entities in the network entity 205 may allocate communication resources to one or more of their UEs 215, which are also allocated to one or more UEs 215 served by another network entity 205, resulting in the simultaneous use of the same communication resources. In some cases, such as when UEs 215 (or their respective serving network entities 205) sharing such communication resources are not close to each other, the simultaneous use of the same communication resources may not cause interference problems due to the large path loss caused by the distance between such UEs 215 (or their respective serving network entities 205). However, in other situations, such as when UEs 215 (or their respective serving network entities 205) sharing such communication resources are close to each other, the simultaneous use of the same communication resources can impair the downlink detection of the affected UE 215 due to downlink transmissions from network entities 205 that are close to the serving network entity 205. For example, when serving network entity 205-a sends a downlink message to UE 215-a, downlink signals transmitted by one or more other network entities 205 close to serving network entity 205-a using the same communication resources (such as downlink signals transmitted by neighboring network entities 205-b and 205-c) can cause interference and affect the ability of UE 215-a to detect downlink messages sent to UE 215-a by serving network entity 205-a. As described herein, the network entity 205 of the serving network entity 205 of a UE 215 whose downlink detection may be affected by its proximity may be referred to as neighboring network entity 205, or in some cases as potential source of interference network entity 205. For example, in the above example, network entity 205-a may be referred to as the serving network entity 205-a of UE 215-a, and network entities 205-b and 205-c may be referred to as neighboring network entities 205-b and 205-c respectively, or in some cases collectively referred to as neighboring network entity 205-b.

[0087] For example, in some cases, the coverage area 210 supported by network entity 205 (e.g., network architecture) may form a hexagonal structure or shape in one or more directions from network entity 205. In such cases, the coverage of network entity 205 may extend in any such direction to cover the hexagonal coverage area 210. Therefore, in some cases, the coverage areas 210 of one or more network entities 205 may overlap. Thus, each UE 215 served by its serving network entity 205 may also receive downlink signals transmitted by the serving network entity 205 near UE 215 or by one or more other network entities 205 near UE 215.

[0088] For example, UE 215-a, served by network entity 205-a, can also receive downlink signals transmitted by neighboring network entities 205-b and 205-c. In this case, the signal observed at UE 215-a can be expressed as ,in It is the primary downlink signal sent from serving network entity 205-a to UE 215-a, where and This refers to the corresponding channel interference between adjacent network entities 205-b and 205-c and UE 215-a (e.g., downlink signals from adjacent network entities 205-b and 205-c), where and It is the corresponding data sent from each of network entities 205-a, 205-b, and 205-c, and in which This is the receiver thermal noise of UE 215-a.

[0089] In some cases, interference caused by downlink signals from one or more neighboring network entities 205-b and 205-c may be significantly lower than interference at the expected primary downlink signal transmitted from serving network entity 205-a to UE 215-a, such as in conditions When satisfied. Therefore, in this case, the observed signal at UE 215-a can be expressed as .

[0090] However, when conditions When not satisfied, downlink detection at UE 215-a may be interfered with by downlink signals from one or more of neighboring network entities 205-b and 205-c. In some cases, neighboring network entities 205-b and 205-c may limit the achievable signal-to-noise ratio (SNR), thereby limiting the achievable data rate. Based on the aspects described herein, the served UE 215 (such as UE 215-a) can be mitigated by using rank-aware channel estimation algorithms (e.g., rank-aware interference suppression algorithms (regarding...)). Figure 3 (Further described) to mitigate interference from neighboring network entities 205-b and 205-c. For example, this can be achieved by increasing the estimated interference and noise covariance matrix performed by the served UE 215-a based on the rank (e.g., number of transmission layers) of one or more neighboring network entities 205-b and 205-c. The accuracy of the estimation is used to enhance the interference suppression algorithm. This enhanced interference suppression algorithm may be referred to as a rank-aware channel estimation algorithm or a rank-aware interference suppression algorithm. For example, the served UE 215-a can obtain the sum of the ranks of the downlink signals of neighboring network entities 205-b and 205-c (e.g., the sum of the number of transmit layers scheduled to be used by neighboring network entities 205-b and 205-c) for a specific communication resource, and can determine whether the summed rank (e.g., the summed number of transmit layers to be used) meets a threshold. For example, the summed rank meets the threshold when it is less than the total number of receive antennas at UE 215-a. If the summed rank meets the threshold, the served UE 215-a can use the rank-aware channel estimation algorithm to improve the noise covariance matrix estimation performed by UE 215-a.

[0091] Figure 3 An example of a wireless communication system environment 300 supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0092] In example environment 300, the wireless system may be provided by serving network entity 305-a (e.g., Figure 1 Network Entity 105 or Figure 2 The UE 315-a served by network entity 205-a, 205-b or 205-c (e.g., network entity 205-a, 205-b or 205-c) is a network entity that serves network entity 205-a, 205-b or 205-c. Figure 1 UE 115 or Figure 2 It consists of UE215-a, 215-b, or 215-c. The serving network entity 305-a may be close to one or more adjacent network entities 305-b and 305-c (e.g., UE215-a, 215-b, or 215-c). Figure 1 Network Entity 105 or Figure 2Network entities 205-a, 205-b, or 205-c. Serving network entity 305-a and one or more adjacent network entities 305-b and 305-c may interact with core network entity 330 (e.g., Figure 1 The core network 130 communicates with each other.

[0093] To determine whether a rank-aware channel estimation algorithm (e.g., a rank-aware interference suppression algorithm) may be needed to mitigate potential interference in downlink communication from serving network entity 305-a caused by downlink signals from one or more neighboring network entities 305-b and 305-c, UE 315-a may initially determine the interference level (e.g., the power of received interference) associated with one or more neighboring network entities 305-b and 305-c. For example, UE 315-a may determine the interference level for a specific communication resource (such as a time slot used for downlink communication). UE 315-a may determine that if the interference level associated with one or more neighboring network entities 305-b and 305-c meets an interference threshold (e.g., whether high interference is detected), then a rank-aware channel estimation algorithm should be applied to mitigate the interference at the communication resource.

[0094] In some cases, to determine whether the interference level associated with one or more neighboring network entities 305-b and 305-c meets an interference threshold (e.g., whether high interference is detected), UE 315-a can estimate the noise covariance of the communication resources. The noise covariance can be estimated by averaging the noise over the entire bandwidth. Assuming two adjacent network entities, 305-b and 305-c (note that the described process for detecting high interference is not limited to two adjacent network entities, but can have any number of adjacent network entities), the noise covariance can be expressed as: (until the estimation error), where It is diagonal (representing the RF noise matrix), and Let be the noise matrix of adjacent network entities 305-b and 305-c, and let the terms be off-diagonal, such that... The diagonal elements can be expressed as:

[0095]

[0096] and Off-diagonal elements can be expressed as:

[0097]

[0098] in In some specific implementations, regarding An example metric could be a function of the reciprocal of the ratio between the absolute value of the largest off-diagonal element and its corresponding largest diagonal element. The row and column of the largest off-diagonal absolute value could be represented as... And it can be explicitly expressed as: Therefore, the corresponding maximum diagonal element is: (Explicitly:) and (The maximum value between). For example, if:

[0099] The ratio is And the metric is: Furthermore, the reciprocal of this ratio is And based on this ratio, the following metric can be calculated:

[0100] in This is the upper limit of the interference-to-noise ratio. Therefore, when When (e.g., a threshold) is reached, UE 315-a can determine that the interference levels of one or more neighboring network entities 305-b and 305-c meet the interference threshold (e.g., sufficiently high compared to the noise level), such that a rank-aware channel estimation algorithm (e.g., a rank-aware interference suppression algorithm) should be applied to mitigate the interference at the communication resource.

[0101] Therefore, when the interference level meets the threshold, UE 315-a may send a request to serving network entity 305-a indicating the number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities 305-b and 305-c. In some cases, this request may be for the aggregated number of transmission layers (e.g., the sum) scheduled for communication within a communication resource by one or more neighboring network entities 305-b and 305-c. For example, the aggregated number may be the sum of the number of transmission layers associated with each of the one or more neighboring network entities 305-b and 305-c. In some cases, the request may indicate a specific granularity at which the number of transmission layers should be reported, such as per resource element, per resource block, or per subcarrier. In some cases, the specific granularity level may be based on the configuration of serving network entity 305-a, the configuration of neighboring network entities 305-b and 305-c, or a combination thereof.

[0102] The number of aggregated layers scheduled for use by one or more adjacent entities 305-b and 305-c can be the rank of the interference observed by UE 315-a. UE 315-a can use the number of aggregated layers to apply to rank-aware channel estimation algorithms (e.g., rank-aware interference suppression algorithms), and can use rank-aware channel estimation algorithms to improve the noise covariance matrix. )estimate.

[0103] In some specific implementations, the rank-aware interference suppression algorithm can be determined as follows. The frequency domain (FD) received signal at UE 315-a can be expressed as: The noise observed by UE315-a can be expressed as .in and It is one or more adjacent network entities 305-b and 305-c with corresponding sizes and The corresponding channel matrix. and It has the corresponding size and The corresponding transmitted signal vectors of one or more adjacent network entities 305-b and 305-c. It has size The additive white Gaussian noise (AWGN) vector. The noise covariance matrix observed by UE 315-a can be expressed as... Based on the knowledge that the precoders of one or more adjacent network entities 305-b and 305-c do not change and that the channels of one or more adjacent network entities 305-b and 305-c have a nearly constant number of consecutive subcarriers, It can be approximated as: Assume that the number of transmission layers for the signals of one or more adjacent network entities 305-b and 305-c within this consecutive number of subcarriers are respectively... and ,but The rank is ,and The rank is The sum of these ranks can be expressed as .observe ( Eigenvalue decomposition (EVD) can confirm that It is diagonal, and it has the following values: … Furthermore, due to It can be observed that: And therefore, EVD decomposition is ,in The diagonal has the following values: … When the initial noise estimate is performed using the following formula: The estimated covariance matrix The singular value decomposition (SVD) can be considered as the same value as previously mentioned, but with estimation errors:

[0104] … These are located in The eigenvalues ​​on the diagonal can be expressed as: And the eigenvector matrix is ​​expressed as: Make: The estimation error can be caused by various factors, such as an insufficient number of consecutive REs used for estimation, leading to channel changes (in some cases, slight changes) in one or more neighboring network entities 305-b and 305-c, potentially causing slight ambiguity in the channel covariance of one or more neighboring network entities 305-b and 305-c; an insufficient number of consecutive REs used for estimation, resulting in insufficient attenuation of the symbols and AWGN of one or more neighboring network entities 305-b and 305-c during averaging; or other noise, such as the channel estimation error of UE 315-a (which may not be constant within the consecutive RE group), which may affect the estimation. The covariance matrix estimated by the rank-aware interference suppression algorithm can be expressed as... and its eigenvalues (lie in (on the diagonal). Furthermore, it can be deduced that, at least for rank 1 and rank 2, a good rank-aware channel estimation algorithm will assume that higher eigenvalues ​​should be preserved, which means: Alternatively, the next eigenvalue contains most of the estimation error and may be ignored, and the lower eigenvalues ​​should be used to estimate AWGN noise, which means: ,in: The offset can be selected as approximately 1 or approximately 2. To complete the estimation: It is a rank-aware channel estimation algorithm that generates covariance matrices for estimating interference sources (e.g., one or more neighboring network entities 305-b and 305-c) and noise.

[0105] Figure 4 An example of a process flow 400 supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown.

[0106] In some examples, process flow 400 can implement various aspects of wireless communication system 100. Process flow 400 can be implemented by UE 415-a, serving network entity 405-a, one or more neighboring network entities 405-b, and core network entity 430. In the following description of process flow 400, communication between UE 415-a, serving network entity 405-a, one or more neighboring network entities 405-b, and core network entity 430 may be sent in a different order than the example order shown, or operations performed by UE 415-a, serving network entity 405-a, one or more neighboring network entities 405-b, and core network entity 430 may be performed in a different order or at different times. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0107] In some examples, the operations illustrated in process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples are provided below, in which some steps may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0108] At step 405, UE 415-a may measure or estimate the noise covariance matrix associated with a specific communication resource (e.g., a downlink slot) to determine the interference level associated with that communication resource. In some cases, UE 415-a may receive an instruction from serving network entity 405-a to perform noise covariance matrix estimation on the communication resource. In such cases, requests may be received periodically, aperiodically, or randomly. In some cases, the specific communication resource may be a future or upcoming communication resource, such as an upcoming downlink slot.

[0109] At step 410, based on the determination that the interference level meets the interference threshold (such as with respect to...), Figure 3(As described), UE 415-a may determine the number of transmission layers that are scheduled for communication within the communication resource by one or more neighboring network entities 405-b (e.g., potential interference source network entities). Therefore, UE 415-a may send a request to the serving network entity 405-a for notification of the number of transmission layers scheduled for communication within the communication resource by one or more neighboring network entities 405-b. In some cases, the request may include an indication of the location or geographic location of UE 415-a. UE 415-a may send the request periodically, aperiodically, or randomly to the serving network entity 405-a. In some cases, the frequency of request transmission may be based on a scheduling configured by the serving network entity 405-a. UE 415-a may send the request via uplink signaling (such as via Uplink Control Information (UCI), Physical Uplink Control Channel (PUCCH), Media Access Control-Control Element (MAC-CE), other uplink control signaling, or any combination thereof).

[0110] At step 415, the serving network entity 405-a may receive a transmission layer number notification request from UE 415-a and may send the request to the core network entity 430, since the core network entity 430 may have knowledge of one or more neighboring network entities 405-b and the ability to communicate with those neighboring network entities. In some cases, the request to the core network entity 430 may also indicate a request for the location or position of UE 415-a (e.g., as indicated in the transmission layer number notification request from UE 415-a). In some cases, the request to the core network entity 430 may additionally indicate the granularity level for reporting the transmission layer number. For example, the granularity level may indicate that the transmission layer number should be reported per subcarrier, per resource block, per resource element, or based on some other granularity level. In some cases, the requested granularity level may depend on the configuration of the serving network entity 405-a.

[0111] At step 420, core network entity 430 may receive a layer number notification request from serving network entity 405-a, and may identify one or more candidate network entities that are close to serving network entity 405-a or have the potential to interfere with the serving network entity as one or more neighboring network entities 405-b, in order to send a request for an indication of the number of transmission layers scheduled for communication within the communication resources. In some cases, this determination may additionally or alternatively be based on the location or geographic location of the requesting UE 415-a (e.g., as indicated in the transmission layer number notification request from UE 415-a).

[0112] At step 425, core network entity 430 may send a request to one or more of the identified neighboring network entities 405-b, notifying core network entity 430 of the number of transmission layers scheduled for communication within the communication resources by that neighboring network entity 405-b. In some cases, the request to one or more neighboring network entities 405-b may also be based on a granularity level requested by serving network entity 405, and core network entity 430 may indicate to one or more neighboring network entities 405-b the granularity level requested by serving network entity 405-a. In other cases, core network entity 430 may determine and indicate to one or more neighboring network entities 405-b a granularity level for reporting the number of transmission layers, rather than the granularity level indicated by serving network entity 405-a. For example, the granularity level may indicate that the number of transmission layers should be reported per subcarrier, per resource block, per resource element, or based on some other granularity level. In some cases, the requested granularity level may depend on the configuration of the serving network entity 305-a, the configuration of the neighboring network entities 305-b and 305-c, or a combination thereof.

[0113] At step 430, one or more adjacent network entities 405-b may individually determine the number of transmission layers scheduled for use by the adjacent network entity 405-b for communication within the communication resources.

[0114] At step 435, one or more neighboring network entities in neighboring network entities 405-b may send an indication to core network entity 430 of the number of their individual transmission layers scheduled for communication within the communication resource. The reported number of transmission layers may be based on a requested granularity level indicated by core network entity 430. For example, one or more interfering neighboring network entities 405 may indicate to core network entity 430 the number of transmissions per subcarrier, per resource element, per resource block, or any combination thereof. Core network entity 430 may then sum these numbers of transmissions per subcarrier, per resource element, per resource block, or any combination thereof.

[0115] At step 440, core network entity 430 may receive from one or more neighboring network entities 405-b the number of its individual transmission layers scheduled for communication by that neighboring network entity 405-b within the communication resources. Core network entity 430 may aggregate the received transmission layer numbers. For example, core network entity 430 may sum the transmission layer numbers received from those neighboring network entities 405-b that report back to core network entity 430. Aggregation may also be performed at a requested granularity level.

[0116] At step 445, the core network entity 430 may send to the service network entity 405-a the number of aggregation (e.g., summation) layers scheduled for communication within the communication resource by one or more adjacent network entities 405-b.

[0117] At step 450, serving network entity 405-a may send a message to UE 415-a indicating the number of transmission layers scheduled for use by one or more adjacent network entities 405-b. The number of transmission layers may be an aggregated (e.g., summed) number of transmission layers. The number of transmission layers may additionally be based on a requested granularity level, such as per subcarrier, per resource element, per resource block, or some other granularity level. The message including the indication of the number of transmission layers from serving network entity 405-a may be sent in downlink control signaling, such as downlink control information (DCI), physical downlink control channel (PDCCH), MAC-CE, other downlink control information, or any combination thereof. In some cases, the message including the indication of the number of transmission layers may be signaling for resource allocation of communication resources or may be included in signaling for resource allocation of communication resources. For example, the signaling may include scheduling permission to allocate communication resources to UE 415-a. In some cases, a message may be sent to UE 415-a before receiving a scheduling permission signal that includes the allocation of communication resources to UE 415-a.

[0118] At step 455, UE 415-a may apply a rank-aware channel estimation algorithm (e.g., a rank-aware interference suppression algorithm) to mitigate interference at communication resources. In some cases, UE 415-a may initially determine whether the number of transmission layers (e.g., the number of summed layers) meets a threshold. For example, the number of transmission layers meets the threshold when it is less than the total number of receive antennas at UE 415-a. Therefore, if the number of transmission layers meets the threshold, UE 415-a may use a rank-aware interference suppression algorithm to improve the noise covariance matrix estimation performed by UE 415-a. For example, in some cases, the number of transmission layers (e.g., the number of summed transmission layers) may be applied to the rank-aware channel estimation algorithm (e.g., a rank-aware interference suppression algorithm) in order to use the rank-aware interference suppression algorithm. An updated rank-aware channel estimation algorithm (e.g., a rank-aware channel estimation algorithm applied together with the number of transmission layers) may be used to update or improve the noise covariance matrix estimation (e.g., an improved C... zz The estimated noise covariance matrix can then be used, at least in part, to perform interference mitigation when receiving downlink messages in communication resources.

[0119] Figure 5A block diagram 500 of an apparatus 505 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. Apparatus 505 may be an example of various aspects of a UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505, or one or more components of apparatus 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0120] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for rank-aware interference suppression based on neighboring cell layer notifications). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0121] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for rank-aware interference suppression based on neighboring cell layer notifications). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0122] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0123] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0124] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0125] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0126] The communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for sending a first message to a first network entity serving the UE requesting a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. The communication manager 520 may be capable of, configured to, or operable to support components for receiving an indication from the first network entity of the number of transmission layers for the communication resource. The communication manager 520 may be capable of, configured to, or operable to support components for receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0127] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., at least one processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can support techniques for improving throughput, performance, and communication reliability.

[0128] Figure 6 A block diagram 600 of a device 605 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for rank-aware interference suppression based on neighboring cell layer notifications). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0130] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for rank-aware interference suppression based on neighboring cell layer notification). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0131] Device 605 or its various components may be examples of parts for performing various aspects of techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, communication manager 620 may include transmit layer request manager 625, transmit layer manager 630, rank-aware channel estimation algorithm manager 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0132] Communication manager 620 may support wireless communication according to examples disclosed herein. Transmission layer request manager 625 is capable of, configured to, or operable to support components for sending a first message to a first network entity serving the UE requesting the number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. Transmission layer manager 630 is capable of, configured to, or operable to support components for receiving an indication from the first network entity of the number of transmission layers for the communication resource. Rank-aware channel estimation algorithm manager 635 is capable of, configured to, or operable to support components for receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0133] Figure 7A block diagram 700 of a communication manager 720 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications, as described herein. For example, the communication manager 720 may include a transmission layer request manager 725, a transmission layer manager 730, a rank-aware channel estimation algorithm manager 735, a noise covariance matrix estimation manager 740, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0134] Communication manager 720 may support wireless communication according to examples disclosed herein. Transmission layer request manager 725 is capable of, configured to, or operable to support components for sending a first message to a first network entity serving the UE requesting the number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. Transmission layer manager 730 is capable of, configured to, or operable to support components for receiving an indication from the first network entity of the number of transmission layers for the communication resource. Rank-aware channel estimation algorithm manager 735 is capable of, configured to, or operable to support components for receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0135] In some examples, the first message is sent based on an estimate of the noise covariance matrix for the communication resources to meet an interference threshold.

[0136] In some examples, the noise covariance matrix estimation manager 740 is capable of, configured to, or operable to support components for receiving control information from a first network entity instructing the performance of noise covariance matrix estimation within a communication resource.

[0137] In some examples, the first message includes an indication of the granularity associated with the requested number of transmission layers. In some examples, the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0138] In some examples, the indication of the number of sending layers includes the sum of the number of sending layers associated with one or more adjacent network entities.

[0139] In some examples, the indication of the number of transmission layers used for communication resources is received via control signaling. In some examples, the control signaling also includes scheduling permission to allocate communication resources to the UE.

[0140] In some examples, the first message is transmitted via a first Media Access Control-Control Element (MAC-CE) or a physical uplink control channel. In some examples, an indication of the number of transmission layers used for communication resources is received via a second MAC-CE or a physical downlink shared channel.

[0141] Figure 8 A diagram of a system 800 including device 805 supporting rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or a component including such devices. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0142] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0143] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0144] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 830 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0145] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0146] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for sending a first message to a first network entity serving the UE requesting a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. The communication manager 820 may be capable of, configured to, or operable to support components for receiving an indication from the first network entity of the number of transmission layers for the communication resource. The communication manager 820 may be capable of, configured to, or operable to support components for receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0147] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for improving throughput, performance, and communication reliability.

[0148] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of techniques for rank-aware interference suppression based on neighboring cell layer notification as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0149] Figure 9 A block diagram 900 illustrates an apparatus 905 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure. Apparatus 905 may be an example of aspects of network entity 105 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Apparatus 905, or one or more components of apparatus 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0150] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0151] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0152] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0153] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0154] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0155] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0156] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving from a UE served by a first network entity a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. The communication manager 920 may be capable of, configured to, or operable to support components for sending to a second network entity a request for a number of transmission layers for the communication resource. The communication manager 920 may be capable of, configured to, or operable to support components for receiving from a second network entity a third message including an indication of the number of transmission layers for the communication resource. The communication manager 920 may be capable of, configured to, or operable to support components for sending to a UE an indication of the number of transmission layers for the communication resource.

[0157] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., at least one processor that controls or otherwise couples to receiver 910, transmitter 915, communication manager 920, or a combination thereof) can support techniques for improving throughput, performance, and communication reliability.

[0158] Figure 10 A block diagram 1000 of an apparatus 1005 supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Apparatus 1005 may be an example of aspects of apparatus 905 or network entity 105 as described herein. Apparatus 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Apparatus 1005, or one or more components of apparatus 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described technique. Each of these components may communicate with each other (e.g., via one or more buses).

[0159] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0160] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0161] Device 1005 or its various components may be examples of parts for performing various aspects of techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, communication manager 1020 may include transmit layer manager 1025, transmit layer request manager 1030, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0162] Communication manager 1020 may support wireless communication according to examples disclosed herein. Transmission layer manager 1025 is capable of, configured to, or operable to support components for receiving from a UE served by a first network entity a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. Transmission layer request manager 1030 is capable of, configured to, or operable to support components for sending to a second network entity a request for a number of transmission layers for the communication resource. Transmission layer manager 1025 is capable of, configured to, or operable to support components for receiving from a second network entity a third message including an indication of the number of transmission layers for the communication resource. Transmission layer manager 1025 is capable of, configured to, or operable to support components for sending to a UE an indication of the number of transmission layers for the communication resource.

[0163] Figure 11 A block diagram 1100 of a communication manager 1120 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications, as described herein. For example, the communication manager 1120 may include a transmission layer manager 1125, a transmission layer request manager 1130, a noise covariance matrix estimation manager 1135, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0164] Communication manager 1120 may support wireless communication according to examples disclosed herein. Transmission layer manager 1125 is capable of, configured to, or operable to support components for receiving from a UE served by a first network entity a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. Transmission layer request manager 1130 is capable of, configured to, or operable to support components for sending to a second network entity a request for a number of transmission layers for the communication resource. In some examples, transmission layer manager 1125 is capable of, configured to, or operable to support components for receiving from a second network entity a third message including an indication of the number of transmission layers for the communication resource. In some examples, transmission layer manager 1125 is capable of, configured to, or operable to support components for sending to a UE an indication of the number of transmission layers for the communication resource.

[0165] In some examples, the first message includes an indication of the granularity associated with the requested number of transmission layers. In some examples, the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0166] In some examples, the indication of the number of transmission layers is based on the indicated granularity.

[0167] In some examples, the noise covariance matrix estimation manager 1135 is capable of, configured to, or able to operate to support components for sending control information to the UE instructing the UE to perform noise covariance matrix estimation on communication resources.

[0168] In some examples, the indication of the number of transmission layers used for communication resources is sent to the UE via control signaling. In some examples, the control signaling also includes scheduling permission to allocate communication resources to the UE.

[0169] In some examples, the first network entity includes a serving gNodeB (gNB) serving the UE, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a set of multiple gNBs, the set of multiple gNBs including the serving gNB and the one or more interference source gNBs.

[0170] In some examples, the first message requesting the number of layers includes information identifying the estimated geographical location of the UE.

[0171] In some examples, the first message is received via a first Media Access Control-Control Element (MAC-CE) or a physical uplink control channel. In some examples, the indication of the number of transmission layers used for communication resources is transmitted via a second MAC-CE or a physical downlink shared channel.

[0172] Figure 12 A diagram of a system 1200 including device 1205 supporting rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components that support output and obtain communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0173] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1210 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215, and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0174] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by a processor in at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may also include a BIOS, among other things, that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0175] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1230) host functions for performing the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operated to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

[0176] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).

[0177] In some examples, the communication manager 1220 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 may manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1220 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1220 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0178] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for receiving from a UE served by a first network entity a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. The communication manager 1220 may be capable of, configured to, or operable to support components for sending to a second network entity a request for a number of transmission layers for the communication resource. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving from a second network entity a third message including an indication of the number of transmission layers for the communication resource. The communication manager 1220 may be capable of, configured to, or operable to support components for sending to a UE an indication of the number of transmission layers for the communication resource.

[0179] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving throughput, performance, and communication reliability.

[0180] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors of at least one processor 1235 to cause device 1205 to perform various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0181] Figure 13 A block diagram 1300 of an apparatus 1305 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure, is shown. Apparatus 1305 may be an example of aspects of a core network entity as described herein. Apparatus 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Apparatus 1305, or one or more components of apparatus 1305 (e.g., receiver 1310, transmitter 1315, and communication manager 1320), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0182] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0183] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0184] The communication manager 1320, receiver 1310, transmitter 1315, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0185] In some examples, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0186] Additionally or alternatively, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0187] In some examples, the communication manager 1320 may be configured to use or otherwise cooperate with the receiver 1310, the transmitter 1315, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated with the receiver 1310, the transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0188] The communication manager 1320 may support wireless communication according to examples disclosed herein. For example, the communication manager 1320 may be capable of, configured to, or operable to support components for receiving a message from a first network entity requesting a number of transmission layers to be scheduled for communication within a communication resource by one or more neighboring network entities. The communication manager 1320 may be capable of, configured to, or operable to support components for requesting a number of transmission layers to be scheduled for communication within a communication resource by at least one of one or more neighboring network entities. The communication manager 1320 may be capable of, configured to, or operable to support components for sending to the first network entity an indication of the number of transmission layers scheduled for communication within a communication resource by at least one neighboring network entity.

[0189] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 (e.g., at least one processor that controls or is otherwise coupled to receiver 1310, transmitter 1315, communication manager 1320, or a combination thereof) can support techniques for improving throughput, performance, and communication reliability.

[0190] Figure 14 A block diagram 1400 of an apparatus 1405 supporting a technique for rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Apparatus 1405 may be an example of an apparatus 1305 as described herein or an aspect of a core network 130. Apparatus 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Apparatus 1405, or one or more components of apparatus 1405 (e.g., receiver 1410, transmitter 1415, and communication manager 1420), may include at least one processor that may be coupled to at least one memory to support the described technique. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 1410 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0192] Transmitter 1415 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1405. For example, transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1415 and receiver 1410 may be co-located in a transceiver, which may include or be coupled to a modem.

[0193] Device 1405 or its various components may be examples of components for performing various aspects of techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, communication manager 1420 may include transmit layer manager 1425, transmit layer request manager 1430, or any combination thereof. Communication manager 1420 may be examples of aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to use or otherwise cooperate with receiver 1410, transmitter 1415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in combination with receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0194] Communication manager 1420 may support wireless communication according to examples disclosed herein. Transmission layer manager 1425 is capable of, configured to, or operable to support components for receiving from a first network entity a message requesting the number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities. Transmission layer request manager 1430 is capable of, configured to, or operable to support components for requesting from at least one of one or more neighboring network entities the number of transmission layers scheduled for communication within a communication resource by at least one neighboring network entity. Transmission layer manager 1425 is capable of, configured to, or operable to support components for sending to the first network entity an indication of the number of transmission layers scheduled for communication within a communication resource by at least one neighboring network entity.

[0195] Figure 15A block diagram 1500 is shown of a communication manager 1520 supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications, according to one or more aspects of this disclosure. The communication manager 1520 may be an example of aspects of the communication manager 1320, communication manager 1420, or both as described herein. The communication manager 1520 or its various components may be examples of components for performing various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein. For example, the communication manager 1520 may include a transmission layer manager 1525, a transmission layer request manager 1530, an interference source identification manager 1535, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate with each other directly or indirectly (e.g., via one or more buses).

[0196] Communication manager 1520 may support wireless communication according to examples disclosed herein. Transmission layer manager 1525 is capable of, configured to, or operable to support components for receiving from a first network entity a message requesting the number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities. Transmission layer request manager 1530 is capable of, configured to, or operable to support components for requesting from at least one of one or more adjacent network entities the number of transmission layers scheduled for communication within a communication resource by at least one adjacent network entity. In some examples, transmission layer manager 1525 is capable of, configured to, or operable to support components for sending to the first network entity an indication of the number of transmission layers scheduled for communication within a communication resource by at least one adjacent network entity.

[0197] In some examples, the message requesting the number of layers includes information identifying the estimated geographical location of the UE served by the first network entity.

[0198] In some examples, the interference source identification manager 1535 is capable of, configured to, or operable to support components for identifying one or more adjacent network entities by determining one or more candidate network entities that have the potential to interfere with the first network entity.

[0199] In some examples, one or more candidate network entities are determined based on the estimated geographic location of the UE based on the number of request-sent layers.

[0200] In some examples, the first network entity includes a serving gNodeB (gNB) serving a UE requesting a certain number of transmission layers, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a set of multiple gNBs, the set of multiple gNBs including the serving gNB and the one or more interference source gNBs.

[0201] Figure 16 A diagram of a system 1600 including a device 1605 supporting rank-aware interference suppression based on neighboring cell layer notification, according to one or more aspects of this disclosure, is shown. Device 1605 may be an example of device 1305, device 1405, or a core network entity as described herein, or a component including such devices. Device 1605 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1620, a transceiver 1610, an antenna 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1640).

[0202] Transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1610 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1610 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1605 may include one or more antennas 1615 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1610 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1615, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1615, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1615 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1615 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1610 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1610, or transceiver 1610 and one or more antennas 1615, or transceiver 1610 and one or more antennas 1615 and one or more processors or one or more memory components (e.g., at least one processor 1635, at least one memory 1625, or both), may be included in a chip or chip assembly mounted in device 1605. In some examples, transceiver 1610 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0203] At least one memory 1625 may include RAM, ROM, or any combination thereof. At least one memory 1625 may store computer-readable, computer-executable code 1630 including instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform the various functions described herein. The code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1630 may not be directly executable by a processor in the at least one processor 1635, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1625 may also include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1635 may include multiple processors, and at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0204] At least one processor 1635 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1635. At least one processor 1635 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1625) to cause device 1605 to perform various functions (e.g., functions or tasks supporting techniques for rank-aware interference suppression based on neighboring cell layer notifications). For example, device 1605 or components of device 1605 may include at least one processor 1635 and at least one memory 1625 coupled to one or more of the at least one processor 1635, wherein at least one processor 1635 and at least one memory 1625 are configured to perform the various functions described herein. At least one processor 1635 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1630) host functions for performing the functions of device 1605. At least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1605 (such as within one or more memories of at least one memory 1625). In some examples, at least one processor 1635 may include multiple processors, and at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1635 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1635) and memory circuitry (which may include at least one memory 1625)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1635 or a processing system including at least one processor 1635 may be configured, configured to, or operated to cause the device 1605 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1625 or otherwise.

[0205] In some examples, bus 1640 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1640 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1605, or communication performed between different components of device 1605 that are co-addressable or may be located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, at least one memory 1625, code 1630 and at least one processor 1635 may be located in one component of different components or partitioned between different components).

[0206] In some examples, the communication manager 1620 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1620 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1620 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1620 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0207] The communication manager 1620 may support wireless communication according to examples disclosed herein. For example, the communication manager 1620 may be capable of, configured to, or operable to support components for receiving a message from a first network entity requesting a number of transmission layers to be scheduled for communication within a communication resource by one or more neighboring network entities. The communication manager 1620 may be capable of, configured to, or operable to support components for requesting a number of transmission layers to be scheduled for communication within a communication resource by at least one of the one or more neighboring network entities. The communication manager 1620 may be capable of, configured to, or operable to support components for sending an indication to the first network entity of the number of transmission layers scheduled for communication within a communication resource by at least one neighboring network entity.

[0208] By including or configuring a communication manager 1620 according to an example as described herein, device 1605 can support techniques for improving throughput, performance, and communication reliability.

[0209] In some examples, the communication manager 1620 may be configured to use or otherwise coordinate with the transceiver 1610, one or more antennas 1615 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by the transceiver 1610, one or more processors in at least one processor 1635, one or more memories in at least one memory 1625, code 1630, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1635, at least one memory 1625, code 1630, or any combination thereof). For example, code 1630 may include instructions that can be executed by one or more processors of at least one processor 1635 to cause device 1605 to perform various aspects of the techniques for rank-aware interference suppression based on neighboring cell layer notifications as described herein, or at least one processor 1635 and at least one memory 1625 may be otherwise configured to perform or support such operations individually or jointly.

[0210] Figure 17 A flowchart illustrating a method 1700 for rank-aware interference suppression based on neighboring cell layer notification, according to various aspects of this disclosure, is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0211] At 1705, the method may include sending a first message to a first network entity serving the UE requesting a transmission layer number scheduled for communication within a communication resource by one or more adjacent network entities. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 7 The described sending layer request manager 725 is executed.

[0212] At 1710, the method may include receiving from a first network entity an indication of the number of transmission layers used for communication resources. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to... Figure 7 The described send layer manager 730 is executed.

[0213] At 1715, the method may include receiving downlink messages via the communication resources using a rank-aware channel estimation algorithm corresponding to the number of transmission layers used for the communication resources. The operation of block 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 7 The described rank-aware channel estimation algorithm is executed by the manager 735.

[0214] Figure 18 A flowchart illustrating a method 1800 for rank-aware interference suppression based on neighboring cell layer notification, according to various aspects of this disclosure, is shown. The operation of method 1800 may be implemented by a network entity or its components as described herein. For example, the operation of method 1800 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0215] At 1805, the method may include receiving from a UE served by a first network entity a first message requesting a transmission layer number scheduled for communication within communication resources by one or more adjacent network entities. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1805 may be provided as referenced. Figure 11 The described sending layer manager 1125 is executed.

[0216] At 1810, the method may include sending a second message to the second network entity requesting a number of transmission layers for communication resources. The operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 11 The described sending layer request manager 1130 is executed.

[0217] At 1815, the method may include receiving from the second network entity a third message including an indication of the number of transmission layers used for communication resources. The operation of block 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to... Figure 11 The described sending layer manager 1125 is executed.

[0218] At 1820, the method may include sending an indication to the UE of the number of transmission layers used for communication resources. The operation of block 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1820 may be provided by reference to... Figure 11 The described sending layer manager 1125 is executed.

[0219] Figure 19 A flowchart illustrating a method 1900 for rank-aware interference suppression based on neighboring cell layer notification, according to various aspects of this disclosure, is shown. The operation of method 1900 may be implemented by a core network entity or its components as described herein. For example, the operation of method 1900 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 13 to 16 The core network entity described herein performs the functions. In some examples, the core network entity may execute a set of instructions to control the functional elements of the core network entity to perform the described functions. Additionally or alternatively, the core network entity may use dedicated hardware to perform aspects of the described functions.

[0220] At 1905, the method may include receiving from a first network entity a message requesting a transmission layer number to be scheduled for communication within a communication resource by one or more adjacent network entities. The operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1905 may be as described in references... Figure 15 The described sending layer manager 1525 is executed.

[0221] At 1910, the method may include requesting from at least one of one or more neighboring network entities a number of transmission layers to be scheduled for communication within the communication resource by at least one neighboring network entity. The operation of block 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to [reference needed]. Figure 15 The described sending layer request manager 1530 is executed.

[0222] At 1915, the method may include sending an indication to a first network entity of the number of transmission layers scheduled for use by at least one adjacent network entity for communication within the communication resource. The operation of block 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1915 may be as described in references... Figure 15 The described sending layer manager 1525 is executed.

[0223] The following provides an overview of the various aspects of this disclosure:

[0224] Aspect 1: A method for wireless communication by a UE, the method comprising: sending to a first network entity serving the UE a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; receiving from the first network entity an indication of the number of transmission layers for the communication resource; and receiving downlink messages via the communication resource using a rank-aware channel estimation algorithm corresponding to the number of transmission layers for the communication resource.

[0225] Aspect 2: According to the method of aspect 1, wherein the first message is sent at least in part based on an estimate of the noise covariance matrix for the communication resource satisfying an interference threshold.

[0226] Aspect 3: According to the method of aspect 2, the method further includes: receiving control information from the first network entity including an instruction to perform the noise covariance matrix estimation within the communication resources.

[0227] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first message includes an indication of granularity associated with the number of transmission layers, and the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0228] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the indication of the number of transmission layers includes the sum of the number of transmission layers associated with the one or more adjacent network entities.

[0229] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the indication of the number of transmission layers for the communication resources is received via control signaling, and the control signaling further includes scheduling permission to allocate the communication resources to the UE.

[0230] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first message is transmitted via a first Media Access Control-Control Element (MAC-CE) or PUCCH, and the indication of the number of transmission layers for the communication resources is received via a second Media Access Control-Control Element (MAC-CE) or PDCCH.

[0231] Aspect 8: A method for wireless communication by a first network entity, the method comprising: receiving from a UE served by the first network entity a first message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more adjacent network entities; sending to a second network entity a second message including the request for the number of transmission layers for the communication resource; receiving from the second network entity a third message including an indication of the number of transmission layers for the communication resource; and sending to the UE the indication of the number of transmission layers for the communication resource.

[0232] Aspect 9: According to the method of aspect 8, wherein the first message includes an indication of granularity associated with the number of transmission layers, and the granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

[0233] Aspect 10: The method according to aspect 9, wherein the indication of the number of transmission layers is at least partially based on the indicated granularity.

[0234] Aspect 11: The method according to any one of Aspects 8 to 10, the method further comprising: sending control information to the UE including an indication to perform noise covariance matrix estimation on the communication resources.

[0235] Aspect 12: The method according to any one of Aspects 8 to 11, wherein the indication of the number of transmission layers for the communication resources is sent to the UE via control signaling, and the control signaling further includes scheduling permission to allocate the communication resources to the UE.

[0236] Aspect 13: The method according to any one of Aspects 8 to 12, wherein the first network entity includes a serving gNodeB (gNB) serving the UE, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a plurality of gNBs, the plurality of gNBs including the serving gNB and the one or more interference source gNBs.

[0237] Aspect 14: The method according to any one of Aspects 8 to 13, wherein the first message includes information indicating the estimated geographical location of the UE.

[0238] Aspect 15: The method according to any one of Aspects 8 to 14, wherein the first message is received via a first Media Access Control-Control Element (MAC-CE) or PUCCH, and the indication of the number of transmission layers for the communication resources is transmitted via a second Media Access Control-Control Element (MAC-CE) or PDCCH.

[0239] Aspect 16: A method for wireless communication by a second network entity, the method comprising: receiving from a first network entity a message including a request for a number of transmission layers scheduled for communication within a communication resource by one or more neighboring network entities; including a request from at least one of the one or more neighboring network entities for a number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity; and sending to the first network entity an indication of the number of transmission layers scheduled for communication within the communication resource by the at least one neighboring network entity.

[0240] Aspect 17: The method according to aspect 16, wherein the message includes information indicating the estimated geographical location of the UE served by the first network entity.

[0241] Aspect 18: The method according to any one of Aspects 16 to 17, the method further comprising: identifying the one or more adjacent network entities based on the determination of one or more candidate network entities that have the potential to interfere with the first network entity.

[0242] Aspect 19: The method according to aspect 18, wherein the determination of the one or more candidate network entities is based at least in part on the estimated geographical location of the UE requesting the number of transmission layers.

[0243] Aspect 20: The method according to any one of Aspects 16 to 19, wherein the first network entity includes a serving gNodeB (gNB) serving a UE requesting the number of transmission layers, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a plurality of gNBs, the plurality of gNBs including the serving gNB and the one or more interference source gNBs.

[0244] Aspect 21: A UE for wireless communication, the UE comprising one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 7.

[0245] Aspect 22: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 7.

[0246] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 7.

[0247] Aspect 24: A first network entity for wireless communication, the first network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first network entity to perform a method according to any one of aspects 8 to 15.

[0248] Aspect 25: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 8 to 15.

[0249] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 8 to 15.

[0250] Aspect 27: A second network entity for wireless communication, the second network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the second network entity to perform a method according to any one of Aspects 16 to 20.

[0251] Aspect 28: A second network entity for wireless communication, the second network entity comprising at least one component for performing the method according to any one of aspects 16 to 20.

[0252] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 16 to 20.

[0253] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0254] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0255] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0256] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0257] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0258] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0259] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0260] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0261] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0262] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0263] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0264] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0265] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Send a first message to a first network entity serving the UE, including a request for a number of transmission layers scheduled for communication within communication resources by one or more adjacent network entities; Receive an indication from the first network entity of the number of transmission layers for the communication resources; as well as Downlink messages are received via the communication resources using a rank-aware channel estimation algorithm corresponding to the number of transmission layers used for the communication resources.

2. The UE of claim 1, wherein the first message is transmitted at least in part based on an estimation of the noise covariance matrix for the communication resource that satisfies an interference threshold.

3. The UE of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive control information from the first network entity, including an instruction to perform the noise covariance matrix estimation within the communication resources.

4. The UE according to claim 1, wherein: The first message includes an indication of the granularity associated with the number of transmission layers, and The granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

5. The UE of claim 1, wherein the indication of the number of transmission layers includes the sum of the number of transmission layers associated with the one or more adjacent network entities.

6. The UE according to claim 1, wherein: The indication of the number of transmission layers used for the communication resources is received via control signaling, and The control signaling also includes scheduling permission to allocate the communication resources to the UE.

7. The UE according to claim 1, wherein: The first message is sent via a first Media Access Control-Control Element (MAC-CE) or a Physical Uplink Control Channel (PUCCH), and The indication of the number of transmission layers used for the communication resources is received via a second medium access control-control element (MAC-CE) or a physical downlink control channel (PDCCH).

8. A first network entity, the first network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the first network entity: Receive a first message from the user equipment (UE) served by the first network entity, including a request for the number of transmission layers to be scheduled for communication within communication resources by one or more adjacent network entities; Send a second message to the second network entity including a request for the number of transmission layers for the communication resources; Receive a third message from the second network entity, including an indication of the number of transmission layers for the communication resources; as well as Send the indication to the UE of the number of transmission layers used for the communication resources.

9. The first network entity according to claim 8, wherein: The first message includes an indication of the granularity associated with the number of transmission layers, and The granularity includes the number of transmission layers per resource element, the number of transmission layers per resource block, the number of transmission layers per time slot, or the number of transmission layers per subcarrier.

10. The first network entity of claim 9, wherein the indication of the number of transmission layers is at least partially based on the granularity.

11. The first network entity of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first network entity to: Control information including an instruction to perform noise covariance matrix estimation on the communication resources is sent to the UE.

12. The first network entity according to claim 8, wherein: The indication of the number of transmission layers used for the communication resources is sent to the UE via control signaling, and The control signaling also includes scheduling permission to allocate the communication resources to the UE.

13. The first network entity according to claim 8, wherein the first network entity includes a serving gNodeB (gNB) serving the UE, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a plurality of gNBs, the plurality of gNBs including the serving gNB and the one or more interference source gNBs.

14. The first network entity of claim 8, wherein the first message includes information indicating the estimated geographical location of the UE.

15. The first network entity according to claim 8, wherein: The first message is received via a first Media Access Control-Control Element (MAC-CE) or a Physical Uplink Control Channel (PUCCH), and The indication of the number of transmission layers for the communication resources is transmitted via a second medium access control-control element (MAC-CE) or a physical downlink control channel (PDCCH).

16. A second network entity, the second network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the second network entity: Receive a message from the first network entity including a request for the number of transmission layers scheduled for communication within the communication resources by one or more adjacent network entities; The number of transmission layers to be scheduled for communication within the communication resource is requested from at least one of the one or more neighboring network entities. as well as Send an indication to the first network entity of the number of transmission layers scheduled for communication within the communication resource by the at least one adjacent network entity.

17. The second network entity of claim 16, wherein the message includes information indicating the estimated geographical location of a user equipment (UE) served by the first network entity.

18. The second network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the second network entity to: The one or more adjacent network entities are identified based on the determination of one or more candidate network entities that have the potential to interfere with the first network entity.

19. The second network entity of claim 18, wherein the determination of the one or more candidate network entities is based at least in part on the estimated geographical location of the UE requesting the number of transmission layers.

20. The second network entity of claim 16, wherein the first network entity includes a serving gNodeB (gNB) serving a UE requesting the number of transmission layers, the one or more adjacent network entities include one or more interference source gNBs, and the second network entity includes a core network entity serving a plurality of gNBs, the plurality of gNBs including the serving gNB and the one or more interference source gNBs.

Images