Techniques for autonomous driving vehicle traffic management

Abstract

Methods, systems, and devices for wireless communication are described. The first network entity communicates a first message indicating an autonomous vehicle traffic management configuration. The first message may be communicated based on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold. Further, the autonomous vehicle traffic management configuration may indicate one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more autonomous vehicle user equipments (UEs). Thus, the first network entity may communicate one or additional messages with the set of one or more autonomous vehicle UEs according to the parameters of the autonomous vehicle traffic management configuration.

Description

TECHNICAL FIELD

[0001] The following relates to wireless communications, including techniques for automated vehicle traffic management. BACKGROUND

[0002] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems can be capable of supporting communication with multiple users by sharing the 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-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which can be referred to as New Radio (NR) systems. These systems can 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 spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system can include one or more base stations, each simultaneously supporting communication with multiple communication devices, which can be otherwise known as user equipment (UE).

[0003] Some wireless communications systems can include vehicle-to-everything (V2X) communications systems that include one or more automated vehicle UEs. An automated vehicle UE can be an example of a vehicle that can involve minimal user interaction for operation. In some examples, one or more automated vehicle UEs can be located within a cell supported by a network entity. Accordingly, the network entity can communicate with and facilitate management of the one or more automated vehicle UEs within the cell. SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for automated vehicle traffic management. For example, the described techniques enable a first network entity to communicate a first message that indicates an automated vehicle traffic management configuration. The first message can be communicated based on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold. Further, the automated vehicle traffic management configuration can indicate one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more automated vehicle user equipment (UEs). Accordingly, the first network entity can communicate one or more additional messages with the set of one or more automated vehicle UEs in accordance with the parameters of the automated vehicle traffic management configuration.

[0005] A method for wireless communication by a first network entity is described. The method can include communicating, based at least on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, a first message indicating an autonomous vehicle traffic management configuration that indicates one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more autonomous vehicle UEs; and communicating one or more additional messages with the set of one or more autonomous vehicle UEs in accordance with the one or more parameters of the autonomous vehicle traffic management configuration.

[0006] A first network entity for wireless communication is described. The first network entity can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories. The one or more processors can be individually or collectively configured to execute the code to cause the first network entity to communicate, based at least on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, a first message indicating an autonomous vehicle traffic management configuration that indicates one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more autonomous vehicle UEs; and communicate one or more additional messages with the set of one or more autonomous vehicle UEs in accordance with the one or more parameters of the autonomous vehicle traffic management configuration.

[0007] Another first network entity for wireless communication is described. The first network entity can include means for communicating, based at least on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, a first message indicating an autonomous vehicle traffic management configuration that indicates one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more autonomous vehicle UEs; and means for communicating one or more additional messages with the set of one or more autonomous vehicle UEs in accordance with the one or more parameters of the autonomous vehicle traffic management configuration.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by one or more processors to: communicate, based at least on a vehicle traffic throughput level of the first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, a first message indicating an autonomous vehicle traffic management configuration that indicates one or more parameters for coordinating wireless communications by the first network entity and the second network entity with a set of one or more autonomous vehicle UEs; and communicate one or more additional messages with the set of one or more autonomous vehicle UEs in accordance with the one or more parameters of the autonomous vehicle traffic management configuration.

[0009] In some examples of the method, the first network entity, and the non-transitory computer-readable medium described herein, the vehicle traffic throughput level of the first network entity and the method, apparatus, and non-transitory computer-readable medium can include further operations, features, means, or instructions for communicating the first message indicating the autonomous vehicle traffic management configuration based on the communication resource congestion level of the first network entity, the second network entity, or both satisfying a communication resource congestion level threshold.

[0010] In some examples of the method, the first network entity, and the non-transitory computer-readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration include an indication to delay a handover or perform an early handover of an autonomous vehicle UE in the set of one or more autonomous vehicle UEs between the first network entity and the second network entity based on the vehicle traffic throughput level of the first network entity, the second network entity, or both satisfying the vehicle traffic congestion level threshold.

[0011] In some examples of the method, the first network entity, and the non-transitory computer-readable medium described herein, the indication to delay the handover or perform the early handover further indicates a time period associated with the delay handover or the early handover and a location associated with the delay handover or the early handover.

[0012] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for receiving, from the autonomous vehicle UE in the set of one or more autonomous vehicle UEs, an indication that the autonomous vehicle UE will delay the handover between the first network entity and the second network entity or perform the early handover between the first network entity and the second network entity, where the autonomous vehicle traffic management configuration can be based on the indication from the autonomous vehicle UE.

[0013] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, communicating the signal indicating that at least one autonomous vehicle UE in the set of one or more autonomous vehicle UEs will handover between the first network entity and the second network entity, where the first message can be communicated based on the signal.

[0014] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration indicate a first bandwidth allocation for the first network entity to use for the wireless communication with the set of one or more autonomous vehicle UEs and indicate a second bandwidth allocation for the second network entity to use for the wireless communication with the set of one or more autonomous vehicle UEs, or both, and the second bandwidth allocation can be different than the first bandwidth allocation.

[0015] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for receiving, from a traffic management server, a second message indicating the autonomous vehicle traffic management configuration based on the vehicle traffic throughput level of the first network entity, the second network entity, or both.

[0016] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting control signaling indicating that the second network entity is to use the second bandwidth allocation based on a bandwidth allocation calculation.

[0017] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting second control signaling indicating that the second network entity is to use the second bandwidth allocation based on an interference level associated with the first bandwidth allocation.

[0018] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration indicate a first transmit power level for the first network entity to use for wireless communications with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to use for wireless communications with the set of one or more autonomous vehicle UEs, or both, and the second transmit power level can be different than the first transmit power level.

[0019] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, based on the vehicle traffic throughput level of the first network entity satisfying the vehicle traffic congestion level threshold, the first transmit power level of the first network entity can be greater than the second transmit power level of the second network entity or less than the second transmit power level of the second network entity.

[0020] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration indicate a multiple-input multiple-output (MIMO) beamforming space of the set of one or more sets of autonomous vehicle UEs that can connect to the first network entity, the second network entity, or both, the MIMO beamforming space indicating wireless channels or beamforming directions for communications with autonomous vehicle UEs that the first network entity, the second network entity, or both are to avoid.

[0021] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for receiving, from a server, a second message indicating the autonomous vehicle traffic management configuration based on the vehicle traffic throughput level of both the first network entity and the second network entity satisfying the vehicle traffic congestion level threshold.

[0022] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, to a server, an additional message indicating a bandwidth allocation, a transmit power level, a beamforming configuration, or any combination thereof based on the vehicle traffic throughput level of the first network entity satisfying the vehicle traffic congestion level threshold.

[0023] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration further indicate a number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both, an indication of resource blocks in a set of bandwidth or resource blocks used by the first network entity, the second network entity, or both, an indication of available bandwidth or available resource blocks, a zone identifier for a subset of the set of one or more autonomous vehicle UEs served by the first network entity, the second network entity, or both, an indication of a channel busy ratio, or any combination thereof.

[0024] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration indicate the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both, and the indication of the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both can be a current indication or can be for a certain time period.

[0025] In some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein, the one or more parameters of the autonomous vehicle traffic management configuration include the indication of resource blocks in the set of bandwidth or resource blocks used by the first network entity, the second network entity, or both, and the indication of available bandwidth or available resource blocks, and both the indication of resource blocks in the set of bandwidth or resource blocks used by the first network entity, the second network entity, or both and the indication of the available bandwidth or available resource blocks can be a current indication or can be an average over a certain time period.

[0026] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for communicating the first message indicating the autonomous vehicle traffic management configuration includes transmitting or receiving the first message.

[0027] Some examples of the method, the first network entity, and the non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for communicating the one or more additional messages with the set of one or more autonomous vehicle UEs includes transmitting or receiving the one or more additional messages with the set of one or more autonomous vehicle UEs. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figures 1 to 4Examples of a wireless communications system that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure are shown.

[0029] Figure 5 Examples of process flows that support techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure are shown.

[0030] Figure 6 And Figure 7 A block diagram of a device that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure is shown.

[0031] Figure 8 A block diagram of a communications manager that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure is shown.

[0032] Figure 9 A diagram of a system including a device that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure is shown.

[0033] Figures 10 to 12 A flow diagram illustrating a method that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0034] In some wireless communications systems, a network entity can be located within and support a cell that serves one or more autonomous vehicles (e.g., autonomous vehicle user equipment (UE)). Generally, autonomous vehicle UEs can involve a certain level of wireless link reliability. Further, the network entity can serve a certain number of autonomous vehicles within the cell, and as the physical vehicle traffic of autonomous vehicle UEs within the cell increases, the network entity can become congested. That is, the network entity supporting the cell can become congested due to the vehicle traffic and due to an increase in communications between the autonomous vehicle UEs within the cell and the network entity. Further, as the network entity can become congested, available communication resources at the network entity for additional autonomous vehicles can decrease and the wireless link reliability of the autonomous vehicle UEs can decrease. To ensure that the network entity can be able to provide reliable wireless links, some autonomous vehicle UEs can be forced to wait outside of a coverage area of the cell until the network entity supporting the cell can be able to provide reliable wireless links to the autonomous vehicle UEs within the coverage area. However, as more autonomous vehicle UEs can be forced to wait outside of the desired cell, the cell in which the autonomous vehicle UEs can be waiting can experience an increase in physical vehicle traffic. Thus, the network entity supporting the cell in which the autonomous vehicle UEs are forced to wait can also become congested, resulting in a decrease in vehicle throughput, which can result in a decrease in reliability and effectiveness of the wireless communications system reliability.

[0035] To improve the reliability and effectiveness of a wireless communications system, aspects of the present disclosure can provide techniques that enable coordination between network entities to increase vehicle traffic flow of autonomous vehicle UEs served by the wireless network. For example, a congested network entity can signal an autonomous vehicle traffic management configuration to a neighboring network entity to assist in managing physical vehicle traffic of the wireless communications system. In some cases, the congested network entity can transmit the autonomous vehicle traffic management configuration based on the network entity experiencing an increase in physical vehicle traffic or a decrease in communication resources. Further, the network entity can be considered a congested network entity based on a vehicle traffic throughput level of the network entity satisfying a vehicle traffic throughput level threshold or satisfying a vehicle traffic congestion level threshold. Thus, a first network entity can communicate the autonomous vehicle traffic management configuration based on the first network entity, a second network entity, or both satisfying the vehicle traffic throughput level threshold, the vehicle traffic congestion level threshold, or both. Further, the autonomous vehicle traffic management configuration can indicate one or more parameters for coordinating wireless communications between the first network entity, the second network entity, or both and autonomous vehicle UEs. Accordingly, the first network entity can communicate one or more additional messages with a set of one or more autonomous vehicle UEs in accordance with the one or more parameters of the autonomous vehicle traffic management configuration.

[0036] In a first example, one or more parameters of the autonomous vehicle traffic management configuration can indicate to delay a handover of an autonomous vehicle between a congested network entity and an adjacent network entity or to perform an early handover of the autonomous vehicle between the congested network entity and the adjacent network entity. By delaying the handover or performing the handover early, the efficiency of the wireless communication system can be improved by allowing the network entities to efficiently allocate resources for communication. In another example, the adjacent network entities can communicate with each other regarding bandwidth allocations used by the adjacent network entities, such that the adjacent network entities can use different bandwidths than the bandwidth being used by the congested network entity. Thus, by using different bandwidth allocations, the network entities can be able to communicate more reliably and more efficiently.

[0037] In some examples, the network entities can also use the autonomous vehicle traffic management configuration to dynamically adjust transmit power levels based on vehicle traffic congestion levels to allow the congested network entity to use higher transmit power to efficiently serve additional autonomous vehicle UEs. Additionally or alternatively, the autonomous vehicle traffic management configuration can indicate that the network entities should form a multiple-input multiple-output (MIMO) beamforming space (e.g., a zero beamforming space) within the beamforming vectors of a set of one or more autonomous vehicle UEs connected to the first network entity, the second network entity, or both. The MIMO beamforming space can indicate wireless channels or beamforming directions that the adjacent network entities should avoid to reduce interference that can potentially be caused to the congested network entity while serving its autonomous vehicle UEs. Thus, by using the techniques of the present disclosure, movement of autonomous vehicles between and within network entities can be enhanced, which can result in a reduction of physical traffic congestion by preventing autonomous vehicle UEs from being forced to wait before entering a cell. Moreover, the techniques described herein can also result in an improvement in the efficiency and reliability of the wireless communication system.

[0038] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described herein with reference to a wireless communication system and process flows. Aspects of the disclosure are further illustrated by and described in terms of apparatus diagrams, system diagrams, and flowcharts that relate to techniques for autonomous vehicle traffic management, and with reference to these diagrams the aspects of the disclosure are described.

[0039] Figure 1An example of a wireless communications system 100 that supports techniques for automated driving vehicle traffic management in accordance with one or more aspects of the present disclosure is shown. The wireless communications system 100 can include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 can be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to some other wireless standard, including future iterations of the wireless standards explicitly mentioned herein and wireless standards not explicitly mentioned herein.

[0040] The network entities 105 can be dispersed throughout the geographic region of the wireless communications system 100, and can each include devices of different form factors or having different capabilities. In various examples, the network entities 105 can be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other examples. In some examples, the network entities 105 and the UEs 115 can wirelessly communicate using one or more communication links 125 (e.g., radio frequency (RF) access links). For example, a network entity 105 can support a coverage area 110 (e.g., a geographic coverage area) within which the network entity 105 and the UEs 115 can establish one or more communication links 125. The coverage area 110 can be an example of a geographic area over which a network entity 105 and a UE 115 can support communication in accordance with one or more radio access technologies (RATs).

[0041] The UEs 115 can be dispersed throughout the coverage areas 110 of the wireless communications system 100, and each UE 115 can be stationary or mobile, or both at different times. The UEs 115 can be devices in different forms or having different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115, or a network entity 105, as shown in FIG. 1. Figure 1 The UEs 115 described herein can be able to communicate as relay devices facilitating communication for other UEs 115.

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

[0043] In some examples, the network entities 105 can communicate with the core network 130, or with each other, or both. For example, the network entities 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an SI, N2, N3, or other interface protocol). In some examples, the network entities 105 can communicate with each other via the backhaul communication links 120 (e.g., directly between the network entities 105, or indirectly via the core network 130, or both). In some examples, the network entities 105 can communicate with each other via the midhaul communication links 162 (e.g., according to a midhaul interface protocol) or the front-haul communication links 168 (e.g., according to a front-haul interface protocol), or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the front-haul communication links 168 can be or include one or more wired links (e.g., electrical, fiber optic), one or more wireless links (e.g., radio, wireless optical), etc., or various combinations thereof. The UEs 115 can communicate with the core network 130 via communication links 155.

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

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

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

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

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

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

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

[0051] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support techniques for autonomous vehicle service 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).

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

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

[0054] 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 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize 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, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

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

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

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

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

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

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

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

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

[0063] 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 common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0064] 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 to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of 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 extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0065] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells 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.

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

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

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

[0069] Some UE 115s (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 115s 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 charging.

[0070] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. 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.

[0071] 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 functionality may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0072] 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 UEs 115s performing D2D communication in a group may be located 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 UEs 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UEs 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UEs 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.

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

[0074] 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 delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0075] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region 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 frequencies (HF) or very high frequencies (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).

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

[0077] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency 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 frequency bands may be combined with component carriers operating with licensed frequency 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.

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

[0079] 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), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

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

[0081] 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 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

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

[0083] 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 set of beams configured across the system bandwidth or one or more sub-bands. 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 for 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).

[0084] 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 (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; 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).

[0085] 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 processing 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 can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

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

[0087] In some examples of the wireless communication system 100, network entity 105 may be located within and support a cell serving one or more autonomous vehicles (e.g., autonomous vehicle UE 115). Typically, the autonomous vehicle UE 115 may require a certain level of wireless link reliability. For example, there may be standards (e.g., International Organization for Standardization (ISO) 26262) that can be applied to safety-related systems in passenger vehicles by ensuring intended functional safety (SOTIF). Therefore, ISOSOTIF can also be extended from general passenger vehicles to autonomous vehicle UE 115. Additionally or alternatively, the standard may define a Vehicle Safety Integrity Level (ASIL), which provides some associated reliability values ​​that the wireless communication system 100 can be expected to meet to achieve a specific ASIL. In some cases, there may be different levels of ASIL (e.g., ASIL A, ASIL B, ASIL C, and ASIL D) that the wireless communication system 100 can be able to meet, where ASIL A is the lowest level and ASIL D is the highest level. Furthermore, V2X systems that meet ASIL requirements are expected to function in vehicle applications (e.g., autonomous driving and remote driving). Additionally or alternatively, such applications can be expected to utilize the functionality of RSUs, MECs, road cameras, and other facilities along the road for vehicle V2X communication.

[0088] Furthermore, network entity 105 can serve a certain number of autonomous vehicle UEs 115 within the cell, and as the physical vehicle traffic of autonomous vehicle UEs 115 within the cell increases, network entity 105 may become congested. That is, due to increased vehicle traffic and increased communication between autonomous vehicle UEs and network entities within the cell, the network entity supporting the cell may become congested. Moreover, as the network entity may become congested, the available communication resources for additional autonomous vehicle UEs 115 at network entity 105 may decrease, and the reliability of the radio links for autonomous vehicle UEs 115 may deteriorate. To ensure that network entity 105 can provide a reliable radio link (e.g., communication link 125), some autonomous vehicle UEs 115 may be forced to wait outside the cell's coverage area until network entity 105 can provide a reliable radio link to the autonomous vehicle UEs 115 within the coverage area. However, since more autonomous vehicle UEs 115 may be forced to wait outside the desired cell, the cell where the autonomous vehicle UEs 115 may be waiting may experience increased physical vehicle traffic. Therefore, the network entities of the cells in which the UEs supporting autonomous vehicles are forced to wait may also become congested, leading to a decrease in vehicle throughput, which in turn reduces the reliability and effectiveness of the wireless communication system 100.

[0089] To improve the reliability and effectiveness of the wireless communication system 100, various aspects of this disclosure provide techniques for coordinating among network entities 105 to increase vehicle service flows for the autonomous vehicle UE 115 served by the wireless network. For example, a congested network entity 105 may send an autonomous vehicle service management configuration to a neighboring network entity 105 to assist in managing the physical vehicle services of the wireless communication system 100. In some cases, a congested network entity may send the autonomous vehicle service management configuration based on an increase in physical vehicle service congestion experienced by network entity 105 or a decrease in available communication resources for managing the services of the autonomous vehicle UE 115. Furthermore, a network entity 105 may be considered a congested network entity 105 based on its vehicle service throughput level meeting a vehicle service throughput level threshold or a vehicle service congestion level threshold. Therefore, a first network entity 105 may communicate the autonomous vehicle service management configuration based on the first network entity 105, a second network entity 105, or both meeting a vehicle service throughput level threshold, a vehicle service congestion level threshold, or both. Furthermore, the autonomous vehicle service management configuration may indicate one or more parameters for coordinating wireless communication between the first network entity 105, the second network entity 105, or both, and the autonomous vehicle UE 115. Therefore, the first network entity 105 may communicate one or more additional messages to a set of one or more autonomous vehicle UEs 115 based on one or more parameters of the autonomous vehicle service management configuration.

[0090] In the first example, one or more parameters of the autonomous driving service management configuration can instruct the autonomous vehicle UE 115 to delay handover between the congested network entity 105 and a neighboring network entity 105, or to perform an early handover between the autonomous vehicle UE 115 and the neighboring network entity. By delaying or early handover, the efficiency of the wireless communication system 100 can be improved by allowing network entity 105 to efficiently allocate resources for communication. In another example, neighboring network entities 105 can communicate with each other regarding the bandwidth allocation used by neighboring network entities 105, such that neighboring network entities 105 can use bandwidth different from that used by the congested network entity 105. Therefore, by using different bandwidth allocations, network entities 105 can be able to conduct more reliable and efficient communication.

[0091] In some examples, network entity 105 may also use an autonomous driving service management configuration to dynamically adjust the transmit power level based on the vehicle traffic congestion level, allowing congested network entity 105 to use higher transmit power to effectively serve the attached autonomous vehicle UE 115. Additionally or alternatively, the autonomous vehicle traffic management configuration may instruct network entity 105 to form a MIMO beamforming space within the beamforming vector of a set of one or more autonomous vehicle UEs connected to a first network entity, a second network entity, or both. The MIMO beamforming space may indicate the radio channels or beamforming directions that adjacent network entities 105 should avoid, allowing congested network entities 105 to serve the attached autonomous vehicle UE 115. Therefore, by using the techniques of this disclosure, the movement of autonomous vehicle UE 115 between or within cells supported by network entity 105 can be enhanced, which can reduce physical traffic congestion by preventing autonomous vehicle UEs from being forced to wait before entering a cell. Furthermore, the techniques described herein can also improve the effectiveness and reliability of the wireless communication system 100.

[0092] Figure 2 Examples of a wireless communication system 200 supporting technologies for operational management of autonomous vehicles according to one or more aspects of this disclosure are shown. In some examples, the wireless communication system 200 may implement or be implemented by the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a, network entity 105-b, autonomous vehicle UE 115-a, and server 205, which may represent references herein. Figure 1 Examples of the corresponding devices described herein. Network entity 105-a can communicate with the autonomous vehicle UE 115-a via communication link 210 and with the server 205 via communication link 215, and network entity 105-b can communicate with the autonomous vehicle UE 115-a via communication link 220 and with the server 205 via communication link 225. Communication links 210, 215, 220, and 225 may be referenced herein. Figure 1 Examples of Uu links, side links, backhaul links, D2D links, or some other type of communication link 125 as described.

[0093] In some examples, the wireless communication system 200 may be an example of a V2X system that includes communication with the autonomous vehicle UE 115-a. In some cases, the autonomous vehicle UE 115-a may be referred to herein as a remotely driven vehicle UE 115 or an autonomous vehicle UE 115. In some examples, the autonomous vehicle UE 115 may be able to perform the functions of a motor vehicle with a limited amount of user input or without any user input. Figure 2 In the illustrated example, network entity 105-a may support a first cell, and network entity 105-b may support a second cell adjacent to the first cell. Furthermore, the autonomous vehicle UE 115-a may be located within the first cell and served by network entity 105-a. Therefore, when the autonomous vehicle UE 115-a communicates with network entity 105-a within the wireless communication system 200, the autonomous vehicle UE 115-a can be expected to maintain a certain ASIL performance rating. However, maintaining an ASIL performance level may increase resource consumption within the wireless communication system 200.

[0094] For example, uplink ASIL D video streaming and sharing may involve a number of retransmissions of 13 (e.g., a maximum), and a single network entity 105 (e.g., network entity 105-a or network entity 105-b) may only be able to serve a limited number of autonomous vehicle UEs 115. Furthermore, due to the resource consumption of V2X communication, network entity 105 may only be able to serve a limited number of autonomous vehicle UEs 115. Therefore, to support efficient resource allocation across network entities 105, wireless communication system 200 may request some form of cooperation or communication between network entities 105-a and 105-b. In some cases, resource allocation may not be an issue in wireless communication system 100 when there may be a relatively small number of autonomous vehicle UEs 115 within the cell. However, when there is a relatively large number of autonomous vehicle UEs 115 within the cell, resource allocation may become an issue and affect the reliability and efficiency of wireless communication system 200.

[0095] For example, since the autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-a) may expect a certain level of radio link reliability, and network entity 105-a may not be able to provide the radio link reliability expected by the autonomous vehicle UE 115-a. For example, network entity 105-a may experience channel fading, and network entity 105-a, network entity 105-b, or both may have a limited number of communication resources to support the autonomous vehicle UE 115-a. Therefore, the wireless communication system 200 may improve coordination between network entity 105-a and network entity 105-b to increase the traffic flow of the autonomous vehicle UE 115 that can be served by the wireless communication system 200.

[0096] In some examples, from a transportation engineering perspective, an increase in road network throughput of the wireless communication system 200 may be desired. For example, improving the overall spectral efficiency of the wireless communication system compared to a conventional wireless communication system may not be sufficient to support the autonomous vehicle UE. Furthermore, dynamically allocating communication resources to cells along the road that may be experiencing some kind of communication bottleneck (e.g., communication latency due to increased physical vehicle traffic) can also improve the traffic flow of the autonomous vehicle UE 115. Additionally or alternatively, various techniques may exist to achieve such improvements in the traffic flow of the autonomous vehicle UE 115. Some examples may include improved handover strategies, dynamic bandwidth allocation, dynamic power allocation, improved beamforming configurations, or any combination thereof. Furthermore, to support such techniques, the wireless communication system 200 may support the exchange of cooperative messages (e.g., X-3 messages) between network entity 105-a and network entity 105-b. In some cases, messages can be exchanged directly between network entity 105-a and network entity 105-b, or via server 205, which may be an example of a service management server 205, which can be a local server 205 or a cloud-based server 205. Such techniques for enhancing the service flow of the wireless communication system 200 through cooperation between network entity 105-a and network entity 105-b can be found elsewhere herein (including references). Figures 3 to 5 (This is a description of the process.)

[0097] Figure 3 Examples of a wireless communication system 300 supporting technologies for autonomous vehicle service management according to one or more aspects of this disclosure are shown. In some examples, the wireless communication system 300 may implement or be implemented by wireless communication system 100 and / or wireless communication system 200. For example, the wireless communication system 300 may include network entity 105-c supporting cell 305-a, network entity 105-d supporting cell 305-b, and autonomous vehicle UE 115, which may represent references herein. Figure 1Examples of the corresponding devices described.

[0098] exist Figure 3 In the illustration, multiple autonomous vehicle UEs 115 may exist within the coverage areas of cells 305-a and 305-b. In this illustration, arrows may indicate that the corresponding autonomous vehicle UE 115 can actively move in the direction of the arrow. In some examples, the autonomous vehicle UE 115 may move at a relatively high speed (e.g., approximately 65 miles per hour (mph) or 105 kilometers per hour (km / h)) on roads within the wireless communication system 300. Based on the capabilities of network entities 105-c and 105-d, network entities 105-c and 105-d may be able to support a certain number of autonomous vehicle UEs 115. For example, based on throughput levels or the amount of communication resources, network entities 105-c and 105-d may be able to support up to seven autonomous vehicle UEs 115. However, as illustrated in cell 305-b, network entity 105-d may not be able to support additional autonomous vehicle UE 115 (e.g., network entity 105-d may already support the maximum number of autonomous vehicle UE 115 that network entity 105-d can serve).

[0099] Therefore, since network entity 105-d cannot support any additional autonomous vehicle UE 115 and / or a limited number of additional autonomous vehicle UE 115, network entity 105-d can be considered a resource-congested network entity 105. In some examples, network entity 105-d can be considered a resource-congested network entity 105 based on the vehicle throughput level meeting a vehicle throughput level threshold (e.g., below the vehicle throughput level threshold). The vehicle throughput level of network entity 105 can be correlated with the number of autonomous vehicle UE 115 entering and leaving cell 305 supported by network entity 105. For example, a high vehicle throughput level can indicate a relatively large number of autonomous vehicle UE 115 entering and leaving cell 305. Therefore, a low vehicle throughput level can indicate a relatively small number of autonomous vehicle UE 115 entering and leaving cell 305. In such cases, if the number of autonomous vehicle UEs 115 entering and leaving cell 305 is small, cell 305 may have a relatively large number of autonomous vehicle UEs 115 within cell 305, which could lead to a reduction in physical traffic flow in wireless communication system 300. Therefore, the vehicle traffic throughput level threshold can correspond to a low vehicle traffic throughput level. In some other examples, network entity 105-d can be considered a resource-congested network entity 105 based on the fact that network entity 105-d meets a vehicle traffic congestion level threshold (e.g., the number of autonomous vehicle UEs 115 exceeds the threshold level). The vehicle traffic congestion level threshold can correspond to physical traffic congestion within cell 305. For example, as discussed herein, if the vehicle traffic throughput level is low, the number of autonomous vehicle UEs 115 within cell 305 can be relatively high. Therefore, the level of physical traffic flow within cell 305 can also be relatively low. In another example, network entity 105-d can be considered a resource-congested network entity 105 based on the amount of resources available at network entity 105-d to support additional autonomous vehicle UEs 115. For example, if the amount of resources available at network entity 105-d to support additional autonomous vehicle UEs 115 is relatively low or below a resource level threshold (e.g., the threshold number of resources), then network entity 105-d can be considered a resource-congested network entity 105. In some cases, the resource-congested network entity 105 described herein may also be considered and referred to as the radio-congested network entity 105. For example, due to an increase in radio traffic, the frequency on which network entity 105 may be operating may become congested.

[0100] In some examples, handovers between network entities 105 may be common and frequent because the autonomous vehicle UE 115 may move at relatively high speeds. The handover process may include the autonomous vehicle UE 115 connecting to a first network entity 105 (e.g., network entity 105-c) and requesting a connection to a second network entity 105 (e.g., network entity 105-d). Furthermore, as part of the handover process, the autonomous vehicle UE 115 may maintain a connection to the first network entity 105 while simultaneously connecting to the second network entity 105. Therefore, the autonomous vehicle UE 115 may maintain a connection to the first network entity 105 until a successful connection to the second network entity 105 is established to support continuous coverage of the autonomous vehicle UE 115. For example, the autonomous vehicle UE 115, which may be connected to network entity 105-c, may begin to leave the coverage area of ​​cell 305-a, which may be supported by network entity 105-c. Therefore, the autonomous vehicle UE 115 may initiate a handover process to connect to network entity 105-d. Additionally or alternatively, as part of the handover process, the autonomous vehicle UE 115 may perform a measurement of the signal quality of network entity 105-d before connecting to network entity 105-d. Such signal quality measurements (e.g., RSRP measurements) ensure that network entity 105-d can support the level of radio link reliability expected by the autonomous vehicle UE 115.

[0101] In some cases, group 310 of autonomous vehicle UE 115 may move within cell 305-a. As group 310 of autonomous vehicle UE 115 moves toward the boundary of cell 305-a, group 310 of autonomous vehicle UE 115 may initiate a handover process to switch from being served by network entity 105-c to being served by network entity 105-d. However, since network entity 105-d may be a resource-congested network entity 105, it may be unable to support group 310 of autonomous vehicle UE 115. Therefore, group 310 of autonomous vehicle UE 115 may be denied entry into the coverage area of ​​cell 305-b and may be forced to wait within cell 305-a. In some cases, such scenarios may be due to reasons such as network entity 105-d having limited communication resources for additional autonomous vehicle UE 115. That is, network entity 105-d may be unable to support any additional autonomous vehicle UE 115.

[0102] Therefore, in the absence of any kind of cooperation between network entity 105-c and network entity 105-d, the group 310 of autonomous vehicle UEs 115 may be forced to wait within cell 305-a and outside cell 305-b, thereby limiting the physical traffic flow of the wireless communication system 300. In some examples, network entity 105-d may experience resource congestion due to serving a certain number of autonomous vehicle UEs 115, which meets a threshold number of autonomous vehicle UEs 115 that network entity 105-d can serve. In some other examples, there may be problems within cell 305-b supported by network entity 105-d that cause network entity 105-d to experience resource congestion (e.g., vehicle accidents, road construction, severe weather problems, or any combination thereof). In such cases, due to resource congestion of network entity 105-d, the attached autonomous vehicle UE 115 (e.g., group 310 of autonomous vehicle UE 115) may be forced to wait in cell 305-a until network entity 105-d can support the attached autonomous vehicle UE 115.

[0103] However, as the number of autonomous vehicles 115 waiting in cell 305-a increases (e.g., as the number of autonomous vehicle UEs 115 in group 310 of autonomous vehicle UEs 115 increases), network entity 105-c may also become a resource-congested network entity 105. Furthermore, since network entity 105-c may also be a resource-congested network entity 105, autonomous vehicle UEs in cell 305-b or any other adjacent cell 305 may also be restricted from entering cell 305-a. Therefore, due to the low traffic levels of the physical autonomous vehicle UEs 115 in the corresponding cell 305 or due to a lack of communication resources at the corresponding network entity, an increasing number of network entities 105 within the wireless communication system 300 may become resource-congested network entities 105. Consequently, the traffic flow of autonomous vehicle UEs 115 within the wireless communication system 300 may significantly decrease, thereby reducing the effectiveness and reliability of the wireless communication system 300.

[0104] Therefore, the technology described in this disclosure introduces cooperation between network entity 105-c and network entity 105-d to prevent either network entity 105 from becoming so congested that the autonomous vehicle UE 115 is forced to wait outside the cell. For example, elsewhere in this document (including references) Figure 4 and Figure 5 The technology described herein can describe a certain collaboration between network entity 105-c and network entity 105-d to improve the service flow of autonomous vehicle UE 115 within a wireless communication system.

[0105] For example, these techniques may include improved handover procedures (e.g., performing early or delayed handover) to allow a non-resource-congested network entity 105 to support the autonomous vehicle UE 115 for a longer period. In another example, these techniques may describe using dynamic bandwidth allocation between network entity 105-c and network entity 105-d to ensure that network entities 105-c and 105-d avoid communicating on the same bandwidth. Furthermore, these techniques may describe using dynamic transmit power allocation between network entity 105-c and network entity 105-d to allow a resource-congested network entity 105 to use higher transmit power. In some other examples, these techniques may also include enhanced beamforming configurations (e.g., MIMO beamforming configurations) where network entity 105 (e.g., network entity 105-c) avoids using beam 315-a from the set of beams 315 to allow a resource-congested network entity 105 to support the additional autonomous vehicle UE 115. Additionally or alternatively, these technologies may also include techniques for managing complex wireless and road network topologies in which multiple resource-congested network entities 105 may exist within the wireless communication system 300.

[0106] Figure 4 Examples of wireless communication systems 400 supporting technologies for autonomous vehicle business management according to one or more aspects of this disclosure are shown. In some examples, wireless communication system 400 may implement, or be implemented by, wireless communication system 100, wireless communication system 200, and / or wireless communication system 300. For example, wireless communication system 400 may include network entity 105-e supporting cell 405-a, network entity 105-f supporting cell 405-b, autonomous vehicle UE 115-b within cell 405-a, autonomous vehicle UE 115-c within cell 405-b, and server 410, which may represent references herein. Figure 1 Examples of corresponding devices described herein. In some examples, network entity 105-e and network entity 105-f may communicate via communication link 415, network entity 105-e may communicate with server 410 via communication link 420, and network entity 105-f may communicate with server 410 via communication link 425. Communication link 415, communication link 420, and communication link 425 may be referenced herein. Figure 1 Examples of Uu links, side links, backhaul links, D2D links, or some other type of communication link 125 as described.

[0107] As described in this article, refer to Figure 2 and Figure 3 To enhance the wireless communication system 400, network entities 105-e and 105-f can communicate with each other via communication link 415. For example, network entity 105-e can send a first message (e.g., a control message, a return message, etc.) to network entity 105-f or receive from network entity 105-f a first message indicating an autonomous vehicle service management configuration 430 (e.g., autonomous vehicle service management configuration 430-a). Autonomous vehicle service management configuration 430-a can indicate one or more parameters for coordinating wireless communication (e.g., V2X communication) between network entities 105-e and 105-f and a set of one or more autonomous vehicle UEs 115 (e.g., autonomous vehicle UE 115-b and autonomous vehicle UE 115-c). In some examples, network entity 105-e can send or receive the first message based on the vehicle traffic throughput level of network entity 105-e, network entity 105-f, or both meeting a vehicle traffic congestion level threshold.

[0108] Alternatively or additionally, the vehicle service throughput level of network entity 105-e, network entity 105-f, or both may be based on the communication resource congestion level. Furthermore, the communication resource congestion level of the corresponding network entity 105 may be determined based on the communication resource consumption of network entity 105-e or network entity 105-f. For example, the communication resource congestion level may increase based on an increase in communication resource consumption and a corresponding decrease in the throughput of the corresponding cell 305. Therefore, network entity 105-e may communicate the autonomous vehicle service management configuration 430-a based on the communication resource congestion level of network entity 105-e, network entity 105-f, or both meeting a communication resource congestion level threshold.

[0109] Furthermore, network entity 105-e may communicate (e.g., send or receive) one or more additional messages with the autonomous vehicle UE 115 according to the parameters of the autonomous vehicle service management configuration 430. Therefore, the introduction of cooperation between network entity 105-e and network entity 105-f under the autonomous vehicle service management configuration 430 can improve the traffic flow of the wireless communication system 400. For example, network entity 105-f supporting cell 405-b may be a resource-congested network entity 105 (e.g., illustrated by the dashed lines around cell 405-b), and the autonomous vehicle service management configuration 430-a can enable network entity 105-f to obtain additional communication resources. Therefore, network entity 105-f may be able to support additional autonomous vehicle UEs and the increased traffic flow within cell 405-b.

[0110] In some examples, such as reference Figure 3 As described, autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-b and autonomous vehicle UE 115-c) may frequently switch between network entities 105 (e.g., network entities 105-e and network entities 105-f) due to the movement of autonomous vehicle UE 115 (e.g., illustrated by arrows, where the direction of the arrows indicates the direction of movement). Furthermore, in Figure 4In the example, network entity 105-e supporting cell 405-a may be a non-resource-congested network entity 105, while network entity 105-f supporting cell 405-b may be a resource-congested network entity 105. However, it should be understood that in some other examples, network entity 105-e may be a resource-congested network entity 105, and network entity 105-f may be a non-resource-congested network entity 105. Therefore, in some cases, as the autonomous vehicle UE 115-b moves toward cell 405-b, the autonomous vehicle UE 115-b in cell 405-a may switch from network entity 105-e to network entity 105-f. In some other cases, as the autonomous vehicle UE 115-c moves toward cell 405-a, the autonomous vehicle UE 115-c in cell 405-b may switch from network entity 105-f to network entity 105-e. In addition, to improve the effectiveness and reliability of the wireless communication system 400, the parameters of the autonomous vehicle service management configuration 430 can instruct the autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-b or autonomous vehicle UE 115-c) to delay or advance the handover.

[0111] For example, when the autonomous vehicle UE 115-c performs a handover from network entity 105-f to network entity 105-e, parameters of the autonomous vehicle service management configuration 430 may instruct the autonomous vehicle UE 115-c to perform an early handover. This instruction may be based on the premise that network entity 105-f is a resource-congested network entity 105. Therefore, by enabling the autonomous vehicle UE 115-c to perform an early handover, network entity 105-f may be able to make additional resources available to support the autonomous vehicle UE 115 entering cell 405-b. In some other examples, when the autonomous vehicle UE 115-b performs a handover from network entity 105-e to network entity 105-f, parameters of the autonomous vehicle service management configuration 430 may instruct the autonomous vehicle UE 115-b to perform a delayed handover. In some cases, the handover from network entity 105-e to network entity 105-f may be delayed until network entity 105-f can support the autonomous vehicle UE 115-b. Therefore, network entity 105-e can support autonomous vehicle UE 115-b for a short period of time, while autonomous vehicle UE 115-b can be located within cell 405-b to free up time for network entity 105-f to release resources to support autonomous vehicle UE 115-b. In some cases, the parameters of the autonomous vehicle service management configuration can also indicate the time period associated with delayed or early handover. For example, this time period can be equal to the amount of time that the handover should be delayed or advanced. Therefore, by causing autonomous vehicle UE 115 to perform handover earlier or later, autonomous vehicle service management configuration 430 can dynamically control the number of autonomous vehicle UE 115s supported by the corresponding network entities.

[0112] In some cases, the parameters of the autonomous vehicle service management configuration 430 may indicate delayed handover or early handover based on the vehicle throughput levels of network entity 105-e, network entity 105-f, or both meeting a threshold throughput level. In other cases, the parameters of the autonomous vehicle service management configuration 430 may indicate delayed handover or early handover based on the vehicle service throughput levels of network entity 105-e, network entity 105-f, or both meeting a vehicle service congestion level threshold. Furthermore, the parameters of the autonomous vehicle service management configuration 430 may also indicate delayed handover or early handover based on the capabilities of network entity 105-e and network entity 105-f. In some examples, the capabilities of network entity 105-e and network entity 105-f may indicate that network entity 105-e, network entity 105-f, or both can support external autonomous vehicle UE 115 for a period of time after autonomous vehicle UE 115 leaves the corresponding cell 405. Additionally or alternatively, the instructions regarding delayed handover or early handover may also include the time period associated with the delayed handover or early handover and the location associated with the delayed handover or early handover.

[0113] For example, a possible handover range may exist on the road between network entity 105-e and network entity 105-f. That is, when an autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-b or autonomous vehicle UE 115-c) is located within the range between network entity 105-e and network entity 105-f, a handover from network entity 105-e to network entity 105-f may occur. In some cases, the range on the road may be several miles in both the direction towards network entity 105-e and the direction towards network entity 105-f. The distance of this range may be previously agreed upon by network entities 105-e and 105-f and may be based on the capabilities of network entities 105-e and 105-f, based on the characteristics of the roads within cell 405 (e.g., road speed limits, average traffic flow on the roads), or any combination thereof. In some other examples, cell 405-a supported by network entity 105-e and cell 405-b supported by network entity 105-f may at least partially overlap, thereby allowing network entity 105-e or network entity 105-f to support early or delayed handover. Therefore, the extent on the road can be a location associated with delayed or early handover, which can be indicated via one or more parameters of the autonomous vehicle business management configuration 430.

[0114] In some cases, early or delayed handover can be initiated based on a Reference Signal Received Power (RSRP) threshold. For example, the autonomous vehicle UE 115 can send or report signal quality measurements (e.g., RSRP measurements) of network entity 105-e, network entity 105-f, or both to the network entity 105 serving the autonomous vehicle UE 115. Therefore, based on the signal quality measurements reported by the autonomous vehicle UE 115, the autonomous vehicle service management configuration 430 can instruct an early handover to alleviate resource congestion at the resource-congested network entity 105, or a delayed handover to allow time for the resource-congested network entity 105 to reduce its resource congestion level to support the autonomous vehicle UE 115. Furthermore, the signal quality measurements can also indicate when neighboring network entities are available for the handover process. For example, when autonomous vehicle UE 115-b performs a handover between network entity 105-e (e.g., a non-resource-congested network entity 105) and network entity 105-f (e.g., a resource-congested network entity 105), the handover can be delayed until the RSRP measurement of network entity 105-f at least meets or exceeds an RSRP threshold that indicates network entity 105-f can support autonomous vehicle UE 115-b. This delayed handover can additionally prevent further increase in resource congestion of network entity 105-f. Similarly, when autonomous vehicle UE 115-c performs a handover between network entity 105-f and network entity 105-e, the handover can be performed earlier because the RSRP measurement of network entity 105-e meets or exceeds an RSRP threshold that indicates network entity 105-e can support autonomous vehicle UE 115-c at the time of measurement. Therefore, by performing the handover in advance, resource congestion of network entity 105-f can be reduced because resources do not need to be provided to support autonomous vehicle UE 115-c.

[0115] Furthermore, in some examples, the autonomous vehicle UE 115 may initiate a handover procedure. That is, the autonomous vehicle UE 115-b or autonomous vehicle UE 115-c may send a signal to network entity 105-e, network entity 105-f, or both, indicating that the corresponding autonomous vehicle UE 115 may anticipate a handover procedure. In either case, network entity 105-e and network entity 105-f may communicate the autonomous vehicle service management configuration 430-a via communication link 415 based on signals from the autonomous vehicle UE 115-b or autonomous vehicle UE 115-c and when network entity 105-e, network entity 105-f, or both are resource-congested network entities 105.

[0116] In some examples, the parameters of the autonomous vehicle service management configuration 430-a may indicate information for assisting in the management and mitigation of resource congestion by network entity 105. Therefore, the parameters of the autonomous vehicle service management configuration 430-a may indicate the current number of autonomous vehicle UEs 115 being served by the sending network entity 105 (e.g., the network entity 105 sending the autonomous vehicle service management configuration 430-a). In some cases, this parameter may also include the number of autonomous vehicle UEs 115 served within a first time period (e.g., in the past X hours), where the value of X may be pre-configured. In some other examples, the parameters of the autonomous vehicle service management configuration 430-a may indicate the bandwidth or resource blocks currently being used by the sending network entity 105 or the average over a second time period (e.g., in the past Y hours), where the value of Y may be pre-configured. In another example, the parameters of the autonomous vehicle service management configuration 430-a may also indicate the currently used or average available bandwidth or resource blocks over a second time period. Additionally or alternatively, the parameters of the autonomous vehicle service management configuration 430-a may also indicate other information related to the service flow of the wireless communication system 400 (e.g., channel busy rate (CBR)). Using such parameters, network entity 105-e can be able to determine the resource congestion level of network entity 105-f, and vice versa. For example, network entity 105-e may determine that network entity 105-f is likely a resource-congested network entity 105 based on the parameters of the autonomous vehicle service management configuration 430-a regarding network entity 105-f. Therefore, network entity 105-e can coordinate with network entity 105-f to alleviate the congestion of network entity 105-f, thereby increasing the vehicle service throughput between network entity 105-e and network entity 105-f.

[0117] Furthermore, after network entities 105-e and 105-f communicate the autonomous vehicle service management configuration 430-a, network entity 105 serving the autonomous vehicle UE 115 capable of performing the handover procedure can calculate a set of handover parameters. For example, when the autonomous vehicle UE 115-b served by network entity 105-e sends a signal indicating that the autonomous vehicle UE 115-b can perform a handover to network entity 105-f, network entity 105-e can calculate the handover parameters. In some examples, network entity 105-e may send the handover parameters to network entity 105-f via communication link 415, send the handover parameters to the autonomous vehicle UE 115-b via a set of beams 435, or both. In some other examples, as part of the handover process, network entity 105-e may send handover parameters to the autonomous vehicle UE 115-b via a downlink control channel (e.g., physical downlink control channel (PDCCH)), a data channel (e.g., physical downlink shared channel (PDSCH)), a MAC header, MAC-CE, or via one of one or more handshake messages.

[0118] In some cases, handover parameters may include an RSRP threshold, whereby handover can be performed early if the RSRP measured by the autonomous vehicle UE 115-b to network entity 105-f is higher than the RSRP threshold. Conversely, if the RSRP measured by the autonomous vehicle UE 115-b to be lower than the RSRP threshold, handover can be delayed until the RSRP measured by the autonomous vehicle UE 115-b to network entity 105-f meets or exceeds the RSRP threshold. For example, as described herein, as part of the handover process, the autonomous vehicle UE 115-b may perform a signal quality measurement (e.g., RSRP measurement) of the connection to network entity 105-f while maintaining a connection to network entity 105-e. If the signal quality measurement is lower than the signal quality measurement threshold (e.g., the RSRP threshold), the signal quality of network entity 105-f may not support V2X communication for the autonomous vehicle UE 115-b. Therefore, the autonomous vehicle UE 115-b may maintain a connection to network entity 105-e, and handover can be performed once the signal quality of network entity 105-f at least meets the signal quality threshold (e.g., thus delaying handover). In other cases where signal quality measurements may exceed the signal quality measurement threshold, network entity 105-f may be able to support V2X communication for autonomous vehicle UE 115-b earlier than expected. Therefore, autonomous vehicle UE 115-b may perform an early handover to free up resources at network entity 105-e (e.g., thereby reducing the congestion level of network entity 105-e).

[0119] Additionally or alternatively, the handover parameters may also indicate the area identifier (ID) of the location where the handover should occur. For example, each cell 405 within the wireless communication system 400 (e.g., cell 405-a and cell 405-b) may contain a set of areas (e.g., coverage areas) with corresponding area IDs. In some cases, network entity 105-e or network entity 105-f may be configured such that if the autonomous vehicle UE 115 enters an area within a subset of the area set, network entity 105-e or network entity 105-f may initiate a handover process to an adjacent network entity 105. Therefore, there may also be a set of areas between each cell 405 where handovers between network entities 105 can occur, and the handover parameters may indicate the area from this set and the corresponding area ID.

[0120] In some other examples, network entities 105-e and 105-f can determine whether autonomous vehicle UE 115-b or autonomous vehicle UE 115-c will perform the handover process. By coordinating network entities 105-e and 105-f, network entity 105 can prevent ping-pong effects during the handover process. For example, if autonomous vehicle UE 115-b moves back and forth between cells 405-a and 405-b, frequent handovers from network entity 105-e to network entity 105-f, and vice versa, may occur (e.g., ping-pong effect or back-and-forth effect). However, by implementing cooperation between network entities 105-e and 105-f, network entity 105 can use techniques such as early handover or delayed handover to reduce or prevent ping-pong effects. For example, network entity 105-e can predict that autonomous vehicle UE 115-b may move frequently between cells 405-a and 405-b. Therefore, network entity 105-e can send an autonomous vehicle service management configuration 430-a to network entity 105-f, which instructs the autonomous vehicle UE 115-b to perform a delayed handover. In some cases, the handover can be delayed until the autonomous vehicle UE 115-b enters the cell 405-b, or until the autonomous vehicle UE 115-b has been in the cell 405-b for a threshold amount of time.

[0121] Furthermore, by enabling network entities 105-e and 105-f to determine the handover, techniques such as proactive caching can be implemented. Using such techniques, network entities 105-e and 105-f can predict when autonomous vehicle UE 115-b or autonomous vehicle UE 115-c is ready to perform a handover and proactively store handover parameters for autonomous vehicle service management configuration 430. For example, network entity 105-e can use some machine learning (ML) techniques to predict the movement of autonomous vehicle UE 115-b. Therefore, network entity 105-e can be able to predict when autonomous vehicle UE 115-b is expected to handover and signal this information to network entity 105-f, allowing network entity 105-f to proactively release resources to support autonomous vehicle UE 115-b.

[0122] Additionally or alternatively, by enabling network entities 105-e and 105-f to determine a switchover, network entity 105 may communicate its current capabilities via communication link 415 through a status report message 440 (e.g., status report message 440-a). Such a status report message 440 may allow network entity 105 to determine the congestion levels of neighboring network entities 105 and which network entities 105 may require assistance in reducing resource congestion levels. In some cases, network entities 105-e and 105-f may send status report messages 440, as X-3 messages, to each other via communication link 415 to communicate the capabilities of their respective network entities.

[0123] Therefore, based on network entity 105-e and network entity 105-f determining that a handover should occur, either network entity 105-e or network entity 105-f may send the autonomous vehicle service management configuration 430-a via communication link 415. The autonomous vehicle service management configuration 430-a may include one or more parameters, which include information related to the sending network entity 105 (e.g., the network entity 105 that sends the autonomous vehicle service management configuration 430-a), the receiving network entity 105 (e.g., the network entity 105 that receives the autonomous vehicle service management configuration 430-a), or both. The information provided by the parameters of the autonomous vehicle service management configuration 430-a can be described elsewhere herein. For example, network entity 105-e may send the autonomous vehicle service management configuration 430-a to network entity 105-f via communication link 415 based on determining that the autonomous vehicle UE 115-b should switch from network entity 105-e to network entity 105-f. After sending the autonomous vehicle service management configuration 430-a, network entity 105-e may send signaling to autonomous vehicle UE 115-b to prepare autonomous vehicle UE 115-b for the handover process. In some cases, autonomous vehicle UE 115-b may send a feedback message (e.g., a HARQ acknowledgment (ACK) / negative ACK (NACK) message) to network entity 105-e, indicating whether autonomous vehicle UE 115-b has successfully received the signal.

[0124] Based on the ACK sent by the autonomous vehicle UE 115-b to network entity 105-e, network entity 105-e can send a message to network entity 105-f instructing network entity 105-f to initiate a handover procedure with the autonomous vehicle UE 115-b to take over the connectivity and support of the autonomous vehicle UE 115-b. In some examples, such a message may include the UE 115 ID or the autonomous vehicle UE 115 ID to indicate which autonomous vehicle UE 115 to connect to. Therefore, network entity 105-f can initiate a handover procedure with network entity 105-b according to handover techniques discussed elsewhere herein (e.g., using handshake signaling). Furthermore, upon completion of the handover procedure, the autonomous vehicle UE 115-b can send a handover success message to network entity 105-b, and the autonomous vehicle UE 115-b is now connected to network entity 105-f. After receiving a message from the autonomous vehicle UE 115-b, network entity 105-e may discard the connection with the autonomous vehicle UE 115-b.

[0125] Furthermore, according to an additional aspect of this disclosure, in some examples, the autonomous vehicle service management configuration 430 may instruct bandwidth allocation across network entities 105 (e.g., network entities 105-e and 105-f). For example, since cell 405-a supported by network entity 105-e and cell 405-b supported by network entity 105-f may be geographically adjacent cells 405, some co-channel interference may exist if network entities 105-e and 105-f use the same bandwidth, which may degrade the communication performance of the wireless communication system 400. Therefore, the techniques of this disclosure can describe a resource-congested network entity 105 (e.g., network entity 105-f) signaling to surrounding network entities 105 (e.g., network entity 105-e) to avoid using the selected bandwidth. In some examples, such signaling may be sent via the autonomous vehicle service management configuration 430. In other words, network entity 105-f can send autonomous vehicle service management configuration 430-a to signal network entity 105-e to avoid using the selected bandwidth.

[0126] In some examples, network entity 105-f may transmit autonomous vehicle service management configuration 430-a based on the knowledge that a higher modulation and decoding scheme (MCS) and a higher decoding rate can be used within the bandwidth. Therefore, network entity 105-f can use a higher MCS and decoding rate to prevent any interference from surrounding network entities 105. Furthermore, by using a higher MCS and decoding rate, network entity 105-f may be able to serve the attached autonomous vehicle UE 115. Additionally, in some cases, network entity 105-f may know about neighboring or adjacent network entities 105 (e.g., network entity 105-e) based on monitoring radio or data channels. In some other cases, network entity 105-f may know about neighboring or adjacent network entities 105 based on communication with server 410 via communication link 425. For example, server 410 may monitor and collect information about network entities 105 (e.g., network entities 105-e and 105-f) within wireless communication system 400. In other words, server 410 can collect information about resource congestion for each network entity 105 (e.g., network entity 105-e and network entity 105-f) within the wireless communication system 400. Based on this information, server 410 can determine the resource congestion level of network entity 105 and send autonomous vehicle service management configuration 430-b to network entity 105-e via communication link 425, and send autonomous vehicle service management configuration 430-c to network entity 105-f via communication link 420.

[0127] In some cases, server 410 may collect information about resource congestion of the respective network entity 105 based on status report messages 440 (e.g., status report messages 440-a and 440-b) sent from both network entities 105-e and 105-f via communication links 420 and 425. For example, network entity 105-e may send status report message 440-a via communication link 425, and network entity 105-f may send status report message 440-b via communication link 420. Status report messages 440 may include information about the current state, past state, average state, or predicted state of the respective network entity. For example, network entity 105-e may indicate the number of autonomous vehicle UEs 115 currently being served, the number served in the past X hours, or (e.g., using ML technology) a prediction of the number of autonomous vehicle UEs to be served in the next few hours. In addition, the status report message 440 may also include an indication of the bandwidth or resource blocks in use or used on average over the past Y hours, an indication of the available bandwidth or resource blocks in use or used on average over the past Y hours, CBR, or any combination thereof. Furthermore, network entities 105-e and 105-f may periodically, semi-periodically, or aperiodically (e.g., triggered based on a request from server 410) send the status report message 440 to server 410.

[0128] Using information from status report messages 440 (e.g., status report messages 440-a and 440-b), server 410 can calculate the bandwidth that each network entity 105 within the wireless communication system 400 should use and operate on, and notify the corresponding network entity 105. In some cases, this indication may be made through autonomous vehicle service management configuration 430 (e.g., autonomous vehicle service management configuration 430-b and 430-c). In other cases, such indication may be an upper-layer message or an application-layer message.

[0129] In another example, a resource-congested network entity 105 (e.g., network entity 105-f) may collect information about resource congestion in each cell 405 from status report messages 440 (e.g., status report message 440-c) from corresponding network entities supporting cells 405 (e.g., cells 405-a and 405-b). For example, network entity 105-e may send status report message 440-c to network entity 105-f via communication link 415, indicating information about network entity 105-e. In some cases, network entity 105-e may send status report message 440-c to network entity 105-f periodically, semi-periodically, or aperiodically (e.g., triggered based on a request from network entity 105-f). Based on the status report message 440-c, network entity 105-f may then send an autonomous vehicle service management configuration 430-a, which informs network entity 105-e of the bandwidth to be used and operated on. In some cases, network entity 105-f may send the autonomous vehicle service management configuration 430-a to network entity 105-e via communication link 415 within an X-3 message. Furthermore, network entity 105-e may send an X-3 message to network entity 105-f via communication link 415, which acknowledges receipt of the X-3 message transmission including the autonomous vehicle service management configuration 430-a. Therefore, the first message instructing the autonomous vehicle service management configuration 430-a may be an X-3 message.

[0130] In some other examples, a head network entity 105 may exist, which performs bandwidth allocation calculations and notifies other network entities 105 within the wireless communication system 400 of the bandwidth they should use and operate on. For example, the head network entity 105 may be selected based on the capabilities of the network entities 105 within the wireless communication system 400. In some cases, the server 410 may select one network entity within the wireless communication system 400 as the head network entity 105 based on receiving status report messages 440 from each network entity 105 within the wireless communication system 400. Once the head network entity 105 is selected, other network entities 105 within the wireless communication system 400 may send status report messages 440 to the head network entity 105 to assist it in performing bandwidth allocation calculations.

[0131] In some examples, when server 410 selects head network entity 105, other network entities 105 may not be aware of this selection, and other network entities 105 may send status report messages 440 to server 410. Therefore, server 410 may forward status report messages 440 to head network entity 105. In such examples, after calculating the bandwidth allocation for each network entity 105 within the wireless communication system 400, head network entity 105 may send a message indicating the bandwidth allocation to server 410. When server 410 forwards status report messages 440 to head network entity 105, server 410 may multiplex each status report message in status report messages 440, and include the network entity 105 ID in each status report message. Therefore, head network entity 105 may demultiplex the messages, and when sending a message indicating the bandwidth allocation for other network entities 105 to server 410, head network entity 105 may multiplex the bandwidth allocations indexed by the network entity 105 ID together. Therefore, server 410 can demultiplex messages from head network entity 105 and send the correct bandwidth allocation to the correct network entity 105 within wireless communication system 400 based on network entity 105 ID.

[0132] In some aspects, the autonomous vehicle service management configuration 430 can also be used to dynamically allocate transmit power among network entities 105 (e.g., network entities 105-e and 105-f) within the wireless communication system 400. For example, parameters of the autonomous vehicle service management configuration 430 can indicate the transmit power that the corresponding network entity 105 should use. Typically, the transmit power can be the same across all network entities 105 within the wireless communication system 400. However, allowing resource-congested network entities 105 (e.g., network entity 105-f) to use higher transmit power and allowing surrounding non-resource-congested (e.g., resource-spared) network entities 105 (e.g., network entity 105-e) to use lower transmit power can reduce congestion of the resource-congested network entities 105, thereby enhancing the wireless communication system 400. Such a configuration can also achieve higher spectral efficiency for the resource-congested network entities 105 and allow the resource-congested network entities 105 to support additional autonomous vehicle UEs 115.

[0133] In some examples, to support such a configuration, server 410 may collect information about the radio congestion status (e.g., resource congestion level) of each cell 405 based on status report messages 440 from the respective network entities 105. Therefore, server 410 may calculate the transmit power of each network entity 105 within the wireless communication system 400 and notify the corresponding network entity 105 based on the status report messages 440. For example, if network entity 105 has a low resource congestion level, its transmit power may be reduced accordingly, and if network entity 105 has a high resource congestion level, its transmit power may be increased accordingly. In some cases, the server may notify network entities 105 (e.g., network entities 105-e and 105-f) of the corresponding transmit power level via autonomous vehicle service management configurations 430 (e.g., autonomous vehicle service management configurations 430-b and 430-c). In some other cases, server 410 may send upper-layer messages or application-layer messages to network entity 105 that indicate the transmit power that each network entity 105 should use.

[0134] In some other examples, a resource-congested network entity 105 (e.g., network entity 105-f) may collect information about the radio congestion status of each cell 405 based on status report messages 440 (e.g., status report message 440-a) from other network entities 105 (e.g., network entity 105-e) within the wireless communication system 400. Therefore, network entity 105-f may notify network entity 105-e of the transmit power it should use based on the fact that network entity 105-f is a resource-congested network entity 105. In some cases, network entity 105-f may notify network entity 105-e via parameters of the autonomous vehicle service management configuration 430-a. In some other cases, network entity 105-f may notify network entity 105-e of the autonomous vehicle service management configuration 430-a via an X-3 message. Furthermore, network entity 105-e may send an X-3 message back to network entity 105-f, indicating that network entity 105-e has successfully received the autonomous vehicle service management configuration 430-a. Additionally or alternatively, network entity 105-e, network entity 105-f, or both may reduce their transmission power level to assist network entity 105 with resource congestion. For example, based on parameters of the autonomous vehicle service management configuration 430, network entity 105-e may determine to use a reduced transmission power level based on the determination that network entity 105-f is likely a resource-congested network entity 105. Therefore, by using a reduced transmission power level, network entity 105-e can assist network entity 105-f in reducing resource congestion by using an increased transmission power level.

[0135] In another example, since a resource-congested network entity 105 (e.g., network entity 105-f) can benefit from using a higher MCS and a higher decoding rate, a non-resource-congested network entity 105 (e.g., network entity 105-e) can be reconfigured with a MIMO beamforming configuration to support the resource-congested network entity 105 using a higher MCS and a higher decoding rate. Therefore, by allowing the resource-congested network entity 105 to use a higher MCS and a higher decoding rate, the resource congestion level of the resource-congested network entity 105 can be reduced. For example, when network entity 105-e calculates the MIMO beamforming vector for beamforming communication via the set of beams 435, network entity 105-e can form a null space (e.g., a MIMO beamforming space) within the MIMO beamforming vector of the beamforming configuration to help reduce the resource congestion of network entity 105-f. Furthermore, the MIMO beamforming space can be used by an autonomous vehicle UE 115 connected to network entity 105-f, network entity 105-g, or both. In some cases, the MIMO beamforming space allows network entity 105-e to avoid performing beamforming on a specific radio channel for the autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-b). In other cases, the MIMO beamforming space can indicate beamforming directions that network entity 105-e should avoid when communicating with the autonomous vehicle UE 115 within cell 405-a. For example, beam 435-a in the set of beams 435 may be pointed toward cell 405-b, and when used by network entity 105-e, this beam may cause resource congestion for network entity 105-f. Therefore, network entity 105-e may avoid sending messages via beam 435-a.

[0136] Furthermore, network entity 105-f may send messages to surrounding network entities 105 (e.g., network entity 105-e) via autonomous vehicle service management configuration 430 or a separate message, transmitting the autonomous vehicle UE 115 ID being served by network entity 105-f, the Global Navigation Satellite System (GNSS) location being served by network entity 105-f, or both. In some cases, using this information, network entity 105-e may be able to monitor the channel between the autonomous vehicle UE 115 and network entity 105-f within cell 405-b to create a MIMO beamforming space. In some examples, network entity 105-f may send this information as an X-3 message to network entity 105-e via communication link 415.

[0137] In some cases, the spectral efficiency of network entity 105-e may be reduced because it has MIMO beamforming space within the MIMO beamforming vector. However, this reduction in spectral efficiency may be a trade-off to limit latency reduction within the wireless communication system 400, which is caused by reduced traffic flow to autonomous vehicle UE 115 due to restricted access to cell 405 when resource congestion occurs at network entity 105. In some examples, network entity 105-e may be configured with a spectral efficiency threshold such that if the spectral efficiency of network entity 105-e drops below the threshold, network entity 105-e can use the full set of beams 435 to perform V2X communication with autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-b) within cell 405-a, regardless of resource congestion at network entity 105-f.

[0138] Furthermore, to determine whether network entity 105 should implement MIMO beamforming space, server 410, resource-congested network entity 105 (e.g., network entity 105-f), or both, may receive status report messages 440 from surrounding network entities 105. For example, network entity 105-e may send status report message 440-a to server 410 via communication link 420, send status report message 440-c to network entity 105-f via communication link 415, or both. Based on the content of status report message 440-a, status report message 440-c, or both, server 410, network entity 105-f, or both can determine whether this trade-off of having MIMO beamforming space will affect the performance of network entity 105-e. In some examples, based on status report message 440, server 410 or network entity 105-f can determine that the performance of network entity 105-e remains the same when using MIMO beamforming space within the MIMO beamforming vector of network entity 105-e. Therefore, server 410 or network entity 105-f may send autonomous vehicle service management configuration 430 (e.g., autonomous vehicle service management configuration 430-a or autonomous vehicle service management configuration 430-b) to network entity 105-e, which instructs network entity 105-e to generate MIMO beamforming space.

[0139] Additionally or alternatively, there may be scenarios with multiple resource-congested network entities 105. For example, both network entity 105-e and network entity 105-f may be resource-congested network entities 105. Furthermore, the topologies of network entities 105-e and 105-f, as well as the topologies of the road networks within communities 405-a and 405-b, may be relatively complex. Therefore, network entities 105-e and 105-f may not be able to communicate via communication link 415. Therefore, to support collaboration between network entities 105-e and 105-f, the respective network entities 105 may communicate via server 410, which may be an example of a cloud-based server 410. That is, the cloud-based server 410 may act as a relay node for communication between network entities 105-e and 105-f.

[0140] In such a scenario, the cloud-based server 410 can collect all information about network entities 105 (e.g., network entities 105-e and 105-f) within the wireless communication system 400 via status report messages 440 (e.g., status report messages 440-a and 440-b). Furthermore, the cloud-based server 410 can perform any calculations using any combination of the techniques described herein (e.g., performing early / delayed handover, dynamically allocating bandwidth for network entities 105, dynamically allocating transmit power for network entities, or forming MIMO beamforming space). Therefore, the cloud-based server 410 can allow network entities 105-e and 105-f to communicate with the autonomous vehicle UE 115 using any available resources, rather than via the communication link 415 between network entities 105-e and 105-f. Therefore, a status report message 440 (e.g., status report message 440-c) transmitted between network entities 105-e and 105-f via X-3 messages can also be sent to a cloud-based server 410. The cloud-based server 410 can then use the status report message 440 to determine parameters of the autonomous vehicle service management configuration 430 as described herein, and send the autonomous vehicle service management configuration 430 to network entity 105 of the wireless communication system 400. For example, the cloud-based server 410 can configure the parameters of the autonomous vehicle service management configuration 430 to indicate changes to early handover configuration / delayed handover configuration, bandwidth allocation configuration, transmit power allocation configuration, or beamforming configuration.

[0141] By using the techniques described herein, wireless communication system 400 may experience an increase in physical traffic flow and a reduction in resource congestion within network entities. For example, cooperation between network entity 105-e and network entity 105-f can be enabled via the indication of parameters in the autonomous vehicle service management configuration 430 to support reliable wireless connectivity to the autonomous vehicle UE 115. Further descriptions of the parameters in the autonomous vehicle service management configuration 430 indicating the techniques of this disclosure can also be found elsewhere herein (including references). Figure 5 )describe.

[0142] Figure 5 An example of a process flow 500 supporting a technology for business management of autonomous vehicles according to one or more aspects of this disclosure is shown. In some examples, process flow 500 may be implemented by or by wireless communication system 100, wireless communication system 200, wireless communication system 300 and / or wireless communication system 400. For example, process flow 500 may include an autonomous vehicle UE 115-d, network entity 105-g, network entity 105-h and server 505, which may be referenced herein. Figure 1 An example of the device described.

[0143] In the following description of process flow 500, the operations between the autonomous vehicle UE 115-d, network entity 105-g, network entity 105-h, and server 505 may be performed in different orders or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although the autonomous vehicle UE 115-d, network entity 105-g, network entity 105-h, and server 505 are shown as performing the operations of process flow 500, some aspects of some operations may also be performed by one or more other wireless devices.

[0144] At point 510, network entity 105-g may convey a first message instructing the autonomous vehicle service management configuration. This autonomous vehicle service management configuration may be based on the vehicle service throughput level of network entity 105-g, network entity 105-h, or both satisfying a vehicle service congestion level threshold. In some cases, the autonomous vehicle service management configuration may also be based on the vehicle service throughput level of network entity 105-g, network entity 105-h, or both satisfying a vehicle service throughput level threshold, a vehicle service congestion level, or both. Furthermore, the autonomous vehicle service management configuration may include one or more parameters for coordinating wireless communications between network entities 105-g and 105-h and a set of one or more autonomous vehicle UEs 115 (e.g., autonomous vehicle UE115-d). In some cases, the vehicle service throughput level of network entities 105-g, network entity 105-h, or both may be based on a communication resource congestion level. Therefore, network entity 105-g may convey a first message instructing the autonomous vehicle service management configuration based on the communication resource congestion level of network entity 105-g, network entity 105-h, or both meeting a communication resource congestion level threshold. Additionally or alternatively, the first message instructing the autonomous vehicle service management configuration may include network entity 105-g sending or receiving a first message. For example, network entity 105-g may send a first message to network entity 105-h, receive a first message from network entity 105-h, send a first message to server 505, receive a first message from server 505, or any combination thereof.

[0145] In some examples, one or more parameters of the autonomous vehicle management configuration may include an indication regarding delaying the handover of one or more autonomous vehicle UEs 115-d from a set of autonomous vehicle UEs 115 between network entities 105-g and 105-h, or an indication regarding performing an early handover between network entities 105-g and 105-h. For example, the indication regarding delaying the handover or performing an early handover may be based on the vehicle traffic throughput level of network entities 105-g, 105-h, or both meeting a vehicle traffic congestion level threshold. Furthermore, the indication regarding delaying the handover or performing an early handover may also indicate the time period associated with the delayed handover or the location associated with the delayed handover or the early handover. In some cases, network entity 105-g or network entity 105-h may receive from autonomous vehicle UE 115-d an indication that autonomous vehicle UE 115-d may delay the handover between network entities 105-g and 105-h or perform an early handover between network entities 105-g and 105-h. Therefore, the autonomous vehicle service management configuration can be based on instructions from autonomous vehicle UE 115-d. In some other cases, network entity 105-g can convey a signal indicating that at least one autonomous vehicle UE 115 in the set of autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-d) can switch between network entity 105-g and network entity 105-h, and can convey a first message based on this signal.

[0146] In some other examples, one or more parameters of the autonomous vehicle service management configuration may indicate a first bandwidth allocation for network entity 105-g to wirelessly communicate with a set of one or more autonomous vehicle UEs 115 and a second bandwidth allocation for network entity 105-h to wirelessly communicate with a set of one or more autonomous vehicle UEs. Furthermore, the second bandwidth allocation may differ from the first bandwidth allocation. In some cases, network entity 105-g may receive a second message indicative of the autonomous vehicle service management configuration from a service management server (e.g., server 505) based on the vehicle throughput level of network entity 105-g, network entity 105-h, or both. In some other cases, network entity 105-g may send control signaling to network entity 105-h based on bandwidth allocation calculations, instructing network entity 105-h to use the second bandwidth allocation. Furthermore, network entity 105-g may send second control signaling based on an interference level associated with the first bandwidth allocation, instructing 105-h to use the second bandwidth allocation.

[0147] In another example, one or more parameters of the autonomous vehicle service management configuration may indicate a first transmit power level for network entity 105-g to wirelessly communicate with a set of one or more autonomous vehicle UEs 115, a second transmit power level for network entity 105-h to wirelessly communicate with a set of one or more autonomous vehicle UEs 115, or both, wherein the second transmit power level is different from the first transmit power level. Furthermore, based on the vehicle service throughput level of network entity 105-g satisfying a vehicle service congestion level threshold, the first transmit power level of network entity 105-g may be greater than or less than the second transmit power level of network entity 105-h. Additionally or alternatively, one or more parameters of the autonomous vehicle service management configuration may indicate a MIMO beamforming space for a set of one or more autonomous vehicle UEs that can connect to network entity 105-g, network entity 105-h, or both. In some cases, the MIMO beamforming space may indicate the wireless channels or beamforming directions that network entity 105-g, network entity 105-h, or both should avoid for communicating with autonomous vehicle UE 115 (e.g., autonomous vehicle UE 115-d).

[0148] In some cases, network entity 105-h may receive a second message from server 505 indicating the configuration of autonomous vehicle service management based on the vehicle service throughput levels of both network entities 105-h and 105-g meeting the vehicle service congestion level. In other cases, network entity 105-h may send a message to server 505 indicating bandwidth allocation, beamforming configuration, or any combination thereof based on the vehicle service throughput level of network entity 105-g meeting a vehicle service congestion level threshold.

[0149] Furthermore, one or more parameters of the autonomous vehicle service management configuration may indicate the number of autonomous vehicle UEs 115 being served by network entity 105-g, network entity 105-h, or both; an indication of the bandwidth or resource blocks in the set of resource blocks used by network entity 105-g, network entity 105-h, or both; an indication of available bandwidth or available resource blocks; a zone identifier of a subset of the set of one or more autonomous vehicle UEs 115 served by network entity 105-g, network entity 105-h, or both; an indication of channel busy rate; or any combination thereof. Additionally, the indication of the number of autonomous vehicle UEs 115 being served by network entity 105-g, network entity 105-h, or both may be a current indication or an indication over a period of time. Additionally or alternatively, the indications of both the bandwidth or resource blocks in the set of resource blocks used by network entity 105-g, network entity 105-h, or both, and the indication of available bandwidth or available resource blocks, may be a current indication or an average over a period of time.

[0150] At point 515, network entity 105-g may communicate one or more additional messages to a set of one or more autonomous vehicle UEs 115 based on one or more parameters configured for autonomous vehicle management. Furthermore, communicating one or more additional messages to the set of autonomous vehicle UEs 115 may include sending or receiving one or more additional messages to the set of one or more autonomous vehicle UEs 115. For example, network entity 105-g, network entity 105-h, or both may send one or more additional messages to autonomous vehicle UE 115-d, or autonomous vehicle UE 115-d may send one or more additional messages to network entity 105-g, network entity 105-h, or both.

[0151] Figure 6 A block diagram 600 illustrates a device 605 supporting technologies for operational management of autonomous vehicles according to one or more aspects of this disclosure. Device 605 may be an example of aspects of network entity 105 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0154] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of the technologies for business management of autonomous vehicles as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0155] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, 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).

[0156] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, 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).

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

[0158] The communication manager 620 may support wireless communication according to examples disclosed herein. For example, the communication manager 620 may be capable of, configured to, or operable to support components that: convey a first message indicative of an autonomous vehicle service management configuration based on the vehicle traffic throughput level of a first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communication between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipments (UEs). The communication manager 620 may be capable of, configured to, or operable to support components that: convey one or more additional messages to the set of one or more autonomous vehicle UEs according to the one or more parameters of the autonomous vehicle service management configuration.

[0159] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., control receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support technologies for network entities to send autonomous vehicle business management configurations to support reduced processing, reduced power consumption and more efficient use of communication resources.

[0160] Figure 7 A block diagram 700 illustrates a device 705 supporting technologies for operational management of autonomous vehicles according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or network entity 105 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720) may include at least one processor that may be coupled to at least one memory to support the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0163] Device 705 or its various components may be examples of parts used to perform various aspects of the technologies for autonomous vehicle business management as described herein. For example, communication manager 720 may include autonomous vehicle business management configuration component 725, messaging component 730, or any combination thereof. Communication manager 720 may be examples of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0164] Communication manager 720 may support wireless communication according to examples disclosed herein. Autonomous vehicle service management configuration component 725 is capable of, configured to, or operable to support components that: convey a first message instructing an autonomous vehicle service management configuration based on a vehicle service throughput level of a first network entity, a second network entity, or both satisfying a vehicle service congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communication between the first and second network entities and a set of one or more autonomous vehicle user equipment (UEs). Message component 730 is capable of, configured to, or operable to support components that: convey one or more additional messages to the set of one or more autonomous vehicle UEs according to the one or more parameters of the autonomous vehicle service management configuration.

[0165] Figure 8A block diagram 800 is shown of a communication manager 820 supporting technologies for autonomous vehicle business management according to one or more aspects of this disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of parts for performing aspects of the technologies for autonomous vehicle business management as described herein. For example, the communication manager 820 may include an autonomous vehicle business management configuration component 825, a messaging component 830, an autonomous vehicle business management configuration receiver 835, a message transmitter 840, a switching indication receiver 845, a switching signal component 850, a bandwidth allocation transmitter 855, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0166] The communication manager 820 may support wireless communication according to examples disclosed herein. The autonomous vehicle service management configuration component 825 is capable of, configured to, or operable to support components that: convey a first message instructing an autonomous vehicle service management configuration based on a vehicle service throughput level of a first network entity, a second network entity, or both satisfying a vehicle service congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communication between the first and second network entities and a set of one or more autonomous vehicle user equipment (UEs). The messaging component 830 is capable of, configured to, or operable to support components that: convey one or more additional messages to the set of one or more autonomous vehicle UEs according to the one or more parameters of the autonomous vehicle service management configuration.

[0167] In some examples, the vehicle traffic throughput level of the first network entity and the autonomous vehicle service management configuration component 825 can be configured or operated to support the following: conveying the first message indicating the autonomous vehicle service management configuration based on the communication resource congestion level of the first network entity, the second network entity, or both meeting a communication resource congestion level threshold.

[0168] In some examples, the one or more parameters of the autonomous vehicle service management configuration include an indication to delay the handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity or to perform an early handover between the first network entity and the second network entity, the indication to delay the handover or perform the early handover being based on the vehicle service throughput level of the first network entity, the second network entity, or both meeting the vehicle service congestion level threshold.

[0169] In some examples, the instruction regarding delaying the switch or performing the switch ahead of schedule includes the time period associated with the delayed switch or the early switch, as well as the location associated with the delayed switch or the early switch.

[0170] In some examples, the handover indication receiver 845 is capable of, configured to, or operable to support components for: receiving from one of the autonomous vehicle UEs in the set of one or more autonomous vehicle UEs an indication that the autonomous vehicle UE will delay the handover between the first network entity and the second network entity or perform the early handover between the first network entity and the second network entity, wherein the autonomous vehicle service management configuration may be based on the indication from the autonomous vehicle UE.

[0171] In some examples, the switching signal component 850 is capable of, configured to, or operable to support components for: conveying a signal indicating that at least one autonomous vehicle UE in the set of one or more autonomous vehicle UEs will switch between the first network entity and the second network entity, wherein the first message is conveyed based on the signal.

[0172] In some examples, the one or more parameters of the autonomous vehicle service management configuration indicate a first bandwidth allocation for the first network entity to use for wireless communication with the set of one or more autonomous vehicle UEs, a second bandwidth allocation for the second network entity to use for wireless communication with the set of one or more autonomous vehicle UEs, or both, wherein the second bandwidth allocation is different from the first bandwidth allocation.

[0173] In some examples, the autonomous vehicle service management configuration receiver 835 is capable of, configured to, or able to operate to support components that receive a second message from the service management server indicative of the autonomous vehicle service management configuration based on the vehicle service throughput level of the first network entity, the second network entity, or both.

[0174] In some examples, the bandwidth allocation transmitter 855 is capable of, configured to, or able to operate to support components that send control signaling based on bandwidth allocation calculations, the control signaling instructing the second network entity to use the second bandwidth allocation.

[0175] In some examples, the bandwidth allocation transmitter 855 is capable of, configured to, or able to operate to support components that send a second control signaling based on an interference level associated with the first bandwidth allocation, the second control signaling instructing the second network entity to use the second bandwidth allocation.

[0176] In some examples, the one or more parameters of the autonomous vehicle service management configuration indicate a first transmit power level for the first network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, or both, wherein the second transmit power level is different from the first transmit power level.

[0177] In some examples, the vehicle service throughput level based on the first network entity meets the vehicle service congestion level threshold, and the first transmission power level of the first network entity is greater than or less than the second transmission power level of the second network entity.

[0178] In some examples, the one or more parameters of the autonomous vehicle service management configuration indicate the MIMO beamforming space of the set of one or more autonomous vehicle UEs connected to the first network entity, the second network entity, or both, which indicates the wireless channels or beamforming directions that the first network entity, the second network entity, or both should avoid for communicating with the autonomous vehicle UEs.

[0179] In some examples, the autonomous vehicle service management configuration receiver 835 is capable of, configured to, or able to operate to support the following component: receiving a second message from the server indicating the autonomous vehicle service management configuration based on the fact that the vehicle service throughput levels of both the first network entity and the second network entity meet the vehicle service congestion level threshold.

[0180] In some examples, message sender 840 is capable of, configured to, or able to operate to support components that send messages to a server indicative of bandwidth allocation, transmit power level, beamforming configuration, or any combination thereof, based on the vehicle traffic throughput level of the first network entity meeting a vehicle traffic congestion level threshold.

[0181] In some examples, the one or more parameters of the autonomous vehicle service management configuration further indicate: the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both; an indication of the resource blocks in the set of bandwidth or resource blocks used by the first network entity, the second network entity, or both; an indication of the available bandwidth or available resource blocks; a district identifier of a subset of the set of one or more autonomous vehicle UEs served by the first network entity, the second network entity, or both; an indication of the channel busy rate; or any combination thereof.

[0182] In some examples, the one or more parameters of the autonomous vehicle service management configuration indicate the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both, and wherein the indication of the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both is a current indication or for a certain period of time.

[0183] In some examples, the one or more parameters of the autonomous vehicle service management configuration include: an indication of the bandwidth or resource blocks in the resource block set used by the first network entity, the second network entity, or both, and an indication of available bandwidth or available resource blocks, wherein both the indication of the bandwidth or resource blocks used by the first network entity, the second network entity, or both and the indication of the available bandwidth or available resource blocks are current indications or average values ​​over a period of time.

[0184] In some examples, the first message conveying instructions on the business management configuration of the autonomous vehicle includes sending or receiving the first message.

[0185] In some examples, communicating the one or more additional messages with the set of one or more autonomous vehicle UEs includes sending or receiving the one or more additional messages with the set of one or more autonomous vehicle UEs.

[0186] Figure 9A diagram is shown of a system 900 including a device 905 supporting business management for autonomous vehicles, according to one or more aspects of this disclosure. Device 905 may be an example of device 605, device 705, or network entity 105 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 905 may include components supporting output and acquisition of communication, such as a communication manager 920, a transceiver 910, an antenna 915, at least one memory 925, code 930, and at least one processor 935. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 940).

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

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

[0189] At least one processor 935 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 935 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 935. At least one processor 935 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 925) to cause device 905 to perform various functions (e.g., functions or tasks supporting technologies for the business management of autonomous vehicles). For example, device 905 or components of device 905 may include at least one processor 935 and at least one memory 925 coupled to one or more processors in at least one processor 935, wherein at least one processor 935 and at least one memory 925 are configured to perform the various functions described herein. At least one processor 935 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions for performing the functions of device 905 (e.g., by executing code 930). At least one processor 935 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 905 (such as within one or more memories of at least one memory 925). In some examples, at least one processor 935 may include multiple processors, and at least one memory 925 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 935 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 935) and memory circuitry (which may include at least one memory 925)) 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. Therefore, at least one processor 935 or a processing system including at least one processor 935 may be configured, configurable, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configurable,” “configurable,” 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 925 or otherwise.

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

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

[0192] 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 that: convey a first message indicative of an autonomous vehicle service management configuration based on the vehicle traffic throughput level of a first network entity, a second network entity, or both meeting a vehicle traffic congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communication between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipments (UEs). The communication manager 920 may be capable of, configured to, or operable to support components that: convey one or more additional messages to the set of one or more autonomous vehicle UEs according to the one or more parameters of the autonomous vehicle service management configuration.

[0193] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies that enable network entities to send autonomous vehicle service management configurations to support improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, and improved utilization of processing power.

[0194] In some examples, the communication manager 920 may be configured to use or otherwise coordinate with the transceiver 910, one or more antennas 915 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the transceiver 910, one or more processors in at least one processor 935, one or more memories in at least one memory 925, code 930, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 935, at least one memory 925, code 930, or any combination thereof). For example, code 930 may include instructions that can be executed by one or more processors in at least one processor 935 to cause the device 905 to perform various aspects of the techniques for autonomous vehicle business management as described herein, or at least one processor 935 and at least one memory 925 may be otherwise configured to perform or support such operations individually or jointly.

[0195] Figure 10 A flowchart illustrating a method 1000 for supporting technologies for business management of autonomous vehicles according to various aspects of this disclosure is shown. The operation of method 1000 may be implemented by a network entity or its components as described herein. For example, the operation of method 1000 may be implemented by, as referenced... Figures 1 to 9 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0196] At 1005, the method may include: conveying a first message indicative of an autonomous vehicle service management configuration based on the vehicle traffic throughput level of a first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipments (UEs). Operation of block 1005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1005 may be provided by reference to [reference needed]. Figure 8 The described autonomous vehicle business management configuration component 825 is used to perform this.

[0197] At 1010, the method may include: communicating one or more additional messages to the set of one or more autonomous vehicle UEs based on one or more parameters of the autonomous vehicle service management configuration. The operation of block 1010 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 8 The message component 830 described is used to execute this.

[0198] Figure 11 A flowchart illustrating a method 1100 for supporting technologies for autonomous vehicle business management according to various aspects of this disclosure is shown. The operation of method 1100 may be implemented by a network entity or its components as described herein. For example, the operation of method 1100 may be implemented by, as referenced... Figures 1 to 9 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0199] At 1105, the method may include: conveying a first message indicative of an autonomous vehicle service management configuration based on the vehicle traffic throughput level of a first network entity, a second network entity, or both satisfying a vehicle traffic congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipment (UEs). Operation of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1105 may be provided by reference to [reference needed]. Figure 8 The described autonomous vehicle business management configuration component 825 is used to perform this.

[0200] At 1110, the method may include: conveying the first message indicative of the autonomous vehicle service management configuration based on the communication resource congestion level of the first network entity, the second network entity, or both satisfying a communication resource congestion level threshold. The operation of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be derived from references... Figure 8 The described autonomous vehicle business management configuration component 825 is used to perform this.

[0201] At 1115, the method may include: communicating one or more additional messages to the set of one or more autonomous vehicle UEs based on one or more parameters of the autonomous vehicle service management configuration. The operation of block 1115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1115 may be provided by reference to [reference needed]. Figure 8 The message component 830 described is used to execute this.

[0202] Figure 12 A flowchart illustrating a method 1200 for supporting technologies for autonomous vehicle business management according to various aspects of this disclosure is shown. The operation of method 1200 may be implemented by a network entity or its components as described herein. For example, the operation of method 1200 may be implemented by, as referenced... Figures 1 to 9 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0203] At 1205, the method may include: sending a message to a server indicating bandwidth allocation, transmit power level, beamforming configuration, or any combination thereof, based on the vehicle traffic throughput level of a first network entity satisfying a vehicle traffic congestion level threshold. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference]. Figure 8 The message sender 840 described is used to perform this.

[0204] At 1210, the method may include: conveying a first message indicative of an autonomous vehicle service management configuration based on the vehicle traffic throughput level of the first network entity, the second network entity, or both satisfying a vehicle traffic congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipment (UEs). Operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be provided by reference to [reference needed]. Figure 8 The described autonomous vehicle business management configuration component 825 is used to perform this.

[0205] At 1215, the method may include: communicating one or more additional messages to the set of one or more autonomous vehicle UEs based on one or more parameters of the autonomous vehicle service management configuration. The operation of block 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference needed]. Figure 8 The message component 830 described is used to execute this.

[0206] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a first network entity, the method comprising: conveying a first message indicating an autonomous vehicle service management configuration based at least in part on a vehicle service throughput level of the first network entity, a second network entity, or both satisfying a vehicle service congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communication between the first network entity and the second network entity and a set of one or more autonomous vehicle UEs; and conveying one or more additional messages to the set of one or more autonomous vehicle UEs according to the one or more parameters of the autonomous vehicle service management configuration.

[0207] Aspect 2: According to the method of aspect 1, wherein the vehicle service throughput level of the first network entity, the second network entity, or both is at least partially based on the communication resource congestion level, and the method further comprises: conveying the first message indicating the autonomous vehicle service management configuration based at least partially on the communication resource congestion level of the first network entity, the second network entity, or both satisfying a communication resource congestion level threshold.

[0208] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the one or more parameters of the autonomous vehicle service management configuration include an indication regarding delaying the handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity or performing an early handover between the first network entity and the second network entity, wherein the indication regarding delaying the handover or performing the early handover is at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying the vehicle service congestion level threshold.

[0209] Aspect 4: According to the first network entity of aspect 3, wherein the indication regarding delaying the handover or performing the early handover further indicates the time period associated with the delayed handover or the early handover and the location associated with the delayed handover or the early handover.

[0210] Aspect 5: The method according to any one of Aspects 3 to 4, the method further comprising: receiving from one of the autonomous vehicle UEs in the set of one or more autonomous vehicle UEs an indication that the autonomous vehicle UE will delay the handover between the first network entity and the second network entity or perform the early handover between the first network entity and the second network entity, wherein the autonomous vehicle service management configuration is based at least in part on the indication from the autonomous vehicle UE.

[0211] Aspect 6: The method according to any one of Aspects 3 to 5, the method further comprising: conveying a signal indicating that at least one autonomous vehicle UE in the set of one or more autonomous vehicle UEs will switch between the first network entity and the second network entity, wherein the first message is conveyed at least in part based on the signal.

[0212] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first bandwidth allocation for the first network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs and indicate a second bandwidth allocation or both for the second network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, and the second bandwidth allocation is different from the first bandwidth allocation.

[0213] Aspect 8: According to the method of aspect 7, the method further includes: receiving a second message indicative of the autonomous vehicle service management configuration from a service management server, based at least in part on the vehicle service throughput level of the first network entity, the second network entity, or both.

[0214] Aspect 9: The method according to any one of Aspects 7 to 8, the method further comprising: sending control signaling at least in part based on bandwidth allocation calculation, the control signaling instructing the second network entity to use the second bandwidth allocation.

[0215] Aspect 10: The method according to aspect 9, the method further comprising: sending a second control signaling at least in part based on an interference level associated with the first bandwidth allocation, the second control signaling instructing the second network entity to use the second bandwidth allocation.

[0216] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first transmit power level for the first network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, or both, and the second transmit power level is different from the first transmit power level.

[0217] Aspect 12: According to the method of aspect 11, wherein at least in part based on the vehicle service throughput level of the first network entity satisfying the vehicle service congestion level threshold, the first transmission power level of the first network entity is greater than or less than the second transmission power level of the second network entity.

[0218] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a multi-input and MIMO beamforming space of one or more sets of autonomous vehicle UEs connected to the first network entity, the second network entity, or both, the MIMO beamforming space indicating a wireless channel or beamforming direction for communicating with the autonomous vehicle UE that the first network entity, the second network entity, or both wish to avoid.

[0219] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: receiving from a server a second message indicating the autonomous vehicle service management configuration based at least in part on the fact that the vehicle service throughput levels of both the first network entity and the second network entity meet the vehicle service congestion level threshold.

[0220] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: sending an additional message to a server, at least in part, based on the fact that the vehicle traffic throughput level of the first network entity meets the vehicle traffic congestion level threshold, indicating bandwidth allocation, transmission power level, beamforming configuration, or any combination thereof.

[0221] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the one or more parameters of the autonomous vehicle service management configuration further indicate: the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both; an indication of a resource block in the set of bandwidth or resource blocks used by the first network entity, the second network entity, or both; an indication of available bandwidth or available resource blocks; a district identifier of a subset of the set of one or more autonomous vehicle UEs served by the first network entity, the second network entity, or both; an indication of channel busy rate; or any combination thereof.

[0222] Aspect 17: According to the method of aspect 16, wherein the one or more parameters of the autonomous vehicle service management configuration indicate the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both, and the indication of the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both is a current indication or for a certain period of time.

[0223] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the one or more parameters of the autonomous vehicle service management configuration include: the indication of the bandwidth or resource blocks in the resource block set used by the first network entity, the second network entity, or both, and the indication of the available bandwidth or available resource blocks, wherein both the indication of the bandwidth or resource blocks in the resource block set used by the first network entity, the second network entity, or both and the indication of the available bandwidth or available resource blocks are current indications or average values ​​over a certain period of time.

[0224] Aspect 19: The method according to any one of Aspects 1 to 18, wherein conveying the first message instructing the business management configuration of the autonomous vehicle includes sending or receiving the first message.

[0225] Aspect 20: The method according to any one of aspects 1 to 19, wherein communicating the one or more additional messages with the set of one or more autonomous vehicle UEs includes sending or receiving the one or more additional messages with the set of one or more autonomous vehicle UEs.

[0226] Aspect 21: A first network entity for wireless communication, the first network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the first network entity to perform a method according to any one of aspects 1 to 20.

[0227] Aspect 22: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 1 to 20.

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

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

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

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

[0232] 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 device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

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

[0235] 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".

[0236] 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".

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

[0238] 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 reference numeral to differentiate them. If only the first reference numeral is used in the description, 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.

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

[0240] 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 network entity, the first network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the first network entity to: A first message is conveyed, at least in part, based on the vehicle traffic throughput level of the first network entity, the second network entity, or both meeting a vehicle traffic congestion level threshold, indicating an autonomous vehicle service management configuration that indicates one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipment (UEs). as well as One or more additional messages are conveyed based on one or more parameters of the autonomous vehicle service management configuration and the set of one or more autonomous vehicle UEs.

2. The first network entity of claim 1, wherein the vehicle traffic throughput level of the first network entity is at least partially based on the communication resource congestion level, and the one or more processors are individually or jointly capable of further operating to execute the code to enable the first network entity to: The first message, which indicates the service management configuration of the autonomous vehicle, is conveyed at least in part based on the fact that the communication resource congestion level of the first network entity, the second network entity, or both meets a communication resource congestion level threshold.

3. The first network entity according to claim 1, wherein the one or more parameters of the autonomous vehicle service management configuration include an indication regarding delaying the handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity or performing an early handover between the first network entity and the second network entity, wherein the indication regarding delaying the handover or performing the early handover is at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying the vehicle service congestion level threshold.

4. The first network entity of claim 3, wherein the indication regarding delaying the handover or performing the early handover further indicates the time period associated with the delayed handover or the early handover and the location associated with the delayed handover or the early handover.

5. The first network entity of claim 3, wherein the one or more processors are individually or jointly capable of further operating to execute the code thereby enabling the first network entity to: The autonomous vehicle UE receives an instruction from one or more autonomous vehicle UEs in the set regarding whether the autonomous vehicle UE will delay the handover between the first network entity and the second network entity or perform the early handover between the first network entity and the second network entity, wherein the autonomous vehicle service management configuration is based at least in part on the instruction from the autonomous vehicle UE.

6. The first network entity of claim 3, wherein the one or more processors are individually or jointly further operable to execute the code thereby enabling the first network entity to: A signal is conveyed to indicate that at least one autonomous vehicle UE in the set of one or more autonomous vehicle UEs will switch between the first network entity and the second network entity, wherein the first message is conveyed at least in part based on the signal.

7. The first network entity of claim 1, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first bandwidth allocation for the first network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, a second bandwidth allocation for the second network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, or both, and wherein the second bandwidth allocation is different from the first bandwidth allocation.

8. The first network entity of claim 7, wherein the one or more processors are individually or jointly further operable to execute the code thereby enabling the first network entity to: The second message instructing the autonomous vehicle service management configuration is received from the service management server based at least in part on the vehicle service throughput level of the first network entity, the second network entity, or both.

9. The first network entity of claim 7, wherein the one or more processors are individually or jointly further operable to execute the code thereby enabling the first network entity to: Control signaling is sent based at least in part on bandwidth allocation calculations, and the control signaling instructs the second network entity to use the second bandwidth allocation.

10. The first network entity of claim 9, wherein the one or more processors are individually or jointly further operable to execute the code thereby enabling the first network entity to: The second control signaling is sent at least in part based on the interference level associated with the first bandwidth allocation, and the second control signaling instructs the second network entity to use the second bandwidth allocation.

11. The first network entity of claim 1, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first transmit power level for the first network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, or both, and wherein the second transmit power level is different from the first transmit power level.

12. The first network entity of claim 11, wherein, based at least in part on the fact that the vehicle traffic throughput level of the first network entity satisfies the vehicle traffic congestion level threshold, the first transmission power level of the first network entity is greater than or less than the second transmission power level of the second network entity.

13. The first network entity of claim 1, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a multiple-input multiple-output (MIMO) beamforming space for the set of autonomous vehicle UEs connected to the first network entity, the second network entity, or both, the MIMO beamforming space indicating a wireless channel or beamforming direction that the first network entity, the second network entity, or both should avoid for communicating with the autonomous vehicle UE.

14. The first network entity of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code thereby causing the first network entity to: The second message instructing the autonomous vehicle service management configuration is received from the server based at least in part on the fact that the vehicle service throughput levels of both the first network entity and the second network entity meet the vehicle service congestion level threshold.

15. The first network entity of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code thereby enabling the first network entity to: At least in part, based on the fact that the vehicle traffic throughput level of the first network entity meets the vehicle traffic congestion level threshold, an additional message indicating bandwidth allocation, transmission power level, beamforming configuration, or any combination thereof is sent to the server.

16. The first network entity of claim 1, wherein the one or more parameters of the autonomous vehicle service management configuration further indicate: the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both; an indication of a resource block in a set of bandwidth or resource blocks used by the first network entity, the second network entity, or both; an indication of available bandwidth or available resource blocks; a district identifier of a subset of the set of one or more autonomous vehicle UEs served by the first network entity, the second network entity, or both; an indication of channel busy rate; or any combination thereof.

17. The first network entity of claim 16, wherein the one or more parameters of the autonomous vehicle service management configuration indicate the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both, and wherein the indication of the number of autonomous vehicle UEs being served by the first network entity, the second network entity, or both is a current indication or for a certain time period.

18. The first network entity of claim 16, wherein the one or more parameters of the autonomous vehicle service management configuration include: The indication of the bandwidth or resource blocks in the resource block set used by the first network entity, the second network entity, or both, and the indication of available bandwidth or available resource blocks, wherein both the indication of the bandwidth or resource blocks in the resource block set used by the first network entity, the second network entity, or both and the indication of available bandwidth or available resource blocks are current indications or average values ​​over a certain period of time.

19. The first network entity according to claim 1, wherein, In order to convey the first message instructing the autonomous vehicle's business management configuration, the one or more processors may individually or jointly operate further to execute the code, thereby enabling the first network entity to send or receive the first message.

20. The first network entity according to claim 1, wherein, In order to communicate the one or more additional messages to the set of one or more autonomous vehicle UEs, the one or more processors may individually or jointly operate further to execute the code so that the first network entity sends or receives the one or more additional messages to the set of one or more autonomous vehicle UEs.

21. A method for wireless communication by a first network entity, the method comprising: A first message instructing an autonomous vehicle service management configuration is conveyed at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying a vehicle service congestion level threshold. The autonomous vehicle service management configuration instructs one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipment (UEs). as well as One or more additional messages are conveyed based on one or more parameters of the autonomous vehicle service management configuration and the set of one or more autonomous vehicle UEs.

22. The method of claim 21, wherein the one or more parameters of the autonomous vehicle service management configuration include an indication regarding delaying the handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity or performing an early handover between the first network entity and the second network entity, wherein the indication regarding delaying the handover or performing the early handover is at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying the vehicle service congestion level threshold.

23. The method of claim 21, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first bandwidth allocation for the first network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, a second bandwidth allocation for the second network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, or both, and wherein the second bandwidth allocation is different from the first bandwidth allocation.

24. The method of claim 21, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first transmit power level for the first network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, or both, and wherein the second transmit power level is different from the first transmit power level.

25. A first network entity for wireless communication, the first network entity comprising: The component is used to: convey a first message indicating an autonomous vehicle service management configuration based at least in part on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying a vehicle service congestion level threshold, the autonomous vehicle service management configuration indicating one or more parameters for coordinating wireless communications between the first network entity and the second network entity and a set of one or more autonomous vehicle user equipment (UEs). and The component is used to convey one or more additional messages to the set of one or more autonomous vehicle UEs based on one or more parameters of the autonomous vehicle business management configuration.

26. The first network entity of claim 25, wherein the one or more parameters of the autonomous vehicle service management configuration include an indication to delay the handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity or to perform an early handover between the first network entity and the second network entity, wherein the indication to delay the handover or to perform the early handover is at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying the vehicle service congestion level threshold.

27. The first network entity of claim 25, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first bandwidth allocation for the first network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, a second bandwidth allocation for the second network entity to perform the wireless communication with the set of one or more autonomous vehicle UEs, or both, and wherein the second bandwidth allocation is different from the first bandwidth allocation.

28. The first network entity of claim 25, wherein the one or more parameters of the autonomous vehicle service management configuration indicate a first transmit power level for the first network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, a second transmit power level for the second network entity to wirelessly communicate with the set of one or more autonomous vehicle UEs, or both, and wherein the second transmit power level is different from the first transmit power level.

29. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable individually or collectively by one or more processors to: A first message instructing an autonomous vehicle service management configuration is conveyed, at least in part, based on the vehicle traffic throughput levels of a first network entity, a second network entity, or both meeting a vehicle traffic congestion level threshold. This autonomous vehicle service management configuration indicates one or more parameters for coordinating wireless communications between the first and second network entities and a set of one or more autonomous vehicle user equipment (UEs). One or more additional messages are conveyed based on one or more parameters of the autonomous vehicle service management configuration and the set of one or more autonomous vehicle UEs.

30. The non-transitory computer-readable medium of claim 29, wherein the one or more parameters of the autonomous vehicle service management configuration include an indication regarding delaying or performing an early handover of one or more autonomous vehicle UEs in the set between the first network entity and the second network entity, wherein the indication regarding delaying the handover or performing the early handover is at least in part based on the vehicle service throughput level of the first network entity, the second network entity, or both satisfying the vehicle service congestion level threshold.

Images