Inter-network node beam coordination for beamforming procedures

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may receive, from another network node, an indication of a first selected beam sequence associated with a first beamforming procedure. The network node may select a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence. The network node may perform the second beamforming procedure based at least in part on the second selected beam sequence. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek patent application No. 20220100691, entitled "INTER-NETWORK NODE BEAMCOORDINATION FOR BEAMFORMING PROCEDURES", filed on August 16, 2022 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 inter-network node beam coordination for beamforming procedures. 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 side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[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) (CP-OFDM) with cyclic prefix (CP) on the downlink, 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; and 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 network node. The method may include receiving an indication of a first selected beam sequence associated with a first beamforming procedure from another network node. The method may include selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence. The method may include performing the second beamforming procedure based at least in part on the second selected beam sequence.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node. The method may include sending an indication of the first selected beam sequence to another network node. The method may include receiving an indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node from the another network node.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a first selected beam sequence associated with a first beamforming procedure from another network node. The one or more processors may be configured to select a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence. The one or more processors may be configured to perform the second beamforming procedure based at least in part on the second selected beam sequence.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to select a first selected beam sequence associated with a first beamforming procedure performed by the network node. The one or more processors may be configured to send an indication of the first selected beam sequence to another network node. The one or more processors may be configured to receive an indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node from the another network node.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive an indication of a first selected beam sequence associated with a first beamforming procedure from another network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to select a second selected beam sequence associated with a second beamforming procedure executed by the network node based at least in part on the indication of the first selected beam sequence. The set of instructions, when executed by one or more processors of the network node, may cause the network node to execute the second beamforming procedure based at least in part on the second selected beam sequence.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to select a first selected beam sequence associated with a first beamforming procedure performed by the network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send an indication of the first selected beam sequence to another network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive an indication of a second selected beam sequence associated with a second beamforming procedure performed by the other network node from the other network node.

[0013] Some aspects described herein are directed to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, an indication of a first selected beam sequence associated with a first beamforming procedure. The apparatus may include means for selecting, based at least in part on the indication of the first selected beam sequence, a second selected beam sequence associated with a second beamforming procedure performed by the apparatus. The apparatus may include means for performing the second beamforming procedure based at least in part on the second selected beam sequence.

[0014] Some aspects described herein are directed to an apparatus for wireless communication. The apparatus may include means for selecting a first selected beam sequence associated with a first beamforming procedure performed by the apparatus. The apparatus may include means for sending an indication of the first selected beam sequence to a network node. The apparatus may include means for receiving, from the network node, an indication of a second selected beam sequence associated with a second beamforming procedure performed by the network node.

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

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively 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 of 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 network node and a user equipment 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 beamforming architecture supporting beamforming for high frequency communications according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a channel state information reference signal beam management procedure according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a network node sensing procedure according to the present disclosure.

[0025] Figure 7 is a diagram of an example associated with inter-network node beam coordination for a beamforming procedure according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

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

[0029] Fig.11 is a diagram of an example apparatus 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 other than the various aspects of the disclosure set forth herein 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 present claim.

[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 may be implemented using hardware, software, or a combination thereof. Whether such 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 applicable to other RATs, such as 3G RAT, 4G RAT and / or 5G and beyond (e.g., 6G) RATs.

[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), 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. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more 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 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, 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. The network node 110 may include, for example, 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 or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0035] In some examples, 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 ​​the network node 110 and / or the network node 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., a radius of several kilometers) 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 network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile network node 110 (e.g., a mobile network node).

[0036] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one 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 is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0038] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, 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 network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node 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 be or 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 or wired 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, which may communicate with a network node, 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, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0042] In general, 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.

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary) using one or more side link channels. 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.

[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 range designations 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] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive an indication of a first selected beam sequence associated with a first beamforming procedure from another network node; select a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence; and perform the second beamforming procedure based at least in part on the second selected beam sequence. Additionally or alternatively, communication manager 150 may select the first selected beam sequence associated with the first beamforming procedure performed by network node 110; send an indication of the first selected beam sequence to another network node; and receive an indication of the second selected beam sequence associated with the second beamforming procedure performed by the other network node from the other network node. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

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

[0049] 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. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0050] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a 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 (CQIs) 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 may 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., precoding) 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0051] 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) the 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.

[0052] 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.

[0053] 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 antennas). Figure 2 One or more antenna elements of one or more components in.

[0054] 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 sent 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, reference Figures 7 to 11 ) any aspects of any of the methods described herein.

[0055] 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 (shown as DEMOD) of the modem 232), 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 communication and / or uplink communication. 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 execute the instructions described herein (e.g., reference 2 Figures 7 to 11 ) any aspects of any of the methods described herein.

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of 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 by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), 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.

[0057] In some aspects, the network node 110 includes: means for receiving an indication of a first selected beam sequence associated with a first beamforming procedure from another network node; means for selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node 110 based at least in part on the indication of the first selected beam sequence; and / or means for performing the second beamforming procedure based at least in part on the second selected beam sequence. In some aspects, means for the network node 110 to perform operations described herein may include, for example, one or more of the following: 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.

[0058] In some other aspects, the network node 110 includes: means for selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node 110; means for sending an indication of the first selected beam sequence to another network node; and / or means for receiving an indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node from the other network node. In some aspects, means for the network node to perform operations described herein may include, for example, one or more of the following: 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.

[0059] 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.

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

[0061] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. 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, a base station, or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0062] An aggregated base station (e.g., an aggregated network node) may be 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). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is 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 examples, 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 a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0063] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration 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 independently. A decomposed base station 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. Individual units of the decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a 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 respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

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

[0066] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the 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, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0067] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the 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, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0068] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming or PRACH extraction and filtering, etc.) based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0069] 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) platform 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, non-RT RIC 315, and near-RTRIC 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 implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0070] 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 communicate 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.

[0071] 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 the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

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

[0073] Figure 4 is a diagram illustrating an example beamforming architecture 400 that supports beamforming for high frequency communications according to the present disclosure. In some aspects, the beamforming architecture 400 may support beamforming for millimeter wave (mmW) communications, sub-terahertz (sub-THz) communications, or similar high frequency communications. In some aspects, the beamforming architecture 400 may implement aspects of the wireless network 100. In some aspects, the beamforming architecture 400 may be implemented in a transmitting device (e.g., a first wireless communication device, UE 120, or network node 110) and / or a receiving device (e.g., a second wireless communication device, UE 120, or network node 110), as described herein.

[0074] Broadly speaking, Figure 4 is a diagram illustrating example hardware components of a wireless communication device according to certain aspects of the present disclosure. The illustrated components may include those components that can be used for antenna element selection and / or for beamforming to transmit wireless signals. There are numerous architectures for antenna element selection and implementing phase shifting, only one example of which is illustrated here. The beamforming architecture 400 includes a modem (modulator / demodulator) 402, a digital-to-analog converter (DAC) 404, a first mixer 406, a second mixer 408, and a splitter 410. The beamforming architecture 400 also includes a plurality of first amplifiers 412, a plurality of phase shifters 414, a plurality of second amplifiers 416, and an antenna array 418 including a plurality of antenna elements 420. In some examples, the modem 402 may be combined with Figure 2 One or more of the modem 232 or the modem 254.

[0075] Transmit lines or other waveguides, wires, and / or traces connecting the various components are shown to illustrate how signals to be transmitted travel between the components. Reference numerals 422, 424, 426, and 428 indicate areas in the beamforming architecture 400 where different types of signals travel or are processed. Specifically, reference numeral 422 indicates an area where digital baseband signals travel or are processed, reference numeral 424 indicates an area where analog baseband signals travel or are processed, reference numeral 426 indicates an area where analog intermediate frequency (IF) signals travel or are processed, and reference numeral 428 indicates an area where analog RF signals travel or are processed. The architecture also includes local oscillator A 430, local oscillator B 432, and a controller / processor 434. In some aspects, the controller / processor 434 corresponds to the above in conjunction with Figure 2 The controller / processor 240 of the network node 110 and / or the above combination Figure 2 The controller / processor 280 of the UE 120.

[0076] Each of the antenna elements 420 may include one or more sub-elements for radiating or receiving RF signals. For example, a single antenna element 420 may include a first sub-element that is cross-polarized with a second sub-element, which may be used to independently transmit a cross-polarized signal. The antenna elements 420 may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between the antenna elements 420 may be such that signals having a desired wavelength transmitted individually by the antenna elements 420 may interact or interfere (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half wavelength, or other fraction of a wavelength of the spacing between adjacent antenna elements 420 to allow interaction or interference of signals transmitted by individual antenna elements 420 within the desired range.

[0077] The modem 402 processes and generates a digital baseband signal, and may also control the operation of the DAC 404, the first mixer 406 and the second mixer 408, the splitter 410, the first amplifier 412, the phase shifter 414 and / or the second amplifier 416 to transmit the signal via one or more or all of the antenna elements 420. The modem 402 may process the signal and control the operation according to a communication standard (such as the wireless standard discussed herein). The DAC 404 may convert the digital baseband signal received from the modem 402 (and to be transmitted) into an analog baseband signal. The first mixer 406 uses the local oscillator A 430 to up-convert the analog baseband signal into an analog IF signal within the IF. For example, the first mixer 406 may mix the signal with an oscillating signal generated by the local oscillator A 430 to "move" the baseband analog signal to the IF. In some cases, some processing or filtering (not shown) may occur at the IF. The second mixer 408 uses local oscillator B 432 to up-convert the analog IF signal to an analog RF signal. Similar to the first mixer, the second mixer 408 can mix the signal with an oscillating signal generated by local oscillator B 432 to "move" the IF analog signal to the RF or frequency to be used to transmit or receive the signal. The modem 402 and / or the controller / processor 434 can adjust the frequency of local oscillator A 430 and / or local oscillator B 432 so that the desired IF and / or RF frequencies are generated and used to facilitate signal processing and transmission within the desired bandwidth.

[0078] In the illustrated beamforming architecture 400, the signal up-converted by the second mixer 408 is split or copied into multiple signals by the splitter 410. The splitter 410 in the beamforming architecture 400 splits the RF signal into multiple identical or nearly identical RF signals. In other examples, the splitting may occur on any type of signal (including baseband signals, baseband analog or IF analog signals). Each of these signals may correspond to an antenna element 420, and the signal travels through amplifiers 412, 416, phase shifters 414 and / or other elements corresponding to the corresponding antenna elements 420 and is processed by these components to be provided to the corresponding antenna element 420 of the antenna array 418 and transmitted by the corresponding antenna element. In one example, the splitter 410 can be an active splitter connected to a power source and provides some gain so that the RF signal leaving the splitter 410 is at a power level equal to or greater than the signal entering the splitter 410. In another example, the splitter 410 is a passive splitter that is not connected to a power source, and the RF signal exiting the splitter 410 may be at a lower power level than the RF signal entering the splitter 410 .

[0079] After being split by splitter 410, the resulting RF signal may enter an amplifier (such as first amplifier 412) or a phase shifter 414 corresponding to antenna element 420. The first amplifier 412 and the second amplifier 416 are illustrated with dotted lines because in some aspects, one or both of them may not be necessary. In some aspects, both the first amplifier 412 and the second amplifier 416 exist. In some aspects, both the first amplifier 412 and the second amplifier 416 do not exist. In some aspects, one of the two amplifiers 412, 416 exists, but the other does not exist. By way of example, if splitter 410 is an active splitter, the first amplifier 412 may not be used. By another example, if phase shifter 414 is an active phase shifter that can provide gain, the second amplifier 416 may not be used.

[0080] The amplifiers 412, 416 can provide a desired level of positive gain or negative gain. Positive gain (positive dB) can be used to increase the amplitude of a signal radiated by a particular antenna element 420. Negative gain (negative dB) can be used to reduce the amplitude of the signal and / or suppress the radiation of the signal by a particular antenna element. Each of the amplifiers 412, 416 can be independently controlled (e.g., by the modem 402 or the controller / processor 434) to provide independent control for the gain of each antenna element 420. For example, the modem 402 and / or the controller / processor 434 may have at least one control line connected to each of the splitter 410, the first amplifier 412, the phase shifter 414, and / or the second amplifier 416, which can be used to configure the gain so as to provide a desired amount of gain for each component and therefore each antenna element 420.

[0081] Phase shifter 414 can provide a configurable phase shift or phase offset to the corresponding RF signal to be sent. Phase shifter 414 can be a passive phase shifter that is not directly connected to a power supply. Passive phase shifters may introduce some insertion losses. The second amplifier 416 can enhance the signal to compensate for the insertion loss. Phase shifter 414 can be an active phase shifter connected to a power supply so that the active phase shifter provides a certain amount of gain or prevents insertion loss. The setting of each phase shifter in phase shifter 414 is independent, meaning that each phase shifter can be independently set to provide a desired phase shift amount or the same phase shift amount or some other configuration. Modem 402 and / or controller / processor 434 may have at least one control line connected to each phase shifter in phase shifter 414, and the at least one control line can be used to configure phase shifter 414 to provide a desired phase shift amount or phase offset amount between antenna elements 420.

[0082] In the illustrated beamforming architecture 400, the RF signal received by the antenna element 420 is provided to one or more first amplifiers 456 to enhance the signal strength. The first amplifier 456 may be connected to the same antenna array 418 (e.g., for time division duplex (TDD) operation). The first amplifier 456 may be connected to different antenna arrays 418. The enhanced RF signal is input to one or more phase shifters 454 to provide a configurable phase shift or phase offset for the corresponding received RF signal to achieve reception via one or more Rx beams. The phase shifter 454 may be an active phase shifter or a passive phase shifter. The setting of the phase shifter 454 is independent, meaning that each phase shifter may be independently set to provide a desired phase shift amount or the same phase shift amount or some other configuration. The modem 402 and / or the controller / processor 434 may have at least one control line connected to each of the phase shifters 454, and the at least one control line may be used to configure the phase shifters 454 to provide a desired phase shift or phase offset between the antenna elements 420 to enable reception via one or more Rx beams.

[0083] The output of phase shifter 454 can be input to one or more second amplifiers 452 for signal amplification of the received RF signal after phase shifting. Second amplifier 452 can be independently configured to provide a configured gain amount. Second amplifier 452 can be independently configured to provide a gain amount to ensure that the signals input to combiner 450 have the same amplitude. Amplifiers 452 and / or 456 are illustrated with dotted lines because in some aspects, they may not be necessary. In some aspects, both amplifier 452 and amplifier 456 exist. On the other hand, both amplifier 452 and amplifier 456 do not exist. In other aspects, one of amplifiers 452 and 456 exists, but the other does not exist.

[0084] In the illustrated beamforming architecture 400, the signals output by the phase shifter 454 (via the amplifier 452 (when present)) are combined in the combiner 450. The combiner 450 in the beamforming architecture 400 combines the RF signals into one signal. The combiner 450 can be a passive combiner (e.g., not connected to a power source), which may result in some insertion loss. The combiner 450 can be an active combiner (e.g., connected to a power source), which may result in some signal gain. When the combiner 450 is an active combiner, it can provide a different (e.g., configurable) amount of gain for each input signal so that the input signals have the same amplitude when combined. When the combiner 450 is an active combiner, the combiner 450 may not need the second amplifier 452 because the active combiner can provide signal amplification.

[0085] The output of combiner 450 is input to mixers 448 and 446. Mixers 448 and 446 typically down-convert the received RF signal using inputs from local oscillators 472 and 470, respectively, to produce intermediate or baseband signals that carry coded and modulated information. The output of mixers 448 and 446 is input to analog-to-digital converter (ADC) 444 for conversion to a digital signal. The digital signal output from ADC 444 is input to modem 402 for baseband processing, such as decoding, deinterleaving, or the like.

[0086] The beamforming architecture 400 is given by way of example only to illustrate an architecture for transmitting and / or receiving signals. In some cases, the beamforming architecture 400 and / or each portion of the beamforming architecture 400 may be repeated multiple times within the architecture to accommodate or provide any number of RF chains, antenna elements, and / or antenna panels. In addition, numerous alternative architectures are possible and contemplated. For example, although only a single antenna array 418 is shown, two, three, or more antenna arrays may be included, each with its own corresponding amplifier, phase shifter, splitter, mixer, DAC, ADC, and / or modem. One or more. For example, a single UE may include two, four, or more antenna arrays for transmitting or receiving signals at different physical locations on the UE or in different directions.

[0087] In addition, mixers, splitters, amplifiers, phase shifters and other components may be located in different signal type areas (e.g., represented by different reference numerals in reference numerals 422, 424, 426, 428) in different architectures implemented. For example, in different examples, splitting the signal to be transmitted into multiple signals may occur at analog RF, analog IF, analog baseband or digital baseband frequencies. Similarly, amplification and / or phase shifting may also occur at different frequencies. For example, in some aspects, one or more of splitter 410, amplifier 412, 416 or phase shifter 414 may be located between DAC 404 and first mixer 406 or between first mixer 406 and second mixer 408. In one example, the functions of one or more of these components may be combined into one component. For example, phase shifter 414 may perform amplification to include or replace first amplifier 412 and / or second amplifier 416. By another example, phase shifting may be implemented by second mixer 408 to eliminate the need for separate phase shifter 414. This technique is sometimes referred to as local oscillator (LO) phase shifting. In some aspects of this configuration, there may be multiple IF-to-RF mixers within the second mixer 408 (e.g., for each antenna element chain), and local oscillator B 432 may supply a different local oscillator signal (with a different phase offset) to each IF-to-RF mixer.

[0088] The modem 402 and / or the controller / processor 434 may control one or more of the other components 404 to 472 to select one or more antenna elements 420 and / or form a beam for transmitting one or more signals. For example, the antenna elements 420 may be independently selected or deselected for transmitting a signal (or signals) by controlling the amplitude of one or more corresponding amplifiers (such as the first amplifier 412 and / or the second amplifier 416). Beamforming includes generating beams using multiple signals on different antenna elements, wherein one or more or all of the multiple signals are shifted in phase with each other. The formed beams may carry physical or higher layer reference signals or information. Since each of the multiple signals is radiated from a corresponding antenna element 420, the radiated signals interact, interfere (constructively and destructively) and amplify with each other to form the resulting beams. The shape (such as the amplitude, width, and / or presence of side lobes) and direction (such as the angle of the beam relative to the surface of the antenna array 418) may be dynamically controlled by modifying the phase shift or phase offset applied by the phase shifter 414 and the amplitude applied by the amplifiers 412, 416 of the multiple signals relative to each other. The controller / processor 434 may be partially or fully located within one or more other components of the beamforming architecture 400. For example, in some aspects, the controller / processor 434 may be located within the modem 402.

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

[0090] Figure 5 5 are diagrams illustrating examples 500, 510, and 520 of a channel state information reference signal (CSI-RS) beam management procedure according to the present disclosure. Figure 5 As shown, examples 500, 510, and 520 include UE 120 communicating with network node 110 in a wireless network (e.g., wireless network 100). Figure 5 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).

[0091] like Figure 5As shown, example 500 may include a network node 110 (e.g., one or more network node devices such as RU, DU, and / or CU, etc.) and a UE 120 communicating to perform beam management using CSI-RS. Example 500 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 search procedure. Figure 5 As shown in example 500, a CSI-RS may be configured to be sent from a network node 110 to a UE 120. The 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 communication information (DCI)).

[0092] 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 network node may use a transmit beam to transmit each CSI-RS multiple times (e.g., with repetitions) within the same RS resource set, so that the UE 120 can sweep the receive beam in multiple transmit instances. For example, if 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 can 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 measurement results 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 500 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.

[0093] like Figure 5As shown, example 510 may include network node 110 and UE 120 communicating to perform beam management using CSI-RS. Example 510 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 network node beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 5 As shown in example 510, a CSI-RS may be configured to be sent from a network node 110 to a UE 120. The CSI-RS may be configured to be non-periodic (e.g., using a 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 measurement results reported by the UE 120 in conjunction with the first beam management procedure). The network node 110 may use each of the one or more transmit beams for beam management to send a CSI-RS. 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 (eg, measured by the UE 120 using a single receive beam).

[0094] like Figure 5 As shown, example 520 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 5As shown in example 520, 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 one or more CSI-RS using a single transmit beam (e.g., determined at least in part based on measurement results 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 network node may use the transmit beam to send multiple (e.g., with repetitions) CSI-RS within the same RS resource set, so that the UE 120 can sweep 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 measurement results received from the UE 120 (e.g., reported measurement results of the CSI-RS of the transmit beam using the one or more receive beams).

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

[0096] Figure 6 is a diagram illustrating an example 600 of a network node sensing procedure according to the present disclosure.

[0097] In some cases, the network node 110 may use a beamforming procedure for purposes other than establishing a connection with the UE 120. For example, in some examples, the network node 110 may use a beamforming procedure as part of a sensing procedure, which is sometimes referred to as a radar procedure. During the sensing procedure, the network node 110 may operate in a full-duplex mode in which the network node 110 simultaneously transmits and receives communications. More specifically, the network node 110 may transmit one or more probe signals, while simultaneously listening for the return of the one or more probe signals (such as by activating a receive beam) in order to sense the returned (e.g., reflected) probe signals. In some cases, the probe signals may be flexibly selected based at least in part on a particular sensing scenario. For example, for an independent sensing transmission, the network node 110 may transmit a frequency modulated continuous wave (FMCW) probe signal, and for a sensing transmission that also transmits data or other information to another node in the network (e.g., a UE 120, a network node 110, or another wireless communication device), the network node 110 may transmit a CP-OFDM probe signal.

[0098] In order to determine the angular location of a target (e.g., an object that reflects a detection signal back to the network node 110), the network node 110 may use beamforming so that the returned detection signal is limited to signals reflected from targets within a narrower angular region corresponding to the narrow beamwidth employed. For example, in some cases, the network node 110 may perform a sensing procedure by transmitting an omnidirectional sensing signal using digital receive beamforming. In such cases, the network node 110 may be able to detect all angular directions and distinguish the angular location of the returned signal using a single transmission. Using omnidirectional sensing signals together with digital receive beamforming may also enable virtual MIMO, which may increase the angular resolution beyond the limitations imposed by multiple physical receive antenna elements. However, using omnidirectional sensing signals together with digital receive beamforming may require a receiver with many RF chains (e.g., one RF chain per antenna element), which may render such implementations impractical for high frequency bands (such as FR2 and above). Furthermore, the use of omnidirectional sensing signals with digital receive beamforming may be limited because the loss of directivity (e.g., beamforming) gain may need to be compensated for by increased transmit duration, which may result in increased interference to other network nodes 110 and increased power, computational, and network resource consumption.

[0099] In some other examples, the network node 110 may perform the sensing procedure by using a pair of matched analog transmit beamformers and analog receive beamformers. Using a pair of matched analog transmit beamformers and analog receive beamformers is simple in terms of RF requirements, but beam scanning may be required. Nevertheless, for high-frequency operations (such as mmW operations associated with a large number of antennas and therefore high resolution), virtual MIMO may not be necessary. Therefore, using a pair of matched analog transmit beamformers and analog receive beamformers may be well suited for mmW operations and other high-frequency operations.

[0100] When the network node 110 performs a sensing procedure (such as one of the sensing procedures described above) or a similar beamforming procedure, the network node 110 may experience interference, such as downlink-to-downlink interference, from transmissions of other network nodes 110. That is, because the network node 110 may enable reception of communications during normal downlink time periods as part of a sensing procedure (e.g., in order to sense returned probe signals), the network node 110 may experience interference from downlink traffic of neighboring network nodes 110. Figure 6 This can be more easily understood with the example shown.

[0101] First, as indicated by reference numeral 602, the victim sensing network node 110-V may experience direct interference (e.g., interference along a line-of-sight (LOS) path) from the aggressor network node 110-A. In this example, the transmit beam 604 of the aggressor network node 110-A may directly interfere with the receive beam 606 of the victim sensing network node 110-V, as shown by reference numeral 608. More specifically, since the transmit beam 604 is aligned with the receive beam 606, any communication and / or detection signal sent by the aggressor network node 110-A may be received by the victim sensing network node 110-V, thereby causing interference with the sensing procedures or other beamforming procedures of the victim sensing network node 110-V.

[0102] In some other examples, the transmit beam and receive beam of the neighboring network node 110 may be misaligned, but the sensing network node 110 may experience indirect interference (e.g., interference along a non-LOS (NLOS) path), as shown in the example indicated by reference numeral 610. In this example, the transmit beam 612 of the aggressor network node 110-A may indirectly interfere with the receive beam 614 of the victim sensing network node 110-V, as shown by reference numeral 616. More specifically, even though the transmit beam 612 and the receive beam 614 are misaligned in this example, the communication and / or detection signals transmitted by the aggressor network node 110-A may be reflected from one or more objects (such as object 618) and received by the victim sensing network node 110-V, thereby causing interference with the sensing procedures or other beamforming procedures of the victim sensing network node 110-V.

[0103] Interference at the sensing network node 110, such as direct interference indicated by reference numeral 608 and / or indirect interference indicated by reference numeral 616, may have several adverse effects at the sensing network node 110. For example, the interference may mask targets during a sensing procedure because returns associated with certain targets (e.g., reflected probe signals) may be associated with power levels that are less than interference levels from neighboring network nodes 110. On the other hand, the interference may result in false targets (e.g., false alarms) during a sensing procedure because interference from neighboring network nodes 110 may be interpreted by the sensing network node 110 as returns from one or more targets that are not actually present.

[0104] If multiple network nodes 110 operate in a licensed frequency band and are under the control of the network, most forms of interference can be eliminated by appropriate resource allocation. For example, a network node 110 communicating with a UE 120 may grant orthogonal resources to the UE 120 to perform transmissions on an uplink or sidelink. In addition, the network node 110 may treat its own sensing communication as a downlink communication and use dedicated resources and orthogonal resources for sounding signal transmission. However, even if both network nodes 110 are operating in downlink mode, the sensing operation may introduce network node to network node interference (sometimes referred to as downlink to downlink interference) because the sensing network node 110 may receive interference from neighboring network nodes, as described above in conjunction with the examples shown in reference numerals 602 and 610. Therefore, sensing operations and / or similar beamforming operations may be associated with high error rates, resulting in degradation and loss of communications and / or increased power, computation, and network resource consumption to correct communication errors.

[0105] Some techniques and apparatus described herein implement coordination between network nodes 110 executing one or more beamforming procedures (such as the sensing procedures described above) to reduce or eliminate downlink-to-downlink interference, such as the interference described in conjunction with the examples shown by reference numerals 602 and 610. In some aspects, a network node 110 may signal to another network node 110 an expected or selected beam sequence that the network node 110 will use to execute a beamforming procedure (e.g., one of the sensing procedures described above), which may include beam scanning using the selected beam sequence. Thus, the other network node 110 may select a beam sequence to be used for its own beamforming procedure (such as another sensing procedure, etc.) based at least in part on the indication of the first beam sequence. In this way, the network node 110 and the other network node 110 may execute respective beamforming procedures (e.g., respective sensing procedures) with little or no risk of interference from neighboring network nodes 110. Thus, the network node 110 may perform more robust sensing procedures and similar beamforming procedures, resulting in reduced error rates and thus improved communication channels with low latency and high throughput, as well as reduced power, computational, and network resource consumption that may be required to correct communication errors.

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

[0107] Figure 7 is a diagram of an example 700 associated with inter-network node beam coordination for a beamforming procedure according to the present disclosure. Figure 7 As shown, a first network node 110-1 (e.g., network node 110, CU, DU, and / or RU) may communicate with a second network node 110-2 (e.g., another network node 110, another CU, another DU, and / or another RU). In some aspects, first network node 110-1 and second network node 110-2 may be part of a wireless network (e.g., wireless network 100). First network node 110-1 and second network node 110-2 may be in communication with each other. Figure 7 The operations shown have previously established a connection (such as via an Xn interface). The first network node 110-1 and / or the second node 110-2 may be capable of beamforming communication, such as described above in conjunction with Figures 4 to 6 The beamforming communication described.

[0108] In some aspects, the first network node 110-1 and / or the second network node 110-2 may select a beam sequence to be used for a beamforming procedure (such as a sensing procedure, etc.), which is described in more detail below in conjunction with reference numerals 715 and 725. In some aspects, selecting a respective beam sequence may be based at least in part on interference measurements performed by the first network node 110-1 and / or the second network node 110-2. More specifically, one or both of the network nodes 110-1, 110-2 may measure interference in certain channels and / or beams, and thus select a beam sequence based at least in part on the interference measurements (e.g., selecting a beam sequence with the least amount of interference, etc.). Thus, as indicated by reference numerals 705 and 715, the first network node 110-1 and / or the second network node 110-2 may perform one or more interference measurements.

[0109] As indicated by reference numeral 715, the first network node 110-1 may select a first selected beam sequence associated with a first beamforming procedure executed by the first network node 110-1. For example, the first selected beam sequence may be used for one or more beamforming procedures, such as described above in conjunction with Figure 5 Additionally or alternatively, the first selected beam sequence may be used in conjunction with a sensing procedure (such as the above-mentioned Figure 6 In some aspects, the first network node 110-1 may select the first selected beam sequence based at least in part on the one or more interference measurements. For example, the first network node 110-1 may select the beam sequence associated with the least amount of interference.

[0110] As indicated by reference numeral 720, the first network node 110-1 may send an indication of the first selected beam sequence associated with the first beamforming procedure, and the second network node 110-2 may receive the indication of the first selected beam sequence associated with the first beamforming procedure. For example, the first network node 110-1 may send the indication of the first selected beam sequence to the second network node 110-2 via an intended beam configuration information element (IE) (sometimes referred to as an IntendedDL_beam_conf IE). Additionally or alternatively, the first network node 110-1 may send the indication of the first selected beam sequence to the second network node 110-2 via an Xn Application Protocol (XnAP) communication. For example, the first network node 110-1 may send the intended beam configuration IE (e.g., IntendedDL_beam_conf IE) to the second network node 110-2 using an XnAP configuration update communication. In some aspects, the expected beam configuration IE may be included in a communication protocol setup request (sometimes referred to as an XN SETUP REQUEST message) between network nodes 110. In some other aspects, the expected beam configuration IE may be included in a communication protocol setup response communication (sometimes referred to as an XN SETUP RESPONSE message) between network nodes 110. In some aspects, the second network node 110-2 may consider the received expected beam configuration IE (e.g., IntendedDL_beam_conf IE) content to be valid until an update is received from the first network node 110-1, which is described in more detail below in conjunction with reference numeral 745.

[0111] In some aspects, for the purpose of performing TDD downlink-uplink coordination, etc., the first network node 110-1 may send an intended TDD configuration IE (sometimes referred to as an Intended TDD DL-UL Configuration NR IE), and the second network node 110-2 may receive the intended TDD configuration IE. More specifically, the intended TDD configuration IE may indicate certain parameters associated with the communication associated with the first network node 110-1, such as the subcarrier spacing (SCS) used, the cyclic prefix (CP) type used, the downlink-uplink periodicity used, one or more time slot configuration parameters used (e.g., whether the symbols associated with the time slot are all downlink symbols, all uplink symbols, or both downlink symbols and uplink symbols including a plurality of consecutive downlink symbols at the beginning of the time slot and a plurality of consecutive uplink symbols at the end of the time slot), etc.

[0112] In some aspects, in addition to indicating the first selected beam sequence to be used by the first network node 110-1, the expected beam configuration IE (e.g., IntendedDL_beam_conf IE) may also be able to indicate similar information to the expected TDD configuration IE (e.g., Intended TDD DL-UL Configuration NR IE), including the SCS used, the CP type used, the downlink-uplink periodicity used, one or more time slot configuration parameters used, or similar parameters. Therefore, in some aspects, if TDD uplink-downlink coordination is performed between the first network node 110-1 and the second network node 110-2, and therefore the expected TDD configuration IE is sent by the first network node 110-1 to the second network node 110-2, then the expected beam configuration IE may be based at least in part on the expected TDD configuration IE. For example, the expected beam configuration IE may indicate only the first selected beam sequence, and the second network node 110-2 may be configured and / or hard-coded to determine any missing information (e.g., the SCS used, the CP type used, the downlink-uplink periodicity used, one or more time slot configuration parameters used, or the like) based on the expected TDD configuration IE.

[0113] In some other aspects, the expected beam configuration IE may also indicate the first selected beam sequence in addition to one or more parameters conventionally indicated by the expected TDD configuration IE (e.g., the SCS used, the CP type used, the downlink-uplink periodicity used, one or more time slot configuration parameters used, or the like). In such aspects, the expected TDD configuration IE may be redundant because all information typically conveyed by the expected TDD configuration IE may be indicated by the expected beam configuration IE. Therefore, in such aspects, the expected TDD configuration IE may be omitted (e.g., may not be sent by the first network node 110-1 to the second network node 110-2), and the network nodes 110-1, 110-2 may alternatively perform TDD downlink-uplink coordination based at least in part on the information conveyed by the expected beam configuration IE. In other words, in some aspects, the second network node 110-2 may determine the expected TDD configuration associated with the first network node 110-1 based at least in part on the expected beam configuration IE.

[0114] As indicated by reference numeral 725, in some aspects, the second network node 110-2 may select a second selected beam sequence associated with a second beamforming procedure performed by the second network node 110-2 based at least in part on the indication of the first selected beam sequence. For example, the second network node 110-2 may select a beam sequence to be used for a sensing procedure to be performed by the second network node 110-2 based at least in part on the indication of the first selected beam sequence. In this manner, the second network node 110-2 may reduce or eliminate interference associated with the sensing procedure (such as in conjunction with Figure 6 In some aspects, the second network node 110-2 may select the second selected beam sequence based at least in part on the interference measurement.

[0115] As indicated by reference numeral 730, in some aspects, the second network node 110-2 may send an indication of the second selected beam sequence associated with the second beamforming procedure performed by the second network node 110-2, and the first network node 110-1 may receive the indication. For example, and in a similar manner as described in conjunction with reference numeral 720, the second network node 110-2 may send the indication of the second selected beam sequence to the first network node 110-1 via an intended beam configuration IE (e.g., IntendedDL_beam_conf IE). Additionally or alternatively, the second network node 110-2 may send the indication of the second selected beam sequence to the first network node 110-1 via an XnAP communication (such as an XnAP configuration update communication). In some aspects, the intended beam configuration IE may be included in an inter-network node 110 communication protocol setup request (e.g., an XN SETUP REQUEST message) or an inter-network node 110 communication protocol setup response communication (e.g., an XN SETUP RESPONSE message). Additionally or alternatively, the first network node 110 - 1 may consider the received intended beam configuration IE (eg, IntendedDL_beam_conf IE) content to be valid until an update is received from the second network node 110 - 2 , which is described in more detail below in conjunction with reference numeral 745 .

[0116] Furthermore, in a similar manner as described in connection with reference numeral 720, in some aspects, for the purpose of performing TDD downlink-uplink coordination, etc., the second network node 110-2 may send an intended TDD configuration IE (e.g., an IntendedTDD DL-UL Configuration NR IE), and the first network node 110-1 may receive the intended TDD configuration IE. Thus, if the TDD downlink-uplink coordination is performed between the second network node 110-2 and the first network node 110-1 (and thus the intended TDD configuration IE is sent by the second network node 110-2 to the first network node 110-1), the intended beam configuration IE may be based at least in part on the intended TDD configuration IE. For example, the intended beam configuration IE may indicate only the second selected beam sequence, and the first network node 110-1 may be configured and / or hard-coded to determine any missing information (e.g., a used SCS, a used CP type, a used downlink-uplink periodicity, one or more slot configuration parameters used, or the like) from the intended TDD configuration IE. In some other aspects and in a similar manner as described above in conjunction with reference numeral 720, the expected TDD configuration IE may be omitted (e.g., may not be sent by the second network node 110-2 to the first network node 110-1), and the network nodes 110-1, 110-2 may instead perform TDD downlink-uplink coordination based at least in part on the information conveyed by the expected beam configuration IE. In other words, in some aspects, the first network node may determine the expected TDD configuration associated with the second network node 110-2 based at least in part on the expected beam configuration IE.

[0117] In some aspects, the information exchange between the first network node 110-1 and the second network node 110-2 (as described in conjunction with reference numerals 720 and 730) may trigger a negotiation phase, such as when the first network node 110-1 and the second network node 110-2 have conflicting requirements. More specifically, if the selected first beam sequence is likely to interfere with the selected second beam sequence, and / or if the selected second beam sequence is likely to interfere with the selected first beam sequence, the first network node 110-1 and the second network node 110-2 may enter a negotiation phase to complete the selection of the first selected beam sequence and / or the second selected beam sequence. For example and as indicated by reference numeral 735, the first network node 110-1 and the second network node 110-2 may send and receive communications to determine beams to be included in the first selected beam sequence and / or the second selected beam sequence.

[0118] As indicated by reference numeral 740, the first network node 110-1 may perform the first beamforming procedure based at least in part on the first selected beam sequence, and as indicated by reference numeral 745, the second network node 110-2 may perform the second beamforming procedure based at least in part on the second selected beam sequence. For example, in some aspects, one or both of the first beam sequence and the second beam sequence may be combined with a sensing procedure (such as described above in conjunction with Figure 6 The first network node 110-1 may perform a first sensing procedure based at least in part on the first selected beam sequence, and / or the second network node 110-2 may perform a second sensing procedure based at least in part on the second selected beam sequence. Furthermore, in some aspects, one or both of the first selected beam sequence or the second selected beam sequence may be associated with communication using pre-allocated resources, such as one of semi-persistent scheduling (SPS) resources or configured grant (CG) resources.

[0119] Additionally or alternatively, one or both of the first network node 110-1 or the second network node 110-2 may adjust the transmit power associated with the corresponding beamforming procedure based at least in part on the indication of the first selected beam sequence or the second selected beam sequence. For example, where the indication of the first selected beam sequence (as described above in conjunction with reference numeral 720) indicates that the second beamforming procedure to be performed by the second network node 110-2 may interfere with aspects of the first network node 110-1, the second network node 110-2 may reduce the transmit power associated with the second beamforming procedure so as to reduce the risk of interfering with the beamforming procedure of the first network node 110-1. Alternatively, where the indication of the first selected beam sequence (as described above in conjunction with reference numeral 720) indicates that the first selected beam sequence may interfere with aspects of the second beamforming procedure to be performed by the second network node 110-2, the second network node 110-2 may increase the transmit power associated with the second beamforming procedure in order to suppress any interfering signals and / or otherwise reduce the risk of interference with transmissions from the first network node 110-1.

[0120] In some aspects, a network node 110 that receives an indication of a selected beam sequence from another network node 110 (such as via an expected beam configuration IE, as described above) may consider the selected beam sequence to be valid until an update is received from the other network node 110. Thus, in some aspects, the first network node 110-1 or the second network node 110-2 may receive an updated expected beam configuration IE and update the selected beam sequence accordingly. For example, in some aspects, the first network node 110-1 may send an updated expected beam configuration IE and the second network node 110-2 may receive the updated expected beam configuration IE, which indicates a third selected beam sequence associated with a third beamforming procedure performed by the first network node 110-1, which may be similar to the indication described in conjunction with reference numeral 720. Furthermore, in some aspects, the third selected beam sequence may be different from the first selected beam sequence. Therefore, the second network node 110-2 may select a fourth selected beam sequence associated with a fourth beamforming procedure performed by the second network node 110-2 based at least in part on the updated expected beam configuration IE, which may be similar to the selection process described in conjunction with reference numeral 725. In addition, the second network node 110-2 may perform the fourth beamforming procedure based at least in part on the fourth selected beam sequence, which may be similar to the execution step described above in conjunction with reference numeral 745.

[0121] Based at least in part on two or more network nodes 110 (e.g., first network node 110-1 and second network node 110-2) coordinating one or more beamforming procedures to reduce or eliminate downlink-to-downlink interference as described above, network node 110 may save computational, power, network, and / or communication resources that may have otherwise been consumed when performing uncoordinated and, therefore, interfering beamforming procedures. For example, based at least in part on two or more network nodes 110 coordinating one or more beamforming procedures to reduce or eliminate downlink-to-downlink interference, network node 110 may utilize reduced error rates for communication and / or for performing sensing procedures, which may save computational, power, network, and / or communication resources that may otherwise have been consumed to detect and / or correct communication errors and / or sensing errors, and / or network node 110 may operate in a channel that includes minimal interference, thereby resulting in a reduction in latency, an increase in throughput, and efficient use of network resources.

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

[0123] Figure 8is a diagram illustrating an example process 800 performed, for example, by a network node according to the present disclosure. The example process 800 is an example in which the network node (eg, the second network node 110-2) performs operations associated with inter-network node beam coordination for a beamforming procedure.

[0124] like Figure 8 As shown, in some aspects, process 800 may include receiving a request from another network node (e.g., Figure 7 A first network node 110-1 of the present invention receives an indication of a first selected beam sequence associated with a first beamforming procedure (block 810). For example, the network node (e.g., using Fig.10 The depicted communications manager 150 and / or receiving component 1002) can receive, from another network node, an indication of a first selected beam sequence associated with a first beamforming procedure, as described above.

[0125] like Figure 8 As further shown, in some aspects, process 800 may include selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence (block 820). Fig.10 The depicted communications manager 150 and / or beamforming component 1008) can select a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence, as described above.

[0126] like Figure 8 As further shown, in some aspects, process 800 may include performing the second beamforming procedure based at least in part on the second selected beam sequence (block 830). Fig.10 The depicted communication manager 150 and / or beamforming component 1008) can perform the second beamforming procedure based at least in part on the second selected beam sequence, as described above.

[0127] 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.

[0128] In a first aspect, the first beamforming procedure is associated with a first sensing procedure performed by the other network node, and the second beamforming procedure is associated with a second sensing procedure performed by the network node.

[0129] In a second aspect, alone or in combination with the first aspect, process 800 includes performing interference measurements, wherein selecting the second selected beam sequence is further based at least in part on the interference measurements.

[0130] In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes adjusting a transmit power associated with the second beamforming procedure based at least in part on the indication of the first selected beam sequence.

[0131] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes sending and receiving communications with the other network node to determine beams to be included in the first selected beam sequence and the second selected beam sequence.

[0132] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

[0133] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication of the first selected beam sequence is received via an expected beam configuration IE.

[0134] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the expected beam configuration IE is received via Xn application protocol communication.

[0135] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the expected beam configuration IE is included in one of a network node communication protocol establishment request communication or a network node communication protocol establishment response communication.

[0136] In a ninth aspect, alone or in combination with one or more of aspects one to eight, process 800 includes receiving an updated expected beam configuration IE from the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the other network node, wherein the third selected beam sequence is different from the first selected beam sequence; selecting a fourth selected beam sequence associated with a fourth beamforming procedure performed by the network node based at least in part on the updated expected beam configuration IE; and performing the fourth beamforming procedure based at least in part on the fourth selected beam sequence.

[0137] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 800 includes receiving an expected time division duplex configuration IE from the other network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

[0138] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 800 includes determining an expected time division duplex configuration associated with the other network node based at least in part on the expected beam configuration IE.

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

[0140] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a network node according to the present disclosure. The example process 900 is a diagram in which the network node (e.g., Figure 7 An example of a first network node 110-1) performing operations associated with inter-network node beam coordination for a beamforming procedure.

[0141] like Fig. 9 As shown, in some aspects, process 900 may include selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node (block 910). For example, the network node (e.g., using Fig.11 The depicted communication manager 150 and / or beamforming component 1108) can select a first selected beam sequence associated with a first beamforming procedure performed by the network node, as described above.

[0142] like Fig. 9 As further shown, in some aspects, process 900 may include sending a signal to another network node (e.g., Figure 7 The second network node 110-2 sends an indication of the first selected beam sequence (block 920). For example, the network node (e.g., using Fig.11 The depicted communication manager 150 and / or transmitting component 1104) can transmit an indication of the first selected beam sequence to another network node, as described above.

[0143] like Fig. 9 As further shown, in some aspects, process 900 may include receiving, from the other network node, an indication of a second selected beam sequence associated with a second beamforming procedure performed by the other network node (block 930). Fig.11 The depicted communications manager 150 and / or receiving component 1102) can receive, from the other network node, an indication of a second selected beam sequence associated with a second beamforming procedure performed by the other network node, as described above.

[0144] 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.

[0145] In a first aspect, the first beamforming procedure is associated with a first sensing procedure performed by the network node and the second beamforming procedure is associated with a second sensing procedure performed by the another network node.

[0146] In a second aspect, alone or in combination with the first aspect, process 900 includes performing the first beamforming procedure based at least in part on the first selected beam sequence.

[0147] In a third aspect, alone or in combination with one or more of the first and second aspects, process 900 includes performing interference measurements, wherein selecting the first selected beam sequence is further based at least in part on the interference measurements.

[0148] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes sending and receiving communications with the other network node to determine beams to be included in the first selected beam sequence and the second selected beam sequence.

[0149] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

[0150] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication of the first selected beam sequence is sent via an expected beam configuration IE.

[0151] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the expected beam configuration IE is sent via Xn application protocol communication.

[0152] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the expected beam configuration IE is included in one of a network node communication protocol establishment request communication or a network node communication protocol establishment response communication.

[0153] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, process 900 includes sending an updated expected beam configuration IE to the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the network node, wherein the third selected beam sequence is different from the first selected beam sequence; and receiving from the other network node an indication of a fourth selected beam sequence associated with a fourth beamforming procedure performed by the other network node.

[0154] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 900 includes sending an expected time division duplex configuration IE to the other network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

[0155] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0156] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. The apparatus 1000 may be a network node 110 (e.g., Figure 7 1000). In some aspects, the apparatus 1000 includes a receiving component 1002 and a sending component 1004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1000 can communicate with another apparatus 1006 (such as a UE 120, a network node 110, or another wireless communication device) using the receiving component 1002 and the sending component 1004. As further shown, the apparatus 1000 may include a communication manager 150. The communication manager 150 may include one or more of a beamforming component 1008, a measuring component 1010, or a determining component 1012, among others.

[0157] In some aspects, the apparatus 1000 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more 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 2One or more components and / or combinations of the network node 110 Figure 4 One or more components of the beamforming architecture 400. Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 One or more components and / or combinations thereof Figure 4 Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is 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.

[0158] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications 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 communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 The network node 110 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0159] 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 network node 110. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0160] Receiving component 1002 may receive, from another network node, an indication of a first selected beam sequence associated with a first beamforming procedure. Beamforming component 1008 may select a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence. Beamforming component 1008 may perform the second beamforming procedure based at least in part on the second selected beam sequence.

[0161] The measuring component 1010 can perform interference measurement, wherein selecting the second selected beam sequence is further based at least in part on the interference measurement.

[0162] The beamforming component 1008 adjusts a transmit power associated with the second beamforming procedure based at least in part on the indication of the first selected beam sequence.

[0163] Receiving component 1102 and / or transmitting component 1004 can send and receive communications with the other network node to determine beams to be included in the first selected sequence of beams and the second selected sequence of beams.

[0164] The receiving component 1002 can receive an updated expected beam configuration IE from the another network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the another network node, wherein the third selected beam sequence is different from the first selected beam sequence.

[0165] The beamforming component 1008 can select a fourth selected beam sequence associated with a fourth beamforming procedure performed by the network node based at least in part on the updated expected beam configuration IE.

[0166] The beamforming component 1008 can perform the fourth beamforming procedure based at least in part on the fourth selected beam sequence.

[0167] Receiving component 1002 can receive an expected time division duplex configuration IE from the other network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

[0168] Determining component 1012 can determine an expected time division duplex configuration associated with the other network node based at least in part on the expected beam configuration IE.

[0169] Fig.10 The number and arrangement of components shown 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. Fig.10Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The illustrated set of component(s) may be described as being executable by Fig.10 Another collection of components shown performs one or more functions.

[0170] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. The apparatus 1100 may be a network node 110 (e.g., Figure 7 1), or the network node 110 may include an apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE 120, a network node, or another wireless communication device) using the receiving component 1102 and the sending component 1104. As further shown, the apparatus 1100 may include a communication manager 150. The communication manager 150 may include one or more of a beamforming component 1108 or a measurement component 1110, etc.

[0171] In some aspects, the apparatus 1100 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 In some aspects, the apparatus 1100 and / or Fig.11 One or more of the components shown may include a combination of Figure 2 One or more components and / or combinations of the network node 110 Figure 4 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 One or more components and / or combinations thereof Figure 4 Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is 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.

[0172] 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 The network node 110 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0173] 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 network node 110. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0174] The beamforming component 1108 can select a first selected beam sequence associated with a first beamforming procedure performed by the network node. The sending component 1104 can send an indication of the first selected beam sequence to another network node. The receiving component 1102 can receive, from the another network node, an indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node.

[0175] The beamforming component 1108 can perform the first beamforming procedure based at least in part on the first selected beam sequence.

[0176] The measuring component 1110 can perform interference measurements, wherein selecting the first selected beam sequence is further based at least in part on the interference measurements.

[0177] The receiving component 1102 and / or the transmitting component 1104 can send and receive communications with the other network node to determine beams to be included in the first selected sequence of beams and the second selected sequence of beams.

[0178] The sending component 1104 can send an updated expected beam configuration IE to the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the network node, wherein the third selected beam sequence is different from the first selected beam sequence.

[0179] Receiving component 1102 can receive, from the other network node, an indication of a fourth selected beam sequence associated with a fourth beamforming procedure performed by the other network node.

[0180] The transmitting component 1104 can transmit an expected time division duplex configuration IE to the other network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

[0181] Fig.11 The number and arrangement of components shown 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. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

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

[0183] Aspect 1: A method of wireless communication performed by a network node, the method comprising: receiving an indication of a first selected beam sequence associated with a first beamforming procedure from another network node; selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence; and performing the second beamforming procedure based at least in part on the second selected beam sequence.

[0184] Aspect 2: The method according to aspect 1, wherein the first beamforming procedure is associated with a first sensing procedure performed by the other network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the network node.

[0185] Aspect 3: The method according to any one of aspects 1 to 2, the method further comprising: performing interference measurement, wherein selecting the second selected beam sequence is further based at least in part on the interference measurement.

[0186] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: adjusting a transmit power associated with the second beamforming procedure based at least in part on the indication of the first selected beam sequence.

[0187] Aspect 5: According to the method according to any one of aspects 1 to 4, the method also includes: sending and receiving communications with the other network node to determine the beams to be included in the first selected beam sequence and the second selected beam sequence.

[0188] Aspect 6: The method according to any one of aspects 1 to 5, wherein the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

[0189] Aspect 7: The method according to any one of aspects 1 to 6, wherein the indication of the first selected beam sequence is received via an expected beam configuration IE.

[0190] Aspect 8: The method according to aspect 7, wherein the expected beam configuration IE is received via Xn application protocol communication.

[0191] Aspect 9: The method according to any one of aspects 7 to 8, wherein the expected beam configuration IE is included in one of a network node communication protocol establishment request communication or a network node communication protocol establishment response communication.

[0192] Aspect 10: According to the method described in any one of Aspects 7 to 9, the method further includes: receiving an updated expected beam configuration IE from the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the other network node, wherein the third selected beam sequence is different from the first selected beam sequence; selecting a fourth selected beam sequence associated with a fourth beamforming procedure performed by the network node based at least in part on the updated expected beam configuration IE; and performing the fourth beamforming procedure based at least in part on the fourth selected beam sequence.

[0193] Aspect 11: According to any one of aspects 7 to 10, the method further includes: receiving an expected time division duplex configuration IE from the other network node, wherein the expected beam configuration IE is at least partially based on the expected time division duplex configuration IE.

[0194] Aspect 12: The method according to any one of aspects 7 to 11, the method further comprising: determining an expected time division duplex configuration associated with the other network node based at least in part on the expected beam configuration IE.

[0195] Aspect 13: A method of wireless communication performed by a network node, the method comprising: selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node; sending an indication of the first selected beam sequence to another network node; and receiving an indication of a second selected beam sequence associated with a second beamforming procedure performed by the other network node from the other network node.

[0196] Aspect 14: The method according to aspect 13, wherein the first beamforming procedure is associated with a first sensing procedure performed by the network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the another network node.

[0197] Aspect 15: The method according to any one of aspects 13 to 14, the method further comprising: performing the first beamforming procedure based at least in part on the first selected beam sequence.

[0198] Aspect 16: The method according to any one of aspects 13 to 15, the method further comprising: performing interference measurement, wherein selecting the first selected beam sequence is further based at least in part on the interference measurement.

[0199] Aspect 17: According to the method according to any one of aspects 13 to 16, the method also includes: sending and receiving communications with the other network node to determine the beams to be included in the first selected beam sequence and the second selected beam sequence.

[0200] Aspect 18: The method according to any one of aspects 13 to 17, wherein the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

[0201] Aspect 19: The method according to any one of aspects 13 to 18, wherein the indication of the first selected beam sequence is sent via an expected beam configuration IE.

[0202] Aspect 20: The method according to aspect 19, wherein the expected beam configuration IE is sent via Xn application protocol communication.

[0203] Aspect 21: The method according to any one of aspects 19 to 20, wherein the expected beam configuration IE is included in one of a network node communication protocol establishment request communication or a network node communication protocol establishment response communication.

[0204] Aspect 22: According to the method described in any one of Aspects 19 to 21, the method further includes: sending an updated expected beam configuration IE to the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the network node, wherein the third selected beam sequence is different from the first selected beam sequence; and receiving from the other network node an indication of a fourth selected beam sequence associated with a fourth beamforming procedure performed by the other network node.

[0205] Aspect 23: According to any one of aspects 19 to 22, the method further includes: sending an expected time division duplex configuration IE to the other network node, wherein the expected beam configuration IE is at least partially based on the expected time division duplex configuration IE.

[0206] 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 12.

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

[0208] 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 12.

[0209] 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 12.

[0210] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions 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 12.

[0211] Aspect 29: 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 13 to 23.

[0212] Aspect 30: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 13 to 23.

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

[0214] Aspect 32: 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 13 to 23.

[0215] Aspect 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions 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 13 to 23.

[0216] 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 may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0217] 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 implemented, procedures and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to specific software codes herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

[0218] 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.

[0219] 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).

[0220] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. 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 to 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. In addition, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "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 used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from another network node, an indication of a first selected beam sequence associated with a first beamforming procedure; selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence; and The second beamforming procedure is performed based at least in part on the second selected beam sequence.

2. The apparatus of claim 1, wherein the first beamforming procedure is associated with a first sensing procedure performed by the another network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the network node.

3. The apparatus of claim 1, wherein the one or more processors are further configured to perform interference measurements, wherein selecting the second selected beam sequence is further based at least in part on the interference measurements.

4. The apparatus of claim 1, wherein the one or more processors are further configured to adjust a transmit power associated with the second beamforming procedure based at least in part on the indication of the first selected beam sequence.

5. The apparatus of claim 1, wherein the one or more processors are further configured to send and receive communications with the another network node to determine beams to be included in the first selected beam sequence and the second selected beam sequence.

6. The apparatus of claim 1, wherein the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

7. The apparatus of claim 1, wherein the indication of the first selected beam sequence is received via an expected beam configuration information element (IE).

8. The apparatus of claim 7, wherein the expected beam configuration IE is received via Xn application protocol communication.

9. The apparatus of claim 7, wherein the expected beam configuration IE is included in one of a network node communication protocol setup request communication or a network node communication protocol setup response communication.

10. The apparatus of claim 7, wherein the one or more processors are further configured to: receiving an updated expected beam configuration IE from the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the other network node, wherein the third selected beam sequence is different from the first selected beam sequence; selecting a fourth selected beam sequence associated with a fourth beamforming procedure performed by the network node based at least in part on the updated expected beam configuration IE; and The fourth beamforming procedure is performed based at least in part on the fourth selected beam sequence.

11. The apparatus of claim 7, wherein the one or more processors are further configured to receive an expected time division duplex configuration IE from the other network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

12. The apparatus of claim 7, wherein the one or more processors are further configured to determine an expected time division duplex configuration associated with the other network node based at least in part on the expected beam configuration IE.

13. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node; sending an indication of the first selected beam sequence to another network node; and An indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node is received from the another network node.

14. The apparatus of claim 13, wherein the first beamforming procedure is associated with a first sensing procedure performed by the network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the another network node.

15. The apparatus of claim 13, wherein the one or more processors are further configured to perform the first beamforming procedure based at least in part on the first selected beam sequence.

16. The apparatus of claim 13, wherein the one or more processors are further configured to perform interference measurements, wherein selecting the first selected beam sequence is further based at least in part on the interference measurements.

17. The apparatus of claim 13, wherein the one or more processors are further configured to send and receive communications with the another network node to determine beams to be included in the first selected beam sequence and the second selected beam sequence.

18. The apparatus of claim 13, wherein the first selected beam sequence is associated with one of a semi-persistently scheduled resource or a configured grant resource.

19. The apparatus of claim 13, wherein the indication of the first selected beam sequence is sent via an expected beam configuration information element (IE).

20. The apparatus of claim 19, wherein the expected beam configuration IE is sent via Xn application protocol communication.

21. The apparatus of claim 19, wherein the expected beam configuration IE is included in one of an inter-network node communication protocol setup request communication or an inter-network node communication protocol setup response communication.

22. The apparatus of claim 19, wherein the one or more processors are further configured to: sending an updated expected beam configuration IE to the other network node, the updated expected beam configuration IE indicating a third selected beam sequence associated with a third beamforming procedure performed by the network node, wherein the third selected beam sequence is different from the first selected beam sequence; and An indication of a fourth selected beam sequence associated with a fourth beamforming procedure performed by the another network node is received from the another network node.

23. The apparatus of claim 19, wherein the one or more processors are further configured to send an expected time division duplex configuration IE to the another network node, wherein the expected beam configuration IE is based at least in part on the expected time division duplex configuration IE.

24. A method of wireless communication performed by a network node, the method comprising: receiving, from another network node, an indication of a first selected beam sequence associated with a first beamforming procedure; selecting a second selected beam sequence associated with a second beamforming procedure performed by the network node based at least in part on the indication of the first selected beam sequence; and The second beamforming procedure is performed based at least in part on the second selected beam sequence.

25. The method of claim 24, wherein the first beamforming procedure is associated with a first sensing procedure performed by the another network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the network node.

26. The method of claim 24, wherein the indication of the first selected beam sequence is received via an expected beam configuration information element (IE).

27. The method according to claim 26, further comprising: An expected time division duplex configuration associated with the other network node is determined based at least in part on the expected beam configuration IE.

28. A method of wireless communication performed by a network node, the method comprising: selecting a first selected beam sequence associated with a first beamforming procedure performed by the network node; sending an indication of the first selected beam sequence to another network node; as well as An indication of a second selected beam sequence associated with a second beamforming procedure performed by the another network node is received from the another network node.

29. The method of claim 28, wherein the first beamforming procedure is associated with a first sensing procedure performed by the network node, and wherein the second beamforming procedure is associated with a second sensing procedure performed by the another network node.

30. The method of claim 28, wherein the indication of the first selected beam sequence is sent via an expected beam configuration information element (IE).

Images