Collaborative measurements by co-located devices

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a node may identify a set of co-located nodes associated with co-located conditions relative to the node. The node may receive measurement information from the set of co-located nodes regarding at least one of: a beam measurement, a transmit receive point (TRP) measurement, or a cell measurement. The node may perform a search based at least in part on the measurement information. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 813,773, filed on July 20, 2022, entitled “COOPERATIVE MEASUREMENT BY CO-LOCATED DEVICES” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for cooperative measurements by co-located devices. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a sidelink (SL), a WiFi link, or a Bluetooth link).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a node. The method may include identifying a group of co-located nodes. The method may include receiving measurement information about at least one of beam measurements, transmit receive point (TRP) measurements, or cell measurements from the group of co-located nodes. The method may include communicating using communication parameters based at least in part on the measurement information.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include identifying a plurality of co-located nodes. The method may include configuring a measurement for a group of nodes in the plurality of co-located nodes, the group of nodes including at least two nodes. The method may include receiving measurement information from the group of nodes based at least in part on the measurement. The method may include scheduling communication of the plurality of co-located nodes based at least in part on the measurement information.

[0009] Some aspects described herein relate to a node for wireless communication. The node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify a group of co-located nodes. The one or more processors may be configured to receive measurement information about at least one of beam measurements, TRP measurements, or cell measurements from the group of co-located nodes. The one or more processors may be configured to communicate using communication parameters based at least in part on the measurement information.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify a plurality of co-located nodes. The one or more processors may be configured to configure measurements for a group of nodes in the plurality of co-located nodes, the group of nodes including at least two nodes. The one or more processors may be configured to receive measurement information from the group of nodes based at least in part on the measurements. The one or more processors may be configured to schedule communications associated with the plurality of co-located nodes based at least in part on the measurement information.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a node. The instruction set, when executed by one or more processors of the node, may cause the node to identify a group of co-located nodes. The instruction set, when executed by one or more processors of the node, may cause the node to receive measurement information about at least one of beam measurements, TRP measurements, or cell measurements from the group of co-located nodes. The instruction set, when executed by one or more processors of the node, may cause the node to communicate using communication parameters based at least in part on the measurement information.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to identify a plurality of co-located nodes. The instruction set, when executed by one or more processors of the network node, may cause the network node to configure measurements for a group of nodes in the plurality of co-located nodes, the group of nodes including at least two nodes. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive measurement information from at least one node based at least in part on the measurement. The instruction set, when executed by one or more processors of the network node, may cause the network node to schedule communications associated with the plurality of co-located nodes based at least in part on the measurement information.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for identifying a set of co-located nodes. The apparatus may include means for receiving measurement information about at least one of beam measurements, TRP measurements, or cell measurements from the set of co-located nodes. The apparatus may include means for communicating using communication parameters based at least in part on the measurement information.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for identifying a plurality of co-located nodes. The apparatus may include components for configuring measurements for a group of nodes in the plurality of co-located nodes, the group of nodes including at least two nodes. The apparatus may include components for receiving measurement information from at least one node based at least in part on the measurements. The apparatus may include scheduling communications associated with the plurality of co-located nodes based at least in part on the measurement information.

[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a beam management procedure according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of measurement information sharing between co-located nodes according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of sharing measurement information between co-located nodes according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example 700 of cooperative measurement as configured at a network node according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process 800 , such as performed by a node, in accordance with the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network node, in accordance with the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus 1000 for wireless communications according to the present disclosure.

[0029] Fig.11 is a diagram of an example apparatus 1100 for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0033] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 includes two or more non-co-located network nodes. A decomposed network node may be configured to utilize a protocol stack that is physically or logically distributed between two or more network nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0034] In some examples, the network node 110 includes an entity, such as an RU, that communicates with the UE 120 via a radio access link. In some examples, the network node 110 includes an entity, such as a DU, that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 includes an entity, such as a CU, that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some aspects, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other and / or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0035] In some aspects, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro base station. A base station for a pico cell may be referred to as a pico base station. A base station for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, network node 110a may be a macro base station for macro cell 102a, network node 110b may be a pico base station for pico cell 102b, and network node 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0036] In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (eg, a mobile base station).

[0037] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120 or network nodes 110. Figure 1 In the example shown, network node 110d (e.g., a relay base station) can communicate with network node 110a (e.g., a macro base station) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, relay base station, relay node, relay, etc.

[0038] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macro base stations, pico base stations, femto base stations, relay base stations, TRPs, RUs, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0039] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may include a CU or a core network device.

[0040] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless medium.

[0041] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0043] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0044] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0047] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node may be implemented in an aggregated architecture or a decomposed architecture. For example, a network node or one or more units (or one or more components) that perform network node functionality may be implemented as an aggregated network node (sometimes referred to as an independent base station or a monolithic base station) or a decomposed network node. A "network entity" or "network node" may refer to a decomposed network node, an aggregated network node, or one or more entities of a decomposed network node (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0048] In some aspects, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0049] Base station type operation or network design may take into account the aggregated nature of network node functionality. For example, a disaggregated network node may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated network node may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design.

[0050] In some aspects, a node (e.g., a UE 120, a TRP, or an antenna panel, etc.) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may perform the following operations: identifying a group of co-located nodes; receiving measurement information about at least one of beam measurements, TRP measurements, or cell measurements from the group of co-located nodes; and communicating using communication parameters based at least in part on the measurement information. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may perform operations such as identifying a plurality of co-located nodes; configuring a measurement for a group of nodes in the plurality of co-located nodes, the group of nodes including at least two nodes; receiving measurement information from the group of nodes based at least in part on the measurement; and scheduling communications for the plurality of co-located nodes based at least in part on the measurement information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0053] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. For example, some network nodes 110 may not include a radio frequency component.

[0054] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0056] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0058] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 3 to 11 )Aspects of any of the methods described herein.

[0059] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 3 to 11 )Aspects of any of the methods described herein.

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the network node 110 may perform one or more techniques associated with the measurement configuration, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0061] In some aspects, a node (e.g., a UE 120, a TRP, or an antenna panel) includes: a component for identifying a group of co-located nodes; a component for receiving measurement information about at least one of beam measurement, TRP measurement, or cell measurement from the group of co-located nodes; and / or a component for communicating using communication parameters based at least in part on the measurement information. In some aspects, the components for the node to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0062] In some aspects, the network node 110 includes: a component for identifying a plurality of co-located nodes; a component for configuring measurements for at least one of the plurality of co-located nodes; a component for receiving measurement information from at least one node based at least in part on the measurements; and / or scheduling communications for the plurality of co-located nodes based at least in part on the measurement information. In some aspects, the components for the network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0063] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] Figure 3 is a diagram illustrating an example 300 decomposed base station architecture according to the present disclosure.

[0066] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., network node 110) or one or more units (or one or more components) that perform base station functionality may be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) may be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a decomposed base station.

[0067] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, DU, and RU may also be implemented as a virtual unit, i.e., a VCU, a VDU, or a VRU.

[0068] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0069] Figure 3 The disaggregated base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0070] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0071] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0072] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0073] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control and user planes of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0074] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0075] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0076] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0077] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0078] Figure 4 4 is a diagram illustrating examples 400, 410, and 420 of a channel state information reference signal (CSI-RS) beam management procedure according to the present disclosure. Figure 4 As shown, examples 400, 410, and 420 include UE 120 communicating with network node 110 in a wireless network (e.g., wireless network 100). Figure 4 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and network node 110 or TRP, between mobile terminal node and control node, between IAB child node and IAB parent node, and / or between scheduled node and scheduling node). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., RRC connected state).

[0079] like Figure 4 As shown, example 400 may include network node 110 and UE 120 communicating to perform beam management using CSI-RS. Example 400 depicts a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam scanning procedure, a cell search procedure, and / or a beam detection procedure. Figure 4 As shown in example 400, CSI-RS may be configured to be sent from network node 110 to UE 120. CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling), and / or aperiodic (e.g., using downlink control information (DCI)).

[0080] The first beam management procedure may include the network node 110 performing beam scanning on multiple transmit (Tx) beams. The network node 110 may use each transmit beam used for beam management to transmit a CSI-RS. In order to enable the UE 120 to perform receive (Rx) beam scanning, the base station may use the transmit beam to transmit each CSI-RS multiple times within the same RS resource set (e.g., using repetition) so that the UE 120 can scan through the receive beam in multiple transmit instances. For example, in the case where the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted M times on each of the N transmit beams, so that the UE 120 may receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam scanning on the receive beam of the UE 120. Thus, the first beam management procedure may enable UE 120 to measure CSI-RS on different transmit beams using different receive beams to support selection of a network node 110 transmit beam / UE 120 receive beam pair. UE 120 may report the measurements to network node 110 to enable network node 110 to select one or more beam pairs for communication between network node 110 and UE 120. Although example 400 has been described in conjunction with CSI-RS, the first beam management procedure may also use synchronization signal blocks (SSBs) to perform beam management in a similar manner as described above.

[0081] like Figure 4As shown, example 410 may include network node 110 and UE 120 communicating to perform beam management using CSI-RS. Example 410 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure may be referred to as a beam refinement procedure, a base station beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 4 As shown in example 410, the CSI-RS may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RS may be configured to be non-periodic (e.g., using DCI). The second beam management procedure may include the network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (e.g., determined at least in part based on measurements reported by the UE 120 in conjunction with the first beam management procedure). The network node 110 may transmit the CSI-RS using each of the one or more transmit beams used for beam management. The UE 120 may measure each CSI-RS using a single (e.g., identical) receive beam (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable the network node 110 to select the best transmit beam based at least in part on measurements of the CSI-RS reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam).

[0082] like Figure 4 As shown, example 420 depicts a third beam management procedure (e.g., P3 CSI-RS beam management). The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, and / or a receive beam refinement procedure. Figure 4As shown in example 420, one or more CSI-RS may be configured to be sent from the network node 110 to the UE 120. The CSI-RS may be configured to be non-periodic (e.g., using DCI). The third beam management procedure may include the network node 110 sending the one or more CSI-RS using a single transmit beam (e.g., determined at least in part based on measurements reported by the UE 120 in conjunction with the first beam management procedure and / or the second beam management procedure). In order to enable the UE 120 to perform receive beam scanning, the base station may use the transmit beam to send (e.g., using repetition) the CSI-RS multiple times within the same RS resource set, so that the UE 120 can scan through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure and / or the second beam management procedure). The third beam management procedure may enable the network node 110 and / or the UE 120 to select the best receive beam based at least in part on reported measurements received from the UE 120 (e.g., the reported measurements are measurements of the CSI-RS of the transmit beam using the one or more receive beams).

[0083] The techniques described herein enable measurements for beam management (and other purposes) to be made based at least in part on a group of nodes that are co-located with each other.

[0084] As indicated above, Figure 4 is provided as an example of a beam management procedure. Other examples of beam management procedures can be found in Figure 4 For example, UE 120 and network node 110 may perform the third beam management procedure before performing the second beam management procedure, and / or UE 120 and network node 110 may perform a similar beam management procedure to select a UE transmit beam.

[0085] Figure 5 is a diagram illustrating an example 500 of measurement information sharing between co-located nodes according to the present disclosure.

[0086] Node 505 (such as UE, TRP or antenna panel, etc.) can perform measurements to facilitate wireless communication. Examples of such measurements include measurements associated with beam management procedures, channel state information (CSI) measurements for measurement reporting purposes, measurements for cell detection, selection, reselection or handover, and measurements for channel access, side link node detection, etc. In some cases, node 505 may be co-located with one or more other nodes 510 (shown as a group of co-located nodes 510). Node 510 may include UE, TRP or antenna panel, etc. In some aspects, node 505 and node 510 may be nodes of the same type (e.g., node 505 and node 510 may all be TRPs, all UEs or all antenna panels). Node 510 may also perform measurements, such as the measurements described in conjunction with node 505. Based at least in part on the co-location condition, nodes 505 and 510 may be considered to be co-located with each other.

[0087] Measurements performed by nodes that are co-located with each other (such as within a "coherence distance", which may be based at least in part on the distance within which a channel remains coherent) may not be independent between nodes. The coherence distance is a distance that defines an area (e.g., a radius) within which changes in signal strength due to reflections from surfaces between a transmitter and a receiver are expected to be below a threshold. For example, given a frequency f c , then the coherence distance can be defined as λ / 4, where λ = c / f c . For example, the measurement information determined by the first node 505 / 510 may be used by the second node 505 / 510 for some purposes, depending on the type of measurement information. This measurement information has typically been determined and utilized individually by each node 505 / 510. However, more and more nodes may co-locate with each other. For example, multiple UEs (such as smart phones, shown as nodes 505 / 510) may be located in a vehicle and may move together and be positioned in close proximity to each other. As another example, a vehicle may be equipped with a modem (e.g., node 505), and one or more UEs (e.g., node 510) may be located in the vehicle. As another example, two or more antenna panels or TRPs (e.g., node 510) may be mounted on a vehicle and associated with a controller such as a vehicle UE (V-UE) or a network node (e.g., node 505). If each of these co-located nodes 505 and 510 performs measurements independently of each other, a large amount of reporting or configuration overhead may result, the measurement load may increase, and the wireless communication performance of the co-located nodes 505 and 510 may be suboptimal relative to coordinating measurements between the co-located nodes 505 and 510 (thereby reducing the overhead and measurement resource usage associated with performing redundant measurements, among other benefits) or performing combined measurement reporting (thereby reducing reporting overhead, among other benefits).

[0088] Some techniques described herein provide for sharing of measurement information between co-located nodes 505 and 510, as shown in reference numeral 515. In some aspects, nodes 505 and 510 identify a group of co-located nodes (e.g., node 505 may identify node 510 as being associated with a co-located condition relative to node 505) and share measurement information between each other. Nodes 505 and 510 may use shared measurement information to reduce the processing complexity of beam / TRP / cell detection, reduce individual measurement load, provide combined measurement reports to network node 520, and the like. Thus, processing efficiency is improved, measurement load is reduced, and reporting overhead is reduced. In some other aspects, network node 520 (e.g., network node 110) may use information about the co-located condition of node 505 / 510 to simplify or improve measurement reporting or measurement configuration. For example, network node 520 may use this information to reduce the signaling overhead of redundant measurement reports by simplifying the measurement configuration of node 505 / 510. As another example, the network node 520 may use the information to combine multiple measurements (e.g., by jointly evaluating measurements from multiple nodes 505 / 510) to improve communications and configuration with the nodes 505 and 510. Thus, efficiency is increased, throughput is increased, and performance of wireless communications between the nodes 505 / 510 and the network node 520 is improved.

[0089] As shown, signaling between network node 520 and nodes 505 / 510 may include, for example, measurement configuration, measurement reporting, co-location indication, etc. Such signaling is described in more detail below.

[0090] Figure 6 600 is a diagram illustrating an example of sharing measurement information between co-located nodes according to the present disclosure. As shown, example 600 includes a node 605 (e.g., node 505) associated with a group of nodes 610 (e.g., node 510) and a network node 615 (e.g., network node 110, network node 520). In example 600, node 605 and a group of nodes 610 are co-located with each other. A group of nodes 610 may include one or more nodes. Node 605 and a group of nodes 610 may be collectively referred to as a plurality of co-located nodes. A plurality of co-located nodes include two or more nodes. Node 605 may include, for example, UE 120, TRP, or antenna panel, etc. Node 610 may include, for example, UE 120, TRP, or antenna panel, etc.

[0091] A TRP may include a DU and / or a RU. A TRP may be associated with an access node controller (ANC) such as a CU. A TRP may provide wireless connectivity to a UE. A UE may communicate with one or more TRPs at a time. TRPs may be distinguished by a parameter called a control source set (CORESET) pool index. A first TRP may be assigned a first CORESET pool index, and a second TRP may be assigned a second CORESET pool index. Communications associated with a given TRP may be assigned a corresponding CORESET pool index.

[0092] like Figure 6 As shown by reference numeral 620, a network node 605 may discover a group of nodes 610. For example, the node 605 may discover other nodes including the group of nodes 610. In some aspects, the group of nodes 610 may discover the node 605. In some aspects, a first node in the group of nodes 610 may discover a second node in the group of nodes 610. For example, the group of nodes 610 and the node 605 may discover each other. References herein to a node 605 discovering a group of nodes 610 should be understood to also apply to a node 610 or another node 610 discovering the node 605.

[0093] In some aspects, the node 605 may discover a set of nodes 610 based at least in part on information received from the network node 615. For example, the network node 615 may provide information identifying a set of nodes 610 and / or other nodes to the node 605, and the node 605 may discover the set of nodes 610 based on the information. In some implementations, the information may identify the set of nodes 610 and / or other nodes based at least in part on the node 610 having a threshold distance from the set of nodes 605 and / or other nodes. In some other implementations, the information may identify the set of nodes 605 and / or other nodes based at least in part on the grouping of the set of nodes 610 and / or other nodes belonging to the same group as the node 610 (e.g., a group of TRPs of the same gNB, a group of antenna panels of the same V-UE, etc.).

[0094] In other aspects, the node 605 may discover a group of nodes 610 based at least in part on a sidelink interface. For example, the node 605 may discover a group of co-located nodes using a sidelink discovery procedure, such as a solicitation-based sidelink discovery procedure or an advertisement-based sidelink discovery procedure. In other aspects, the node 605 may discover a group of nodes 610 based at least in part on a RAT interface, such as a WiFi interface, a Bluetooth interface, etc. For example, the node 610 may discover a group of nodes 610 using a discovery and / or communication procedure associated with a RAT interface.

[0095] As shown at reference numeral 625, the node 605 may identify a set of nodes 610 that are co-located with respect to the node 605. In some aspects, the node 605 may identify that the set of nodes 610 is associated with a co-location condition. In some aspects, the node 605 may select a set of nodes 610 from a plurality of nodes identified via discovery at reference numeral 620 based at least in part on the co-location condition. For example, the node 605 may select nodes that are associated with the co-location condition.

[0096] In some aspects, the node 605 may identify a group of nodes 610 based at least in part on information communicated between the group of nodes 610. For example, the communicated information may include location information, measurement information, etc. "Measurement information" is measurement information related to a group of nodes 610. For example, the measurement information may include measurement information obtained before identifying a group of nodes 610. In some aspects, the measurement information may include historical measurement information, such as measurement information obtained during an earlier time window. In some aspects, the measurement information may include measurement information based at least in part on measurements performed by the node 605, measurements performed by a group of nodes 610, measurements performed by another device, or a combination thereof. In some aspects, the node 605 may identify a co-located node based at least in part on the communicated information indicating that the node is within a threshold distance of the node 605 or is associated with a moving speed or rate that is lower than a threshold speed or rate difference relative to the node 605. In some aspects, the node 605 may identify a co-located node based at least in part on the measurement information being within a threshold (e.g., a similarity threshold) of the node 605's separately determined (its own) measurement information.

[0097] In some aspects, the node 605 may identify a group of nodes 610 based at least in part on the co-location indication received from the network node 615. The co-location information may include information identifying a group of nodes 610 as being co-located with the node 605. For example, the co-location information may indicate a plurality of co-located nodes including the node 605 and the group of nodes 610. The network node 615 may identify the plurality of co-located nodes based at least in part on measurements reported to the network node 615 by the plurality of co-located nodes, current location information and / or earlier location information associated with the plurality of co-located nodes, and / or the like. In some aspects, the network node 615 may provide the co-location indication based at least in part on a request from the node 605 or the node 610. For example, the request may be associated with identifying a group of nodes 610 (e.g., the request may instruct the network node 615 to provide the co-location indication). In some aspects, the network node 615 may configure the node 605 and / or one or more nodes 610 to identify the co-located nodes based at least in part on the request. For example, the network node 615 may configure the nodes 605 / 610 to perform measurements (such as sidelink measurements) and report measurement information to the network node 615 or to other nodes 605 / 610 based at least in part on these measurements. The network node 615 or nodes 605 / 610 may use such measurement information to identify a group of nodes 610.

[0098] As shown in reference numeral 630, the node 605 and a group of nodes 610 may share measurement information with each other. In some aspects, all nodes 605 / 610 may share measurement information with each other (such as by using a broadcast or multicast configuration or sending the measurement information via one or more unicast links). In some aspects, the node 605 may selectively share the measurement information with the node 610, or the node 610 may selectively share the measurement information with the node 605. In some aspects, the node 605 / 610 may selectively send the measurement information based at least in part on the configuration received from the network node 615. For example, the configuration may indicate how the node 605 / 610 should share the measurement information (e.g., the resource on which the measurement information is sent, the period or condition associated with the shared measurement information, the interface associated with sending the measurement information, the node 605 / 610 with which the measurement information is shared, etc.). For another example, the configuration may indicate which measurement information should be shared (e.g., measurement information of a specific type, measurement information about a specific node, etc.).

[0099] In some aspects, the nodes 605 / 610 may selectively share measurement information based at least in part on a measurement sharing indication from the network node 615. For example, the measurement sharing information may include or may be included in the above configuration. For another example, the measurement sharing indication may include a signal that triggers the node 605 / 610 to send measurement information to other co-located nodes.

[0100] In some aspects, the nodes 605 / 610 may share measurement information based at least in part on the capabilities of the nodes. For example, the nodes 605 / 610 may selectively transmit measurements based at least in part on the measurement capabilities of the nodes 605 / 610, the transmission capabilities of the nodes 605 / 610, and the like.

[0101] In some aspects, the node 605 / 610 may selectively share measurement information based at least in part on the battery charge of the node. For example, the node 605 / 610 may determine and / or send measurement information when the battery charge of the node 605 / 610 meets a threshold, and may stop determining and / or sharing measurement information when the battery charge of the node 605 / 610 fails to meet the threshold.

[0102] In some aspects, a node 605 / 610 may selectively share measurement information based at least in part on a measurement metric at the node. For example, a node 605 / 610 may send measurement information if a measurement metric (or a set of measurement metrics) satisfies a threshold (or a set of thresholds). The measurement metric may include, for example, RSRP, RSRQ, RSSI, signal to interference plus noise ratio (SINR), the number of beams detected by the node 605 / 610 (e.g., the number of nodes associated with a threshold measurement value), or a combination thereof.

[0103] In some aspects, the nodes 605 / 610 may selectively share measurement information based at least in part on one or more negotiations between the node 605 and a group of nodes 610. For example, the nodes 605 / 610 may communicate with each other to identify a configuration for sharing measurements, such as a configuration based at least in part on a measurement metric, capability, battery level, device type, etc. The negotiation may include a first one of the nodes 605 and 610 providing a suggested configuration, and a second one of the nodes 605 and 610 accepting and / or modifying the suggested configuration.

[0104] In some aspects, the node 605 / 610 may selectively share the measurement information based at least in part on an information ownership parameter. The information ownership parameter includes information indicating an entity that controls whether a set of information is shared. For example, the measurement information may be assigned an information ownership parameter indicating which node 605 / 610 is allowed to share the measurement information. For another example, the information ownership parameter may indicate a subscriber associated with the node 605 / 610, and the subscriber's preferences may control whether the node 605 / 610 shares the measurement information and / or which measurement information is shared.

[0105] In some aspects, node 605 can be a cluster head of multiple co-located nodes. In some aspects, a cluster head is a node among multiple nodes (in this example, multiple co-located nodes 605 / 610). Multiple nodes can be referred to as a cluster. The cluster head can collect measurement information from other nodes of the cluster. In some aspects, the cluster head can be responsible for processing the collected measurement information, reporting the collected measurement information, combining the collected measurement information and / or using the collected measurement information. For example, the cluster head can generate a combined measurement report, can perform detection based at least in part on the measurement information, can evaluate the criteria for sending the measurement report, can send the measurement report, or can trigger a conditional handover based at least in part on the measurement information, as described elsewhere herein. In some aspects, the cluster head of the cluster can be a V-UE, a controller of one or more IoT devices, etc.

[0106] In some aspects, the measurement information may include information regarding beam measurements. For example, the measurement information may be based at least in part on measurements performed as part of a beam management procedure, such as information regarding Figure 4 As described. For another example, the measurement information may be based at least in part on measurements performed as part of a sidelink beam management procedure. In some aspects, the measurement information may include information about TRP measurements. For example, the measurement information may be based at least in part on measurements performed on one or more reference signals sent by the TRP. In some aspects, the measurement information may include information about cell measurements. For example, the measurement information may be based at least in part on measurements performed on one or more reference signals associated with a cell, such as SSB measurements, CSI-RS measurements, DMRS measurements, etc.

[0107] In some aspects, the measurement information may include information associated with a set of detected beams. In some aspects, the measurement information may include information associated with a set of detected TRPs. In some aspects, the measurement information may include information associated with a set of detected cells. For example, the measurement information may include measurement metrics associated with the detected beams, TRPs and / or cells (such as RSRP, RSSI, RSRQ, signal-to-noise ratio (SNR), SINR, etc.). In some aspects, the measurement metrics may be instantaneous metrics (such as layer 1 metrics, which may be unfiltered metrics). In some aspects, the measurement metrics may be filtered metrics (such as layer 3 metrics). In some aspects, the measurement metrics may be statistical values, such as percentages (e.g., channel busy rate, channel occupancy, etc.). In some aspects, the measurement information may include time information, such as the time interval at which the beams, TRPs or cells are detected. In some aspects, the measurement information may include location information, such as geographic information, spatial information, etc. For example, the location information may relate to the detected beams, TRPs or cells. In some aspects, the location information may indicate an absolute position (e.g., relative to a fixed position). In some aspects, the location information may indicate a relative position. For example, the relative position may be relative to the node 605 / 610 reporting the measurement information, the node 605 / 610 receiving the position information, an average of the positions of the node 605 / 610 reporting the measurement information and the node 605 / 610 receiving the position information, a common reference (such as spatial information relative to a common direction of the node 605 / 610 reporting the measurement information and the node 605 / 610 receiving the position information), etc. In some aspects, the measurement information may include information indicating an estimated propagation delay or distance. In some aspects, the measurement information may include an indication of resources associated with the detected or measured reference signal or cell. For example, the resources may include time resources, frequency resources, synchronization grating positions, etc.

[0108] In some aspects, the measurement information may include an indication that one or more beams, TRPs, or cells were not detected. For example, the indication may indicate that detection of the one or more beams, TRPs, or cells has ceased. In some aspects, the one or more beams, TRPs, or cells that have ceased detection are associated with a measurement metric that has fallen below a threshold, etc.

[0109] In some aspects, the measurement information may include information about one or more sidelink devices. For example, at least a portion of the information described above as being associated with a cell, TRP, or beam may be determined about a sidelink device (e.g., UE 120) and sent as measurement information.

[0110] In some aspects, the measurement information may include a measurement report, a compressed measurement report, or a portion of a measurement report. For example, a node 605 / 610 may send a measurement report (or a simplified version of a measurement report, such as a compressed measurement report or a portion of a measurement report) to another node 605 / 610.

[0111] In some aspects, the measurement information may be sent periodically. For example, the node 605 / 610 may send the measurement information according to periodicity. In some aspects, the measurement information may be sent on demand. For example, the node 605 / 610 may send the measurement information in conjunction with receiving a trigger signal. In some aspects, the measurement information may be sent at least in part based on a trigger event. For example, the measurement information may be associated with a condition such as a reporting condition. The node 605 / 610 may send the measurement information at least in part based on determining that the reporting condition is met. In some aspects, the node 605 / 610 may send the measurement information using a combination of periodic transmission, on-demand transmission, or event-triggered transmission. For example, some measurement information may be sent periodically, while other measurement information may be sent on demand or according to a trigger event.

[0112] In some aspects, the node 605 / 610 may send a notification associated with the measurement information. The notification may indicate that the node 605 / 610 has measurement information that may be shared with other co-located nodes 605 / 610. In some aspects, the co-located node 605 / 610 may provide a response to the notification, such as a request for measurement information or a trigger signal.

[0113] In some aspects, the node 605 / 610 may send a solicitation for measurement information. For example, the solicitation may request all available measurement information of the co-located node, specific measurement information, types of measurement information, measurement information within a specific time range, etc. In some aspects, the co-located node 605 / 610 may send measurement information based at least in part on the solicitation, such as all measurement information available for the network node or the measurement information requested by the solicitation.

[0114] As shown by reference numeral 635, in some aspects, node 605 may communicate using communication parameters based at least in part on the measurement information. The communication may include beam detection (e.g., in conjunction with Figure 4The communication parameter may indicate, for example, a priority associated with a beam, a TRP, or a cell, or one or more parameters for beam, TRP, or cell detection. In TRP detection, the node 605 may monitor a reference signal sent by the TRP for the purpose of communicating with the TRP. In cell detection, the node 605 may monitor a reference signal associated with a cell for the purpose of cell selection, reselection, handover, conditional handover, etc. In some aspects, the node 605 may identify resources associated with a cell, a TRP, or a beam, a direction associated with a cell, a TRP, or a beam, a location associated with a cell, a TRP, a beam, etc. based at least in part on the measurement information. The node 605 may use the information to perform detection.

[0115] In some aspects, the node 605 may prioritize beams, TRPs, or cells based at least in part on measurement information indicating that the beams, TRPs, or cells are detected. For example, when performing detection, the node 605 may monitor prioritized beams, TRPs, or cells more frequently or earlier than unprioritized (or deprioritized) beams, TRPs, or cells. In some aspects, the node 605 may deprioritize beams, TRPs, or cells based at least in part on measurement information indicating that the beams, TRPs, or cells are not detected. For example, when performing detection, the node 605 may monitor unprioritized beams, TRPs, or cells less frequently or later than unprioritized (or prioritized) beams, TRPs, or cells. In some aspects, the node 605 may determine the order and / or priority of beams, cells, or TRPs based at least in part on measurement information, and may perform detection according to the order and / or priority.

[0116] As shown in reference numeral 640, in some aspects, the node 605 may send a measurement report based at least in part on the measurement information. For example, the measurement report may include a CSI report, a neighboring cell measurement report, a beam report, etc. In some aspects, the node 605 may send a random access channel (RACH) message or another form of signaling associated with accessing a TRP or a cell based at least in part on the measurement information. Thus, the node 605 may access a cell or a TRP based at least in part on the measurement information. In some aspects, the node 605 may use the measurement information to report the node 605.

[0117] As shown by reference numeral 645, in some aspects, the node 605 may trigger a conditional handover based at least in part on the measurement information. A conditional handover is a handover from one network node to another network node (e.g., a transfer of the context of the node 605). The conditional handover is associated with a condition at the node 605. If the condition is met, the node 605 may trigger the conditional handover. In this example, if the measurement information meets the condition, the node 605 may trigger the conditional handover.

[0118] In example 600 , node 605 may perform any one or more of the operations illustrated by reference numerals 635 , 640 , and 645 .

[0119] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0120] Figure 7 700 is a diagram illustrating an example of collaborative measurement as configured by a network node according to the present disclosure. As shown, example 700 includes multiple co-located nodes 705 and network nodes 710 (e.g., network node 110, network node 520, network node 615). A group of co-located nodes 710 includes one or more nodes. Node 705 may include, for example, UE 120, TRP, or antenna panel, etc. In example 700, network node 710 may use information about the co-location of node 705 to simplify or improve measurement and / or configuration of network node 710.

[0121] like Figure 7 As shown by reference numeral 715, the network node 710 can identify multiple co-located nodes 705. In some aspects, the network node 710 can use information about Figure 6 625 to identify the plurality of co-located nodes 705. In some aspects, a node 705 in the plurality of co-located nodes 705 may provide an indication that the plurality of co-located nodes are co-located. For example, the plurality of co-located nodes 705 may be as described with respect to Figure 6 The co-located nodes 705 identify each other as described in the figure 625, and provide an indication to the network node 710 that the multiple co-located nodes 705 are co-located.

[0122] In some aspects, the network node 710 may identify multiple co-located nodes 705 based at least in part on multiple co-located nodes 705 belonging to the same group. For example, the network node may identify multiple co-located nodes 705 based at least in part on the fact that the multiple co-located nodes 705 are a group of TRPs of the same network node (such as the TRP of the same mobile cell or mobile IAB node), are different V-UEs of the same train (where each V-UE is installed on a different train car of the train), etc. In the above example, the multiple co-located nodes 705 may have a fixed spatial relationship with each other in terms of position, orientation and / or distance. In some aspects, one or more of the multiple co-located nodes 705 (e.g., the TRP of the same mobile cell or mobile IAB node) may signal the network node 710 (e.g., another TRP of the same mobile cell or mobile IAB node) about the fixed spatial relationship, and the network node 710 may use the information to configure measurements, evaluate measurements, etc.

[0123] As shown in the figure numeral 720, in some aspects, the network node 710 may receive location information indicating the location of a first node 705 among a plurality of co-located nodes 705. The location may be relative to a second node 705 among a plurality of co-located nodes. For example, a DU and a CU (or a CU and another network node) may exchange TRP information via an F1 interface. The TRP information may indicate a geographic location or orientation of a TRP associated with the DU. In a mobile system including a plurality of co-located nodes 705, the geographic location and orientation are not fixed. By signaling the location (e.g., location, orientation, and / or distance) of the first node 705 relative to the second node 705, the signaling overhead is reduced relative to repeatedly signaling the locations of the two nodes 705 due to changes in location information.

[0124] As indicated by reference numeral 725, the network node 710 may configure measurements for at least one of the plurality of co-located nodes 705. For example, the network node 710 may send one or more measurement configurations to the at least one node 705. In some aspects, at least one measurement configuration may be based at least in part on the co-location of the plurality of nodes 705. For example, given a first measurement, a second measurement, and a third measurement, the network node 710 may configure the first node 705 to perform the first measurement, the second node 705 to perform the second measurement, and the third node 705 to perform the third measurement. Thus, relative to redundantly configuring the plurality of nodes 705 to perform the same measurement, overhead, measurement resources, and measurement load may be reduced. In some aspects, as described elsewhere herein, at least one measurement configuration may instruct an appropriate subset of the nodes 705 to send measurement reports, thereby reducing signaling overhead for redundant measurement reports.

[0125] As shown at 730, the plurality of nodes 705 may perform measurements. For example, at least one of the plurality of nodes 705 may perform measurements according to one or more measurement configurations described in conjunction with reference numeral 725. In some aspects, at least one of the nodes 705 may share measurement information with other nodes in the plurality of co-located nodes 705, such as in conjunction with Figure 6 Described in detail.

[0126] As indicated by reference numeral 735, the plurality of nodes 705 may send measurement information to the network node 710 based at least in part on the measurements. For example, at least one node 705 of the plurality of nodes 705 may send the measurement information to the network node 710. In some aspects, the measurement information may include a measurement report generated based at least in part on the measurements indicated by reference numeral 730. For example, at least one node 705 may generate a measurement report and may send the measurement report to the network node 710. In some aspects, at least one node 705 may receive measurement information from other nodes 705, and the at least one node 705 may use the received measurement information to generate the measurement report, as described above with respect to Figure 6Therefore, compared to configuring each node 705 to perform measurements and measurement reporting individually, overhead is reduced.

[0127] In some aspects, the network node 710 may combine measurement information of multiple nodes 705. For example, the network node 710 may jointly evaluate the measurement information by determining an average measurement metric, a composite channel matrix, or a CSI parameter, among others.

[0128] As shown by reference numeral 740, the network node 710 may schedule communications of the plurality of co-located nodes 705 based at least in part on the measurement information. For example, the network node 710 may schedule communications of a first node 705 from which no measurement information has been received. The network node 710 may schedule communications of the first node 705 based at least in part on the measurement information received from a second node 705 in the plurality of co-located nodes 705. Thus, the network node 710 may use the co-located nature of the nodes 705 to reduce overhead and improve scheduling efficiency.

[0129] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0130] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a node in accordance with the present disclosure. Example process 800 is an example in which a node (eg, node 505, node 510, node 605, node 610, node 705) performs operations associated with cooperative measurement of co-located devices.

[0131] like Figure 8 As shown, in some aspects, process 800 may include identifying a set of co-located nodes (block 810). For example, a node (e.g., using Fig.10 The communication manager 140 and / or identification component 1008 depicted in FIG. 1004 may identify a set of co-located nodes. In some aspects, the set of co-located nodes is associated with a co-location condition relative to the node, as described above.

[0132] like Figure 8 As further shown, in some aspects, process 800 may include receiving measurement information from the set of co-located nodes regarding at least one of: a beam measurement, a TRP measurement, or a cell measurement (block 820). For example, the node (e.g., using Fig.10 The communication manager 140 and / or receiving component 1002 depicted in the figure may receive measurement information about at least one of the following: beam measurements, TRP measurements, or cell measurements, as described above, from the group of co-located nodes.

[0133] like Figure 8As further shown, in some aspects, process 800 may include communicating using communication parameters based at least in part on the measurement information (block 830). Fig.10 The communication manager 140 and / or the measurement component 1010 depicted in FIG. 100 may communicate using communication parameters based at least in part on the measurement information, as described above. As described herein, communicating using communication parameters may include performing beam detection, performing cell detection, performing TRP detection, and / or de-prioritizing or prioritizing beams, TRPs, or cells for detection, and the like.

[0134] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0135] In a first aspect, communicating using the communication parameters further comprises performing at least one of: beam detection, TRP detection, or cell detection based at least in part on the measurement information.

[0136] In a second aspect, either alone or in combination with the first aspect, communicating using communication parameters also includes de-prioritizing a beam, TRP, or cell based at least in part on measurement information indicating that the beam, TRP, or cell for detection was not detected.

[0137] In a third aspect, either alone or in combination with one or more of the first and second aspects, communicating using communication parameters also includes prioritizing the beam, TRP or cell based at least in part on measurement information indicating that the beam, TRP or cell for detection is detected.

[0138] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes sending a measurement report based at least in part on the measurement information.

[0139] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes triggering a conditional handover based at least in part on the measurement information.

[0140] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, identifying a set of co-located nodes is based at least in part on a co-located indication received from a network node.

[0141] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes sending a request associated with identifying a set of co-located nodes to a network node, wherein the co-location indication is based at least in part on the request.

[0142] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, identifying a group of co-located nodes is based at least in part on communicating at least one of location information or measurement information with the group of co-located nodes.

[0143] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, the measurement information is first measurement information, and wherein the method further comprises performing the measurement, and selectively sending second measurement information to a group of co-located nodes based at least in part on the measurement.

[0144] In a tenth aspect, alone or in combination with one or more of the first to seventh aspects, selectively sending the second measurement information is based at least in part on a configuration received from the network node.

[0145] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, selectively sending the second measurement information is based at least in part on receiving one or more solicitations for the second measurement information from a group of co-located nodes.

[0146] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 800 includes sending a notification associated with the second measurement information.

[0147] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the second measurement information is selectively sent based at least in part on a measurement sharing configuration from a network node, capabilities of the node, a battery charge of the node, a measurement metric at the node, one or more negotiations between the node and a group of co-located nodes, or at least one of information ownership parameters.

[0148] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the measurement information includes at least one of information about a set of detected beams, information about a set of detected TRPs, information about a set of detected cells, an indication that one or more beams, TRPs or cells are not detected, a measurement report, a compressed measurement report or a portion of a measurement report.

[0149] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, receiving the measurement information is based at least in part on the node being a cluster head associated with a group of co-located nodes.

[0150] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, identifying a set of co-located nodes further comprises identifying a set of co-located nodes based at least in part on associating the set of co-located nodes with a co-location condition.

[0151] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0152] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network node in accordance with the present disclosure. Example process 900 is an example in which a network node (eg, network node 520, network node 615, network node 710) performs operations associated with cooperative measurement of co-located devices.

[0153] like Fig. 9 As shown, in some aspects, process 900 may include identifying a plurality of co-located nodes (block 910). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or identification component 1108 depicted in FIG. 10A may identify multiple co-located nodes, as described above.

[0154] like Fig. 9 As further shown, in some aspects, process 900 may include configuring measurements for a group of nodes in a plurality of co-located nodes, the group of nodes including at least two nodes (block 920). Fig.11 The communication manager 140 and / or configuration component 1110 depicted in FIG. 1 may configure measurements of a group of nodes in a plurality of co-located nodes, as described above. The group of nodes may include at least two nodes.

[0155] like Fig. 9 As further shown, in some aspects, process 900 may include receiving measurement information from the set of nodes based at least in part on the measurement (block 930). Fig.11 The depicted communications manager 150 and / or receiving component 1102) can receive measurement information from the set of nodes based at least in part on the measurement, as described above.

[0156] like Fig. 9 As further shown, in some aspects, process 900 may include scheduling communications associated with a plurality of co-located nodes based at least in part on the measurement information (block 940). Fig.11The depicted communications manager 140 and / or scheduling component 1112) may schedule communications associated with the plurality of co-located nodes based at least in part on the measurement information, as described above. In some aspects, the plurality of co-located nodes may include a plurality of UEs, and the network node may schedule communications for the plurality of UEs. Additionally or alternatively, the plurality of co-located nodes may include a plurality of TRPs or antenna panels, and the network node may schedule communications for UEs associated with (e.g., communicating with) the plurality of TRPs or antenna panels.

[0157] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0158] In a first aspect, scheduling communications associated with a plurality of co-located nodes further comprises scheduling communications associated with a node of the plurality of co-located nodes from which no measurement information was received, wherein the communications are scheduled based at least in part on the measurement information.

[0159] In a second aspect, alone or in combination with the first aspect, scheduling communications associated with a plurality of co-located nodes is based at least in part on combining measurement information received from two or more of the plurality of co-located nodes.

[0160] In a third aspect, alone or in combination with one or more of the first and second aspects, identifying the plurality of co-located nodes is based at least in part on receiving an indication from one or more of the plurality of co-located nodes that the plurality of co-located nodes are co-located.

[0161] In a fourth aspect, alone or in combination with one or more of the first to third aspects, identifying the plurality of co-located nodes is based at least in part on the plurality of co-located nodes belonging to a same group.

[0162] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 900 includes receiving location information indicating a location of a first node among a plurality of co-located nodes, wherein the location is relative to a second node among the plurality of co-located nodes.

[0163] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0164] Fig.101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a node, or a node may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include one or more of identification component 1008 or detection component 1010, etc.

[0165] In some aspects, the apparatus 1000 may be configured to perform Figures 3 to 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more of the processes described herein (such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0166] Receiving component 1002 can receive communications from device 1006, such as reference signals, control information, data communications, or combinations thereof.

[0167] The receiving component 1002 may provide the received communication to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communication and may provide the processed signal to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described nodes.

[0168] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described nodes. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0169] The identifying component 1008 can identify a group of co-located nodes. The receiving component 1002 can receive measurement information about at least one of beam measurement, TRP measurement, or cell measurement from the group of co-located nodes. The detecting component 1010 or the sending component 1004 can communicate using communication parameters based at least in part on the measurement information.

[0170] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of (one or more) components shown in the executable is described as being composed of Fig.10 Another collection of components shown in the figure performs one or more functions.

[0171] Fig.111 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include one or more of an identification component 1108, a configuration component 1110, or a scheduling component 1112, among others.

[0172] In some aspects, the apparatus 1100 may be configured to perform Figures 3 to 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more of the processes described herein (such as Fig. 9 In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0173] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0174] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0175] The identifying component 1108 can identify a plurality of co-located nodes. The configuring component 1110 can configure measurements for a group of nodes in the plurality of co-located nodes. The receiving component 1102 can receive measurement information from the group of nodes based at least in part on the measurements. The scheduling component 1112 can schedule communications associated with the plurality of co-located nodes based at least in part on the measurement information.

[0176] Fig.11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.11 Two or more components shown in may be implemented in a single component, or Fig.11 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The assembly of (one or more) components shown in the executable is described as being composed of Fig.11 Another collection of components shown in the figure performs one or more functions.

[0177] The following provides an overview of some aspects of the disclosure:

[0178] Aspect 1: A method of wireless communication performed by a node, the method comprising: identifying a set of co-located nodes relative to the node; receiving measurement information about at least one of the following from the set of co-located nodes: beam measurement, transmit receive point (TRP) measurement or cell measurement; and communicating using communication parameters based at least in part on the measurement information.

[0179] Aspect 2: The method according to aspect 1, wherein communicating using the communication parameters further comprises performing at least one of the following based at least in part on the measurement information: beam detection, TRP detection, or cell detection.

[0180] Aspect 3: A method according to any one of Aspects 1 to 2, wherein communicating using the communication parameters also includes: deprioritizing the beam, TRP or cell based at least in part on the measurement information indicating that the beam, TRP or cell for detection is not detected.

[0181] Aspect 4: A method according to any one of Aspects 1 to 3, wherein communicating using the communication parameters also includes: prioritizing the beam, TRP or cell based at least in part on the measurement information indicating that the beam, TRP or cell for detection is detected.

[0182] Aspect 5: The method according to any one of aspects 1 to 4, further comprising sending a measurement report based at least in part on the measurement information.

[0183] Aspect 6: The method according to any one of aspects 1 to 5, further comprising triggering a conditional handover based at least in part on the measurement information.

[0184] Aspect 7: The method according to any one of aspects 1 to 6, wherein identifying the set of co-located nodes is based at least in part on a co-located indication received from a network node.

[0185] Aspect 8: The method according to aspect 7, the method further comprising sending a request associated with identifying the set of co-located nodes to the network node, wherein the co-location indication is based at least in part on the request.

[0186] Aspect 9: The method according to any one of aspects 1 to 8, wherein identifying the set of co-located nodes is based at least in part on communicating at least one of location information or measurement information with the set of co-located nodes.

[0187] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the measurement information is first measurement information, and wherein the method further comprises: performing measurement; and selectively sending second measurement information to the group of co-located nodes based at least in part on the measurement.

[0188] Aspect 11: The method according to aspect 10, wherein selectively sending the second measurement information is based at least in part on a configuration received from a network node.

[0189] Aspect 12: The method of aspect 10, wherein selectively sending the second measurement information is based at least in part on receiving one or more solicitations for the second measurement information from the set of co-located nodes.

[0190] Aspect 13: The method according to aspect 10, further comprising sending a notification associated with the second measurement information.

[0191] Aspect 14: A method according to Aspect 10, wherein selectively sending the second measurement information is based at least in part on at least one of: a measurement sharing configuration from a network node, a capability of the node, a battery charge of the node, a measurement metric at the node, one or more negotiation or information ownership parameters between the node and the group of co-located nodes.

[0192] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the measurement information includes at least one of the following: information about a set of detected beams, information about a set of detected TRPs, information about a set of detected cells, an indication that one or more beams, TRPs or cells are not detected, a measurement report, a compressed measurement report or a portion of a measurement report.

[0193] Aspect 16: The method according to any one of aspects 1 to 15, wherein receiving the measurement information is based at least in part on the node being a cluster head associated with the set of co-located nodes.

[0194] Aspect 17: The method according to any one of aspects 1 to 16, wherein identifying the set of co-located nodes further comprises identifying the set of co-located nodes based at least in part on the set of co-located nodes being associated with a co-location condition.

[0195] Aspect 18: A method for wireless communication performed by a network node, the method comprising: identifying a plurality of co-located nodes; configuring measurements for a group of nodes among the plurality of co-located nodes, the group of nodes comprising at least two nodes; receiving measurement information from the group of nodes based at least in part on the measurements; and scheduling communications associated with the plurality of co-located nodes based at least in part on the measurement information.

[0196] Aspect 19: A method according to Aspect 18, wherein scheduling communications associated with the multiple co-located nodes also includes scheduling communications associated with nodes in the multiple co-located nodes from which no measurement information is received, wherein the communications are scheduled at least in part based on the measurement information.

[0197] Aspect 20: The method according to any one of aspects 18 to 19, wherein scheduling communications associated with the plurality of co-located nodes is based at least in part on combining measurement information received from two or more of the plurality of co-located nodes.

[0198] Aspect 21: The method according to any one of aspects 18 to 20, wherein identifying the plurality of co-located nodes is based at least in part on receiving an indication that the plurality of co-located nodes are co-located from one or more of the plurality of co-located nodes.

[0199] Aspect 22: The method according to any one of aspects 18 to 21, wherein identifying the plurality of co-located nodes is based at least in part on the plurality of co-located nodes belonging to the same group.

[0200] Aspect 23: According to the method described in any one of Aspects 18 to 22, the method further includes receiving location information indicating the location of a first node among the multiple co-located nodes, wherein the location is relative to a second node among the multiple co-located nodes.

[0201] Aspect 24: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 23.

[0202] Aspect 25: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 23.

[0203] Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 23.

[0204] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 23.

[0205] Aspect 28: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 23.

[0206] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0207] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0208] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0209] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0210] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A node for wireless communication, the node comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: identifying a set of co-located nodes relative to the node; receiving, from the set of co-located nodes, measurement information regarding at least one of: Beam measurement, Transmit Receive Point (TRP) measurements, or Cell measurements; and Communicating using communication parameters based at least in part on the measurement information.

2. The node of claim 1 , wherein to communicate using the communication parameters, the one or more processors are configured to: Based at least in part on the measurement information, perform at least one of the following: Beam detection, TRP testing, or Cell detection.

3. The node of claim 1 , wherein to communicate using the communication parameters, the one or more processors are configured to: The beam, TRP, or cell is deprioritized based at least in part on the measurement information indicating that the beam, TRP, or cell for detection was not detected.

4. The node of claim 1 , wherein to communicate using the communication parameters, the one or more processors are configured to: The beams, TRPs, or cells are prioritized based at least in part on the measurement information indicating that the beams, TRPs, or cells are detected for detection.

5. The node of claim 1 , wherein the one or more processors are further configured to: A measurement report is sent based at least in part on the measurement information.

6. The node of claim 1 , wherein the one or more processors are further configured to: A conditional handover is triggered based at least in part on the measurement information.

7. The node of claim 1, wherein to identify the set of co-located nodes, the one or more processors are configured to identify the set of co-located nodes based at least in part on a co-location indication of a network node.

8. The node of claim 7, wherein the one or more processors are further configured to: A request associated with identifying the set of co-located nodes is sent to the network node, wherein the co-location indication is based at least in part on the request.

9. A node according to claim 1, wherein to identify the group of co-located nodes, the one or more processors are configured to identify the group of co-located nodes based at least in part on at least one of location information or measurement information communicated together with the group of co-located nodes.

10. The node according to claim 1, wherein the measurement information is first measurement information, and wherein the one or more processors are further configured to: Performing measurements; and Second measurement information is selectively sent to the set of co-located nodes based at least in part on the measurement.

11. The node of claim 10, wherein to selectively send the second measurement information, the one or more processors are configured to selectively send the second measurement information based at least in part on a configuration from a network node.

12. The node of claim 10, wherein to selectively send the second measurement information, the one or more processors are configured to selectively send the second measurement information based at least in part on one or more solicitations for the second measurement information from the set of co-located nodes.

13. The node of claim 10, wherein the one or more processors are further configured to: A notification associated with the second measurement information is sent.

14. The node of claim 10, wherein to selectively send the second measurement information, the one or more processors are configured to selectively send the second measurement information based at least in part on at least one of: Measurement sharing configuration from network nodes, The capabilities of the node, the battery level of the node, The measurement metric at the node, one or more negotiations between the node and the set of co-located nodes, or Information ownership parameters.

15. The node according to claim 10, wherein the measurement information comprises at least one of: Information about a set of detected beams, Information about a set of detected TRPs, Information about a set of detected cells, An indication that one or more beams, TRPs or cells were not detected, Measurement reports, Compressed measurement reports, or Part of the measurement report.

16. The node of claim 10, wherein to receive the measurement information, the one or more processors are configured to receive the measurement information based at least in part on the node being a cluster head associated with the set of co-located nodes.

17. The node of claim 10, wherein to identify the set of co-located nodes, the one or more processors are configured to identify the set of co-located nodes based at least in part on the set of co-located nodes being associated with a co-location condition.

18. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: Identify multiple co-located nodes; configuring measurements for a group of nodes in the plurality of co-located nodes, the group of nodes comprising at least two nodes; receiving measurement information from the set of nodes based at least in part on the measurements; as well as Communications associated with the plurality of co-located nodes are scheduled based at least in part on the measurement information.

19. The network node of claim 18, wherein to schedule communications associated with the plurality of co-located nodes, the one or more processors are configured to: Communications associated with a node of the plurality of co-located nodes from which no measurement information was received are scheduled based at least in part on the measurement information.

20. A network node according to claim 18, wherein, in order to schedule communications associated with the multiple co-located nodes, the one or more processors are configured to schedule communications associated with the multiple co-located nodes based at least in part on measurement information received from two or more of the multiple co-located nodes.

21. The network node of claim 18, wherein to identify the plurality of co-located nodes, the one or more processors are configured to identify the plurality of co-located nodes based at least in part on an indication from one or more of the plurality of co-located nodes that the plurality of co-located nodes are co-located.

22. The network node of claim 18, wherein to identify the plurality of co-located nodes, the one or more processors are configured to identify the plurality of co-located nodes based at least in part on the plurality of co-located nodes belonging to a same group.

23. The network node of claim 18, wherein the one or more processors are further configured to: Position information indicating a position of a first node of the plurality of co-located nodes is received, wherein the position is relative to a second node of the plurality of co-located nodes.

24. A method of wireless communication performed by a node, the method comprising: identifying a set of co-located nodes relative to the node; receiving, from the set of co-located nodes, measurement information regarding at least one of: Beam measurement, Transmit Receive Point (TRP) measurements, or Cell measurements; and Communicating using communication parameters based at least in part on the measurement information.

25. The method of claim 24, wherein communicating using the communication parameters further comprises: Based at least in part on the measurement information, perform at least one of the following: Beam detection, TRP testing, or Cell detection.

26. The method of claim 24, wherein communicating using the communication parameters further comprises: The beam, TRP, or cell is deprioritized based at least in part on the measurement information indicating that the beam, TRP, or cell for detection was not detected.

27. A method of wireless communication performed by a network node, the method comprising: Identify multiple co-located nodes; configuring measurements for a group of nodes in the plurality of co-located nodes, the group of nodes comprising at least two nodes; receiving measurement information from the set of nodes based at least in part on the measurements; as well as Communications associated with the plurality of co-located nodes are scheduled based at least in part on the measurement information.

28. The method of claim 27, wherein scheduling communications associated with the plurality of co-located nodes further comprises: Communications associated with a node of the plurality of co-located nodes from which no measurement information was received are scheduled, wherein the communications are scheduled based at least in part on the measurement information.

29. The method of claim 27, wherein scheduling communications associated with the plurality of co-located nodes is based at least in part on combining measurement information received from two or more of the plurality of co-located nodes.

30. The method of claim 27, wherein identifying the plurality of co-located nodes is based at least in part on receiving an indication from one or more of the plurality of co-located nodes that the plurality of co-located nodes are co-located.

Images