Auxiliary beam management

Abstract

Methods, systems, and devices are described for wireless communication. A first device can receive a first message that indicates location information of a second device. The first device can obtain map information corresponding to a geographic region associated with the location information. The first device can perform a beam sweep procedure to determine a beam to use for communication with the second device. The first device can communicate with the second device using the determined beam. Additionally or alternatively, the first device can receive a first message that includes intersection information, the intersection information including beam information associated with an intersection. The first device can perform a beam sweep procedure with the second device to determine a beam to use for communication with the second device based on the intersection information. The first device can communicate with the second device using the determined beam.

Description

Cross-referencing

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 533,131, entitled “ASSISTED BEAMMANAGEMENT”, filed December 7, 2023, by DAS et al., which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following pertains to wireless communication, including auxiliary beam management. Background Technology

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

[0004] In some wireless communication systems, wireless devices can perform beam scanning. However, such methods can be improved. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses supporting auxiliary beam management. For example, a first wireless device may receive a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. The first wireless device may obtain map information corresponding to a geographic area associated with the location information. The first wireless device may perform a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a plurality of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device, at least in part based on the location information and map information. The first wireless device may use one or more beams from the first subset of beams to communicate one or more messages with the second wireless device on the second frequency band.

[0006] Additionally or alternatively, the first wireless device may receive, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes. The first wireless device may perform a beam scanning procedure with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a plurality of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the intersection information. The first wireless device may communicate one or more messages with the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0007] A method for wireless communication by a first wireless device is described. The method may include: receiving a first vehicle safety message indicating location information of a second wireless device on a first frequency band; obtaining map information corresponding to a geographic area associated with the location information; performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the location information and the map information; and conveying one or more messages to the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0008] A first wireless device for wireless communication is described. The first wireless device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code such that the first wireless device: receives a first traffic safety message indicating location information of a second wireless device on a first frequency band; obtains map information corresponding to a geographic area associated with the location information; performs a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the location information and the map information; and conveys one or more messages with the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0009] Another first wireless device for wireless communication is described. The first wireless device may include: components for receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band; components for obtaining map information corresponding to a geographic area associated with the location information; components for performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the location information and the map information; and components for conveying one or more messages with the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a first vehicle safety message indicating the location information of a second wireless device on a first frequency band; obtain map information corresponding to a geographic area associated with the location information; perform a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the location information and the map information; and convey one or more messages to the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0011] The methods described herein, examples of the first wireless device, and some examples of non-transitory computer-readable media may further include operations, features, components, or instructions for receiving, on a first frequency band, a first message from a second wireless device including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes, and wherein performing a beam scanning process may be based on the intersection information.

[0012] The methods described herein, examples of the first wireless device, and some examples of non-transitory computer-readable media may also include features, components, or instructions for receiving map information from a second wireless device.

[0013] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first wireless device may be an onboard unit (OBU) and the second wireless device may be a network entity co-located with a roadside unit.

[0014] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first wireless device may be a first onboard unit (OBU) associated with a first vehicle, and the second wireless device may be a second OBU associated with a second vehicle.

[0015] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first frequency band may be the Intelligent Transportation System (ITS) frequency band.

[0016] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the second frequency band may be a millimeter-wave frequency band.

[0017] A method for wireless communication by a first wireless device is described. The method may include: receiving, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes; performing a beam scanning procedure with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the intersection information; and conveying one or more messages to the second wireless device on the second frequency band using the one or more beams from the first subset of beams.

[0018] A first wireless device for wireless communication is described. The first wireless device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code such that the first wireless device: receives, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes; performs a beam scanning procedure with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine, based on the intersection information, one or more beams from the first subset of beams to be used for communication with the second wireless device; and communicates one or more messages with the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0019] Another first wireless device for wireless communication is described. The first wireless device may include: means for receiving, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes; means for performing a beam scanning process with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the intersection information; and means for conveying one or more messages with the second wireless device on the second frequency band using one or more beams in the first subset of beams.

[0020] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes; perform a beam scanning procedure with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the intersection information; and communicate one or more messages with the second wireless device on the second frequency band using one or more beams from the first subset of beams.

[0021] The methods described herein, examples of the first wireless device, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving a second vehicle safety message indicating the location information of a second wireless device on a first frequency band; obtaining map information corresponding to a geographic area associated with the location information; and wherein performing a beam scanning process may be based on the location information and the map information.

[0022] In some examples of the methods described herein, the first wireless device, and the non-transitory computer-readable medium, the first vehicle safety message may be a signal phase and timing message, a map data message, or a road geometry attribute message.

[0023] In some examples of the methods described herein, the first wireless device, and the non-transitory computer-readable medium, the first vehicle safety message includes a beam number parameter indicating a set of multiple beams, a beam azimuth parameter for each beam in the set of multiple beams, a beam elevation parameter for each beam in the set of multiple beams, a current beam parameter for a subset of a set of multiple lanes, or any combination thereof.

[0024] In some examples of the methods, first wireless devices, and non-transitory computer-readable media described herein, the current beam parameters may be associated with lane connection parameters that may be associated with a subset of a set of multiple lanes, wherein the beam scanning process may be performed based on the current beam parameters.

[0025] The methods described herein, examples of the first wireless device, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for performing a beam scanning process based on a subset of a set of multiple lanes corresponding to a first vehicle associated with the first wireless device, wherein a subset of the set of multiple lanes corresponds to a first subset of the beam.

[0026] In some examples of the methods described herein, the first wireless device, and the non-transitory computer-readable medium, the first vehicle safety message includes a set of multiple identifiers associated with a set of multiple available beams, and one or more beams in a first subset of the beams can be determined based on corresponding identifiers in the set of multiple identifiers.

[0027] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first wireless device may be an onboard unit (OBU) and the second wireless device may be a network entity co-located with a roadside unit.

[0028] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first vehicle safety message indicates a Public Land Mobile Network (PLMN) identifier associated with the second wireless device.

[0029] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first frequency band may be the Intelligent Transportation System (ITS) frequency band.

[0030] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the second frequency band may be a millimeter-wave frequency band. Attached Figure Description

[0031] Figure 1 An example of a wireless communication system supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0032] Figure 2 An example of a wireless communication system supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0033] Figure 3 An example of a wireless communication system supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0034] Figure 4 An example of a process flow supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0035] Figure 5 An example of a process flow supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0036] Figure 6 An example of a wireless communication system supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0037] Figure 7 An example of a process flow supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0038] Figure 8 An example of a process flow supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0039] Figure 9 and Figure 10 A block diagram of an apparatus supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0040] Figure 11 A block diagram of a communication manager supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0041] Figure 12 A diagram of a system including a device supporting auxiliary beam management, according to one or more aspects of this disclosure, is shown.

[0042] Figure 13 and Figure 14 A flowchart illustrating a method for supporting auxiliary beam management according to one or more aspects of this disclosure is shown. Detailed Implementation

[0043] Wireless communication devices can use mmWave communication for communication, which involves predicting current and future beam indices for both Wireless Wide Area Network (WWAN) and sidelink communication. Determining the narrow beam to be used for communication can involve excessive beam training overhead, consuming computational resources and incurring latency costs. Furthermore, this becomes more challenging for highly mobile applications (e.g., vehicle-to-everything (V2X) communication) because channels can change rapidly and beam training may be performed more frequently.

[0044] In some examples, a first wireless device (e.g., an onboard unit) may communicate with a second wireless device (e.g., a roadside unit (RSU) in a WWAN scenario or another OBU in a sidelink scenario) and may receive location information associated with the first wireless device (e.g., geographic location, GPS coordinates, relative positioning of the first wireless device, etc.), which may overlap with map information (e.g., pre-loaded map information, received map information, or any combination thereof). The first wireless device, the second wireless device, or both may select one or more beams to be used for the beam scanning process based on the location information and the map information, and may exclude one or more beams that may not be effective for communication based on the location information and the map information. Such a beam scanning process may be performed on an access link, a PC5 link, one or more other communication links, or any combination thereof. The first and second wireless devices may then perform a beam scanning process on this improved set of beams to select or identify beams to be used for communication.

[0045] Additionally or alternatively, in some examples, the second wireless device may transmit message relays (e.g., Signal Phase and Time (SPaT), Map Data (MAP) messages, one or more other messages, or any combination thereof) that may include information associated with the traffic intersection and beam information associated with a subset of lanes included in or associated with the traffic intersection. The first wireless device, the second wireless device, or both may exclude one or more beams from available beams based on the beam information included in the message relays and may perform a beam scanning process.

[0046] As a result of this enhanced beam management, latency (e.g., synchronization latency, connection latency, or beam alignment latency) can be reduced because the beam scanning process can take into account fewer beams selected based on location information (e.g., compared to a set of beams selected without considering location information). Furthermore, processing overhead or workload and power consumption can also be reduced.

[0047] The aspects of this disclosure are first described in the context of a wireless communication system. Then, the aspects of this disclosure are described with reference to wireless communication systems and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to auxiliary beam management.

[0048] Figure 1An example of a wireless communication system 100 supporting assisted beam management according to one or more aspects of this disclosure is shown. 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 under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

[0051] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

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

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

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

[0057] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0058] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0059] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0060] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support auxiliary beam management as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

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

[0064] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate 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 identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

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

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

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

[0068] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

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

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

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

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

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

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

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

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

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

[0078] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with 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 acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0079] Some UE 115s can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at reduced peak rates. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

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

[0082] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may 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.

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

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

[0085] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted for transmissions using one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

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

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

[0088] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

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

[0090] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, 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 transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) by transmission along different beam directions for later transmission or reception by network entity 105.

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

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

[0093] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver 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).

[0094] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0095] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0096] For example, a wireless device (e.g., an OBU or UE) may receive location information and may overlay map information with the location information to aid in performing a beam scanning process (e.g., to reduce the number of beams to be scanned during the beam scanning process). Additionally or alternatively, the wireless device may receive intersection information (e.g., in an SPaT or MAP message) that may include beam information (e.g., beam direction information or other information about one or more beams associated with the intersection) that can aid in performing the beam scanning process (e.g., to reduce the number of beams to be scanned during the beam scanning process).

[0097] Figure 2 An example of a wireless communication system 200 supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0098] In WWAN communications (e.g., involving mmWave communications), wireless devices can predict current and future beam indices to be used for communication. However, determining the beams to be used for communication can involve excessive beam training overhead, which consumes computational resources and incurs latency costs. Furthermore, for highly mobile applications, beam prediction or management may involve additional challenges due to rapid channel changes and more frequent beam training.

[0099] Some methods use sensed information about the environment (e.g., through cameras, LiDAR, or other environmental sensors) to reduce training overhead. For example, a wireless device can use sensory input from the same time step to predict one or more beams, or it can use sensory input from previous time steps to predict one or more future beams.

[0100] However, such methods can be improved by utilizing location information in vehicle safety messages (e.g., vehicle-to-vehicle (V2V) messages or vehicle-to-infrastructure (V2I) messages) exchanged between one or more OBUs, one or more RSUs, one or more network entities co-located with one or more RSUs, or any combination thereof, thereby further reducing the training overhead for WWAN beam prediction and tracking. Once such information is obtained and a beam has been selected or predicted, this obtained beam information can be sent to a rear OBU (or an OBU located in any location, such as its location relative to or adjacent to the first radio device) to similarly further reduce the overhead of that OBU.

[0101] For example, an RSU 220 co-located with network entity 105-a may communicate with a first OBU 210 (which may be associated with a vehicle). In some examples, such communication may be performed on a first channel 235 that may be associated with an ITS band. Such communication may help facilitate beam management of communication between OBU 210 and network entity 105-a. In some examples, various wireless devices (e.g., first OBU 210, second OBU 215, RSU 220, network entity 105-a, or any combination thereof) may include multiple antenna elements or arrays to communicate via different frequency bands such as an ITS band (e.g., to which the first channel 235 may be associated) and an mmWave band (e.g., to which the second channel 240 may be associated).

[0102] In some examples, the first OBU 210 may receive a first vehicle safety message 255 (e.g., a V2I or I2V message) on a first channel 235 that may be associated with an ITS band (such as the 5.9 GHz band) from the RSU 220. This first vehicle safety message may include location information 280 associated with the RSU 220, the co-located network entity 105-a, or both. The included location information 280 may allow for more efficient beam management of communications on a second channel 240 (e.g., which may be associated with the mmWave band or the FR2 band).

[0103] For example, the first OBU 210 and network entity 105-a may perform a beam scanning process based on location information received from a first vehicle safety message on the first channel 235. The first OBU 210 and network entity 105-a may employ beam scanning including beams (e.g., beams 225, 230, or both) oriented towards one or more locations indicated in the location information 280. (E.g., using only a subset of the available beams of the first OBU 210 during the beam scanning process, wherein the beams in this subset are oriented in the direction of the location information 280, and other beams among the available beams are excluded from the beam scanning process.) This subset of beams may include beams located within one or more sectors of a sphere, or beams within an azimuth range corresponding to the location information 280, or beams having an elevation range corresponding to the location information 280, and other available beams may be excluded. For example, beams pointing in different directions (such as beam 285 of the first OBU 210) can be excluded from the beam scanning process. Network entity 105-a and OBU 215 may similarly have one or more beams pointing in directions opposite to the desired direction, and these one or more beams can also be excluded from the beam scanning process. As part of the beam scanning process, beams 225 and 230 can be scanned separately to determine which beams 225 and 230 should be used for communication between the first OBU 210 and network entity 105-a (e.g., for conveying one or more first messages 260).

[0104] Using such location information 280 during the initial access process can reduce synchronization and connection latency, as well as processor workload. Furthermore, it can reduce power consumption at one or more devices (e.g., OBU, RSU, network entity, small cell RSU / gNB, or any combination thereof).

[0105] In addition, the first OBU 210 may optionally send path prediction information to network entity 105-a or RSU 220 in a Basic Safety Message (BSM). This path prediction information may include one or more predicted locations of the first OBU 210 or associated vehicles at one or more points in time. Network entity 105-a may use this path prediction information for finer beam tracking, such as by refining the beam scanning process (e.g., by selecting one or more beams that correspond to the prediction information or the location indicated therein).

[0106] In some examples, the first OBU 210 may be associated with an autonomous vehicle. In such examples, the autonomous vehicle or the first OBU 210 may send a path trajectory to network entity 105-a to improve the beam scanning process in a similar manner (e.g., by allowing network entity 105-a to select a beam for the beam scanning process corresponding to the path trajectory sent by the first OBU 210).

[0107] In some examples, network entity 105-a may send an indication of future beam selection 275 associated with one or more future points in time for beam 225, beam 230, or both. The first OBU 210 may use the information from beam selection 275 (e.g., by reducing the number of beam pools to be scanned during beam scanning) to further reduce the complexity of the beam scanning process and improve beam tracking.

[0108] In some examples, the first OBU 210 may (e.g., on a third channel 245 that may be associated with the mmWave band) send Sensor Data Sharing Messages (SDSM) or Common Sensing Messages (CPM), such as SDSM / CPM 265 (which may be SDSM or CPM), to a second OBU 215 that may be associated with a second vehicle (e.g., a rear vehicle or a vehicle located at any location, such as relative to the location of the first OBU 210 or adjacent to the first wireless device). In some examples, the first OBU 210 may not send SDSM or CPM, but instead send another type of signaling or message that performs a similar function as described herein with respect to SDSM or CPM or carries similar information as described herein with respect to SDSM or CPM. Additionally or alternatively, the first OBU 210 may send information associated with network entity 105-a, such as the number of beams, geographic location, one or more services provided by network entity 105-a, other information associated with network entity 105-a, or any combination thereof. Furthermore, SDSM / CPM 265 may also include information associated with the first OBU 210, such as the location of the first OBU 210. If RSU 220 is co-located with network entity 105-a, using SDSM / CPM may be beneficial if network entity 105-a does not send I2V messages including its location information. In some examples, following vehicles may adjust their travel paths accordingly (e.g., to eventually enter the good coverage area of ​​network entity 105-a).

[0109] The second OBU 215 can use information from SDSM / CPM 265 to more efficiently select and perform the beam scanning process. For example, the second OBU 215 can select (e.g., beams 250, 230, or both) one or more beams that correspond to the location of network entity 105-a, or that correspond to beams determined through the beam scanning process between the first OBU 210 and network entity 105-a (e.g., one or more beams in beam 230). In this way, the second OBU 215 can perform its own beam scanning process with network entity 105-a with reduced synchronization and connection latency, processor workload, and power consumption. The second OBU 215 can then use one or more beams (e.g., selected or determined) as a result of the beam scanning process between the second OBU 215 and network entity 105-a to communicate one or more second messages 270.

[0110] Such use of the SDSM / CPM 265 may be particularly useful when the RSU 220, which is co-located with network entity 105-a, does not send the first vehicle safety message 255 or does not include location information 280 in the first vehicle safety message 255. Therefore, even if the first OBU 210 does not use location information 280 during its beam scanning process with network entity 105-a, the second OBU 215 can utilize the results of the beam scanning process (e.g., beam selection) between the first OBU 210 and network entity 105-a to reduce latency, overhead, and power consumption during the beam scanning process between the second OBU 215 and network entity 105-a.

[0111] In some examples, a second vehicle associated with the second OBU 215 may change its travel path based on SDSM / CPM 265. For example, the second vehicle may adjust its travel path to better traverse the coverage area of ​​network entity 105-a, thereby improving the beam scanning process between the second OBU 215 and network entity 105-a, as well as the communication performed using the beams determined or selected during the beam scanning process (e.g., conveying one or more second messages 270).

[0112] In some examples, SDSM, CPM, or other signaling may include source data, detected object data, or both. In some examples, SDSM / CPM 265 may include information or parameters from host data, such as the following example sensor sharing message, which may include MmWave parameters. This parameter or sequence, one or more other parameters or sequences, or both may indicate information associated with network entity 105-a, such as the number of beams, location, one or more services provided by network entity 105-a, other information associated with network entity 105-a, or any combination thereof.

[0113]

[0114] In some examples, the MmWaveData parameter or sequence may include information such as that included in the following examples of MmWaveData parameters or sequences.

[0115]

[0116] Furthermore, SDSM / CPM 265 or other signaling may also include information or parameters in the detected object data (e.g., one or more detected or sensed objects), such as the example DetetectedObjectList below, which may include DetectedObjectData of the detected objects. Such instances of DetectedObjectData may include the DetMmWave parameter. This parameter or sequence, one or more other parameters or sequences, or both may indicate information associated with network entity 105-a, such as the number of beams, location, one or more services provided by network entity 105-a, other information associated with network entity 105-a, or any combination thereof.

[0117]

[0118] In some examples, the detMmWave parameter or sequence may include information such as that included in the following example of the detMmWave parameter or sequence.

[0119]

[0120] In some examples, map information 290 may be obtained from the first OBU 210, network entity 105-a, second OBU 215, or any combination thereof. This map information may correspond to or be associated with location information 280, the location of the first OBU 210, the location of the RSU 220, the location of network entity 105-a, the location of the second OBU 215, or any combination thereof. In some examples, map information 290 may be independent of location information (e.g., location information 280). The first OBU 210, network entity 105-a, second OBU 215, or any combination thereof may overlap with map information 290 and location information 280 (or other location information as described herein), and a beam scanning process may be performed using one or more beams (e.g., beam 225, beam 230, or beam 250), which may be selected at least in part based on map information 290, location information 280, other location information as described herein, or any combination thereof for the beam scanning process. The use of map information 290 can be applied to the beam scanning process between the first OBU 210 and network entity 105-a, the beam scanning process between the second OBU 215 and network entity 105-a, or any combination thereof.

[0121] In some examples, map information 290 can be pre-loaded, obtained via a wireless communication network, or any combination thereof. For example, a coarse or less detailed version of map information 290 can be pre-loaded at the device, and more detailed map information can be downloaded via a wireless communication network (e.g., based on the location of such a device). Furthermore, in some examples, the entire map information 290 can be downloadable via a wireless communication network.

[0122] Using this type of map information 290 can help improve location information 280 or other location information for the first OBU 210, the second OBU 215, network entity 105-a, or any combination thereof. For example, the location of RSU 220 or the first OBU 210 can be calculated or obtained more accurately (e.g., lane positioning or location can be determined more precisely). In some examples, obstacles, road trajectories, geographic features, buildings, or other environmental conditions or objects can be determined based on map information 290, and the beam scanning process can be adjusted accordingly (e.g., by selecting one or more beams to be used in the beam scanning process based on map information 290).

[0123] Figure 3 An example of a wireless communication system 300 supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0124] Just as the beam scanning process between an OBU and network entity 105-a can be improved, the beam scanning process between multiple OBUs communicating in a sidelink can also be improved. For example, in sidelink communication (e.g., including sidelink mmWave communication), the wireless device can predict the current and future beam indices to be used for communication. However, determining narrow beams can involve excessively high beam training overhead, which consumes computational resources and incurs latency costs. Furthermore, for highly mobile applications, beam prediction or management may involve additional challenges due to rapid channel changes and more frequent beam training.

[0125] Some methods (e.g., in stationary situations) use sensed information about the environment (e.g., via cameras, LiDAR, or other environmental sensing) to reduce training overhead. For example, a wireless device can use sensed input from the same or current time to predict one or more beams, or it can use sensed input from previous time steps to predict one or more future beams. However, such methods can be improved by leveraging location and beam management information in SSB communications (or other signaling) and MSCM exchanged between OBUs, thereby reducing the training overhead for sidelink beam prediction and tracking. For example, OBUs can communicate via unicast sessions in unlicensed sidelink mmWave communications for applications such as raw sensor sharing with a first antenna and hardware, and can also use the ITS band to transmit vehicle safety messages (e.g., BSMs) via a second antenna or hardware.

[0126] For example, to establish a unicast sidelink session, the first OBU 310 and the second OBU 315 can align their beams during a beam scan, optionally involving sidelink SSB communication or any other type of signaling compatible with the beam scan process. Other types of sensing can be used, for example. While the examples included herein may describe multiple types of signaling, other types of signaling with the same or similar techniques (e.g., certain types of RF sensing signaling) can also be used. These techniques can also be used to establish unicast sidelink sessions between OBU-RSUs. Such operations can transmit a beam scan, but this can involve additional latency compared to the WWAN case due to differences in periodicity. For example, in a sidelink, a transmit beam scan of 64 beams has a duration of at least 8 ms (e.g., in the case of an S-SSB burst). Since an S-SSB burst has a periodicity of 160 ms, assuming there are 8 beams on the receiving side, the entire beam scan process can have a duration of more than 1.28 seconds. This type of latency is higher than the beam alignment latency in a WWAN (e.g., in a WWAN, the periodicity of an SSB burst can be 20ms). Given this increase in latency, including location information (e.g., geographic location information, relative location information, or other location information) in vehicle safety messages (e.g., BSM) or other messages can help significantly reduce latency, overhead, and power consumption.

[0127] In some examples, the OBU may transmit such vehicle safety messages (e.g., BSM) at different rates (e.g., 10 Hz or lower, depending on the level of congestion). Therefore, the location information 395 included in the first vehicle safety message 355 may be used to adjust beam 325, beam 330, or both during initial alignment and session establishment, as well as during tracking operations. In some examples, sidelink positioning information or procedures may be used to enhance the accuracy of the location information 395. Such sidelink positioning information may be applicable to OBU-to-OBU communication, or to OBU-to-RSU communication where the RSU has an accurate understanding of its own true location.

[0128] For example, the second OBU 315 may send a first vehicle safety message 355 (e.g., a BSM) to the second OBU 310 on a first channel 335 (which may be associated with an ITS band). The first vehicle safety message 355 may include location information 395 that may be associated with the second OBU 315. Such location information 395 may indicate one or more locations of the second OBU 315 in the past, present, or future. The first OBU 310 and the second OBU 315 may perform a beam scanning procedure (e.g., on a second channel 340 that may be associated with an mmWave band) to select or determine (e.g., beam 325, beam 330, or both) one or more beams to be used for communication (e.g., for conveying one or more first messages 360 on the second channel 340).

[0129] In some examples, location information 395 can be used to select or determine (or alternatively exclude) one or more beams from a pool of candidate beams to be used in performing the beam scanning process. For example, some of beams, such as beams 325, 330, or both, may be oriented in a direction corresponding to location information 395 or toward a position corresponding to that location information, and thus may be included in the beam scanning process. However, if other beams are not at least partially oriented in a direction corresponding to location information 395 or toward a position corresponding to that location information, they may be excluded from the beam scanning process.

[0130] In some examples, when the first OBU 310 and the second OBU 315 exchange MSCM 365 to coordinate maneuvers 370 (such as lane changes), they can participate in mmWave unicast sessions (e.g., for raw sensor sharing). Maneuver 370 may include one or more locations (by P1, P2...P... n (Specified), the first vehicle may be located at one or more locations at a certain time during the maneuver.

[0131] As part of the mobility coordination process, the first OBU 310 and the second OBU 315 are interchangeable with various types of MSCM365 (e.g., including...). Figure 3As depicted herein, these MSCMs (e.g., individually or collectively) can be unicast messages, multicast messages, or broadcast messages. For example, a first OBU 310 may send a first MSCM 365, which may be a maneuver request message (e.g., a type 1 MSCM), to a second OBU 315. The maneuver request message may include information such as maneuver start and end times, minimum and maximum speeds, and target road resources (TRR). Other MSCM types may include maneuver intent (mSCM type = 0), maneuver request (mSCM type = 1), maneuver response (mSCM type = 2), maneuver reservation (mSCM type = 3), HV (e.g., vehicle ahead) maneuver cancellation (mSCM type = 4), RV (e.g., vehicle behind or vehicle located at any location (such as relative to the OBU or other radio equipment associated with the vehicle, or adjacent to the OBU or other radio equipment associated with the vehicle)) maneuver cancellation request (mSCM type = 5), emergency maneuver reservation (mSCM type = 6), and maneuver execution status (mSCM type = 7).

[0132] However, in some examples, the maneuver coordination process using MSCM 365 can be improved by including additional types of MSCM 365, which may include beam management requests (MSCM type = 8), beam management responses (MSCM type = 9), or both.

[0133] For example, a first OBU 310 may send a beam management request MSCM (e.g., a type 8 MSCM) to initiate a beam management session with one or more specific OBUs or vehicles (e.g., a second OBU 315 associated with a second vehicle), identified by one or more destination IDs that may be included in the beam management request MSCM. The beam management request MSCM may also include additional information about the maneuver to be performed (which may not yet be included in the maneuver request), such as intermediate locations P1 and P2 with corresponding time instances. In some examples, the maneuver request message may include data fields to indicate the OBU or vehicle to which beam management is to be performed.

[0134] The second OBU 315 can take into account information about the maneuvering of the first OBU 310 and calculate relevant beams (e.g., beams B1, B2...B1) during its maneuvering process. nThe second OBU 315 may send a beam management response MSCM (e.g., a type 9 MSCM) to the first OBU 310, which may include the calculated relevant beams to be used during maneuvering. The beam management response MSCM may indicate positioning (e.g., P1, P2...P...). n ) and beams (B1, B2...B n The correlation between beams can be unicast, multicast, or broadcast messages. In some examples, the angular coverage of each beam (e.g., in the azimuth and elevation directions) can also be delivered in the beam management response MSCM.

[0135] In some examples, the first OBU 310, the second OBU 315, or any combination thereof may obtain map information 398, which may correspond to or be associated with the location information 395, the location of the first OBU 310, the second OBU 315, or any combination thereof. In some examples, the map information 398 may be independent of the location information (e.g., location information 395). The first OBU 310, the second OBU 315, or any combination thereof may overlap with the map information 398 and the location information 395 (or other location information as described herein), and a beam scanning process may be performed using one or more beams (e.g., beam 225, beam 230, or beam 250), which may be selected for the beam scanning process based at least in part on the map information 398, the location information 395, other location information as described herein, or any combination thereof. The use of map information 398 can be applied to the beam scanning process between the first OBU 310 and network entity 105-a, the beam scanning process between the second OBU 315 and network entity 105-a, or any combination thereof.

[0136] In some examples, map information 398 can be pre-loaded, obtained via a wireless communication network, or any combination thereof. For example, a coarse or less detailed version of map information 398 can be pre-loaded at the device, and more detailed map information can be downloaded via a wireless communication network (e.g., based on the location of such a device). Furthermore, in some examples, the entire map information 398 can be downloaded via a wireless communication network.

[0137] Using this type of map information 398 can help improve location information 395 or other location information for the first OBU 310, the second OBU 315, network entity 105-a, or any combination thereof. For example, the location of the first OBU 310 or the second OBU 315 can be calculated or obtained more accurately (e.g., lane positioning or location can be determined more precisely). In some examples, obstacles, road trajectories, geographic features, buildings, or other environmental conditions or objects can be determined based on map information 398, and the beam scanning process can be adjusted accordingly (e.g., by selecting one or more beams to be used in the beam scanning process based on map information 398).

[0138] Figure 4 An example of a process flow 400 supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0139] Process flow 400 can implement various aspects of the present disclosure described herein. Elements described in process flow 400 (e.g., first wireless device 405, second wireless device 410, and third wireless device 415) can be examples of similarly named elements described herein.

[0140] In some examples described herein, the second wireless device 410 may be an RSU, a network entity, a network entity co-located with an RSU, an OBU, or another wireless device. In some cases, the different operations described in process flow 400 may be applicable to different examples of the second wireless device 410. For example, as shown in process flow 400, an example of the second wireless device 410 is a network entity co-located with an RSU, and another example of the second wireless device 410 is an OBU; these two examples are depicted side by side. In some examples, one or more operations in process flow 400 may be applicable to, or associated with, an example of a network entity co-located with an RSU, an example of an OBU, or both. Although some elements and operations are shown as examples, other combinations of elements, operations, or other subjects disclosed herein are possible.

[0141] In the following description of process flow 400, operations between various entities or elements may be performed in different order or at different times. Some operations may also be excluded from process flow 400, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 400, some aspects of some operations may also be performed by other entities or elements of process flow 400, or by entities or elements not depicted in the process flow, or any combination thereof.

[0142] At 420, the first wireless device 405 can receive a first vehicle safety message on a first frequency band that indicates the location information of the second wireless device 410. In some examples, the first wireless device is an onboard unit (OBU) and the second wireless device 410 is a network entity co-located with a roadside unit (RSU). In some examples, the first wireless device is a first onboard unit (OBU) and the second wireless device 410 is a second OBU. In some examples, the first frequency band is an Intelligent Transportation System (ITS) frequency band.

[0143] At 425, the first wireless device 405 can send the predicted path to be taken by the first wireless device to the second wireless device 410. In some examples, the first subset of the beam corresponds to the predicted path and the location information.

[0144] At 430, the first wireless device 405 can receive an indication of the first subset of the beam from the second wireless device 410.

[0145] At 435, the first wireless device 405 may perform a beam scanning procedure with the second wireless device 410 on a second frequency band different from the first frequency band using a first subset of beams from a plurality of available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device 410, each beam in the first subset of beams being oriented at least partially in a direction corresponding to the location information of the second wireless device 410. In some examples, the beam scanning procedure may be performed on an access link, a PC5 link, one or more other communication links, or any combination thereof. In some examples, the second frequency band is a millimeter-wave band.

[0146] At 440, the first wireless device 405 may use one or more beams from the first subset of the beams on the second frequency band to communicate one or more messages with the second wireless device 410. In some examples, the first wireless device 405 may use one or more beams from the first subset of the beams on the second frequency band to communicate with the second wireless device 410 in a sidelink unicast session.

[0147] At 445, the first wireless device 405 may send an indication of one or more beams in the first subset of beams to a third wireless device 415 associated with the second vehicle, wherein the first subset of beams corresponds to the location of the first wireless device and the location information, and wherein the first subset of beams is identified based on the location of the first wireless device and the location information. In some examples, the first wireless device 405 may send the indication of one or more beams in the first subset of beams via a sensor data sharing message or a co-sensing message.

[0148] At 450, the first wireless device 405 may send to the third wireless device 415 an indication of the number of one or more beams in the first subset of the beams, an indication of one or more azimuth angles associated with one or more beams in the first subset of the beams, an indication of one or more elevation angles associated with one or more beams in the first subset of the beams, an indication of one or more services provided by the second wireless device 410, or any combination thereof.

[0149] At 455, the first wireless device 405 may send a first Mobility Sharing and Coordination Message (MSCM) to the second wireless device 410, which may include a beam management session request and mobility information associated with a mobility to be performed by a vehicle associated with the first wireless device. In some examples, the first MSCM may indicate one or more wireless devices associated with a corresponding vehicle that has been requested to participate in the beam scanning process.

[0150] At 460, the first wireless device 405 may receive from the second wireless device 410 a second MSCM that may include an indication of the first subset of the beam, the first subset of the beam being at least partially oriented toward one or more locations associated with the maneuver.

[0151] Figure 5 An example of a process flow 500 supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0152] Process flow 500 can implement various aspects of the present disclosure described herein. Elements described in process flow 500 (e.g., first wireless device 505, second wireless device 510, and third wireless device 515) may be examples of similarly named elements described herein.

[0153] In the following description of process flow 500, operations between various entities or elements may be performed in different order or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 500, some aspects of some operations may also be performed by other entities or elements of process flow 500, or by entities or elements not depicted in the process flow, or any combination thereof.

[0154] At 520, the second wireless device 510 can transmit a first vehicle safety message on the first frequency band that indicates the location information of the second wireless device. In some examples, the first wireless device 505 is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit (RSU). In some examples, the first frequency band is an Intelligent Transportation System (ITS) band. In some examples, the second frequency band is a millimeter-wave band.

[0155] At 525, the second wireless device 510 can receive from the first wireless device 505 the predicted path to be taken by the first wireless device 505, and a first subset of the beam can correspond to the predicted path and the location information.

[0156] At 530, the second wireless device 510 can send an indication of the first subset of the beam to the first wireless device 505.

[0157] At 535, the second wireless device 510 may use a first subset of beams from a plurality of available beams to perform a beam scanning process with the first wireless device 505 on a second frequency band different from the first frequency band to determine one or more beams in the first subset of beams to be used for communication with the first wireless device 505, each beam in the first subset of beams being oriented at least partially in a direction corresponding to the location information of the second wireless device.

[0158] At 540, the second wireless device 510 may use one or more beams from the first subset of the beams on the second frequency band to communicate one or more messages with the first wireless device 505.

[0159] At 545, the second wireless device 510 may perform a second beam scanning process with the third wireless device 515 on the second frequency band and based on one or more beams in the first subset of beams to determine one or more second beams in the first subset of beams to be used for communication with the third wireless device 515, and the location of the third wireless device 515 corresponds to the location information of the second wireless device.

[0160] At 550, the second wireless device 510 may use the one or more second beams on the second frequency band to communicate one or more second messages with the third wireless device 515.

[0161] Figure 6 An example of a wireless communication system 600 supporting assisted beam management according to one or more aspects of this disclosure is shown.

[0162] In some examples, a first wireless device 605 (e.g., an OBU) may communicate with a second wireless device 610. The second wireless device 610 may include an RSU, a network entity, or both. In some examples, the second wireless device 610 may include a co-located RSU and a network entity. The first wireless device 605 may be associated with vehicles that may be traveling near an intersection 650, which may include one or more lanes 655.

[0163] In some examples, the first wireless device 605 may receive a first vehicle safety message 620 from the second wireless device 610. In some examples, the first vehicle safety message 620 may be a signal phase and timing (SPaT) message, a TSPAT message, a map information (MAP) message, or a road geometry attribute message. The first vehicle safety message 620 may include intersection information 625 associated with intersection 650. The intersection information 625 may include information associated with beam 635, beam 640, or both, which can be used in the beam scanning process between the first wireless device 605 and the second wireless device 610.

[0164] For example, intersection information 625 may include information associated with the intersection, including intersection identifiers, reference points, one or more indications of lanes 655, one or more connections associated with one or more lanes 655, one or more signal groups (e.g., including or associated with one or more connections), or any combination thereof. Such information may be included in a MAP message, such as the following example MAP message:

[0165]

[0166] Additionally or alternatively, intersection information 625 may include the intersection status of intersection 650, the intersection identifier associated with intersection 650, one or more indications of one or more signal groups, the current phase of the signal group, the end time of the current phase of the signal group, one or more upcoming phases of the signal group, or any combination thereof. Such information may be expressed as shown in the following example of an SPaT message:

[0167]

[0168] Additionally or alternatively, the intersection information 625 may include a Public Land Mobile Network (PLMN) identifier, beam azimuth information, beam elevation information, current beam information (e.g., the beam used at the second radio device 610), or any combination thereof. Such information may be associated with the intersection geometry portion of a MAP message, one or more connection portions of a MAP message, or any combination thereof. Additionally or alternatively, such information may be associated with signal groups indicated or included in an SPaT message. Furthermore, such information may be expressed as in the following example of a millimeter-wave data element:

[0169]

[0170] In some examples, intersection information 625 can be static, semi-static, or dynamic. For example, in some situations or at intersection 650, traffic direction or other characteristics of the intersection may vary at different times of day or based on other factors. In some examples, the second wireless device 610 (e.g., the network entity of the second wireless device 610) may include the ability for antenna steering, which can be used to adjust the amount of wireless coverage or bandwidth to one or more lanes 655 of intersection 650. In some examples, the beamwidth of beam 635, beam 640, or both may be adjusted based on different traffic conditions.

[0171] Therefore, the second wireless device 610 may indicate one or more beams, beam direction information, beam exclusion information, or any combination thereof to the first wireless device 605 and other wireless devices. Such information may be applicable to one or more lanes 655 at an intersection. For example, first beam information may be applicable to devices associated with a first set of lanes (e.g., in lanes 655), while second beam information (e.g., different from the first beam information) may be applicable to devices associated with a second set of lanes (e.g., in lanes 655). A set of lanes may include one or more entrance lanes, one or more exit lanes, or any combination thereof.

[0172] After performing a beam scanning process or in response to performing a beam scanning process, the first wireless device 605 and the second wireless device 610 may use one or more beams determined or selected through the beam scanning process to convey one or more messages 630.

[0173] Figure 7 An example of a process flow 700 supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0174] Process flow 700 can implement various aspects of the present disclosure described herein. Elements described in process flow 700 (e.g., first wireless device 705 and second wireless device 710) can be examples of similarly named elements described herein.

[0175] In the following description of process flow 700, operations between various entities or elements may be performed in different order or at different times. Some operations may also be excluded from process flow 700, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 700, some aspects of some operations may also be performed by other entities or elements of process flow 700, or by entities or elements not depicted in the process flow, or any combination thereof.

[0176] At 720, the first wireless device 705 can receive a first vehicle safety message indicating the location information of the second wireless device on a first frequency band. In some examples, the first wireless device is an onboard unit (OBU) and the second wireless device 710 is a network entity co-located with a roadside unit. In some examples, the first wireless device is a first onboard unit (OBU) associated with a first vehicle and the second wireless device 710 is a second OBU associated with a second vehicle. In some examples, the first frequency band is an Intelligent Transportation System (ITS) frequency band.

[0177] At 725, the first wireless device 705 may receive, on a first frequency band, a first message from the second wireless device that may include intersection information associated with an intersection that may include multiple lanes, and the intersection information may include beam direction information associated with a subset of the multiple lanes.

[0178] At 730, the first wireless device 705 can obtain map information corresponding to the geographic area associated with the location information. In some examples, the first wireless device 705 can receive map information from a second wireless device.

[0179] At 735, the first wireless device 705 may use a first subset of beams from a plurality of available beams on a second frequency band different from the first frequency band to perform a beam scanning procedure with the second wireless device 710 to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on location information and map information. In some examples, the beam scanning procedure is performed based on intersection information. In some examples, the second frequency band is a millimeter-wave band.

[0180] At 740, the first wireless device 705 may use one or more beams from the first subset of the beams in the second frequency band to communicate one or more messages with the second wireless device 710.

[0181] Figure 8 An example of a process flow 800 supporting auxiliary beam management according to one or more aspects of this disclosure is shown.

[0182] Process flow 800 can implement various aspects of the present disclosure described herein. Elements described in process flow 800 (e.g., first wireless device 805 and second wireless device 810) may be examples of similarly named elements described herein.

[0183] In the following description of process flow 800, operations between various entities or elements may be performed in different order or at different times. Some operations may also be excluded from process flow 800, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 800, some aspects of some operations may also be performed by other entities or elements of process flow 800, or by entities or elements not depicted in the process flow, or any combination thereof.

[0184] At 820, the first wireless device 805 may receive, on a first frequency band, a first traffic safety message that may include intersection information associated with an intersection that may include multiple lanes, and the intersection information may include beam direction information associated with a subset of the multiple lanes. In some examples, the first traffic safety message is a signal phase and timing message, a map data message, or a road geometry attribute message. In some examples, the first traffic safety message may include a beam count parameter indicating multiple beams, a beam azimuth parameter for each of the multiple beams, a beam elevation parameter for each of the multiple beams, a current beam parameter for a subset of the multiple lanes, or any combination thereof. In some examples, the current beam parameter is associated with a lane connection parameter associated with a subset of the multiple lanes. In some examples,

[0185] The first vehicle safety message may include multiple identifiers associated with multiple available beams. In some examples, the first radio device is an onboard unit (OBU) and the second radio device 810 is a network entity co-located with a roadside unit. In some examples, the first vehicle safety message indicates a Public Land Mobile Network (PLMN) identifier associated with the second radio device. In some examples, the first frequency band is an Intelligent Transportation System (ITS) frequency band.

[0186] At 825, the first wireless device 805 can receive a second vehicle safety message on the first frequency band that indicates the location information of the second wireless device.

[0187] At 830, the first wireless device 805 can obtain map information corresponding to the geographic area associated with the location information.

[0188] At 835, the first wireless device 805 may use a first subset of beams from a plurality of available beams in a second frequency band different from the first frequency band to perform a beam scanning procedure with the second wireless device 810 to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on intersection information. In some examples, the beam scanning procedure is performed based on location information and map information. In some examples, the first wireless device 805 may perform the beam scanning procedure based on a subset of multiple lanes corresponding to a first vehicle associated with the first wireless device and the subset of multiple lanes corresponding to a first subset of beams. In some examples, the beam scanning procedure is performed based on current beam parameters. In some examples,

[0189] One or more beams in the first subset of the beams are determined based on corresponding identifiers among a plurality of identifiers. In some examples, the second frequency band is a millimeter-wave frequency band.

[0190] At 840, the first wireless device 805 may use one or more beams from the first subset of the beams in the second frequency band to communicate one or more messages with the second wireless device 810.

[0191] Figure 9 A block diagram 900 of a device 905 supporting assisted beam management according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0192] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to auxiliary beam management). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0193] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to auxiliary beam management). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0194] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of auxiliary beam management as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

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

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

[0198] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. The communication manager 920 may be capable of, configured to, or operable to support components for obtaining map information corresponding to a geographic area associated with the location information. The communication manager 920 may be capable of, configured to, or operable to support components for performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the location information and map information. The communication manager 920 may be capable of, configured to, or operable to support components for conveying one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0199] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving a first traffic safety message on a first frequency band, including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. The communication manager 920 may be capable of, configured to, or operable to support components for performing a beam scanning process with a second wireless device on a second frequency band different from the first frequency band, using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the intersection information. The communication manager 920 may be capable of, configured to, or operable to support components for communicating one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0200] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920, or a combination thereof or at least one processor coupled thereto) can support techniques for reducing processing, lowering power consumption, more efficient use of communication resources, or any combination thereof.

[0201] Figure 10 A block diagram 1000 of a device 1005 supporting assisted beam management according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or UE 115 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0202] Receiver 1010 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to auxiliary beam management). The information may be passed to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

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

[0204] Device 1005 or its various components may be examples of parts used to perform various aspects of auxiliary beam management as described herein. For example, communication manager 1020 may include location information component 1025, map information component 1030, beam scanning process component 1035, communication component 1040, intersection information component 1045, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0205] Communication manager 1020 can support wireless communication according to examples disclosed herein. Location information component 1025 is capable of, configured to, or operable to support components for receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. Map information component 1030 is capable of, configured to, or operable to support components for obtaining map information corresponding to a geographic area associated with the location information. Beam scanning process component 1035 is capable of, configured to, or operable to support components for performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the location information and map information. Communication component 1040 is capable of, configured to, or operable to support components for communicating one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0206] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. The intersection information component 1045 is capable of, configured to, or operable to support components for receiving a first traffic safety message on a first frequency band, including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. The beam scanning process component 1035 is capable of, configured to, or operable to support components for performing a beam scanning process with a second wireless device on a second frequency band different from the first frequency band, using a first subset of beams from a set of multiple available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the intersection information. The communication component 1040 is capable of, configured to, or operable to support components for communicating one or more messages with the second wireless device on the second frequency band using the one or more beams from the first subset of beams.

[0207] Figure 11 A block diagram 1100 of a communication manager 1120 supporting assisted beam management according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of assisted beam management as described herein. For example, the communication manager 1120 may include a location information component 1125, a map information component 1130, a beam scanning process component 1135, a communication component 1140, an intersection information component 1145, a beam information component 1150, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0208] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. The location information component 1125 is capable of, configured to, or operable to support components for receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. The map information component 1130 is capable of, configured to, or operable to support components for obtaining map information corresponding to a geographic area associated with the location information. The beam scanning process component 1135 is capable of, configured to, or operable to support components for performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on the location information and map information. The communication component 1140 is capable of, configured to, or operable to support components for conveying one or more messages with the second wireless device on the second frequency band using the one or more beams from the first subset of beams.

[0209] In some examples, the intersection information component 1145 is capable of, configured to, or operable to support components for receiving, on a first frequency band, a first message from a second wireless device including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. In some examples, the beam scanning process component 1135 is capable of, configured to, or operable to support components for performing a beam scanning process based on the intersection information.

[0210] In some examples, map information component 1130 is capable of, configured to, or operable as a component for receiving map information from a second wireless device.

[0211] In some examples, the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with the roadside unit.

[0212] In some examples, the first wireless device is a first onboard unit (OBU) associated with a first vehicle and the second wireless device is a second OBU associated with a second vehicle.

[0213] In some examples, this first frequency band is the Intelligent Transportation Systems (ITS) band.

[0214] In some examples, this second frequency band is the millimeter-wave band.

[0215] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. The intersection information component 1145 is capable of, configured to, or operable to support components for receiving a first traffic safety message on a first frequency band that includes intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. In some examples, the beam scanning process component 1135 is capable of, configured to, or operable to support components for performing a beam scanning process with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the intersection information. In some examples, the communication component 1140 is capable of, configured to, or operable to support components for communicating one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0216] In some examples, the location information component 1125 is capable of, configured, or operable to support components for receiving a second vehicle safety message indicating the location information of a second wireless device on a first frequency band. In some examples, the map information component 1130 is capable of, configured, or operable to support components for obtaining map information corresponding to a geographic area associated with the location information. In some examples, the beam scanning process component 1135 is capable of, configured, or operable to support components for performing a beam scanning process based on the location information and map information.

[0217] In some examples, the first vehicle safety message is a signal phase and timing message, a map data message, or a road geometry attribute message.

[0218] In some examples, the first vehicle safety message includes a beam number parameter indicating a set of multiple beams, a beam azimuth parameter for each beam in the set of multiple beams, a beam elevation parameter for each beam in the set of multiple beams, a current beam parameter for a subset of the set of multiple lanes, or any combination thereof.

[0219] In some examples, the current beam parameters are associated with lane connection parameters that are associated with a subset of the set of multiple lanes, and the beam scanning process is performed based on the current beam parameters.

[0220] In some examples, beam scanning process component 1135 is capable of, configured to, or operable to support components for performing a beam scanning process based on a subset of a set of multiple lanes corresponding to a first vehicle associated with a first wireless device, wherein the subset of the set of multiple lanes corresponds to a first subset of the beam.

[0221] In some examples, the first vehicle safety message includes a set of multiple identifiers associated with a set of multiple available beams. In some examples, one or more beams in the first subset of beams are determined based on corresponding identifiers in the set of multiple identifiers.

[0222] In some examples, the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with the roadside unit.

[0223] In some examples, the first vehicle safety message indicates the Public Land Mobile Network (PLMN) identifier associated with the second wireless device.

[0224] In some examples, this first frequency band is the Intelligent Transportation Systems (ITS) band.

[0225] In some examples, this second frequency band is the millimeter-wave band.

[0226] Figure 12 A diagram of a system 1200 including a device 1205 supporting auxiliary beam management, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or UE 115 as described herein, or a component including such devices. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may communicate electronically via one or more buses (e.g., bus 1245) or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

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

[0228] In some cases, device 1205 may include a single antenna 1225. However, in other cases, device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired link, or a wireless link as described herein. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

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

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

[0231] Additionally or alternatively, the communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. The communication manager 1220 may be capable of, configured to, or operable to support components for obtaining map information corresponding to a geographic area associated with the location information. The communication manager 1220 may be capable of, configured to, or operable to support components for performing a beam scanning process with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the location information and map information. The communication manager 1220 may be capable of, configured to, or operable to support components for conveying one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0232] Additionally or alternatively, the communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for receiving a first traffic safety message on a first frequency band, including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. The communication manager 1220 may be capable of, configured to, or operable to support components for performing a beam scanning process with a second wireless device on a second frequency band different from the first frequency band, using a first subset of beams from a set of multiple available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device based on the intersection information. The communication manager 1220 may be capable of, configured to, or operable to support components for communicating one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0233] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 may support techniques for improving communication reliability, reducing latency, improving and reducing processing-related user experience, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof.

[0234] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or executed by at least one processor 1240, at least one memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions that can be executed by at least one processor 1240 to cause device 1205 to perform various aspects of auxiliary beam management as described herein, or at least one processor 1240 and at least one memory 1230 may be otherwise configured to perform or support such operations individually or jointly.

[0235] Figure 13 A flowchart illustrating a method 1300 for supporting assisted beam management according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be achieved by, as referenced... Figures 1 to 12 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0236] At 1305, the method may include receiving a first vehicle safety message indicating the location information of a second wireless device on a first frequency band. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be derived from references... Figure 11 The described location information component 1125 is executed.

[0237] At 1310, the method may include obtaining map information corresponding to a geographic area associated with the location information. The operation of box 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 11 The map information component 1130 described herein is used to perform this action.

[0238] At 1315, the method may include performing a beam scanning procedure with a second wireless device on a second frequency band different from a first frequency band using a first subset of beams from a set of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on location information and map information. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 11The described beam scanning process is performed by component 1135.

[0239] At 1320, the method may include using one or more beams from the first subset of the beams to communicate one or more messages with the second wireless device on the second frequency band. Operation of block 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 11 The described communication component 1140 is executed.

[0240] Figure 14 A flowchart illustrating a method 1400 for supporting assisted beam management according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be achieved by, as referenced... Figures 1 to 12 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0241] At 1405, the method may include receiving, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a set of multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the set of multiple lanes. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 11 The intersection information component 1145 described is used to perform this.

[0242] At 1410, the method may include performing a beam scanning procedure with a second wireless device on a second frequency band different from a first frequency band using a first subset of beams from a set of available beams to determine one or more beams from the first subset of beams to be used for communication with the second wireless device based on intersection information. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to [reference needed]. Figure 11 The described beam scanning process is performed by component 1135.

[0243] At 1415, the method may include using one or more beams from the first subset of the beams to communicate one or more messages with the second wireless device on the second frequency band. Operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1415 may be provided by reference to [reference needed]. Figure 11 The described communication component 1140 is executed.

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

[0245] Aspect 1: A method for wireless communication at a first wireless device, the method comprising: receiving a first vehicle safety message indicating location information of a second wireless device on a first frequency band; obtaining map information corresponding to a geographic area associated with the location information; performing a beam scanning procedure with the second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a plurality of available beams to determine one or more beams in the first subset of beams to be used for communication with the second wireless device, at least in part based on the location information and the map information; and conveying one or more messages with the second wireless device on the second frequency band using the one or more beams in the first subset of beams.

[0246] Aspect 2: According to the method of aspect 1, the method further includes: receiving, on the first frequency band, from the second wireless device a first message including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes; wherein the beam scanning process is performed at least in part based on the intersection information.

[0247] Aspect 3: The method according to any one of aspects 1 to 2, the method further includes: receiving the map information from the second wireless device.

[0248] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit.

[0249] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first wireless device is a first onboard unit (OBU) associated with a first vehicle and the second wireless device is a second OBU associated with a second vehicle.

[0250] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first frequency band is an Intelligent Transportation System (ITS) frequency band.

[0251] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the second frequency band is a millimeter-wave frequency band.

[0252] Aspect 8: A method for wireless communication at a first wireless device, the method comprising: receiving, on a first frequency band, a first traffic safety message including intersection information associated with an intersection comprising a plurality of lanes, wherein the intersection information includes beam direction information associated with a subset of the plurality of lanes; performing a beam scanning procedure with a second wireless device on a second frequency band different from the first frequency band using a first subset of beams from a plurality of available beams to determine, at least in part based on the intersection information, one or more beams from the first subset of beams to be used for communication with the second wireless device; and conveying one or more messages with the second wireless device on the second frequency band using the one or more beams from the first subset of beams.

[0253] Aspect 9: According to the method of aspect 8, the method further includes: receiving a second vehicle safety message indicating the location information of the second wireless device on the first frequency band; and obtaining map information corresponding to a geographic area associated with the location information; wherein the beam scanning process is performed at least in part based on the location information and the map information.

[0254] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the first vehicle safety message is a signal phase and timing message, a map data message, or a road geometry attribute message.

[0255] Aspect 11: The method according to any one of Aspects 8 to 10, wherein the first vehicle safety message includes a beam number parameter indicating a plurality of beams, a beam azimuth parameter for each of the plurality of beams, a beam elevation parameter for each of the plurality of beams, a current beam parameter for the subset of the plurality of lanes, or any combination thereof.

[0256] Aspect 12: According to the method of aspect 11, wherein the current beam parameter is associated with lane connection parameters associated with the subset of the plurality of lanes, wherein the beam scanning process is performed at least in part based on the current beam parameter.

[0257] Aspect 13: The method according to any one of Aspects 8 to 12, the method further comprising: performing the beam scanning process at least in part based on the subset of the plurality of lanes corresponding to a first vehicle associated with the first wireless device, wherein the subset of the plurality of lanes corresponds to the first subset of the beam.

[0258] Aspect 14: The method according to any one of Aspects 8 to 13, wherein the first vehicle safety message includes a plurality of identifiers associated with the plurality of available beams; and the one or more beams in the first subset of the beams are determined at least in part based on a corresponding identifier among the plurality of identifiers.

[0259] Aspect 15: The method according to any one of Aspects 8 to 14, wherein the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit.

[0260] Aspect 16: The method according to any one of Aspects 8 to 15, wherein the first vehicle safety message indicates a Public Land Mobile Network (PLMN) identifier associated with the second wireless device.

[0261] Aspect 17: The method according to any one of Aspects 8 to 16, wherein the first frequency band is an Intelligent Transportation System (ITS) frequency band.

[0262] Aspect 18: The method according to any one of Aspects 8 to 17, wherein the second frequency band is a millimeter wave frequency band.

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

[0264] Aspect 20: A first wireless device for wireless communication, the first wireless device comprising at least one component for performing the method according to any one of aspects 1 to 7.

[0265] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 7.

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

[0267] Aspect 23: A first wireless device for wireless communication, the first wireless device comprising at least one component for performing the method according to any one of aspects 8 to 18.

[0268] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 8 to 18.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A first wireless device, the first wireless device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the first wireless device: Receive a first vehicle safety message indicating the location information of a second wireless device on a first frequency band; Obtain map information corresponding to the geographical region associated with the location information; A beam scanning process is performed with the second wireless device using a first subset of beams from a plurality of available beams on a second frequency band different from the first frequency band to determine, at least in part, one or more beams from the first subset of beams to be used for communication with the second wireless device, based on the location information and the map information. as well as One or more beams from the first subset of beams are used to communicate one or more messages with the second wireless device on the second frequency band.

2. The first wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first wireless device to: Receive a first message from the second wireless device on the first frequency band, including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes; The beam scanning process is performed based at least in part on the intersection information.

3. The first wireless device of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first wireless device to: Receive the map information from the second wireless device.

4. The first wireless device according to claim 1, wherein the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit.

5. The first wireless device of claim 1, wherein the first wireless device is a first onboard unit (OBU) associated with a first vehicle and the second wireless device is a second OBU associated with a second vehicle.

6. The first wireless device according to claim 1, wherein the first frequency band is an Intelligent Transportation System (ITS) frequency band.

7. The first wireless device according to claim 1, wherein the second frequency band is a millimeter-wave frequency band.

8. A first wireless device, the first wireless device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the first wireless device: A first vehicle safety message is received on a first frequency band, including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes; A beam scanning process is performed with a second wireless device using a first subset of beams from a plurality of available beams on a second frequency band different from the first frequency band to determine, at least in part, one or more beams from the first subset of beams to be used for communication with the second wireless device, based on the intersection information. as well as One or more beams from the first subset of beams are used to communicate one or more messages with the second wireless device on the second frequency band.

9. The first wireless device of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first wireless device to: Receive a second vehicle safety message indicating the location information of the second wireless device on the first frequency band; as well as Obtain map information corresponding to the geographical region associated with the location information; The beam scanning process is performed based, at least in part, on the location information and the map information.

10. The first wireless device according to claim 8, wherein the first vehicle safety message is a signal phase and time message, a map data message, or a road geometry attribute message.

11. The first wireless device of claim 8, wherein the first vehicle safety message includes a beam number parameter indicating a plurality of beams, a beam azimuth parameter for each of the plurality of beams, a beam elevation parameter for each of the plurality of beams, a current beam parameter for the subset of the plurality of lanes, or any combination thereof.

12. The first wireless device of claim 11, wherein the current beam parameters are associated with lane connection parameters associated with the subset of the plurality of lanes, and wherein the beam scanning process is performed at least in part based on the current beam parameters.

13. The first wireless device of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first wireless device to: The beam scanning process is performed at least in part based on the subset of the plurality of lanes corresponding to a first vehicle associated with the first wireless device, wherein the subset of the plurality of lanes corresponds to the first subset of the beam.

14. The first wireless device according to claim 8, wherein: The first vehicle safety message includes multiple identifiers associated with the plurality of available beams; and The one or more beams in the first subset of the beams are determined at least in part based on the corresponding identifiers among the plurality of identifiers.

15. The first wireless device of claim 8, wherein the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit.

16. The first wireless device of claim 8, wherein the first vehicle safety message indicates a Public Land Mobile Network (PLMN) identifier associated with the second wireless device.

17. The first wireless device according to claim 8, wherein the first frequency band is an Intelligent Transportation System (ITS) frequency band.

18. The first wireless device according to claim 8, wherein the second frequency band is a millimeter-wave frequency band.

19. A method for performing wireless communication at a first wireless device, the method comprising: Receive a first vehicle safety message indicating the location information of a second wireless device on a first frequency band; Obtain map information corresponding to the geographical region associated with the location information; A beam scanning process is performed with the second wireless device using a first subset of beams from a plurality of available beams on a second frequency band different from the first frequency band to determine, at least in part, one or more beams from the first subset of beams to be used for communication with the second wireless device, based on the location information and the map information. as well as One or more beams from the first subset of beams are used to communicate one or more messages with the second wireless device on the second frequency band.

20. The method of claim 19, further comprising: Receive a first message from the second wireless device on the first frequency band, including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes; The beam scanning process is performed based at least in part on the intersection information.

21. The method of claim 19, wherein the first wireless device is an onboard unit (OBU) and the second wireless device is a network entity co-located with a roadside unit.

22. The method of claim 19, wherein the first wireless device is a first onboard unit (OBU) associated with a first vehicle and the second wireless device is a second OBU associated with a second vehicle.

23. A method for performing wireless communication at a first wireless device, the method comprising: A first vehicle safety message is received on a first frequency band, including intersection information associated with an intersection comprising multiple lanes, wherein the intersection information includes beam direction information associated with a subset of the multiple lanes; A beam scanning process is performed with a second wireless device using a first subset of beams from a plurality of available beams on a second frequency band different from the first frequency band to determine, at least in part, one or more beams from the first subset of beams to be used for communication with the second wireless device, based on the intersection information. as well as One or more beams from the first subset of beams are used to communicate one or more messages with the second wireless device on the second frequency band.

24. The method according to claim 23, further comprising: Receive a second vehicle safety message indicating the location information of the second wireless device on the first frequency band; as well as Obtain map information corresponding to the geographical region associated with the location information; The beam scanning process is performed based, at least in part, on the location information and the map information.

25. The method of claim 23, wherein the first vehicle safety message is a signal phase and time message, a map data message, or a road geometry attribute message.

26. The method of claim 23, wherein the first vehicle safety message includes a beam number parameter indicating a plurality of beams, a beam azimuth parameter for each of the plurality of beams, a beam elevation parameter for each of the plurality of beams, a current beam parameter for the subset of the plurality of lanes, or any combination thereof.

27. The method of claim 26, wherein the current beam parameter is associated with lane connection parameters associated with the subset of the plurality of lanes, and wherein the beam scanning process is performed at least in part based on the current beam parameter.

28. The method according to claim 23, further comprising: The beam scanning process is performed at least in part based on the subset of the plurality of lanes corresponding to a first vehicle associated with the first wireless device, wherein the subset of the plurality of lanes corresponds to the first subset of the beam.

29. The method according to claim 23, wherein: The first vehicle safety message includes multiple identifiers associated with the plurality of available beams; and The one or more beams in the first subset of the beams are determined at least in part based on the corresponding identifiers among the plurality of identifiers.

30. The method of claim 23, wherein the first vehicle safety message indicates a Public Land Mobile Network (PLMN) identifier associated with the second wireless device.

Images