Sensing assisted radio access technology communications

Abstract

Methods, systems, and devices for wireless communication are described. In general, the described techniques provide for using contextual information provided by a first user equipment (UE) to a first network entity to assist communication between a second UE and a second network entity. The first network entity can receive the contextual information from the first UE and can generate assistance information associated with the second UE based on the contextual information. The contextual information can be sensing data collected at the first UE, and in some examples can include locations, velocities, accelerations, etc. associated with the second UE and other UEs surrounding the second UE. The first network entity can then provide the assistance information to the second network entity, the second UE, or both, and the devices can use the assistance information to identify an appropriate configuration for communicating with each other.

Description

Technical Field

[0001] The following relates to wireless communications, including sensing-assisted radio access technology (RAT) communications. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0003] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may use one or more radio access technologies (RATs) to support communication between UEs and network entities. In such systems, it may be appropriate for the UE and network entity to identify a suitable configuration for communicating using one or more RATs. Improved techniques for identifying a configuration for communicating using one or more RATs may be desirable. Summary of the invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting sensing-assisted radio access technology (RAT) communications. In general, the described techniques provide context information sent by a first UE to a first network entity to assist communication between a second UE and the second network entity. The first network entity can receive the context information from the first UE and can generate assistance information associated with the second UE based on the context information. The context information can be sensing data collected at the first UE, and in some examples can include location, velocity, acceleration, etc. associated with the second UE and other UEs surrounding the second UE. The first network entity can then provide the assistance information to the second network entity, the second UE, or both, and the devices can use the assistance information to identify a suitable configuration for communicating with each other.

[0005] A method for wireless communication at a first network entity is described. The method may include: receiving context information from a first UE; generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE; and sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0006] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive context information from a first UE; generate assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE; and send at least a portion of the assistance information to a second network entity different from the first network entity.

[0007] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for receiving context information from a first UE; means for generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE; and means for sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to: receive context information from a first UE; generate assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE; and send at least a portion of the assistance information to a second network entity different from the first network entity.

[0009] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, devices, or instructions for: determining a first location of a second UE based on contextual information; and determining a second location of a second network entity, wherein sending auxiliary information to the second network entity may be based on a distance between the first location and the second location satisfying a distance threshold.

[0010] In some examples of the methods, devices, and non-transitory computer-readable media described herein, generating auxiliary information may include operations, features, devices, or instructions for identifying one or more recommended or restricted beam directions for beam selection at a second network entity based on contextual information, and wherein sending at least a portion of the auxiliary information to the second network entity includes sending one or more recommended or restricted beam directions for beam selection to the second network entity.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending at least another portion of the assistance information to the second UE to assist communication between the second UE and the second network entity.

[0012] In some examples of the methods, devices, and non-transitory computer-readable media described herein, another portion of the auxiliary information includes: one or more recommended or restricted beam directions for beam selection at the second UE, a range of beam scanning for the second UE to perform during beam selection, or a combination thereof.

[0013] In some examples of the methods, devices, and non-transitory computer-readable media described herein, another portion of the auxiliary information includes: handover information associated with a third network entity, measurements associated with the third network entity, an indication of interference from a nearby network entity, a measurement request from a nearby network entity, or a combination thereof.

[0014] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for determining that a second network entity can be associated with a serving cell for communicating with a second UE, wherein sending the assistance information to the second network entity can be based on the determination.

[0015] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatuses, or instructions for: selecting one or more network entities including a second network entity for coordinated multi-point communication with a second UE; and coordinating communication between the second UE and the selected one or more network entities based on auxiliary information.

[0016] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, devices, or instructions for predicting a future location of a second UE based on contextual information, wherein sending the assistance information to the second network entity includes sending a message indicating the predicted future location to the second network entity.

[0017] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the contextual information includes: the location of the second UE, propagation losses associated with communications with the second UE, the speed of the second UE, the direction of movement of the second UE, the velocity of the second UE, the acceleration of the second UE, the location or other motion information of one or more objects surrounding the second UE, or a combination thereof.

[0018] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the context information may be based on data collected at one or more sensors at the first UE, one or more sensors at one or more other UEs, or a combination thereof.

[0019] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the first network entity and the second network entity may be associated with different radio access technologies or the same RAT.

[0020] A method for wireless communication at a first network entity is described. The method may include: receiving assistance information associated with a first UE from a second network entity, wherein the assistance information is based on context information from a second UE different from the first UE; determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity; and communicating with the first UE using the one or more configurations.

[0021] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive assistance information associated with a first UE from a second network entity, wherein the assistance information is based on context information from a second UE different from the first UE; determine one or more configurations for communicating with the first UE based on the assistance information received from the second network entity; and communicate with the first UE using the one or more configurations.

[0022] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for receiving assistance information associated with a first UE from a second network entity, wherein the assistance information is based on context information from a second UE different from the first UE; means for determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity; and means for communicating with the first UE using the one or more configurations.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to: receive assistance information associated with a first UE from a second network entity, wherein the assistance information is based on context information from a second UE different from the first UE; determine one or more configurations for communicating with the first UE based on the assistance information received from the second network entity; and communicate with the first UE using the one or more configurations.

[0024] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a first UE may include operations, features, devices, or instructions for determining a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the first UE based on auxiliary information, and the method also includes performing a beam scanning operation using the set of directional beams, wherein communication with the first UE can be based on the beam scanning operation.

[0025] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a first UE may include operations, features, devices, or instructions for determining at least one of resources or modulation and coding schemes for communicating with the first UE based on auxiliary information, wherein communication with the first UE may be based on the resources, the modulation and coding scheme, or both.

[0026] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a first UE may include operations, features, devices, or instructions for determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the first UE based on auxiliary information, wherein communicating with the first UE may be based on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0027] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, devices, or instructions for sending control information based on auxiliary information, wherein the control information is configured for one or more of a directional beam set associated with a beam scanning operation, a reference signal transmission, or a threshold number of retransmissions for communicating with a first UE, wherein communication with the first UE can be based on the control information.

[0028] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the contextual information includes: the location of the first UE, propagation losses associated with communications with the first UE, the speed of the first UE, the direction of movement of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

[0029] A method for wireless communication at a first UE is described. The method may include: receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE; determining one or more configurations for communicating with a network entity based on the assistance information; and communicating with the network entity using the one or more configurations.

[0030] An apparatus for wireless communication at a first UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE; determine one or more configurations for communicating with a network entity based on the assistance information; and communicate with the network entity using the one or more configurations.

[0031] Another apparatus for wireless communication at a first UE is described. The apparatus may include: means for receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE; means for determining one or more configurations for communicating with a network entity based on the assistance information; and means for communicating with the network entity using the one or more configurations.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to: receive assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE; determine one or more configurations for communicating with a network entity based on the assistance information; and communicate with the network entity using the one or more configurations.

[0033] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a network entity may include operations, features, devices, or instructions for determining a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the network entity based on auxiliary information, and the method also includes performing a beam scanning operation using the set of directional beams, wherein communication with the network entity can be based on the beam scanning operation.

[0034] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a network entity may include operations, features, devices, or instructions for determining at least one of a resource or a modulation and coding scheme for communicating with the network entity based on auxiliary information, wherein communicating with the network entity may be based on the resource, the modulation and coding scheme, or both.

[0035] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining one or more configurations for communicating with a network entity may include operations, features, devices, or instructions for determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the network entity based on auxiliary information, wherein communicating with the network entity may be based on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0036] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the contextual information includes: the location of the first UE, propagation losses associated with communications with the first UE, the speed of the first UE, the direction of movement of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

[0037] The features and technical advantages of 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 the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims.

[0038] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovation. In some actual settings, the equipment in conjunction with the aspects and features must also include other components and features for the specific implementation and practice of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting sensing-assisted radio access technology (RAT) communication according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a network architecture supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 3 An example of a wireless communication system supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 4 An example of a wireless communication system supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 5 An example of a process flow in a system supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 6and Figure 7 A block diagram of a device supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0045] Figure 8 A block diagram of a communication manager supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0046] Fig. 9 A diagram of a system including a device supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0047] Fig.10 and Fig.11 A block diagram of a device supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0048] Fig.12 A block diagram of a communication manager supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0049] Fig.13 A diagram of a system including a device supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown.

[0050] Figures 14 to 16 A flow chart illustrating a method of supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] Some wireless communication systems may use one or more radio access technologies (RATs) to support communications between UEs and network entities. In such systems, it may be challenging for the UE and network entity to identify a suitable configuration for communicating using one or more RATs. For example, for millimeter wave (mmW) communications between a UE and a network entity, the UE and the network entity may identify a suitable beam for communicating. Therefore, the UE and the network entity may each support a technique for sending and receiving reference signals on multiple beams to identify a beam (e.g., an optimal beam) for mmW communications. Sending and receiving reference signals on multiple beams may be referred to as beam scanning. However, if the UE is constantly moving or changing position, the UE and the network entity may repeatedly perform beam scanning procedures to identify a suitable beam for mmW communications, resulting in relatively high overhead and increased power consumption.

[0052] As described herein, UEs and network entities in a wireless communication system may support efficient techniques for identifying configurations for communicating using one or more RATs. Specifically, the described techniques provide for assisting communication between a second UE and a second network entity using context information transmitted by a first UE to a first network entity. The first network entity is capable of receiving the context information from the first UE and is capable of generating assistance information associated with the second UE based on the context information. The context information may include sensory data collected at the first UE, and in some examples may include a location, velocity, acceleration, etc. associated with the second UE and other UEs surrounding the second UE. The first network entity may then provide the assistance information to the second network entity, the second UE, or both, and the second UE and the second network entity may use the assistance information to identify a suitable configuration for communicating with each other.

[0053] In one example, the second network entity, the second UE, or both may use the assistance information to reduce the scope of one or more beam scanning procedures for identifying a suitable beam for mmW communication (e.g., reducing the number of directional beams), resulting in relatively reduced overhead and reduced power consumption at the second network entity and the second UE. In another example, the second network entity, the second UE, or both may use the assistance information to perform handover prediction to allow efficient transition from communicating with the second network entity to communicating with another network entity. In yet another example, the second network entity, the second UE, or both may use the assistance information to identify a suitable configuration for mmW communication (e.g., transmit power, modulation and coding scheme (MCS), resources, etc.), resulting in relatively reduced overhead (e.g., from fewer retransmissions) and improved throughput.

[0054] First, various aspects of the present disclosure are described in the context of a wireless communication system. Then, examples of processes and signaling exchanges to support sensing-assisted RAT communications are described. Various aspects of the present disclosure are further illustrated by device diagrams, system diagrams, and flow charts related to sensing-assisted RAT communications, and various aspects of the present disclosure are described with reference to these device diagrams, system diagrams, and flow charts.

[0055] Figure 1 An example of a wireless communication system 100 supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0056] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0057] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.

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

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

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

[0061] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0062] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, channel) between layers of a protocol stack supported by the respective network entities 105 communicating over those communication links.

[0063] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support sensing-assisted RAT communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0065] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

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

[0067] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0068] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0069] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configurable to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0070] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0071] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0072] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

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

[0075] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0077] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0078] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

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

[0080] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0081] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0082] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating with limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

[0085] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

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

[0087] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0088] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, there may be even greater atmospheric attenuation and a shorter range for the propagation of EHF transmissions than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0089] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

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

[0091] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0092] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.

[0093] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0094] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0095] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0096] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission on a logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to a physical channel.

[0097] As mentioned, the wireless communication system 100 may be an example of an NR system and may support fifth generation (5G) communications. In 5G communications and other communications, mmW may be one of a variety of technologies supported to increase the data rate of communications. In order to overcome the poor propagation characteristics associated with mmW communications, it may be appropriate for the UE 115 or the network entity 105 to use multiple antennas to form narrow beams for communication. In addition, it may be appropriate for the UE 115 and the network entity 105 to achieve beam alignment for mmW communications (e.g., support techniques for beam management, beam selection, etc.). Given a particular environmental geometry (e.g., compared to lower frequency channels), mmW channel properties may be relatively more certain, and the UE 115 or the network entity 105 may identify suitable beams for communicating with each other based on the mmW channel properties.

[0098] In some implementations, the UE 115 and the network entity 105 may perform an exhaustive search-based beam scanning procedure (e.g., scanning through each available beam or a wide range of beams) to identify one or more suitable beams for communicating with each other. However, the exhaustive search-based beam scanning procedure may result in relatively increased overhead (e.g., taking a relatively long amount of time) for both the initial beam establishment (e.g., identifying the initial beam for mmW communication) and the beam tracking procedure (e.g., updating the beam for mmW communication). In some cases (e.g., with the advent of wireless technology and V2X technology in the automotive industry), some vehicles (e.g., autonomous vehicles, which may also be referred to as self-driving vehicles, driverless cars, self-aware vehicles, self-aware cars, or other similar terms) may be equipped with sensors such as satellite navigation, radar, light detection and ranging radar (LiDAR), cameras, etc. In addition, there may be techniques that use deep learning or machine learning methods (e.g., with relatively good evaluation results) to support beam tracking for mmW systems. Given these sensors and techniques for supporting beam tracking, the UE 115, the network entity 105, or both in the wireless communication system 100 may support efficient techniques for identifying configurations for communicating with each other.

[0099] For example, the wireless communication system 100 may support efficient techniques for using a wide coverage provider network entity 105 (e.g., a sub-6 GHz network entity) to assist the mmW network entity 105 in communicating with one or more in-vehicle UEs 115 (e.g., UEs 115 located in a vehicle) or other UEs 115. Specifically, a first UE 115 and a first network entity 105 in the wireless communication system 100 may support efficient techniques for identifying configurations for communicating using one or more RATs, and a second UE 115 and a second network entity 105 may support efficient techniques for assisting the first UE 115 and the first network entity 105 in identifying these configurations. The described techniques may be referred to as sensing-assisted communication. In an example, the wide coverage provider network entity 105 may facilitate efficient beam tracking procedures to reduce the overhead of beam tracking at the mmW network entity 105 or the UE 115 or both. Additionally, the wide coverage provider network entity 105 may help provide a robust wireless link (eg, for mmW communications) to the UE 115 based on sensing data collected from self-aware vehicles or surrounding smart onboard units (OBUs) or roadside units (RSUs).

[0100] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be served by multiple RUs 170-a simultaneously.

[0101] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0102] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0103] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0104] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0105] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a 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 (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a can communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a can also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0106] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

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

[0108] In some aspects, the network architecture 200 may support efficient techniques for identifying configurations for communicating using one or more RATs. Specifically, the network architecture 200 may use context information transmitted by the first UE 115 to the first network entity 105 to assist communication between the second UE 115 and the second network entity 105. The first network entity 105 and the second network entity 105 may refer to one or more of the CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, and open eNB (O-eNB) 210. The first network entity 105 may receive context information from the first UE 115 and may generate assistance information associated with the second UE 115 based on the context information. The context information may include sensory data collected at the first UE 115, and in some examples may include location, velocity, acceleration, etc. associated with the second UE 115 and other UEs 115 surrounding the second UE 115. The first network entity 105 may then provide the assistance information to the second network entity 105, the second UE 115, or both, and the second UE 115 and the second network entity 105 may use the assistance information to identify a suitable configuration for communicating with each other.

[0109] Figure 3 An example of a wireless communication system 300 supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 includes UE 115-b and UE 115-c, which may be reference Figure 1 The wireless communication system 300 also includes network entities 105-a, 105-b, and 105-c, which may be referenced. Figure 1An example of a network entity 105 described. The wireless communication system 300 may implement aspects of the wireless communication system 100 or the network architecture 200. For example, the UE 115-c, the network entity 105-b, and the network entity 105-c in the wireless communication system 300 may support efficient techniques for identifying configurations for communicating using one or more RATs, and the UE 115-b and the network entity 105-a may support efficient techniques for assisting the UE 115-c, the network entity 105-b, and the network entity 105-c in identifying these configurations.

[0110] In a wireless communication system 300 (e.g., a 5G network), there may be a sub-6 GHz network entity (e.g., network entity 105-a) and several mmW network entities (e.g., network entity 105-b and network entity 105-c) providing wireless services in a certain area. In an example, network entity 105-a may provide relatively wide wireless coverage, and network entity 105-b and network entity 105-c may enhance the peak throughput of some UEs 115 (e.g., in-vehicle UEs 115, UEs 115 located in a vehicle, or very close to a vehicle). Figure 3 The UE 115-b (e.g., a vehicle) depicted in the figure can be RRC connected to the network entity 105-a (e.g., a sub-6 GHz network entity). The UE 115-b can be equipped with, for example, a modem (e.g., a 5G modem) and one or more antennas mounted on the top, front, or rear of the UE 115-b. Various types of sensors such as radars and cameras (e.g., for autonomous driving purposes) can also be equipped in the UE 115-b. In addition, there can be at least one UE 115-c in the UE 115-b that provides advanced applications (e.g., entertainment, high-resolution movie downloads, etc.) to passengers in the UE 115-b.

[0111] In such a scenario where UE 115-c may be close to UE 115-b, UE 115-c may be paired or linked with UE 115-b, and sensing data collected by UE 115-b may be used to assist communication at UE 115-c. Such techniques may be referred to as sensing-assisted communication or sensing-assisted cross-RAT communication (e.g., because UE 115-b may be connected to a sub-6 GHz network entity 105-a and UE 115-c may be connected to a mmW network entity 105). In sensing-assisted cross-RAT communication, sensors equipped in UE 115-b or sensors equipped in other UEs 115 (e.g., sensors equipped in a vehicle) may collect environmental information for autonomous driving. This environmental information may be referred to as sensing data. The sensing data may then be used to derive the location of an object and for motion prediction, which may then be used for wireless communication.

[0112] To facilitate sensing-assisted communication, UE 115-b may report (fused) sensing data to network entity 105-a via a sub-6 GHz frequency band. If the sensing data is collected at UE 115-b and other UEs 115 or is based on data collected at UE 115-b and other UEs 115, the sensing data may be referred to as fused sensing data. The network entity 105-a may then indicate the location of UE 115-c or other information associated with UE 115-c to a serving network entity 105 (e.g., network entity 105-b or network entity 105-c) of UE 115-c in order to communicate with UE 115-c (e.g., the nearest mmW network entity). The serving network entity 105 may use the location of UE 115-c or other information associated with UE 115-c for beam tracking or to identify other coverage enhancement instructions (e.g., for location-based serving cell selection, handover prediction, serving beam instructions). Additionally or alternatively, the network entity 105-a may explicitly or implicitly provide the UE 115-c with location information of the serving network entity 105. The serving network entity 105 may then allocate sufficient resources and identify an appropriate beam or configuration (e.g., number of retransmissions, channel state information (CSI) prediction) to enhance communication with the UE 115-c based on the information received from the network entity 105-a.

[0113] As an illustrative example, UE 115-c may be located inside UE 115-b (e.g., a vehicle), and UE 115-b may be moving at a certain rate along a particular path, route, or route. UE 115-b may use one or more sensors or other instruments supported by UE 115-b to collect sensory data (e.g., over time), and the sensory data may be associated with speed, position, acceleration, direction of motion, or other parameters associated with UE 115-b and / or the environment surrounding UE 115-b. In any case, UE 115-b may send a message including contextual information to network entity 105-a. Network entity 105-a may then use the contextual information to assist other devices in wireless communication system 300. For example, network entity 105-a may provide assistance information to one or both of network entities 105-b or 105-c, which assistance information may be used to facilitate efficient beam management procedures or other procedures (e.g., handover to network entity 105-c when UE 115-b is in motion). Additionally or alternatively, network entity 105-a may provide assistance information to UE 115-c, which assistance information may similarly be used to enhance beam management or other procedures.

[0114] Figure 4An example of a wireless communication system 400 supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 includes UE 115-d and UE 115-e, which may be reference Figure 1 and Figure 2 The wireless communication system 400 also includes a network entity 105-d and a network entity 105-e, which may be referenced Figure 1 and Figure 2 Examples of network entities 105 are described.

[0115] The wireless communication system 400 may implement aspects of the wireless communication system 100, the network architecture 200, or the wireless communication system 300. For example, the UE 115-d, UE 115-e, network entity 105-d, and network entity 105-e in the wireless communication system 400 may support efficient techniques for identifying configurations for communicating using one or more RATs, and the UE 115-d and network entity 105-d may support efficient techniques for assisting the UE 115-e and network entity 105-e in identifying these configurations. These techniques may be referred to as sensing-assisted RAT communication or sensing-assisted cross-RAT communication, and may reduce the complexity of supporting mmW communication at the UE 115-e, reduce latency for beam selection at the UE 115-e and the network entity 105-e, and improve coverage in some cases (e.g., if used to schedule coordinated multi-point (CoMP) communications with the UE 115-e).

[0116] UE 115-d may report sensing data or context information 405 (e.g., context awareness information) to network entity 105-d via a sub-6 GHz frequency band. The sensing data or context information 405 may be based on sensors of the vehicle or fused data from sensor sharing messages received from surrounding vehicles or infrastructure (e.g., RSUs). In some examples, the sensing data or context information 405 may include the current location of UE 115-e and propagation losses associated with communicating with UE 115-e (e.g., from in-vehicle scenes). In some examples, the sensing data or context information 405 may include the speed, direction, acceleration, or other motion information of UE 115-e. In some examples, the sensing data or context information 405 may include the location or other motion information of objects surrounding UE 115-e, potential blockages in the future (e.g., at a future point in time), etc.

[0117] The network entity 105-d may then forward the location of the UE 115-e or other information associated with the UE 115-e to the network entity 105-e (e.g., the nearest mmW network entity). In some cases, the network entity 105-d may predict the future location of the UE 115-e (e.g., using machine learning) and indicate the future location of the UE 115-e to the network entity 105-e in advance (e.g., before the UE 115-e arrives at the future location). Additionally or alternatively, the network entity 105-d may provide recommended or restricted beam directions to the network entity 105-e (e.g., the selected serving mmW network entity 105-e) based on the sensing data or contextual information 405 to minimize beam tracking efforts. Furthermore, in some examples, network entity 105-d may select more than one serving network entity or cell based on sensing data or contextual information 405 to enable downlink CoMP to UE 115-e for better coverage (e.g., when UE 115-e is in a cell edge region).

[0118] The information sent by the network entity 105-d to the network entity 105-e may be referred to as assistance information 410. The network entity 105-d may receive sensing data or context information 405 from the UE 115-e (e.g., via a first RAT, such as a sub-6 GHz RAT), and generate the assistance information 410 based on the sensing data or context information 405. In some cases, the network entity 105-d may select or identify a serving cell to communicate with or be in communication with the UE 115-e (e.g., via a second RAT), and the network entity 105-d may identify beam set recommendations or restrictions, link state indications, etc. to provide to the network entity 105-e to assist in communications between the network entity 105-e and the UE 115-e. The network entity 105-d may send the motion information of the UE 115-e, the beam set recommendations or restrictions, the link state indications, etc. to the network entity 105-e in the assistance information 410. The network entity 105 - e may then use the assistance information 410 to determine a set of scanning beams for initial beam selection and beam tracking, or to select resource allocation, MCS, or other parameters for communicating with the UE 115 - e.

[0119] In some aspects, the network entity 105-d may also send assistance information 410 to the UE 115-e based on the sensing data or context information 405 received from the UE 115-d. That is, after selecting or identifying the network entity 105-e that serves the UE 115-e (e.g., a serving cell associated with the network entity 105-e), the network entity 105-d may signal the UE 115-e with information associated with the network entity 105-e. The assistance information 410 sent by the network entity 105-d to the UE 115-e may include explicit location information of the network entity 105-e, a recommended receiver-side beam set for receiving data from the network entity 105-e (e.g., without explicit location information of the network entity 105-e), a restricted scanning beam set for minimizing a beam scanning process at the UE 115-e, and other information.

[0120] Additionally or alternatively, the network entity 105-d may notify the UE 115-e of other radio link context information in the assistance information 410. In some examples, the assistance information 410 sent to the UE 115-e may include an indication of a potential handover to another network entity 105 or a measurement indication (e.g., a requirement) for another network entity 105. In some examples, the assistance information 410 sent to the UE 115-e may include a warning of a potential increase in interference or measurement requirements from a nearby network entity 105 (e.g., a mmW network entity 105). In some examples, the assistance information 410 sent to the UE 115-e may include link state information to assist the UE 115-e in resource management and configuration determination (e.g., power allocation enhancement in a certain direction or a certain beam, interference mitigation at a certain point in time).

[0121] Once the network entity 105-e receives the assistance information 410 from the network entity 105-d, the network entity 105-e may allocate sufficient resources for communicating with the UE 115-e. The network entity 105-e may also identify a directional beam or determine a configuration (e.g., number of retransmissions, CSI prediction, etc.) for communicating with the UE 115-e to enhance communication. In some examples, the network entity 105-e may schedule a beamforming set for beam scanning by the UE 115-e (e.g., sending the beamforming set to the UE 115-e). In some examples, the network entity 105-e may schedule a CSI-RS for beamforming of the UE 115-e based on the assistance information 410. The pre-decoder generation of the CSI-RS may be based on a directional indication in the assistance information 410 or an explicit beam indication (e.g., based on the sensing data or context information 405).

[0122] In some examples, if the network entity 105-e determines that the UE 115-e is at a cell edge or the transmit power of the network entity 105-e is power limited, the network entity 105-e may set a larger maximum number of retransmissions for sending packets to the UE 115-e. For example, the network entity 105-e may determine the maximum number of retransmissions or the maximum number of retransmissions for sending to the UE 115-e based on the assistance information 410, and the network entity 105-e may send an indication of the maximum number of retransmissions or the maximum number of retransmissions to the UE 115-e. In some examples, the network entity 105-e may select an initial or default physical layer resource configuration (e.g., MCS, MU-MIMO configuration) for communicating with the UE 115-e based on the assistance information 410 from the network entity 105-d.

[0123] Although the examples described herein relate to a cross-RAT sensing-assisted scenario in which the network entity 105-d and the network entity 105-e are associated with different RATs, the techniques described for sensing-assisted communication may be applicable to other scenarios. For example, a sub-6 GHz cell may use the described techniques to assist another sub-6 GHz cell, or a sub-6 GHz primary cell may use the described techniques to assist another sub-6 GHz secondary cell. In some cases, sensing information or contextual information 405 provided by a UE 115-d to a network entity 105-d may be collected from one or more smart UEs 115 (e.g., vehicles). Additionally or alternatively, the sub-6 GHz or mmW network entity 105 may be equipped with a camera that may have a certain level of sensitivity, and the network entity 105-e or UE 115-e may identify a suitable configuration for communicating based on the sensing information from the sub-6 GHz or mmW network entity 105. In some examples, UE 115-d and UE 115-e may also establish a wireless connection and may communicate directly so that UE 115-d may assist UE 115-e (e.g., provide sensing data or contextual information 405) in communications between UE 115-e and network entity 105-e.

[0124] In some cases, the prediction of vehicle motion parameters (e.g., motion parameters of UE 115-d) may be different for different situations (e.g., based on the specific implementation of network entity 105-d). In some cases, network entity 105-d may predict vehicle motion parameters (e.g., motion parameters of UE 115-d or UE 115-e) to be included in assistance information 410 or used to generate assistance information 410. In other cases, network entity 105-e may predict vehicle motion parameters based on assistance information 410 received from network entity 105-d. In one example, network entity 105-d or network entity 105-e may use a motion model (e.g., a Kalman filter or other model) to predict vehicle motion based on reported states (e.g., context information 405 or assistance information 410). In another example, UE 115-d may send the trained model to network entity 105-d, and network entity 105-d may use the trained model to predict vehicle movement, or network entity 105-d may provide the trained model to network entity 105-e, so that network entity 105-e may use the trained model to predict vehicle movement.

[0125] Figure 5 An example of a process flow 500 in a system supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is illustrated. The process flow 500 includes UE 115-f and UE 115-g, which may be reference Figure 1 -to Figure 3 The process flow 500 also includes network entity 105-f and network entity 105-g, which may be reference Figure 1 -to Figure 3 An example of a network entity 105 is described. The network entity 105-f and the network entity 105-g may be associated with different RATs or the same RAT. The process flow 500 may implement aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, or the wireless communication system 400. For example, the devices in the process flow 500 may support efficient techniques for identifying a configuration for communicating using one or more RATs.

[0126] In the following description of process flow 500, signaling exchanged between UE 115-f, network entity 105-f, network entity 105-g, and UE 115-g may be exchanged in an order different from the example order shown, or operations performed by UE 115-f, network entity 105-f, network entity 105-g, and UE 115-g may be performed in a different order or at a different time. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0127] At 505, UE 115-f may send context information to network entity 105-f. The context information may be sensed data collected at UE 115-f, or may be based on sensed data collected at UE 115-f. The sensed data may be collected from one or more sensors at UE 115-f or proximity sensors near UE 115-f (e.g., sensors of nearby vehicles or RSUs). In some examples, the context information may include the size, position, speed, direction of movement, velocity, acceleration, motion information, or other information of UE 115-f, other UEs 115, or mobile or stationary objects. In addition, the context information may include the location of UE 115-f, other UEs 115, or mobile or stationary objects or propagation losses associated with communicating with UE 115-g. UE 115-f may send context information to network entity 105-f periodically, aperiodically, or semi-persistently.

[0128] At 510, the network entity 105-f may generate assistance information associated with the UE 115-g based on the context information received at 505. The assistance information may include one or more parameters indicating a condition of the UE 115-g (e.g., propagation loss or link status). For example, the assistance information may include a portion or all of the context information (e.g., for transparently forwarding the assistance information to the network entity 105-g and the UE 115-g). Alternatively, the assistance information may include instructions or recommendations extracted or processed from the context information (e.g., beam, resource allocation, transmit power, MCS, or other recommendations).

[0129] At 515, the network entity 105-f may send assistance information to the network entity 105-g, the UE 115-g, or both. In one example, the network entity 105-f may determine a first location of the UE 115-g based on the context information and a second location of the network entity 105-g, and if a distance between the first location and the second location satisfies a distance threshold, the network entity 105-f may send the assistance information to the network entity 105-g. In this example, the assistance information may include handover or cell selection information, and a handover to the network entity 105-g or a cell selection of the network entity 105-g may be implemented. In another example, the network entity 105-f may determine that the network entity 105-g is associated with a serving cell for communicating with the UE 115-g, and the network entity 105-f may send the assistance information to the network entity 105-g based on the network entity 105-g being associated with the serving cell. In yet another example, the network entity 105-f may select one or more network entities 105 including the network entity 105-g for CoMP communication with the UE 115-g, and the network entity 105-f may coordinate communication between the UE 115-g and the selected one or more network entities based on the assistance information. The network entity 105-f may send the assistance information to the network entity 105-g, the UE 115-g, or both periodically, aperiodically (e.g., triggered for high throughput or high priority applications or triggered by communication failures), or semi-persistently.

[0130] In some aspects, the network entity 105-f may identify one or more recommended or restricted beam directions for beam selection at the network entity 105-g, the UE 115-g, or both based on the context information, and the network entity 105-f may send the one or more recommended or restricted beam directions for beam selection to the network entity 105-g, the UE 115-g, or both. The recommended or restricted beam directions may be referred to as beam set instructions and may have different forms. For example, the beam directions or beam set instructions may include an angle of arrival (AoA) for transmissions to the network entity 105-g, the UE 115-g, or both, an angle of departure (AoD) for transmissions from the network entity 105-g, the UE 115-g, or both, or a beam index (e.g., if there is pre-coordination between the network entity 105-f and the network entity 105-g regarding beam management). In other aspects, the network entity 105-f may predict a future location of the UE 115-g based on the contextual information, and the network entity 105-f may send a message indicating the predicted future location to the network entity 105-g, the UE 115-g, or both.

[0131] In some cases, the network entity 105-f may send a first portion of the assistance information to the network entity 105-g and a second portion of the assistance information to the UE 115-g. In other cases, the network entity 105-f may send the same portion or all of the assistance information to the network entity 105-g and the UE 115-g. In any case, a portion or all of the assistance information sent to the network entity 105-g, the UE 115-g, or both may include one or more recommended or restricted beam directions for beam selection at the network entity 105-g, the UE 115-g, or both, or a range for beam scanning to be performed by the network entity 105-g, the UE 115-g, or both during beam selection. Alternatively, part or all of the auxiliary information sent to the network entity 105-g, the UE 115-g, or both may include handover information associated with one or more other network entities 105, measurements associated with the other network entities 105, indications of interference from nearby network entities 105, or measurement requests from nearby network entities 105.

[0132] At 520, the network entity 105-g, the UE 115-g, or both may identify a configuration for communicating with each other based on the assistance information received from the network entity 105-f. In one example, the network entity 105-g, the UE 115-g, or both may determine a set of directional beams associated with a beam scanning operation for selecting beams for communicating with each other based on the assistance information, and the network entity 105-g, the UE 115-g, or both may perform the beam scanning operation using the set of directional beams. In another example, the network entity 105-g, the UE 115-g, or both may determine at least one of a resource or an MCS for communicating with each other based on the assistance information. In yet another example, the network entity 105-g, the UE 115-g, or both may determine one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with each other based on the assistance information. In some cases, the network entity 105-g may send control information to the UE 115-g based on the assistance information that configures one or more of a set of directional beams associated with a beam scanning operation, a reference signal transmission, or a threshold number of retransmissions for communicating with the UE 115-g. At 525, the network entity 105-g and the UE 115-g may then communicate using the configuration identified at 520.

[0133] Figure 6A block diagram 600 of a device 605 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the network entity 105 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0136] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0137] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise support means for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0138] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0139] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0140] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a first network entity. For example, the communication manager 620 may be configured as or otherwise support means for receiving context information from a first UE. The communication manager 620 may be configured as or otherwise support means for generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE. The communication manager 620 may be configured as or otherwise support means for sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0141] Additionally or alternatively, according to examples as disclosed herein, the communication manager 620 may support wireless communications at the first network entity. For example, the communication manager 620 may be configured as or otherwise support means for receiving assistance information associated with the first UE from the second network entity, wherein the assistance information is based on context information from a second UE that is different from the first UE. The communication manager 620 may be configured as or otherwise support means for determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity. The communication manager 620 may be configured as or otherwise support means for communicating with the first UE using one or more configurations.

[0142] By including or configuring a communication manager 620 according to examples as described herein, a device 605 (e.g., a processor controlling or otherwise coupled to a receiver 610, a transmitter 615, a communication manager 620, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 605 may receive assistance information generated based on sensing data or context information from a network entity, the device 605 may be able to identify a suitable configuration for communicating with the UE based on the assistance information. Thus, beam management at the device 605 may be improved, and retransmissions from the device 605 may be avoided or reduced (e.g., resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources).

[0143] Figure 7 A block diagram 700 of a device 705 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or the network entity 105 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0146] The device 705 or its various components may be examples of apparatuses for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 720 may include a context information manager 725, an auxiliary information manager 730, a configuration manager 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0147] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a first network entity. The context information manager 725 may be configured as or otherwise support means for receiving context information from a first UE. The assistance information manager 730 may be configured as or otherwise support means for generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE. The assistance information manager 730 may be configured as or otherwise support means for sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0148] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the first network entity. The assistance information manager 730 may be configured as or otherwise support means for receiving assistance information associated with the first UE from the second network entity, wherein the assistance information is based on context information from a second UE different from the first UE. The configuration manager 735 may be configured as or otherwise support means for determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity. The configuration manager 735 may be configured as or otherwise support means for communicating with the first UE using one or more configurations.

[0149] Figure 8 A block diagram 800 of a communication manager 820 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be an example of an apparatus for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 820 may include a context information manager 825, an assistance information manager 830, a configuration manager 835, a CoMP manager 840, a beam manager 845, a control information manager 850, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0150] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a first network entity. The context information manager 825 may be configured as or otherwise support means for receiving context information from a first UE. The assistance information manager 830 may be configured as or otherwise support means for generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE. In some examples, the assistance information manager 830 may be configured as or otherwise support means for sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0151] In some examples, the assistance information manager 830 may be configured as or otherwise support means for determining a first location of the second UE based on the context information. In some examples, the assistance information manager 830 may be configured as or otherwise support means for determining a second location of a second network entity, wherein sending the assistance information to the second network entity is based on a distance between the first location and the second location satisfying a distance threshold.

[0152] In some examples, to support generating the assistance information, the assistance information manager 830 may be configured as or otherwise support means for identifying one or more recommended or restricted beam directions for beam selection at the second network entity based on the context information, and wherein sending at least a portion of the assistance information to the second network entity comprises. In some examples, to support generating the assistance information, the assistance information manager 830 may be configured as or otherwise support means for sending one or more recommended or restricted beam directions for beam selection to the second network entity.

[0153] In some examples, assistance information manager 830 may be configured as or otherwise support means for sending at least another portion of the assistance information to the second UE to assist communication between the second UE and the second network entity.

[0154] In some examples, another portion of the assistance information includes: one or more recommended or restricted beam directions for beam selection at the second UE, a range of beam scanning for the second UE to perform during beam selection, or a combination thereof.

[0155] In some examples, another portion of the assistance information includes: handover information associated with a third network entity, measurements associated with a third network entity, an indication of interference from a nearby network entity, a measurement requirement from a nearby network entity, or a combination thereof.

[0156] In some examples, assistance information manager 830 may be configured as or otherwise support means for determining that the second network entity is associated with a serving cell for communicating with the second UE, wherein sending the assistance information to the second network entity is based on the determination.

[0157] In some examples, CoMP manager 840 may be configured or otherwise support means for selecting one or more network entities including a second network entity for coordinated multi-point communication with a second UE. In some examples, CoMP manager 840 may be configured or otherwise support means for coordinating communications between the second UE and the selected one or more network entities based on the assistance information.

[0158] In some examples, the assistance information manager 830 may be configured as or otherwise support means for predicting a future location of the second UE based on the context information, wherein sending the assistance information to the second network entity comprises. In some examples, the assistance information manager 830 may be configured as or otherwise support means for sending a message indicating the predicted future location to the second network entity.

[0159] In some examples, the contextual information includes: the location of the second UE, propagation losses associated with communications with the second UE, the speed of the second UE, the direction of movement of the second UE, the velocity of the second UE, the acceleration of the second UE, the location or other motion information of one or more objects surrounding the second UE, or a combination thereof.

[0160] In some examples, the contextual information is based on data collected at one or more sensors at the first UE, one or more sensors at one or more other UEs, or a combination thereof.

[0161] In some examples, the first network entity and the second network entity are associated with different radio access technologies or the same radio access technology.

[0162] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. In some examples, the assistance information manager 830 may be configured as or otherwise support means for receiving assistance information associated with the first UE from the second network entity, wherein the assistance information is based on context information from a second UE different from the first UE. The configuration manager 835 may be configured as or otherwise support means for determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity. In some examples, the configuration manager 835 may be configured as or otherwise support means for communicating with the first UE using one or more configurations.

[0163] In some examples, to support determining one or more configurations for communicating with the first UE, the beam manager 845 may be configured as or otherwise support means for determining, based on the auxiliary information, a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the first UE. In some examples, to support determining one or more configurations for communicating with the first UE, the beam manager 845 may be configured as or otherwise support means for performing a beam scanning operation using a set of directional beams, wherein communicating with the first UE is based on the beam scanning operation.

[0164] In some examples, to support determining one or more configurations for communicating with a first UE, the configuration manager 835 may be configured as or otherwise support a device for determining at least one of resources or modulation and coding schemes for communicating with the first UE based on auxiliary information, wherein communication with the first UE is based on the resources, the modulation and coding scheme, or both.

[0165] In some examples, to support determining one or more configurations for communicating with a first UE, the configuration manager 835 may be configured as or otherwise support a device for determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the first UE based on auxiliary information, wherein communication with the first UE is based on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0166] In some examples, the control information manager 850 may be configured as or otherwise support a device for sending control information based on auxiliary information, wherein the control information is configured for one or more of a set of directional beams associated with a beam scanning operation, a reference signal transmission, or a threshold number of retransmissions for communicating with a first UE, wherein communication with the first UE is based on the control information.

[0167] In some examples, the contextual information includes: the location of the first UE, propagation losses associated with communications with the first UE, the speed of the first UE, the direction of movement of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

[0168] Fig. 9 A diagram of a system 900 including a device 905 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a network entity 105 as described herein, or include components thereof. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 905 may include components that support output and acquisition of communications, such as a communication manager 920, a transceiver 910, an antenna 915, a memory 925, a code 930, and a processor 935. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 940).

[0169] The transceiver 910 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 910 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 910 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 905 may include one or more antennas 915 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 910 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 915, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 915, from a wired receiver); and demodulating the signal. The transceiver 910 or the transceiver 910 and one or more antennas 915 or wired interfaces (where applicable) may be examples of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0170] The memory 925 may include random access memory (RAM) and read-only memory (ROM). The memory 925 may store computer-readable, computer-executable code 930 including instructions that, when executed by the processor 935, cause the device 905 to perform various functions described herein. The code 930 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 930 may not be directly executable by the processor 935, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 925 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0171] The processor 935 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 935 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 935. The processor 935 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 925) to enable the device 905 to perform various functions (e.g., functions or tasks supporting sensing-assisted RAT communication). For example, the device 905 or a component of the device 905 may include a processor 935 and a memory 925 coupled to the processor 935, and the processor 935 and the memory 925 are configured to perform various functions described herein. The processor 935 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)), which may host functions (e.g., by executing code 930) to perform the functions of the device 905.

[0172] In some examples, bus 940 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 940 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 905, or communications performed between different components of device 905 that may be co-located or located in different locations (e.g., where device 905 may refer to a system in which one or more of communication manager 920, transceiver 910, memory 925, code 930, and processor 935 may be located in one of these different components or divided between different components).

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

[0174] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a first network entity. For example, the communication manager 920 may be configured as or otherwise support means for receiving context information from a first UE. The communication manager 920 may be configured as or otherwise support means for generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE. The communication manager 920 may be configured as or otherwise support means for sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0175] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. For example, the communication manager 920 may be configured as or otherwise support means for receiving assistance information associated with the first UE from the second network entity, wherein the assistance information is based on context information from a second UE different from the first UE. The communication manager 920 may be configured as or otherwise support means for determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity. The communication manager 920 may be configured as or otherwise support means for communicating with the first UE using one or more configurations.

[0176] By including or configuring a communication manager 920 according to examples as described herein, the device 905 may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 905 may receive assistance information generated based on sensing data or context information from a network entity, the device 905 may be able to identify a suitable configuration for communicating with the UE based on the assistance information. Thus, beam management at the device 905 may be improved, and retransmissions from the device 905 may be avoided or reduced (e.g., resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources).

[0177] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 910, one or more antennas 915 (e.g., where applicable), or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 935, the memory 925, the code 930, the transceiver 910, or any combination thereof. For example, the code 930 may include instructions executable by the processor 935 to cause the device 905 to perform various aspects of the sensing-assisted RAT communication as described herein, or the processor 935 and the memory 925 may be otherwise configured to perform or support such operations.

[0178] Fig.10 A block diagram 1000 of a device 1005 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0179] The receiver 1010 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sensing-assisted RAT communications). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0180] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to sensing-assisted RAT communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0181] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0182] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microprocessor, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise support means for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0183] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0184] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0185] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a first UE. For example, the communication manager 1020 may be configured as or otherwise support means for receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE. The communication manager 1020 may be configured as or otherwise support means for determining one or more configurations for communicating with a network entity based on the assistance information. The communication manager 1020 may be configured as or otherwise support means for communicating with a network entity using one or more configurations.

[0186] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor that controls or otherwise couples with the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 1005 can receive auxiliary information generated based on the sensing data or context information from the network entity, the device 1005 can be able to identify a suitable configuration for communicating with another network entity based on the auxiliary information. Therefore, beam management at the device 1005 can be improved, and retransmissions to the device 1005 can be avoided or reduced (e.g., resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources).

[0187] Fig.11 A block diagram 1100 of a device 1105 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 1110 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to sensing-assisted RAT communications). The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0189] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to sensing-assisted RAT communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0190] The device 1105 or its various components may be examples of apparatuses for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 1120 may include an auxiliary information manager 1125, a configuration manager 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0191] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a first UE. The assistance information manager 1125 may be configured as or otherwise support means for receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE. The configuration manager 1130 may be configured as or otherwise support means for determining one or more configurations for communicating with a network entity based on the assistance information. The configuration manager 1130 may be configured as or otherwise support means for communicating with a network entity using one or more configurations.

[0192] Fig.12 A block diagram 1200 of a communication manager 1220 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of devices for performing various aspects of sensing-assisted RAT communications as described herein. For example, the communication manager 1220 may include an assistance information manager 1225, a configuration manager 1230, a beam manager 1235, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0193] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a first UE. The assistance information manager 1225 may be configured as or otherwise support means for receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE. The configuration manager 1230 may be configured as or otherwise support means for determining one or more configurations for communicating with a network entity based on the assistance information. In some examples, the configuration manager 1230 may be configured as or otherwise support means for communicating with a network entity using one or more configurations.

[0194] In some examples, to support determining one or more configurations for communicating with a network entity, beam manager 1235 may be configured as or otherwise support means for determining, based on the auxiliary information, a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the network entity. In some examples, to support determining one or more configurations for communicating with a network entity, beam manager 1235 may be configured as or otherwise support means for performing a beam scanning operation using a set of directional beams, wherein communicating with the network entity is based on the beam scanning operation.

[0195] In some examples, to support determining one or more configurations for communicating with a network entity, configuration manager 1230 may be configured as or otherwise support a device for determining at least one of a resource or a modulation and coding scheme for communicating with the network entity based on auxiliary information, wherein communication with the network entity is based on the resource, the modulation and coding scheme, or both.

[0196] In some examples, to support determining one or more configurations for communicating with a network entity, configuration manager 1230 may be configured as or otherwise support a device for determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the network entity based on auxiliary information, wherein communication with the network entity is based on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0197] In some examples, the contextual information includes: the location of the first UE, propagation losses associated with communications with the first UE, the speed of the first UE, the direction of movement of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

[0198] Fig.13A diagram of a system 1300 including a device 1305 supporting sensing-assisted RAT communications according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).

[0199] I / O controller 1310 can manage input and output signals for device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor (such as processor 1340). In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0200] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired or wireless links as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 may be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or components thereof as described herein.

[0201] Memory 1330 may include RAM and ROM. Memory 1330 may store computer-readable, computer-executable code 1335 including instructions that, when executed by processor 1340, cause device 1305 to perform various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1330 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0202] The processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to enable the device 1305 to perform various functions (e.g., functions or tasks that support sensing-assisted RAT communication). For example, the device 1305 or a component of the device 1305 may include a processor 1340 and a memory 1330 coupled to or to the processor 1340, and the processor 1340 and the memory 1330 are configured to perform the various functions described herein.

[0203] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a first UE. For example, the communication manager 1320 may be configured as or otherwise support means for receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE. The communication manager 1320 may be configured as or otherwise support means for determining one or more configurations for communicating with a network entity based on the assistance information. The communication manager 1320 may be configured as or otherwise support means for communicating with a network entity using one or more configurations.

[0204] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 1305 may receive assistance information generated based on sensing data or context information from a network entity, the device 1305 may be able to identify a suitable configuration for communicating with another network entity based on the assistance information. Thus, beam management at the device 1305 may be improved, and retransmissions to the device 1305 may be avoided or reduced (e.g., resulting in reduced processing, reduced power consumption, and more efficient utilization of communication resources).

[0205] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform various aspects of the sensing-assisted RAT communication as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0206] Fig.14 A flowchart illustrating a method 1400 for supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 9 The network entity described herein may be executed by the network entity. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0207] At 1405, the method may include receiving context information from the first UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described context information manager 825 is executed.

[0208] At 1410, the method may include generating assistance information associated with a second UE different from the first UE, the assistance information being based on the context information and including one or more parameters indicating a condition of the second UE, the second UE being linked to the first UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The described auxiliary information manager 830 is executed.

[0209] At 1415, the method may include sending at least a portion of the assistance information to a second network entity different from the first network entity. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The described auxiliary information manager 830 is executed.

[0210] Fig.15 A flowchart illustrating a method 1500 for supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 9 The network entity described herein may be executed by the network entity. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0211] At 1505, the method may include receiving assistance information associated with the first UE from a second network entity, wherein the assistance information is based on context information from a second UE different from the first UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described auxiliary information manager 830 is executed.

[0212] At 1510, the method may include determining one or more configurations for communicating with the first UE based on the assistance information received from the second network entity. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The described configuration manager 835 is executed.

[0213] At 1515, the method may include communicating with the first UE using one or more configurations. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The described configuration manager 835 is executed.

[0214] Fig.16 A flowchart illustrating a method 1600 for supporting sensing-assisted RAT communication according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 5 and Figures 10 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1605, the method may include receiving assistance information associated with the first UE, wherein the assistance information is based on context information from a second UE different from the first UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.12 The described auxiliary information manager 1225 is executed.

[0216] At 1610, the method may include determining one or more configurations for communicating with a network entity based on the assistance information. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.12 The described configuration manager 1230 is executed.

[0217] At 1615, the method may include using one or more configurations to communicate with a network entity. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.12 The described configuration manager 1230 is executed.

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

[0219] Aspect 1: A method for wireless communication at a first network entity, comprising: receiving context information from a first UE; generating assistance information associated with a second UE different from the first UE, the assistance information being at least partially based on the context information and including one or more parameters indicating a status of the second UE, the second UE being linked to the first UE; and sending at least a portion of the assistance information to a second network entity different from the first network entity.

[0220] Aspect 2: The method according to Aspect 1 also includes: determining a first position of the second UE based at least in part on the situational information; and determining a second position of the second network entity, wherein sending the auxiliary information to the second network entity is based at least in part on a distance between the first position and the second position satisfying a distance threshold.

[0221] Aspect 3: A method according to any one of Aspects 1 to 2, wherein generating the auxiliary information includes: identifying one or more recommended or restricted beam directions for beam selection at the second network entity based at least in part on the contextual information, and wherein sending at least a portion of the auxiliary information to the second network entity includes: sending the one or more recommended or restricted beam directions for beam selection to the second network entity.

[0222] Aspect 4: The method according to any one of aspects 1 to 3 further includes: sending at least another part of the assistance information to the second UE to assist communication between the second UE and the second network entity.

[0223] Aspect 5: A method according to Aspect 4, wherein the other part of the auxiliary information includes: one or more recommended or restricted beam directions for beam selection at the second UE, a range of beam scanning for the second UE to perform during beam selection, or a combination thereof.

[0224] Aspect 6: A method according to any one of Aspects 4 to 5, wherein the other part of the auxiliary information includes: handover information associated with a third network entity, measurements associated with the third network entity, an indication of interference from a nearby network entity, a measurement request from a nearby network entity, or a combination thereof.

[0225] Aspect 7: The method according to any one of Aspects 1 to 6 also includes: determining that the second network entity is associated with a serving cell for communicating with the second UE, wherein sending the auxiliary information to the second network entity is at least partly based on the determination.

[0226] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: selecting one or more network entities including the second network entity for collaborative multi-point communication with the second UE; and coordinating communication between the second UE and the selected one or more network entities based at least in part on the auxiliary information.

[0227] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: predicting the future position of the second UE based at least in part on the contextual information, wherein sending the auxiliary information to the second network entity includes: sending a message indicating the predicted future position to the second network entity.

[0228] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the contextual information includes: the position of the second UE, the propagation loss associated with communication with the second UE, the speed of the second UE, the moving direction of the second UE, the velocity of the second UE, the acceleration of the second UE, the location or other motion information of one or more objects surrounding the second UE, or a combination thereof.

[0229] Aspect 11: The method according to any one of aspects 1 to 10, wherein the context information is based at least in part on data collected at one or more sensors at the first UE, one or more sensors at one or more other UEs, or a combination thereof.

[0230] Aspect 12: The method according to any one of aspects 1 to 11, wherein the first network entity and the second network entity are associated with different radio access technologies or the same radio access technology.

[0231] Aspect 13; A method for wireless communication at a first network entity, comprising: receiving auxiliary information associated with a first UE from a second network entity, wherein the auxiliary information is at least partially based on contextual information from a second UE different from the first UE; determining one or more configurations for communicating with the first UE based at least partially on the auxiliary information received from the second network entity; and using the one or more configurations to communicate with the first UE.

[0232] Aspect 14: A method according to Aspect 13, wherein determining the one or more configurations for communicating with the first UE includes: determining a directional beam set associated with a beam scanning operation for selecting a beam for communicating with the first UE based at least in part on the auxiliary information, and the method also includes: using the directional beam set to perform the beam scanning operation, wherein communicating with the first UE is at least in part based on the beam scanning operation.

[0233] Aspect 15: A method according to any one of Aspects 13 to 14, wherein determining the one or more configurations for communicating with the first UE includes: determining at least one of the resources or modulation and coding schemes for communicating with the first UE based at least in part on the auxiliary information, wherein communicating with the first UE is at least in part based on the resources, the modulation and coding scheme, or both.

[0234] Aspect 16: A method according to any one of Aspects 13 to 15, wherein determining the one or more configurations for communicating with the first UE includes: determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the first UE based at least in part on the auxiliary information, wherein communicating with the first UE is based at least in part on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0235] Aspect 17: The method according to any one of Aspects 13 to 16 further includes: sending control information based at least in part on the auxiliary information, the control information being configured for one or more of a directional beam set associated with a beam scanning operation, a reference signal transmission, or a threshold number of retransmissions for communicating with the first UE, wherein communication with the first UE is based at least in part on the control information.

[0236] Aspect 18: A method according to any one of Aspects 13 to 17, wherein the contextual information includes: the location of the first UE, propagation loss associated with communication with the first UE, the speed of the first UE, the moving direction of the first UE, the velocity of the first UE, the acceleration of the first UE, the location or other motion information of objects surrounding the first UE, or a combination thereof.

[0237] Aspect 19: A method for wireless communication at a first UE, comprising: receiving auxiliary information associated with the first UE, wherein the auxiliary information is at least partially based on contextual information from a second UE different from the first UE; determining one or more configurations for communicating with a network entity based at least partially on the auxiliary information; and using the one or more configurations to communicate with the network entity.

[0238] Aspect 20: A method according to Aspect 19, wherein determining the one or more configurations for communicating with the network entity includes: determining a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the network entity based at least in part on the auxiliary information, the method also including: performing the beam scanning operation using the set of directional beams, wherein communicating with the network entity is at least in part based on the beam scanning operation.

[0239] Aspect 21: A method according to any one of Aspects 19 to 20, wherein determining the one or more configurations for communicating with the network entity includes: determining at least one of the resources or modulation and decoding schemes for communicating with the network entity based at least in part on the auxiliary information, wherein communicating with the network entity is at least in part based on the resources, the modulation and decoding scheme, or both.

[0240] Aspect 22: A method according to any one of Aspects 19 to 21, wherein determining the one or more configurations for communicating with the network entity includes: determining one or more power allocation configurations, one or more interference mitigation configurations, or both for communicating with the network entity based at least in part on the auxiliary information, wherein communicating with the network entity is at least in part based on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

[0241] Aspect 23: A method according to any one of Aspects 19 to 22, wherein the contextual information includes: the location of the first UE, propagation loss associated with communication with the first UE, the speed of the first UE, the moving direction of the first UE, the velocity of the first UE, the acceleration of the first UE, the location or other motion information of objects surrounding the first UE, or a combination thereof.

[0242] Aspect 24: An apparatus for wireless communication at a first network entity, 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 a method according to any one of Aspects 1 to 12.

[0243] Aspect 25: An apparatus for wireless communication at a first network entity, comprising at least one means for performing the method according to any one of aspects 1 to 12.

[0244] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.

[0245] Aspect 27: An apparatus for wireless communication at a first network entity, 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 a method according to any one of Aspects 13 to 18.

[0246] Aspect 28: An apparatus for wireless communication at a first network entity, comprising at least one means for performing a method according to any one of aspects 13 to 18.

[0247] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 13 to 18.

[0248] Aspect 30: An apparatus for wireless communication at a first UE, 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 a method according to any one of Aspects 19 to 23.

[0249] Aspect 31: An apparatus for wireless communication at a first UE, comprising at least one means for performing a method according to any one of aspects 19 to 23.

[0250] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 19 to 23.

[0251] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0252] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0254] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0255] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0256] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates the transfer of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code means and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0258] The terms "determine" or "determining" encompass a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0259] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between the similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.

[0260] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving context information from a first user equipment (UE); generating assistance information associated with a second UE different from the first UE, the assistance information being based at least in part on the context information and comprising one or more parameters indicative of a condition of the second UE, the second UE being linked to the first UE; as well as At least a portion of the assistance information is sent to a second network entity different from the first network entity.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: determining a first location of the second UE based at least in part on the context information; and A second location of the second network entity is determined, wherein sending the assistance information to the second network entity is based at least in part on a distance between the first location and the second location satisfying a distance threshold.

3. The apparatus of claim 1 , wherein the instructions for generating the auxiliary information are executable by the processor to cause the apparatus to: identifying one or more recommended or restricted beam directions for beam selection at the second network entity based at least in part on the context information, and wherein sending the at least a portion of the assistance information to the second network entity comprises: The one or more recommended or restricted beam directions for beam selection are sent to the second network entity.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: At least another portion of the assistance information is sent to the second UE to assist communication between the second UE and the second network entity.

5. The apparatus of claim 4, wherein the other portion of the auxiliary information comprises: One or more recommended or restricted beam directions for beam selection at the second UE, ranges of beam scanning for the second UE to perform during beam selection, or a combination thereof.

6. The apparatus of claim 4, wherein the another portion of the auxiliary information comprises: Handover information associated with a third network entity, measurements associated with the third network entity, an indication of interference from a nearby network entity, a measurement requirement from a nearby network entity, or a combination thereof.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Determining that the second network entity is associated with a serving cell for communicating with the second UE, wherein sending the assistance information to the second network entity is based at least in part on the determination.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: selecting one or more network entities including the second network entity for coordinated multi-point communication with the second UE; and Communications between the second UE and the selected one or more network entities are coordinated based at least in part on the assistance information.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: and predicting a future location of the second UE based at least in part on the context information, wherein sending the assistance information to the second network entity comprises: A message is sent to the second network entity indicating the predicted future position.

10. The apparatus of claim 1, wherein the context information comprises: The position of the second UE, propagation loss associated with communication with the second UE, the speed of the second UE, the moving direction of the second UE, the velocity of the second UE, the acceleration of the second UE, the location or other motion information of one or more objects surrounding the second UE, or a combination thereof.

11. The apparatus of claim 1, wherein the context information is based at least in part on data collected at one or more sensors at the first UE, one or more sensors at one or more other UEs, or a combination thereof.

12. The apparatus of claim 1, wherein the first network entity and the second network entity are associated with different radio access technologies or the same radio access technology.

13. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving assistance information associated with a first user equipment (UE) from a second network entity, wherein the assistance information is based at least in part on context information from a second UE different from the first UE; determining, based at least in part on the assistance information received from the second network entity, one or more configurations for communicating with the first UE; as well as Communicate with the first UE using the one or more configurations.

14. The apparatus of claim 13, wherein the instructions for determining the one or more configurations for communicating with the first UE are executable by the processor to cause the apparatus to: determining, based at least in part on the assistance information, a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the first UE, wherein the instructions are further executable by the processor to cause the apparatus to: The beam scanning operation is performed using the set of directional beams, wherein communicating with the first UE is based at least in part on the beam scanning operation.

15. The apparatus of claim 13, wherein the instructions for determining the one or more configurations for communicating with the first UE are executable by the processor to cause the apparatus to: At least one of resources or a modulation and coding scheme for communicating with the first UE is determined based at least in part on the assistance information, wherein communicating with the first UE is based at least in part on the resources, the modulation and coding scheme, or both.

16. The apparatus of claim 13, wherein the instructions for determining the one or more configurations for communicating with the first UE are executable by the processor to cause the apparatus to: One or more power allocation configurations, one or more interference mitigation configurations, or both, are determined based at least in part on the auxiliary information for communicating with the first UE, wherein communicating with the first UE is based at least in part on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

17. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: Control information is sent at least in part based on the auxiliary information, and the control information is configured to configure one or more of a set of directional beams associated with a beam scanning operation, a reference signal transmission, or a threshold number of retransmissions for communicating with the first UE, wherein the communication with the first UE is at least in part based on the control information.

18. The apparatus of claim 13, wherein the context information comprises: The location of the first UE, propagation loss associated with communication with the first UE, the speed of the first UE, the moving direction of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

19. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving assistance information associated with the first UE, wherein the assistance information is based at least in part on context information from a second UE different from the first UE; determining one or more configurations for communicating with a network entity based at least in part on the assistance information; as well as The one or more configurations are used to communicate with the network entity.

20. The apparatus of claim 19, wherein the instructions for determining the one or more configurations for communicating with the network entity are executable by the processor to cause the apparatus to: determining, based at least in part on the assistance information, a set of directional beams associated with a beam scanning operation for selecting a beam for communicating with the network entity, wherein the instructions are further executable by the processor to cause the apparatus to: The beam scanning operation is performed using the set of directional beams, wherein communicating with the network entity is based at least in part on the beam scanning operation.

21. The apparatus of claim 19, wherein the instructions for determining the one or more configurations for communicating with the network entity are executable by the processor to cause the apparatus to: At least one of resources or a modulation and coding scheme for communicating with the network entity is determined based at least in part on the assistance information, wherein communicating with the network entity is based at least in part on the resources, the modulation and coding scheme, or both.

22. The apparatus of claim 19, wherein the instructions for determining the one or more configurations for communicating with the network entity are executable by the processor to cause the apparatus to: One or more power allocation configurations, one or more interference mitigation configurations, or both, are determined based at least in part on the auxiliary information for communicating with the network entity, wherein communicating with the network entity is based at least in part on the one or more power allocation configurations, the one or more interference mitigation configurations, or both.

23. The apparatus of claim 19, wherein the context information comprises: The location of the first UE, propagation loss associated with communication with the first UE, the speed of the first UE, the moving direction of the first UE, the velocity of the first UE, the acceleration of the first UE, the location of objects surrounding the first UE or other motion information, or a combination thereof.

24. A method for wireless communication at a first network entity, the method comprising: receiving context information from a first user equipment (UE); generating assistance information associated with a second UE different from the first UE, the assistance information being based at least in part on the context information and comprising one or more parameters indicative of a condition of the second UE, the second UE being linked to the first UE; as well as At least a portion of the assistance information is sent to a second network entity different from the first network entity.

25. The method according to claim 24, further comprising: determining a first location of the second UE based at least in part on the contextual information; as well as A second location of the second network entity is determined, wherein sending the assistance information to the second network entity is based at least in part on a distance between the first location and the second location satisfying a distance threshold.

26. The method of claim 24, wherein generating the auxiliary information comprises: identifying one or more recommended or restricted beam directions for beam selection at the second network entity based at least in part on the context information, and wherein sending the at least a portion of the assistance information to the second network entity comprises: The one or more recommended or restricted beam directions for beam selection are sent to the second network entity.

27. The method according to claim 24, further comprising: At least another portion of the assistance information is sent to the second UE to assist communication between the second UE and the second network entity.

28. The method of claim 27, wherein the another portion of the auxiliary information comprises: One or more recommended or restricted beam directions for beam selection at the second UE, ranges of beam scanning for the second UE to perform during beam selection, or a combination thereof.

29. The method of claim 27, wherein the another portion of the auxiliary information comprises: Handover information associated with a third network entity, measurements associated with the third network entity, an indication of interference from a nearby network entity, a measurement requirement from a nearby network entity, or a combination thereof.

30. The method of claim 24, further comprising: Determining that the second network entity is associated with a serving cell for communicating with the second UE, wherein sending the assistance information to the second network entity is based at least in part on the determination.

Images