Optimized Vehicle-to-Everything (V2X) Messaging

Abstract

Systems and techniques are described for providing optimized vehicle-to-everything (V2X) safety messages via a wide area network (Uu) interface. A method for wireless communication can include receiving, by a network device, one or more first messages from one or more vehicles. Each of the first messages includes vehicle information associated with each vehicle. The method can include determining, by the network device, one or more receiving vehicles with respect to one or more second messages based on at least a portion of the vehicle information from the first messages and characteristics associated with each receiving vehicle. The method can include transmitting, by the network device, the second messages to the receiving vehicles.

Description

Technical Field

[0001] This disclosure generally relates to network communication. For example, aspects of this disclosure relate to providing optimized vehicle-to-everything (V2X) messaging.

Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system can employ a multiple access technology that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multi-connectivity techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An exemplary telecommunications standard is the 5th Generation (5G) New Radio (NR). 5G NR is part of the continuous mobile broadband evolution published by the Third Generation Partnership Project (3GPP™) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Aspects of wireless communication may include device-to-device communication such as vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, and / or device-to-device (D2D) communication. Further improvements are needed for V2X, V2V, and / or D2D technologies. These improvements may also be applicable to other multi-connectivity techniques and the telecommunications standards that employ these techniques. SUMMARY OF THE INVENTION

[0004] The following presents a simplified overview of one or more aspects disclosed in this specification. Accordingly, the following overview should not be regarded as an extensive overview of all contemplated aspects, nor should the following overview be regarded as identifying key or important elements of all contemplated aspects or as delimiting the scope of any particular aspect. Thus, the sole purpose of the following overview is to present, in a simplified form, certain concepts related to one or more aspects of the mechanisms disclosed herein prior to the detailed description presented below.

[0005] Systems, apparatuses, methods, and computer-readable media for providing optimized messaging over a wide area network (e.g., Uu) interface are disclosed. According to at least one example, a method for wireless communication in a network device includes receiving, at the network device, from one or more vehicles remote from the network device, one or more first messages, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles; determining, at the network device, one or more receiving vehicles for one or more second messages based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective ones of the one or more receiving vehicles, the one or more receiving vehicles being remote from the network device; and transmitting, at the network device, the one or more second messages to the one or more receiving vehicles.

[0006] In another example, there is provided an apparatus for wireless communication that includes at least one memory (configured to store data such as, for example, virtual content data, one or more images) and at least one processor coupled to the at least one memory (e.g., implemented within a circuit). The at least one processor is configured to receive, from one or more vehicles remote from the apparatus, one or more first messages, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles, determine, based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective receiving vehicles of the one or more receiving vehicles, one or more receiving vehicles remote from the apparatus for one or more second messages, and output one or more second messages for transmission to the one or more receiving vehicles.

[0007] In another example, there is provided a non-transitory computer-readable medium of a network device storing instructions that, when executed by one or more processors, cause the one or more processors to receive, from one or more vehicles remote from the network device, one or more first messages, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles, determine, based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective receiving vehicles of the one or more receiving vehicles, one or more receiving vehicles remote from the network device for one or more second messages, and output one or more second messages for transmission to the one or more receiving vehicles.

[0008] In another example, an apparatus for wireless communication is provided. The apparatus includes means for receiving one or more first messages from one or more vehicles, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles remote from the apparatus; means for determining one or more receiving vehicles, remote from the apparatus, for one or more second messages based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective ones of the one or more receiving vehicles; and means for transmitting the one or more second messages to the one or more receiving vehicles.

[0009] In some aspects, the apparatus is by, or is part of, a network device (e.g., a multi-access edge computing (MEC) device, a gNodeB (gNB), an evolved NodeB (eNB), a location server such as a location management function (LMF), or a part thereof), or a component or system of a network device (e.g., a chipset). In some cases, the apparatus may be a vehicle (e.g., an automobile, a truck, etc., or a component or system of an automobile, a truck, etc.), a mobile device (e.g., a mobile phone or a so-called "smartphone" or other mobile device), a wearable device, an extended reality device (e.g., a virtual reality (VR) device, an augmented reality (AR) device, or a mixed reality (MR) device), a personal computer, a laptop computer, a server computer, a robotic device, or other device, or a part thereof. In some aspects, the apparatus includes radio detection and ranging (radar) for capturing radio frequency (RF) signals. In some aspects, the apparatus includes one or more light detection and ranging (LIDAR) sensors, radar sensors, or other light-based sensors for capturing other light-based (e.g., optical frequency) signals. In some aspects, the apparatus includes one camera or a plurality of cameras for capturing one or more images. In some aspects, the apparatus further includes a display for displaying one or more images, notifications, and / or other displayable data. In some aspects, the apparatus described above can include one or more sensors that can be used to determine the location of the apparatus, the state of the apparatus (e.g., temperature, humidity level, and / or other states), and / or for other purposes.

[0010] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to the entire specification of this patent, any or all of the drawings, and the appropriate portions of each claim.

[0011] Other objects and advantages related to the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and the detailed description.

[0012] The accompanying drawings are presented to assist in the description of various embodiments of the present disclosure and are provided only for purposes of illustration of the embodiments and not limitation.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2A

Figure 2B

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7A

Figure 7B

Figure 7C

Figure 7D

Figure 8

Figure 9A

Figure 9B

Figure 10

Figure 11

Figure 12

Figure 13

Figure 13

Figure 14

Figure 15

Figure 15

Figure 16

Figure 16

Figure 17

Figure 18

[0014] Certain aspects of the present disclosure are provided below for purposes of illustration. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure are not described in detail or are omitted so as not to obscure relevant details of the present disclosure. As will be apparent to those skilled in the art, some of the aspects described herein may be applied independently, and some of them may be applied in combination. In the following description, specific details are set forth for purposes of explanation to provide a thorough understanding of the aspects of the present application. However, it will be apparent that the various aspects may be practiced without these specific details. The figures and the description are not intended to be limiting.

[0015] The following description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of the exemplary embodiments provides those skilled in the art with an explanation that enables the exemplary embodiments to be implemented. It should be understood that various changes may be made to the functions and configurations of the elements without departing from the spirit and scope of the present application as set forth in the appended claims.

[0016] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” should not necessarily be construed as preferred or advantageous over other aspects. Similarly, the term “aspect of the present disclosure” does not necessarily require that all aspects of the present disclosure include the discussed feature, advantage, or mode of operation.

[0017] Wireless communication systems have been deployed to provide various telecommunications services, including, among other things, telephony, video, data, messaging, and broadcast. Wireless communication systems have evolved through various generations. The 5G mobile standard requires, among other improvements, higher data transfer speeds, a greater number of connections, and better coverage. The 5G standard (also referred to as “New Radio” or “NR”) is designed to provide a data rate of tens of megabits per second to each of tens of thousands of users according to the Next Generation Mobile Networks Alliance.

[0018] A vehicle is an example of a system that may include wireless communication capabilities. For example, a vehicle (e.g., especially an automobile, autonomous vehicle, aircraft, ship) can communicate with other vehicles and / or other devices having wireless communication capabilities. A wireless vehicle communication system includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-pedestrian (V2P) communication, all of which are collectively referred to as vehicle-to-everything (V2X) communication. V2X communication is a vehicle communication system that supports the wireless transmission of information from a vehicle to other entities (e.g., other vehicles, pedestrians with smartphones, and / or other traffic infrastructure) located within a transportation system that can affect that vehicle. The main purpose of V2X technology is to improve road safety, fuel savings, and traffic efficiency.

[0019] In a V2X communication system, information is transmitted from vehicle sensors (and other sources) through a wireless link so that the information can be communicated to other vehicles, pedestrians, and / or traffic infrastructure. By sharing this information with other vehicles, V2X technology helps improve the awareness of vehicles (and drivers) regarding potential hazards and reduce collisions with other vehicles and entities. Additionally, V2X technology improves traffic efficiency by providing traffic alerts regarding potential future road hazards and obstacles to vehicles so that the vehicles can select alternative traffic routes.

[0020] As described above, V2X technology includes V2V communication, which can also be referred to as peer-to-peer communication. V2V communication enables vehicles to directly wirelessly communicate with each other while on the road. Through V2V communication, a vehicle can obtain situation awareness by receiving information from other vehicles regarding potential future road hazards (e.g., unexpected approaching vehicles, accidents, and road conditions).

[0021] The IEEE 802.11p standard supports a dedicated short-range communication (DSRC) interface for V2X wireless communication. The features of the IEEE 802.11p-based DSRC interface include low latency and the use of the unlicensed 5.9 gigahertz (GHz) frequency band. However, the IEEE 802.11p-based DSRC interface has the drawback of having a short range (e.g., less than about 1 kilometer (km)).

[0022] Cellular V2X (C-V2X) has been adopted as an alternative to the use of the IEEE 802.11p-based DSRC interface for wireless communication. The 5G Automotive Association (5GAA) supports the use of C-V2X technology. In some cases, the C-V2X technology uses Long-Term Evolution (LTE) as the underlying technology, and the C-V2X function is based on LTE technology. C-V2X includes multiple operating modes. One of the operating modes enables direct wireless communication between vehicles via the LTE sidelink PC5 interface. Similar to the IEEE 802.11p-based DSRC interface, the LTE C-V2X sidelink PC5 interface operates in the 5.9 GHz frequency band. The LTE C-V2X sidelink PC5 interface and the DSRC interface also have the drawback of having a short range (e.g., less than about 1 km).

[0023] Both the IEEE 802.11p-based DSRC interface and the LTE C-V2X side-link PC5 interface have the drawback that their ranges are limited (e.g., to about 1 km), so these wireless technologies do not enable wireless exchange of information between vehicles located far apart beyond the limited range (e.g., more than 1 km apart). In some cases, for example, when at least one of the vehicles is traveling at high speed, in order to prevent collisions, vehicles may need to receive information such as a do not pass warning (DNPW) from each other at a distance of more than 1 km. Therefore, an improved V2X wireless technology that enables longer-range transmission of information is needed.

[0024] In this specification, systems, devices, processes (also called methods), and computer-readable media (collectively referred to as "systems and techniques") are provided for optimizing vehicle situation awareness, such as awareness of potential road hazards (e.g., unexpected approaching vehicles, accidents, and road conditions) that may occur in the future, by effectively increasing the range of information exchange between vehicles. The systems and techniques provide the ability for vehicles and / or other devices to receive information messages from each other even when the vehicles and / or other devices are located far apart from each other beyond the limited range of the V2X wireless technology used for V2X communication by the vehicles and / or other devices (e.g., more than 1 km apart from each other). The systems and techniques provide the ability for vehicles and / or other devices to become aware of unexpected potential road hazards not within their field of view, caused, for example, by obstacles (e.g., interfering vehicles, structures, and / or objects) within their field of view. Therefore, the systems and techniques can provide a see-through function to vehicles and / or other devices (e.g., essentially, "seeing through" obstacles by becoming aware of road hazards that are blocked).

[0025] The disclosed systems and techniques employ the use of network devices that operate as intelligent relays for messages transmitted between vehicles. The network devices have the advantage of providing low latency along with a high range of transmission (e.g., a transmission range of over 1 km). In some examples, a multi-access edge computing (MEC) device (e.g., a 5G MEC device) can be employed as the network device. In some cases, the network device (e.g., MEC) can be collocated with a cellular base station (e.g., a base station such as a gNodeB (gNB), evolved NodeB (eNB), etc. for 3G, 4G, 5G, etc.) or a portion of a cellular base station (e.g., one or more of a central unit (CU), distributed unit (DU), radio unit (RU), quasi-real-time (quasi-RT) RAN Intelligent Controller (RIC), or non-real-time (non-RT) RIC, which will be described in more detail below). The wide area network (Uu) interface of the network entity (e.g., the base station or a portion thereof) can be utilized as the air interface for transmissions between the vehicle and the network device (e.g., MEC). The range of the Uu interface is higher than the ranges of C-V2X and DSRC. For example, using the Uu interface, the network entity (e.g., the base station or a portion thereof) can have a transmission range of at least several kilometers (kms).

[0026] In some aspects, a network device can receive one or more information messages (e.g., vehicle-based messages) (e.g., a first information message from a first vehicle, a second information message from a second vehicle, etc.) from one or more vehicles. Information messages from vehicles can include information or characteristics related to the vehicle (e.g., the vehicle's location, location accuracy, vehicle speed, direction in which the vehicle is traveling, and / or other information related to the vehicle), traffic conditions (e.g., low-speed traffic and / or congested traffic, high-speed traffic, information related to an accident, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., an emergency message, a non-emergency or "normal" message), road topology (line-of-sight (LOS) or non-LOS (NLOS), etc.), any combination of these, and / or other information. In some examples, the information message can also include information regarding the preferences of the vehicle receiving the information message from another particular vehicle. In some cases, the information message can include the current capabilities of the vehicle, such as the vehicle's processing capabilities, the vehicle's thermal state (which can affect the vehicle's ability to process data), and the vehicle's health state. In some implementations, the information message can include specific use cases or safety warnings, such as a do not pass warning (DNPW) or a forward collision warning (FCW), related to the current state of the vehicle. In some examples, the information message can be in the form of a standard basic safety message (BSM), a cooperative awareness message (CAM), a sensor data sharing message (SDSM), and / or other formats.

[0027] After a network device receives one or more information messages from one or more vehicles, the network device uses the information contained in the information message(s) together with other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or scenes, weather conditions, traffic conditions, etc.) to determine which other vehicles and / or other devices (e.g., pedestrian devices / UEs such as mobile phones, network-connected infrastructure devices such as network-connected traffic lights) currently located within the transportation system (including vehicles and other V2X-capable devices within the communication range of the network device) will send a response message (or response messages) containing the information from the one or more vehicles from which the information message was received. The vehicles and / or other devices determined to receive the response message(s) are referred to herein as the receiving vehicle or receiving device. Although an example using the receiving vehicle is described herein as an example for the description of the device determined to receive the response message, the techniques described herein are applicable to other types of receiving devices (e.g., receiving RSU, receiving pedestrian device / UE, receiving network-connected infrastructure device, etc.).

[0028] In some embodiments, the response message sent to the receiving vehicle or other device may include the information message received by the network device from a particular vehicle. For example, the network device can forward the information message received from the vehicle to the receiving vehicle. In some examples, other information used by the network entity to determine which other vehicles and / or other devices will send the response message includes characteristics of other vehicles, location information associated with the location of other vehicles or scenes, current weather conditions, traffic conditions, sunlight conditions (e.g., daily sunlight hour conditions), road topology conditions, obstacle conditions, any combination thereof, and / or other information related to some or all of the vehicles located within the transportation system. In some examples, the other information may include characteristics of a particular receiving vehicle, such as quality of service (QoS) associated with the receiving vehicle, performance parameters (e.g., thermal characteristics or requirements of the receiving vehicle, processing capabilities of the receiving vehicle, health status of the receiving vehicle, etc.).

[0029] In some embodiments, the network device can use the information contained in the information message from the vehicle, together with other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or scenes, weather conditions, traffic conditions, etc.), to generate a dynamic neighbor list (also referred to as a local dynamic map (LDM) or a dynamic surrounding map) for each of the receiving vehicles. The dynamic neighbor list may also be referred to as a local dynamic map (LDM). For example, each dynamic neighbor list may include a listing of all vehicles located within a particular predetermined distance (or radius of distance) from the corresponding receiving vehicle. In some cases, each dynamic neighbor list may include a mapping that includes all vehicles located within a particular predetermined distance (or radius of distance) from the corresponding receiving vehicle and includes roads and terrain topology. In some examples, each receiving vehicle can use the information contained in the response message, together with other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or scenes, weather conditions, traffic conditions, etc.), to generate a dynamic neighbor list for itself.

[0030] In some cases, the network device uses the information included in the information message from the vehicle, the QoS associated with each of the receiving vehicles, the performance parameters of each of the receiving vehicles, and / or other information or characteristics described above to determine which vehicle can be the receiving vehicle that should send one or more response messages and / or when to send one or more response messages to the receiving vehicle and / or other devices. In some examples, the QoS is the level of service associated with the receiving vehicle, which is related to the level of priority at which the receiving vehicle must receive the message. Thus, for example, a receiving vehicle with a high QoS will have a higher priority of receiving a response message earlier than a receiving vehicle with a low QoS. In some examples, the performance parameters may include an end-to-end latency threshold and / or an age-of-information threshold. The end-to-end latency threshold specifies a predetermined threshold amount of time between when the response message is sent and when the response message is received. The age-of-information threshold specifies a predetermined threshold amount of the age of the vehicle information (e.g., related to an amount of time or "freshness" or "staleness").

[0031] In some examples, the network device can determine to wait to send at least a portion of the response messages to the receiving vehicle and / or other devices in order to improve transmission efficiency (e.g., when not urgent, such as in a non-emergency situation). In such examples, the network device can bundle multiple response messages together and send them to the receiving vehicle and / or other devices simultaneously. In some cases, the network device uses the information included in the information message from the vehicle, other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or the scene, weather conditions, traffic conditions, etc.), the QoS associated with each of the receiving vehicles, and the performance parameters associated with each of the receiving vehicles to determine whether to bundle at least a portion of the response messages for transmission.

[0032] In some cases, the network device can send a response message to the receiving vehicle via a network entity such as a base station or a part thereof. In some examples, a gNodeB (gNB) or an evolved NodeB (eNB) can be employed for the network entity. As described above, the network device and the network entity can be co-located together (e.g., MEC is co-located with gNB or eNB), or alternatively, the network device and the network entity can be located remotely from each other (e.g., MEC is located remotely from gNB or eNB). In some techniques, the network entity can be used to determine whether to bundle some of the response messages for transmission.

[0033] Additional features of the present disclosure are described in more detail below.

[0034] As used herein, the terms "user equipment" (UE) and "network entity" are not intended to be specific to, or limited to, any particular radio access technology (RAT) unless otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.) used by a user to communicate via a wireless communication network, a wearable (e.g., a smartwatch, smart glasses, wearable ring, and / or extended reality (XR) device, e.g., a virtual reality (VR) headset, augmented reality (AR) headset or glasses, or a mixed reality (MR) headset), a vehicle (e.g., a car, motorcycle, bicycle, etc.), and / or an Internet of Things (IoT) device, etc. The UE may be mobile or (e.g., at a certain time) stationary and may communicate with a radio access network (RAN). The term "UE" as used herein may be interchangeably referred to as "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variations thereof. Generally, a UE can communicate with a core network via a RAN, and through the core network, the UE can be connected to an external network such as the Internet and to other UEs. Of course, other mechanisms for connecting to a core network and / or the Internet, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the IEEE802.11 communication standard, etc.), are also possible for the UE.

[0035] The network entity can be implemented in an integrated or monolithic base station architecture or, alternatively, in a non-integrated base station architecture and can include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. A base station (e.g., an integrated / monolithic base station architecture or a non-integrated base station architecture) may operate according to one of a plurality of RATs that communicate with a UE, roadside units (RSUs), and / or other devices according to the deployed network and, alternatively, may be referred to as an access point (AP), a network node, a Node B (NB), an evolved Node B (eNB), a next-generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. The base station may be mainly used to support wireless access by a UE, including supporting a data connection, a voice connection, and / or a signaling connection for the supported UE. In some systems, the base station may provide an edge node signaling function, while in other systems, it may provide additional control and / or network management functions. A communication link through which a UE can send a signal to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send a signal to the UE is called a downlink (DL), or a forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forward traffic channel, etc.). The term traffic channel (TCH), as used herein, can refer to any of an uplink, a reverse or downlink, and / or a forward traffic channel.

[0036] The term "network entity" or "base station" (e.g., having a centralized / monolithic base station architecture or a non-centralized base station architecture) can refer to a single physical TRP, or multiple physical TRPs that may or may not be collocated. For example, when the term "network entity" or "base station" refers to a single physical TRP, that physical TRP can be an antenna of the base station corresponding to a cell (or some cell sectors) of the base station. When the term "network entity" or "base station" refers to multiple collocated physical TRPs, the physical TRPs can be an array of antennas of the base station (such as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRPs can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium), or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-collocated physical TRP can be a serving base station that receives measurement reports from a UE and neighboring base stations whose reference radio frequency (RF) signals (or simply "reference signals") the UE is measuring. Since a TRP is a point from which the base station transmits and receives wireless signals, references to transmissions from or receptions at the base station, as used herein, should be understood to refer to a particular TRP of the base station.

[0037] In some implementations that support UE positioning, a network entity or a base station may not support wireless access by the UE (e.g., may not support a data connection, a voice connection, and / or a signaling connection for the UE), but instead may send to the UE a reference signal to be measured by the UE and / or may receive and measure a signal transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when sending a signal to the UE) and / or a location measurement unit (e.g., when receiving and measuring a signal from the UE).

[0038] A roadside unit (RSU) is a device that can send and receive messages to and from one or more UEs, other RSUs, and / or base stations via a communication link or interface (e.g., a cellular-based sidelink or PC5 interface, an 802.11 or WiFi (trademark)-based dedicated short range communication (DSRC) interface, and / or other interfaces). Examples of messages that can be sent and received by an RSU include vehicle-to-everything (V2X) messages, which are described in more detail below. An RSU can be located in various transportation infrastructure systems, including roads, bridges, parking lots, toll plazas, and / or other infrastructure systems. In some examples, an RSU can facilitate communication between a UE (e.g., a vehicle, a pedestrian device, and / or other UE) and a transportation infrastructure system. In some implementations, an RSU can communicate with a server, a base station, and / or other systems that can perform a centralized management function.

[0039] The RSU can communicate with the communication system of the UE. For example, the intelligent transport system (ITS) of the UE (e.g., a vehicle and / or another UE) can be used to generate and sign a message for transmission to the RSU and to verify a message received from the RSU. The RSU can communicate with vehicles traveling along a road, bridge, or other infrastructure system (e.g., via a PC5 interface, a DSRC interface, etc.) to obtain traffic-related data (e.g., the time, speed, location of the vehicle, etc.). In some cases, in response to obtaining traffic-related data, the RSU can determine or estimate traffic congestion information (e.g., the start of traffic congestion, the end of traffic congestion, etc.), travel time, and / or other information about a specific location. In some examples, the RSU can communicate with other RSUs (e.g., via a PC5 interface, a DSRC interface, etc.) to determine traffic-related data. The RSU can transmit information (e.g., traffic congestion information, travel time information, and / or other information) to other vehicles, pedestrian UEs, and / or other UEs. For example, the RSU can broadcast or transmit information to any UE (e.g., a vehicle, a pedestrian UE, etc.) within the coverage range of the RSU.

[0040] A radio frequency signal or "RF signal" includes electromagnetic waves of a given frequency that transfer information through the space between a transmitter and a receiver. As used herein, a transmitter can transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of the RF signal through a multipath channel, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted along different paths between the transmitter and the receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" when the context makes it clear that the term "signal" refers to a wireless signal or an RF signal.

[0041] FIG. 1 is a diagram illustrating an example of a wireless communication system and an access network 100 in various aspects. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and a core network (e.g., 5GC) 190. The base station 102 may include a macro cell (high-power cellular base station) and / or a small cell (low-power cellular base station). The macro cell includes the base station. The small cell includes a femto cell, a pico cell, and a micro cell. In some aspects, the base station 102 may also be referred to as a “network entity” or a “network node”. One or more of the base stations 102 may be implemented in an integrated or monolithic base station architecture. Additionally, or alternatively, one or more of the base stations 102 may be implemented in a non-integrated base station architecture and may include one or more of a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a Near Real-Time (Near RT) RAN Intelligent Controller (RIC), or a Non-Real-Time (Non RT) RIC.

[0042] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through a backhaul link 132 (e.g., the S1 interface). The base station 102 configured for NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a backhaul link 184. In addition to other functions, the base station 102 can perform one or more of the following functions, namely, transfer of user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, setup and release of connections, load distribution, delivery of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), tracking of subscribers and devices, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate directly or indirectly with each other (e.g., through the EPC 160 or the core network 190) via a backhaul link 134 (e.g., the X2 interface). The backhaul link 134 can be wired or wireless.

[0043] The base station 102 can wirelessly communicate with the UE 104. Each of the base stations 102 can provide communication coverage regarding its respective geographical coverage area 110. There may be overlapping geographical coverage areas 110. In one aspect, one or more cells can be supported by the base stations 102 within each coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., via several frequency resources such as those referred to as carrier frequency, component carrier, carrier, band, etc.), and may be associated with an identifier (e.g., physical cell identifier (PCI), virtual cell identifier (VCI), cell global identifier (CGI)) for distinguishing cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that can provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may, depending on the context, refer to one or both of the logical communication entity and the base station that supports it. Additionally, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographical coverage area (e.g., sector) of a base station as long as a carrier frequency is detected and can be used for communication within a portion.

[0044] The geographical coverage area 110 of the neighboring macro cell base station 102 may partially overlap (e.g., in the handover area), and some of the geographical coverage areas 110 may be significantly overlapped by a larger geographical coverage area 110. For example, the small cell base station 102' may have a coverage area 110' that significantly overlaps with the coverage area 110 of one or more macro cell base stations 102. A network including both small cell base stations and macro cell base stations may be known as a heterogeneous network. The heterogeneous network may also include home eNBs (HeNBs) that may provide services to a limited group known as a closed subscriber group (CSG).

[0045] The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also referred to as the reverse link) transmission from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as the forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more frequencies (e.g., carriers or subcarriers). The base station 102 / UE 104 can use a spectrum with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.), which is allocated in a carrier aggregation of up to Yx MHz (x component carriers) used for transmission in each direction. Those carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric for DL and UL (e.g., a larger or smaller number of carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be called a secondary cell (SCell).

[0046] Specific UE104s may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE802.11 standard, LTE, or NR.

[0047] The wireless communication system may further include a Wi-Fi or WLAN access point (AP) 150 that communicates with Wi-Fi or WLAN stations (STAs) 152 via a communication link 154 in an unlicensed frequency spectrum (e.g., 5 gigahertz (GHz)). When communicating in the unlicensed frequency spectrum, the WLAN STA152 and / or the WLAN AP150 may perform a clear channel assessment (CCA) or a listen before talk (LBT) procedure before communicating to determine whether the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UE104s, base stations 102, APs 150, etc. using the ultra-wideband (UWB) spectrum. The UWB spectrum may span from 3.1 GHz to 10.5 GHz.

[0048] The small cell base station 102’ can operate in the licensed frequency spectrum and / or the unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell base station 102’ can utilize LTE technology or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102’ adopting LTE and / or 5G in the unlicensed frequency spectrum can expand the coverage to the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be called NR-U. LTE in the unlicensed spectrum may be called LTE-U, licensed assisted access (LAA), or MulteFire.

[0049] The wireless communication system 100 may further include an mmW base station 180 that communicates with the UE 182 and can operate at millimeter wave (mmW) frequencies and / or near mmW. The mmW base station 180 can be implemented in an integrated or monolithic base station architecture or, alternatively, in a non-integrated base station architecture (including, for example, one or more of a CU, DU, RU, near RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band can be called millimeter waves. Near mmW can drop down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also called centimeter waves. Communication using the mmW and / or near mmW radio frequency band has high path loss and a relatively short distance. The mmW base station 180 and the UE 182 can utilize beamforming (transmission and / or reception) via the mmW communication link 184 to compensate for the extremely high path loss and short distance. Further, in an alternative configuration, it will be understood that one or more base stations 102 can also perform transmission using mmW or near mmW and beamforming. Accordingly, it will be understood that the above examples are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0050] The device may use beamforming to transmit and receive communications. For example, FIG. 1 shows that base station 180 may transmit a beamformed signal to UE 104 in one or more transmission directions 182’. UE 104 may receive the beamformed signal from base station 180 in one or more reception directions 182’’. UE 104 may also transmit a beamformed signal to base station 180 in one or more transmission directions. Base station 180 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the best reception and transmission directions for each of base station 180 / UE 104. The transmission direction and reception direction for base station 180 may or may not be the same. The transmission direction and reception direction for UE 104 may or may not be the same. Although a beamformed signal is shown between UE 104 and base stations 102 / 180, the beamforming manner may similarly be applied by UE 104 or RSU 107 to communicate with another UE 104 or RSU 107, for example, based on sidelink communications such as V2X or D2D communications.

[0051] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 can communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, and the Serving Gateway 166 itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides functions such as the allocation of the UE's IP address. The PDN Gateway 172 and the BM-SC 170 are connected to an IP service 176. The IP service 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 can provide functions related to the provisioning and delivery of MBMS user services. The BM-SC 170 can serve as an entry point for the MBMS transmission of content providers, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and can be used to schedule MBMS transmissions.The MBMS gateway 168 can be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a specific service, and can be involved in session management (start / stop) and collection of charging information related to eMBMS.

[0052] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 can communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides functions such as allocation of the UE's IP address. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services.

[0053] Base station 102 may also be referred to by gNB, Node B, evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small cooking appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional device. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be called a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0054] Some wireless communication networks can communicate from vehicle - based communication devices, including vehicle - to - vehicle (V2V), vehicle - to - infrastructure (V2I) (e.g., from a vehicle - based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle - to - network (V2N) (e.g., from a vehicle - based communication device to one or more network nodes such as a base station), cellular - vehicle - to - everything (C - V2X), enhanced V2X (e - V2X), and / or combinations thereof, and / or can communicate with other devices, which can be collectively referred to as vehicle - to - everything (V2X) communication. Referring back to FIG. 1, in some aspects, UE104, e.g., a transmitting vehicle user equipment (VUE) or other UE, can be configured to directly transmit a message to another UE104. The communication can be based on other device - to - device (D2D) communication such as V2X or proximity services (ProSe). Communication based on V2X and / or D2D can also be transmitted and received by other transceiver devices such as RSU107. The mode of communication can be based on PC5 or sidelink communication, as described, for example, in relation to the example of FIG. 2A. The following description may provide examples of V2X / D2D communication related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE - A, CDMA, GSM, and other wireless technologies.

[0055] Figure 2A is a block diagram 200 of a first wireless communication device 210 communicating with a second wireless communication device 250 via, for example, V2V / V2X / other communication. The device 210 may comprise a receiving device, for example, a transmitting device that communicates with the device 250. The communication may be based on, for example, sidelink. The transmitting device 210 may comprise a UE, an RSU, etc. The receiving device may comprise a UE, an RSU, etc. Packets may be provided to a controller / processor 275 that implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.

[0056] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 processes the mapping to a signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream is then mapped to OFDM subcarriers and multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then an Inverse Fast Fourier Transform (IFFT) is used to combine them together to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate a plurality of spatial streams. The channel estimates from the channel estimator 274 can be used to determine the encoding and modulation scheme and for spatial processing. The channel estimates can be derived from the reference signals transmitted by the device 250 and / or channel state feedback. Each spatial stream can then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX can modulate an RF carrier with its respective spatial stream for transmission.

[0057] In device 250, each receiver 254RX receives signals via its respective antenna 252 of the receiver. Each receiver 254RX recovers the information modulated on the RF carrier and provides that information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functions associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial stream intended for device 250. If multiple spatial streams are intended for device 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by device 210. These soft decisions may be based on the channel estimates calculated by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by device 210 on the physical channel. Next, the data and control signals are provided to the controller / processor 259, which implements the functions of layer 3 and layer 2.

[0058] The controller / processor 259 may be associated with a memory 260 that stores program code and data. The memory 260 may be referred to as a computer-readable medium. The controller / processor 259 may provide demultiplexing, packet reassembly, decoding, header decompression, and control signal processing between the transport channel and the logical channel. The controller / processor 259 is also involved in error detection using the ACK and / or NACK protocol to support HARQ operations.

[0059] Similar to the functions described in relation to the transmission by device 210, the controller / processor 259 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting, PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification), and RLC layer functions associated with transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs, and MAC layer functions associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0060] Channel estimates derived by the channel estimator 258 from reference signals or feedback transmitted by device 210 can be used by the TX processor 268 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 268 can be provided to different antennas 252 via separate transmitters 254TX. Each transmitter 254TX can modulate an RF carrier with its respective spatial stream for transmission.

[0061] Transmission is processed at device 210 in a manner similar to that described in relation to the receiver function at device 250. Each receiver 218RX receives signals via its respective antenna 220. Each receiver 218RX recovers the information modulated on the RF carrier and provides that information to the RX processor 270.

[0062] The controller / processor 275 may be associated with a memory 276 that stores program code and data. The memory 276 may be referred to as a computer-readable medium. The controller / processor 275 provides demultiplexing between a transport channel and a logical channel, packet reassembly, decoding, header decompression, and control signal processing. The controller / processor 275 is also involved in error detection using an ACK and / or NACK protocol to support HARQ operations.

[0063] At least one of the TX processor 268, RX processor 256, or controller / processor 259 of device 250, or TX 216, RX processor 270, or controller / processor 275 may be configured to perform the aspects described in connection with 298 or 299 of FIG. 1.

[0064] FIG. 2B is a diagram illustrating an example of a non-agglomerated base station 2200 architecture that may be employed by the disclosed system to provide vehicle-based messages (e.g., safety messages) optimized for an equipped vehicle (e.g., a V2X-capable vehicle) according to some examples. The deployment of a communication system such as a 5G NR system may be configured in multiple ways using various components or constituents. In a 5G NR system, or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network devices such as base stations (BS), or one or more units (or one or more constituents) implementing base station functions may be implemented in an agglomerated architecture or a non-agglomerated architecture. For example, a BS (e.g., Node B (NB), evolved NB (eNB), NR BS, 5G NB, AP, transmit receive point (TRP), or cell, etc.) may be implemented as an agglomerated base station (also known as a stand-alone BS or a monolithic BS) or a non-agglomerated base station.

[0065] The centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The non-centralized base station can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central units or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU can be implemented within the RAN node, and one or more DUs can be collocated with the CU or, alternatively, can be geographically or virtually distributed across one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0066] The operation or network design of the base station type can consider the aggregation characteristics of the base station functions. For example, the non-centralized base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Non-aggregation can include distributing functions across two or more units at various physical locations and virtually distributing the functions of at least one unit, which can enable flexibility in network design. The various units of the non-centralized base station, or the non-centralized RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0067] As described above, FIG. 2B shows a diagram illustrating the architecture of an exemplary non - centralized base station 2200. The architecture of the non - centralized base station 2200 may include one or more central units (CUs) 2210 that can communicate directly with the core network 2220 via a backhaul link or communicate indirectly with the core network 2220 through one or more non - centralized base station units (e.g., a near - real - time (near - RT) RAN intelligent controller (RIC) 2225 via an E2 link, or a non - real - time (non - RT) RIC 2215 associated with a service management and orchestration (SMO) framework 2205, or both). The CU 2210 can communicate with one or more distributed units (DUs) 2230 via respective mid - haul links such as an F1 interface. The DU 2230 can communicate with one or more radio units (RUs) 2240 via respective front - haul links. The RU 2240 can communicate with respective UEs 2220 via one or more RF access links. In some implementations, a UE 2220 can be served simultaneously by multiple RUs 2240.

[0068] Each of the units, namely, CU2210, DU2230, RU2240, and the quasi-RT RIC2225, non-RT RIC2215, and SMO framework 2205, may include one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired transmission medium or a wireless transmission medium, or may be coupled to such one or more interfaces. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of the units, may be configured to communicate with one or more of the other units via the transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, a unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), and the wireless interface is configured to receive signals from, transmit signals to, or both, one or more of the other units via a wireless transmission medium.

[0069] In some aspects, CU2210 can host one or more upper layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals with other control functions hosted by CU2210. CU2210 can be configured to process user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, CU2210 can be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface when implemented in an O-RAN configuration. CU2210 can be implemented to communicate with DU2230 as needed for network control and signaling.

[0070] The DU2230 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU2240s. In some aspects, the DU2230 can host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules related to forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least partially according to function splitting, such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU2230 can further host one or more lower PHY layers. Each layer (or module) can be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU2230 or control functions hosted by the CU2210.

[0071] The lower layer functions can be implemented by one or more RU2240s. In some deployments, the RU2240s controlled by the DU2230 can correspond to logical nodes that host RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on function splitting such as lower layer function splitting. In such an architecture, the RU(s) 2240 can be implemented to handle over the air (OTA) communication with one or more UE2220s. In some implementations, the real-time and non-real-time modes of control and user plane communication with the RU(s) 2240 can be controlled by the corresponding DU2230. In some scenarios, this configuration can enable the implementation of the DU(s) 2230 and CU2210 in a cloud-based RAN architecture such as a vRAN architecture.

[0072] The SMO framework 2205 can be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. In the case of non-virtualized network elements, the SMO framework 2205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as an O1 interface). In the case of virtualized network elements, the SMO framework 2205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 2290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CU2210, DU2230, RU2240, and quasi-RT RIC2225. In some implementations, the SMO framework 2205 can communicate with the hardware aspects of 4G RAN, such as the open eNB (O-eNB) 2211, via the O1 interface. Additionally, in some implementations, the SMO framework 2205 can communicate directly with one or more RU2240s via the O1 interface. The SMO framework 2205 can also include a non-RT RIC2215 configured to support the functions of the SMO framework 2205.

[0073] The non-RT RIC 2215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, an artificial intelligence / machine learning (AI / ML) workflow including model training and updating, or policy-based guidance of applications / features in the quasi-RT RIC 2225. The non-RT RIC 2215 may be coupled to the quasi-RT RIC 2225 or communicate with the quasi-RT RIC 2225 (such as via an A1 interface). The quasi-RT RIC 2225 may be configured to include a logical function that enables quasi-real-time control and optimization of RAN elements and resources via data collection and actions through one or more CU 2210, one or more DU 2230, or both, and an interface connecting the O-eNB to the quasi-RT RIC 2225 (such as via an E2 interface).

[0074] In some implementations, the non-RT RIC 2215 may receive parameters or external enrichment information from an external server to generate an AI / ML model deployed in the quasi-RT RIC 2225. Such information may be utilized by the quasi-RT RIC 2225 and may be received in the SMO framework 2205 or the non-RT RIC 2215 from a non-network data source or a network function. In some examples, the non-RT RIC 2215 or the quasi-RT RIC 2225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 2215 may monitor long-term trends and patterns in performance and employ an AI / ML model to execute corrective measures through the SMO framework 2205 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0075] Figure 3 shows examples of different communication mechanisms used by various UEs. In one example of sidelink communication, Figure 3 shows vehicles 304, 305, and RSU 303 communicating with each other using a PC5, DSRC, or other direct device-to-device signaling interface. Additionally, vehicles 304 and 305 may communicate with a base station 302 (shown as BS 302) using a network (Uu) interface. In some examples, base station 302 may include a gNB. Figure 3 also shows a user device 307 communicating with base station 302 using a network (Uu) interface. As described below, based on one or more characteristics or factors (e.g., temperature, humidity, etc.), functions may be transferred from a vehicle (e.g., vehicle 304) to a user device (e.g., user device 307). In one example for illustration, as shown in Figure 3, a V2X function may be transferred from vehicle 304 to user device 307, and then user device 307 may communicate with other vehicles (e.g., vehicle 305) via a PC5 interface (or other direct device-to-device interface such as a DSRC interface).

[0076] Figure 3 shows a specific number of vehicles (e.g., two vehicles 304 and 305) communicating with each other and / or communicating with RSU 303, BS 302, and / or user device 307, but the present disclosure is not limited thereto. For example, dozens or hundreds of such vehicles may communicate with each other and / or with RSU 303, BS 302, and / or user device 307. At any given time, each such vehicle, RSU 303, BS 302, and / or user device 307 may transmit various types of information as messages to other neighboring vehicles, such that each vehicle (e.g., vehicles 304 and / or 305), RSU 303, BS 302, and / or user device 307 may receive hundreds or thousands of messages per second from other neighboring vehicles, RSUs, base stations, and / or other UEs.

[0077] The PC5 interface is shown in Figure 3, although various UEs (e.g., vehicles, user devices, etc.) and RSU(s) can communicate directly using any suitable type of direct interface, such as an 802.11 DSRC interface, a Bluetooth™ interface, and / or other interfaces. For example, a vehicle can communicate with a user device via a direct communication interface (e.g., using PC5 and / or DSRC), a vehicle can communicate with another vehicle via a direct communication interface, a user device can communicate with another user device via a direct communication interface, a UE (e.g., a vehicle, a user device, etc.) can communicate with an RSU via a direct communication interface, and an RSU can communicate with another RSU via a direct communication interface, and so on.

[0078] FIG. 4 is a block diagram illustrating an example of a vehicle computing system 450 of a vehicle 404. The vehicle 404 can communicate with a network (e.g., an eNB, a gNB, a positioning beacon, a position measurement unit, and / or other network entities) via a Uu interface and can communicate with other UEs using V2X communication via a PC5 interface (or other direct device-to-device interface such as a DSRC interface). It is an example of a UE. As shown, the vehicle computing system 450 can include at least a power management system 451, a control system 452, an infotainment system 454, an intelligent transportation system (ITS) 455, one or more sensor systems 456, and a communication system 458. In some cases, the vehicle computing system 450 can include any type of processing device or system such as one or more central processing units (CPUs), digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), application processors (APs), graphics processing units (GPUs), vision processing units (VPUs), neural network signal processors (NSPs), microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems, or can be implemented using them.

[0079] The control system 452 can be configured to control one or more operations of the vehicle 404, the power management system 451, the computing system 450, the infotainment system 454, the ITS 455, and / or one or more other systems of the vehicle 404 (e.g., a braking system, a steering system, a safety system other than the ITS 455, a cabin system, and / or other systems). In some examples, the control system 452 can include one or more electronic control units (ECUs). The ECU can control one or more of the electronic systems or subsystems within the vehicle. Specific examples of ECUs that can be included as part of the control system 452 include, among others, an engine control module (ECM), a powertrain control module (PCM), a transmission control module (TCM), a brake control module (BCM), a central control module (CCM), and a central timing module (CTM). In some cases, the control system 452 can receive sensor signals from one or more sensor systems 456 and communicate with other systems of the vehicle computing system 450 to operate the vehicle 404.

[0080] The vehicle computing system 450 also includes a power management system 451. In some implementations, the power management system 451 can include a power management integrated circuit (PMIC), a standby battery, and / or other components. In some cases, other systems of the vehicle computing system 450 can include one or more PMICs, batteries, and / or other components. The power management system 451 can perform power management functions for the vehicle 404, such as managing the power supply for the computing system 450 and / or other parts of the vehicle. For example, the power management system 451 can provide a stable power supply, taking into account power fluctuations, for example, based on starting the vehicle's engine. In another example, the power management system 451 can perform thermal monitoring operations, such as by checking the ambient temperature and / or the transistor junction temperature. In another example, based on detecting a specific temperature level, the power management system 451 can perform certain functions, such as cooling specific components of the vehicle computing system 450 (such as the control system 452, for example, one or more ECUs) by a specific function, among others, such as a cooling system (such as one or more fans, an air conditioning system, etc.), or shutting off specific functions of the vehicle computing system 450 (such as restricting the infotainment system 454 by, for example, shutting off one or more displays, disconnecting from a wireless network, etc.).

[0081] The vehicle computing system 450 further includes a communication system 458. The communication system 458 can include both software components and hardware components for transmitting signals to a network (e.g., a gNB or other network entity via the Uu interface) and / or other UEs, and receiving signals from the network and / or other UEs (e.g., to another vehicle or UE via the PC5 interface, WiFi interface (e.g., DSRC), Bluetooth™ interface, and / or other wireless and / or wired interfaces). For example, the communication system 458 is configured to wirelessly transmit and receive information via any suitable wireless network (e.g., a 3G network, 4G network, 5G network, WiFi network, Bluetooth™ network, and / or other networks). The communication system 458 includes various components or devices used to perform wireless communication functions, including a subscriber identification module (referred to as a SIM or SIM card) 460 for a partner trademark manufacturer (OEM), a user SIM 462, and a modem 464. Although the vehicle computing system 450 is shown as having two SIMs and one modem, in some implementations, the computing system 450 can have any number of SIMs (e.g., one SIM or three or more SIMs) and any number of modems (e.g., one modem, two modems, or three or more modems).

[0082] A SIM is a device (e.g., an integrated circuit) that can securely store the international mobile subscriber identity (IMSI) number and related keys (e.g., encryption-decryption keys) of a specific subscriber or user. The IMSI and keys can be used to identify and authenticate the subscriber of a specific UE. The OEM SIM460 can be used by the communication system 458 to establish a wireless connection for vehicle-based operations, among other things, to perform an emergency call (eCall) function and to communicate with the vehicle manufacturer's communication system (e.g., for software updates). The OEM SIM460 can be important for the OEM SIM to support emergency services such as eCall for making emergency calls in the event of a car accident or other emergency. For example, eCall can include services that automatically call an emergency call number (e.g., "9-1-1" in the United States, "1-1-2" in Europe, etc.) in the case of a vehicle accident and transmit the location of the vehicle to emergency services such as the police and fire departments.

[0083] The user SIM 462 can be used by a communication system 458 to perform a wireless network access function to support a user data connection (for example, for performing services related to, among other things, calls, messaging, and infotainment). In some cases, the user's user device can be connected to the vehicle computing system 450 via an interface (for example, PC5, Bluetooth™, WiFI™ (for example, DSRC), universal serial bus (USB) port, and / or other wireless or wired interfaces). Once connected, the user device can transfer the wireless network access function from the user device to the vehicle's communication system 458, in which case the user device can stop performing the wireless network access function (for example, during the period when the communication system 458 is performing the wireless access function). The communication system 458 can start interacting with the base station and perform one or more wireless communication operations, among other operations, such as facilitating calls and transmitting and / or receiving data (for example, messaging, video, audio, etc.). In such a case, other components of the vehicle computing system 450 can be used to output the data received by the communication system 458. For example, an infotainment system 454 (described below) can display video received by the communication system 458 on one or more displays and / or output audio received by the communication system 458 using one or more speakers.

[0084] A modem is a device that modulates one or more carrier signals to encode digital information for transmission and demodulates the signal to decode the transmitted information. Modem 464 (and / or one or more other modems of communication system 458) can be used for data communication for OEM SIM 460 and / or user SIM 462. In some examples, modem 464 can include a 4G (or LTE) modem, and another modem (not shown) of communication system 458 can include a 5G (or NR) modem. In some examples, communication system 458 can include one or more Bluetooth (trademark) modems (e.g., for Bluetooth (trademark) Low Energy (BLE) or other types of Bluetooth communication), one or more WiFi (trademark) modems (e.g., for DSRC communication and / or other WiFi communication), a wideband modem (e.g., an ultra-wideband (UWB) modem), any combination thereof, and / or other types of modems.

[0085] In some cases, modem 464 (and / or one or more other modems of communication system 458) can be used to perform V2X communication (e.g., V2V communication with other vehicles, D2D communication with other devices, V2I communication with infrastructure systems, V2P communication with pedestrian UEs, etc.). In some examples, communication system 458 can include a V2X modem used to perform V2X communication (e.g., sidelink communication via a PC5 interface or a DSRC interface), in which case the V2X modem can be separate from one or more modems used for wireless network access functions (e.g., network communication via a network / Uu interface and / or sidelink communication other than V2X communication).

[0086] In some examples, the communication system 458 may be, or may include, a telematics control unit (TCU). In some implementations, the TCU can include a network access device (NAD) (which may also be referred to as a network control unit or NCU in some cases). The NAD can include a modem 464, any other modem not shown in FIG. 4, an OEM SIM 460, a user SIM 462, and / or other components used for wireless communication. In some examples, the communication system 458 can include a Global Navigation Satellite System (GNSS). In some cases, as described below, the GNSS can be part of one or more sensor systems 456. The GNSS can provide the vehicle computing system 450 with the ability to execute one or more location services, navigation services, and / or other services that can utilize GNSS functionality.

[0087] In some cases, the communication system 458 can further include one or more wireless interfaces (e.g., including one or more transceivers and one or more baseband processors for each wireless interface) for transmitting and receiving wireless communication, one or more wired interfaces (e.g., serial interfaces such as Universal Serial Bus (USB) inputs, lightning connectors, and / or other wired interfaces) for communicating over one or more hardwired connections, and / or other components that can enable the vehicle 404 to communicate with a network and / or other UEs.

[0088] The vehicle computing system 450 can also include an infotainment system 454 that can control content and one or more output devices of the vehicle 404 that can be used to output the content. The infotainment system 454 can also be referred to as an in-vehicle infotainment (IVI) system or an in-car entertainment (ICE) system. The content can include, among other things, navigation content, media content (e.g., video content, music or other audio content, and / or other media content). The one or more output devices can include one or more graphical user interfaces, one or more displays, one or more speakers, one or more extended reality devices (e.g., VR, AR, and / or MR headsets), one or more haptic feedback devices (e.g., one or more devices configured to vibrate a seat, a steering wheel, and / or other parts of the vehicle 404), and / or other output devices.

[0089] In some examples, computing system 450 can include intelligent transportation system (ITS) 455. In some examples, ITS 455 can be used to implement V2X communication. For example, the ITS stack of ITS 455 can generate V2X messages based on information from the application layer of the ITS. In some cases, the application layer can generate messages for use by ITS 455 and / or determine whether certain conditions are met for generating messages to be transmitted to other vehicles (in the case of V2V communication), pedestrian UEs (in the case of V2P communication), and / or infrastructure systems (in the case of V2I communication). In some cases, communication system 458 and / or ITS 455 can obtain controller area network (CAN) information (e.g., from other components of the vehicle via a CAN bus). In some examples, communication system 458 (e.g., TCU NAD) can obtain CAN information via a CAN bus and transmit the CAN information to the PHY / MAC layer of ITS 455. ITS 455 can provide the CAN information to the ITS stack of ITS 455. The CAN information can include vehicle-related information such as, among other things, the orientation of the vehicle, the speed of the vehicle, braking information, etc. The CAN information can be provided to ITS 455 continuously or periodically (e.g., every 1 millisecond (ms), every 10 ms, etc.).

[0090] The conditions used to determine whether to generate a message can be determined using CAN information based on safety-related uses and / or other uses, including road safety, traffic efficiency, infotainment, business-related uses, and / or other uses. In an example for illustration, ITS455 can perform lane change assistance or adjustment. For example, using CAN information, ITS455 can determine that the driver of vehicle 404 is attempting to change lanes from the current lane to an adjacent lane (e.g., based on the turn indicator being activated, the user changing or steering the direction towards the adjacent lane, etc.). Based on the determination that vehicle 404 is attempting to change lanes, ITS455 can determine that the lane change conditions related to the message to be sent to other vehicles in the adjacent lane near that vehicle are met. ITS455 can cause one or more messages to be generated in the ITS stack for transmission to other vehicles, which can be used to coordinate lane changes with other vehicles. Other examples of uses include, among others, forward collision warning, automatic emergency braking, lane departure warning, pedestrian avoidance or protection (e.g., when a pedestrian is detected near vehicle 404 based on V2P communication with the user's UE, etc.), traffic sign recognition.

[0091] ITS455 can generate messages (e.g., V2X messages) using any suitable protocol. Examples of protocols that can be used by ITS455 include one or more SAE standards such as Society of Automotive Engineering (SAE) J2735, SAE J2945, SAE J3161, and / or other standards, which are hereby incorporated by reference in their entirety for all purposes.

[0092] The security layer of ITS455 can be used to securely sign messages from the ITS stack that are transmitted to and verified by other UEs configured for V2X communication, such as other vehicles, pedestrian UEs, and / or infrastructure systems. The security layer can also verify messages received from such other UEs. In some implementations, the signing and verification processes can be based on the vehicle's security context. In some examples, the security context may include one or more encryption-decryption algorithms, public and / or private keys used to generate signatures using the encryption-decryption algorithms, and / or other information. For example, each ITS message generated by ITS455 can be signed by the security layer of ITS455. The signature can be obtained using a public key and an encryption-decryption algorithm. A vehicle, pedestrian UE, and / or infrastructure system that receives the signed message can verify the signature to confirm that the message is from an approved vehicle. In some examples, the one or more encryption-decryption algorithms can include one or more symmetric encryption algorithms (e.g., advanced encryption standard (AES), data encryption standard (DES), and / or other symmetric encryption algorithms), one or more asymmetric encryption algorithms that use public and private keys (e.g., Rivest-Shamir-Adleman (RSA) and / or other asymmetric encryption algorithms), and / or other encryption-decryption algorithms.

[0093] In some examples, ITS455 can determine some operations (e.g., V2X-based operations) to be performed based on messages received from other UEs. The operations can include safety-related operations and / or other operations, such as operations for road safety, traffic efficiency, infotainment, business, and / or other uses. In some examples, the operations can include causing a vehicle (e.g., control system 452) to perform automatic functions, such as, among other things, automatic braking, automatic steering (e.g., to maintain orientation in a particular lane), and automatic lane change negotiation with other vehicles. In an example for one illustration, a message indicating that another vehicle has made an emergency stop can be received by the communication system 458 from another device (e.g., via a PC5 interface, a DSRC interface, or a direct interface between other devices). In response to receiving the message, the ITS stack can generate a message or command and send the message or command to the control system 452, thereby causing the control system 452 to automatically brake the vehicle 404 so that the vehicle 404 stops before colliding with another vehicle. In an example for another illustration, the operations can include, among other things, triggering the display of a message warning the driver that there is another vehicle in the adjacent lane of the vehicle, a message warning the driver to stop the vehicle, a message warning the driver that there is a pedestrian at a crosswalk ahead, and a message warning the driver that a toll booth is within a certain distance (e.g., within one mile) of the vehicle.

[0094] In some examples, ITS455 can receive a number of messages from other UEs (e.g., vehicles, RSUs, etc.). In this case, ITS455 authenticates (e.g., decrypts and deciphers) each of the messages and / or determines which actions to perform. Such a number of messages can lead to a large computational load for the vehicle computing system 450. In some cases, the large computational load can increase the temperature of the computing system 450. The increase in temperature of the components of the computing system 450 can adversely affect the ability of the computing system 450 to process a number of received messages. Based on the temperature of the vehicle computing system 450 (or its components) exceeding or approaching one or more thermal levels, one or more functions can be transferred from the vehicle 404 to another device (e.g., a user device, an RSU, etc.). Transferring one or more functions can reduce the computational load of the vehicle 404 and help lower the temperature of the components. A thermal load balancer can be provided that enables the vehicle computing system 450 to perform thermal-based load balancing to control the processing load according to the temperature of the computing system 450 and the processing capabilities of the vehicle computing system 450.

[0095] Computing system 450 further includes one or more sensor systems 456 (e.g., including a first sensor system to an Nth sensor system, where N is a value of 0 or more). When including a plurality of sensor systems, the sensor system(s) 456 can include various types of sensor systems that can be disposed on or within various parts of vehicle 404. The sensor system(s) 456 can include one or more camera sensor systems, LIDAR sensor systems, radio detection and ranging (RADAR) sensor systems, electromagnetic detection and ranging (EmDAR) sensor systems, sound navigation and ranging (SONAR) sensor systems, sound detection and ranging (SODAR) sensor systems, global navigation satellite system (GNSS) receiver systems (e.g., one or more global positioning system (GPS) receiver systems), accelerometers, gyroscopes, inertial measurement units (IMUs), infrared sensor systems, laser rangefinder systems, ultrasonic sensor systems, ultra-low frequency sensor systems, microphones, any combination thereof, and / or other sensor systems. It should be understood that any number of sensors or sensor systems can be included as part of the computing system 450 of vehicle 404.

[0096] Although vehicle computing system 450 is shown as including certain components and / or systems, one of ordinary skill in the art will understand that vehicle computing system 450 may include more or fewer components than those shown in FIG. 4. For example, vehicle computing system 450 may also include one or more input devices and one or more output devices (not shown). In some implementations, vehicle computing system 450 may also include at least one processor and at least one memory having computer-executable instructions executed by the at least one processor (e.g., as part of, or separate from, control system 452, infotainment system 454, communication system 458, and / or sensor system 456 (singular or plural)). The at least one processor is in communication with and / or electrically connected to (referred to as "coupled" or "communicatively coupled") the at least one memory. The at least one processor may include, for example, one or more microcontrollers, one or more central processing units (CPUs), one or more field programmable gate arrays (FPGAs), one or more graphics processing units (GPUs), one or more application processors (e.g., for running or executing one or more software applications), and / or other processors. The at least one memory may include, for example, read-only memory (ROM), random access memory (RAM) (e.g., static RAM (SRAM)), electrically erasable programmable read-only memory (EEPROM), flash memory, one or more buffers, one or more databases, and / or other memory.Computer-executable instructions stored at least in memory or at least on memory can be executed to perform one or more of the functions or operations described herein.

[0097] FIG. 5 shows an example of a computing system 570 of a user device 507. The user device 507 is an example of a UE that can be used by an end user. For example, the user device 507 can include a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smartwatch, glasses, an XR device, etc.), an Internet of Things (IoT) device, and / or other devices used by a user to communicate via a wireless communication network. The computing system 570 can include software components and hardware components that can be electrically or communicatively coupled via a bus 589 (or communicate in another suitable manner as appropriate). For example, the computing system 570 includes one or more processors 584. The one or more processors 584 can include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems. The bus 589 can be used by the one or more processors 584 to communicate between cores and / or with one or more memory devices 586.

[0098] The computing system 570 may also include one or more memory devices 586, one or more digital signal processors (DSPs) 582, one or more SIMs 574, one or more modems 576, one or more wireless transceivers 578, an antenna 587, one or more input devices 572 (e.g., a camera, a mouse, a keyboard, a touch-sensitive screen, a touch pad, a keypad, a microphone, etc.), and one or more output devices 580 (e.g., a display, a speaker, a printer, etc.).

[0099] One or more wireless transceivers 578 can receive a wireless signal (e.g., signal 588) via antenna 587 from one or more other devices, such as other user devices, vehicles (e.g., vehicle 404 of FIG. 4 described above), network devices (e.g., base stations such as eNBs and / or gNBs, WiFi routers, etc.), cloud networks, etc. In some examples, computing system 570 can include multiple antennas. Wireless signal 588 may be transmitted via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a WiFi network), a Bluetooth™ network, and / or other networks. In some examples, one or more wireless transceivers 578 can include an RF front end that includes one or more components, such as, among other components, an amplifier, a mixer for signal downconversion (also called a signal multiplier), a frequency synthesizer (also called an oscillator) that provides a signal to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, etc. The RF front end can generally process the selection of wireless signal 588 and the conversion to a baseband frequency or an intermediate frequency, and can convert the RF signal into the digital domain.

[0100] In some cases, computing system 570 can include an encoding - decoding device (or CODEC) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 578. In some cases, computing system 570 can include an encryption - decryption device or component configured to encrypt and / or decrypt data transmitted and / or received by one or more wireless transceivers 578 (e.g., according to the AES and / or DES standards).

[0101] Each of the one or more SIMs 574 can securely store the IMSI number and associated keys assigned to the user of user device 507. As described above, the IMSI and keys can be used to identify and authenticate a subscriber when accessing the network provided by the network service provider or operator associated with the one or more SIMs 574. One or more modems 576 can modulate one or more signals to encode the information to be transmitted using one or more wireless transceivers 578. One or more modems 576 can also demodulate the signals received by one or more wireless transceivers 578 to decode the transmitted information. In some examples, the one or more modems 576 can include a 4G (or LTE) modem, a 5G (or NR) modem, a modem configured for V2X communication, and / or other types of modems. The one or more modems 576 and the one or more wireless transceivers 578 can be used to communicate data for the one or more SIMs 574.

[0102] Computing system 570 can also include (and / or communicate with) one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 586), which can be local storage and / or network-accessible storage, a disk drive, an array of drives, an optical storage device, and / or a solid-state storage device such as RAM and / or ROM, which can be programmable, flash-updatable, etc., but is not limited thereto. Such storage devices may be configured to implement any suitable data storage device, including but not limited to various file systems, database structures, etc.

[0103] In various aspects, the functionality may be stored in a memory device(s) 586 as one or more computer program products (e.g., instructions or code) and may be executed by one or more processors(s) 584 and / or one or more DSPs 582. Computing system 570 can also include software elements (e.g., within one or more memory devices 586) including other code such as, for example, an operating system, device drivers, executable libraries, and / or one or more application programs, and the one or more application programs may include computer programs that implement the functionality provided in various ways and / or are designed to implement the methods described herein and / or configure the systems described herein.

[0104] FIG. 6 shows an example 600 of wireless communication between devices based on sidelink communication such as V2X or other D2D communication. The communication may be based on, for example, a slot structure. For example, the transmitting UE 602 may transmit a transmission 614 including, for example, a control channel and / or a corresponding data channel, and the transmission 614 may be received by the receiving UEs 604, 606, 608. At least one UE may include an autonomous vehicle or a drone. The control channel may include information for decoding the data channel and may be used by the receiving device to avoid interference by refraining from transmitting on the occupied resources during data transmission. The number of TTIs, as well as the RBs occupied by the data transmission, may be indicated by a control message from the transmitting device. Each of the UEs 602, 604, 606, 608 may be capable of operating as a transmitting device in addition to operating as a receiving device. Thus, UEs 606, 608 are shown as each transmitting transmissions 616, 620, respectively. Transmissions 614, 616, 620 (and 618 by RSU 607) may be broadcast or multicast to nearby devices. For example, UE 614 can transmit a communication intended to be received by other UEs within the range 601 of UE 614. Additionally / alternatively, RSU 607 may receive communications from UEs 602, 604, 606, 608 and / or transmit communication 618 to them.

[0105] In wireless communications such as V2X communication, a V2X entity may perform sensor sharing with other V2X entities for cooperative and automated driving. For example, referring to FIG. 700 of FIG. 7A, a host vehicle (HV) 702 may detect some items in its environment. For example, the HV 702 may detect the presence of a non-V2X entity (NV) 706 in block 732. The HV 702 may notify other entities such as the first remote vehicle (RV1) 704 and / or the roadside unit (RSU) 708 of the presence of the NV 706 if the RV1 704 and / or the RSU 708 cannot detect the NV 706 by themselves. The HV 702 notifying the RV1 704 and / or the RSU 708 about the NV 706 is sensor information sharing. Referring to FIG. 710 of FIG. 7B, the HV 702 may detect physical obstacles 712 such as depressions, debris, or objects that may be obstacles in the path of the HV 702 and / or the RV1 704 and that have not yet been detected by the RV1 704 and / or the RSU 708. The HV 702 may notify the RV1 and / or the RSU 708 about the obstacle 712 so that the obstacle 712 can be avoided. Referring to FIG. 720 of FIG. 7C, the HV 702 may detect the presence of a vulnerable road user (VRU) 722, and may share the detection of the VRU 722 with the RV1 704 and the RSU 708 if the RSU 708 and / or the RV1 704 cannot detect the VRU 722. Referring to FIG. 730 of FIG. 7D, when the HV detects nearby entities (e.g., NV, VRU, obstacle), it may transmit a sensor data sharing message (SDSM) 734 to the RV and / or the RSU to share the detection of the entities. The SDSM 734 may be a broadcast message such that any receiving device (e.g., vehicle, pedestrian device, RSU, etc.) within the vicinity of the HV can receive the message. In some cases, the shared information may be relayed to other entities such as the RV. For example, referring to FIG. 800 of FIG. 8, the HV 802 may detect the presence of the NV 806 and / or the VRU 822.HV802 can broadcast SDSM810 to RSU808 to report the detection of NV806 and / or VRU822. RSU808 can relay the SDSM810 received from HV802 to the remote vehicle so that the remote vehicle can be aware of the presence of NV806 and / or VRU822. For example, RSU808 can send SDSM812 to RV1 804, and SDSM812 contains information related to the detection of NV806 and / or VRU822.

[0106] Figures 9A and 9B are diagrams showing exemplary ranges for V2X-capable vehicles (which may be, for example, C-V2X compliant vehicles) according to some aspects of the present disclosure. As described above, V2X communication may employ an IEEE 802.11p-based DSRC interface, an LTE C-V2X side-link PC5 interface, or other inter-device communication interfaces. In V2X communication, these interfaces can be used for the communication of safety messages such as basic safety messages (BSMs) and / or cooperative awareness messages (CAMs) between V2X-capable vehicles in an intelligent transportation system (ITS). Examples of key performance parameters (KPIs) for these safety messages can include end-to-end latency and age of information (e.g., the amount of time from the acquisition or determination of information).

[0107] Safety messages (e.g., BSM and CAM) can be broadcast to all V2X-capable vehicles located within range via these interfaces. Communication via these interfaces is performed at the physical layer, and the broadcast is essentially a side-link between V2X-capable vehicles. The range of message communication is limited because the UE (e.g., the V2X-capable vehicle) has a range bounded by several device characteristics such as the maximum transmit power. The range can be defined as the distance at which the message is received with at least 90 percent (%) accuracy.

[0108] Both the IEEE 802.11p-based DSRC interface and the LTE C-V2X side-link PC5 interface have the drawback that, due to their limited range (e.g., about 1 km), they do not enable wireless exchange of information between vehicles located far apart beyond the limited range (e.g., more than 1 km apart). This range limitation implicitly controls an effective "neighbor list" for each V2X-enabled vehicle.

[0109] In the examples of FIGS. 9A and 9B, each V2X-enabled vehicle (e.g., the transmitter / receiver vehicle) may have a communication range such that the V2X-enabled vehicle (e.g., the transmitter / receiver vehicle) can transmit and / or receive messages only from V2X-enabled vehicles located within a distance of three V2X-enabled vehicles from the V2X-enabled vehicle (in any direction). For example, based on the position of a particular V2X-enabled vehicle (e.g., the transmitter / receiver vehicle) in FIG. 9A or 9B, the V2X-enabled vehicle (e.g., the transmitter / receiver vehicle) can receive messages from a maximum of six V2X-enabled vehicles (e.g., the "neighbor list" of the V2X-enabled vehicle may include a maximum of six V2X-enabled vehicles). The number of V2X-enabled vehicles within the communication range will vary based on the range and traffic density.

[0110] For example, in the exemplary road configuration 900 of FIG. 9A including V2X vehicles 910a, 910b, 910c, 910d, 910e, 910f, 910g, 910h, 910i, and 910j (collectively referred to as V2X vehicles 910a - 910j), the V2X - enabled vehicle 910a can transmit and / or receive messages only from V2X - enabled vehicles 910b, 910c, and 910d. In the exemplary road configuration 905 of FIG. 9A including V2X vehicles 920a, 920b, 920c, 920d, 920e, 920f, 920g, 920h, 920i, and 920j (collectively referred to as V2X vehicles 920a - 920j), the V2X - enabled vehicle 920b can transmit and / or receive messages only from V2X - enabled vehicles 920a, 920c, 920d, and 920d. In the exemplary road configuration 915 of FIG. 9A including V2X vehicles 930a, 930b, 930c, 930d, 930e, 930f, 930g, 930h, 930i, and 930j (collectively referred to as V2X vehicles 930a - 930j), the V2X - enabled vehicle 930c can transmit and / or receive messages only from V2X - enabled vehicles 930a, 930b, 930d, 930e, and 930f.

[0111] Also, in the exemplary road configuration 925 of FIG. 9B including V2X vehicles 940a, 940b, 940c, 940d, 940e, 940f, 940g, 940h, 940i, and 940j (collectively referred to as V2X vehicles 940a - 940j), the V2X - enabled vehicle 940d can transmit and / or receive only messages from V2X - enabled vehicles 940a, 940b, 940c, 940e, 940f, and 940g. In the exemplary road configuration 935 of FIG. 9B including V2X vehicles 950a, 950b, 950c, 950d, 950e, 950f, 950g, 950h, 950i, and 950j (collectively referred to as V2X vehicles 950a - 950j), the V2X - enabled vehicle 950e can transmit and / or receive only messages from V2X - enabled vehicles 950b, 950c, 950d, 950f, 950g, 950h. In the exemplary road configuration 945 of FIG. 9B including V2X vehicles 960a, 960b, 960c, 960d, 960e, 960f, 960g, 960h, 960i, and 960j (collectively referred to as V2X vehicles 960a - 960j), the V2X - enabled vehicle 960f can transmit and / or receive only messages from V2X - enabled vehicles 960c, 960d, 960e, 960g, 960h, and 960i.

[0112] As described above, both the IEEE 802.11p - based DSRC interface and the LTE C - V2X side - link PC5 interface are limited in range (e.g., to about 1 km), and thus these wireless technologies do not enable wireless exchange of information between vehicles located far apart (e.g., more than 1 km apart) beyond the limited range. In some wireless systems such as LTE, 5G, etc., to increase the communication range between V2X - enabled vehicles, messages can be communicated with network entities (e.g., base stations, multi - access edge computing (MEC), or parts thereof, etc.).

[0113] FIG. 10 is a diagram showing an exemplary system 1000 that includes a network entity 1020 that broadcasts messages to V2X-enabled vehicles 1010a, 1010b, 1010c, 1010d, 1010e, 1010f, 1010g, 1010h, 1010i, and 1010j (collectively referred to as V2X-enabled vehicles 1010a-1010j). The network entity 1020 may include a MEC, a base station, or a portion thereof (e.g., one or more of a central unit (CU) of the base station, a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC). In FIG. 10, the V2X-enabled vehicles 1010a-1010j can communicate vehicle information (e.g., safety messages such as BSM and / or CAM) to the network entity 1020 located within the respective ranges of the V2X-enabled vehicles 1010a-1010j. The network entity 1020 can then broadcast all of the received vehicle information to each of the V2X-enabled vehicles 1010a-1010j located within its range. Note that the network entity 1020 does not have intelligence or specific control regarding the transmission of specific vehicle information to specific V2X-enabled vehicles 1010a-1010j. Thus, the network entity 1020 only needs to send a group broadcast including all of the received vehicle information to all of the V2X-enabled vehicles 1010a-1010j within its range. When flooding the air interface with a group broadcast, the network entity 1020 does not use the transmission power and / or frequency bandwidth efficiently.

[0114] Note that the range limitations of the IEEE 802.11p-based DSRC interface and the LTE C-V2X side-link PC5 interface can lead to problems associated with overtaking situations, for example, when a vehicle is attempting to overtake (pass) an obstructive vehicle (e.g., a truck) that is located in front of the vehicle and blocking the line of sight of an oncoming vehicle. In these cases, when the vehicle is traveling at high speed, a much larger range is required to receive safety messages such as a Do Not Pass Warning (DNPW) in time to prevent a collision.

[0115] FIG. 11 is a diagram illustrating an example of a vehicle configuration 1100 (e.g., an overtaking situation) with an obstructive vehicle 1102 according to some aspects of the present disclosure. The vehicle configuration 1100 of FIG. 11 shows an example of a "see-through use case". In particular, in FIG. 11, vehicle 1104 is shown as traveling behind an obstructive vehicle (e.g., a truck) 1102. Vehicle 1104 (or the driver of the vehicle) wishes to pass (overtake) obstructive vehicle 1102. However, obstructive vehicle 902 blocks the field of view (FOV) of vehicle 1104, and thus vehicle 1104 is unaware of oncoming vehicle 1106, which is located in the oncoming lane and traveling in the opposite direction of vehicle 1104, because vehicle 1104 cannot see (or sense) oncoming vehicle 1106 through obstructive vehicle 1102. In general, note that a "see-through use case" targets vehicle configurations where at least one obstacle (e.g., an obstructive vehicle such as obstructive vehicle 1102, or another obstructive structure or object) blocks the FOV of a vehicle with respect to at least one potential future road hazard. As used herein, the FOV of a vehicle refers to the FOV of each of one or more sensors of the vehicle (e.g., cameras, radar, LIDAR, any combination thereof, and / or other sensors). Further, references herein to a vehicle "seeing" or "not seeing" another object such as another vehicle, a pedestrian, etc. refer to whether the other object is within the FOV of one or more sensors of the vehicle.

[0116] To effectively increase the range of information exchange between equipped vehicles (e.g., V2X-enabled vehicles), the system of the present disclosure employs a central network device to orchestrate and manage the sharing of vehicle information (e.g., vehicle-based messages such as safety messages including BSM and CAM) between equipped vehicles. Communication and computing are centralized in a single network device, thereby providing efficient use of bandwidth and power and supporting ultra-low latency. The network device has the advantage of providing low latency along with a high range of transmission (e.g., a transmission range of over 1 km). In one or more examples, a 5G multi-access edge computing (MEC) device that may have a transmission range of at least several kilometers (kms) can be employed as the network device. In some examples, a wide area network (Uu) interface can be utilized as the air interface for transmission between an equipped vehicle and the network device.

[0117] FIG. 12 is a diagram showing an disclosed system 1200 for providing optimized vehicle-based messages (e.g., safety messages such as BSM and CAM) to equipped vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f, 1210g, 1210h, 1210i, and 1210j (collectively referred to as equipped vehicles 1210a-1210j) according to some aspects of the present disclosure. The equipped vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f, 1210g, 1210h, 1210i, and 1210j can be V2X equipped vehicles or corresponding vehicles configured to communicate using any type of sidelink communication mechanism (e.g., C-V2X, DSRC, etc.). In FIG. 12, the system 1200 can include the equipped vehicles 1210a-1210j, a base station 1220 (e.g., eNB or gNB), and a network device 1230 (e.g., MEC device). It should be noted that the disclosed system 1200 can have more or fewer equipped vehicles, base stations, and / or network devices than those shown in FIG. 12. In some implementations, the vehicles 1210a-1210j can communicate directly with the network device 1230, in which case the base station 1220 may not be involved in the exchange of messages between the equipped vehicles 1210a-1210j and the network device 1230.

[0118] During operation of the disclosed system 1200 of FIG. 12, one or more of the equipped vehicles 1210a - 1210j can transmit one or more information messages (e.g., via the Uu interface or other information) to a base station 1220 (or a portion thereof, such as one or more of the CU, DU, RU, quasi-RT RIC, or non-RT RIC of the base station 1220) located within the range of each of the equipped vehicles 1210a - 1210j. For example, each equipped vehicle from the equipped vehicles 1210a - 1210j can transmit a respective information message having information associated with the respective equipped vehicle 1210a - 1210j to the base station 1220 (or a portion thereof). The one or more information messages can include information (e.g., vehicle information) or characteristics related to the equipped vehicles 1210a - 1210j (e.g., the respective position of each vehicle, the accuracy of each position, the speed of each vehicle, the direction in which each vehicle is traveling, an event of each vehicle, e.g., braking or lane change, and / or other information related to each vehicle), traffic conditions (e.g., low-speed and / or congested traffic, high-speed traffic, information related to an accident, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "normal" message), road topology (e.g., line-of-sight (LOS) or non-LOS (NLOS), etc.), any combination thereof, and / or other information or characteristics.

[0119] One or more information messages may also include information regarding the preferences or parameters of each vehicle from equipped vehicles 1210a - 1210j indicating whether they receive information messages from some other specific equipped vehicles 1210a - 1210j. In some cases, one or more information messages may include the current capabilities of each vehicle from equipped vehicles 1210a - 1210j, e.g., the processing capabilities of each vehicle, the thermal requirements of each vehicle, capabilities, or situations (which may affect the vehicle's data processing capabilities), the health status of each vehicle, etc. In some implementations, one or more information messages may include information indicating specific use cases or safety warnings related to the current state of each vehicle from equipped vehicles 1210a - 1210j, e.g., Do Not Pass Warning (DNPW) or Forward Collision Warning (FCW). In some examples, one or more information messages may be in the form of Standard Basic Safety Messages (BSM), Cooperative Awareness Messages (CAM), Sensor Data Sharing Messages (SDSM), and / or other formats. Note that in one or more examples, at least some of this information may be provided by a Traffic Message Channel (TMC) and / or RSU (e.g., to network device 1230) instead of from one or more information messages.

[0120] In some aspects, some or all of the equipped vehicles 1210a - 1210j can transmit one or more values or scores associated with the exemplary information or characteristics described above instead of transmitting actual information or characteristics. For example, in one example for illustration, instead of transmitting the thermal capabilities or thermal requirements of vehicle 1210a, vehicle 1210a can transmit a value from 0 - 10 indicating the relative level of the thermal capabilities or thermal requirements of vehicle 1210a. For example, a value of 0 may indicate that vehicle 1210a has a very low thermal capability (e.g., cannot operate at high temperatures), while a value of 10 may indicate that vehicle 1210a has a high thermal capability (e.g., can operate at high temperatures). In some cases, each vehicle can transmit a value or score for each item of information or characteristics associated with the vehicle (e.g., the vehicle's processing capabilities, the vehicle's thermal requirements or capabilities, the vehicle's health status, etc.).

[0121] The base station 1220 can send one or more information messages to the network device 1230. After the network device 1230 receives one or more information messages from the base station 1220, the network device 1230 uses the information contained in the one or more information messages together with other information (e.g., characteristics of other vehicles, locations of other vehicles or location information associated with the scene, weather conditions, traffic conditions, etc.) to generate one or more response messages and determine which equipped devices (e.g., other equipped devices such as equipped vehicles 1210a - 1210j and / or V2X - compliant devices including RSU, pedestrian devices / UEs, network - equipped infrastructure such as network - equipped traffic lights, etc.) currently located within the communication range of the network device 1230 (and / or the base station 1220) will send the one or more response messages. As described herein, each response message may include information associated with one or more of the equipped vehicles 1210a - 1210j. As used herein, the equipped vehicles 1210a - 1210j determined to receive one or more response messages are referred to as receiving - side vehicles, and other devices determined to receive one or more response messages are referred to as receiving - side devices.

[0122] In some embodiments, a response message transmitted to a receiving vehicle (e.g., any one of equipped vehicles 1210a - 1210j) or another equipped device (e.g., RSU, pedestrian UE, network equipment infrastructure, etc.) (e.g., via the Uu interface) may include an information message received by network device 1230 from a particular vehicle (or in some cases, multiple information messages received from multiple vehicles) among equipped vehicles 1210a - 1210j. For example, in such an embodiment, network device 1230 may transfer the information message received from an equipped vehicle among equipped vehicles 1210a - 1210j to the receiving vehicle from equipped vehicle 1210a - 1210j or another network equipped device (e.g., network equipment infrastructure such as RSU, pedestrian device / UE, network equipment signal light, etc.).

[0123] In some examples, other information used by network device 1230 to generate one or more response messages and / or to determine to which equipped device to send one or more response messages may include current weather conditions, traffic conditions, sunlight conditions (e.g., daily sunlight duration conditions), road topology conditions, obstacle conditions, any combination thereof, and / or other information related to some or all of equipped vehicles 1210a - 1210j located within the transportation system. Once network device 1230 generates one or more response messages and determines the receiving vehicle and / or other devices, network device 1230 may transmit the one or more response messages to the determined receiving vehicle and / or other devices via base station 1220.

[0124] In some aspects, the network device 1230 can use the information contained in one or more information messages from one or more equipped vehicles 1210a - 1210j, along with other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or scenes, weather conditions, traffic conditions, etc.), to generate a dynamic neighbor list (also referred to as a local dynamic map (LDM) or dynamic surrounding map) for each of the vehicles 1210a - 1210j (e.g., for each of the receiving vehicles or the transmitting vehicle). For example, each dynamic neighbor list can include listings of all vehicles located within a specific predetermined distance (or radius of distance) from the corresponding vehicle 1210a - 1210j. In some cases, each dynamic neighbor list can include a mapping that includes all vehicles located within a specific predetermined distance (or radius of distance) from the corresponding receiving vehicle 1210a - 1210j and includes roads and terrain topology. In some aspects, the network device 1230 can use the dynamic neighbor list to determine which device (e.g., receiving vehicle 1210a - 1210j or other vehicle or device) can be the receiving device to which a message should be sent. In some cases, the network device 1230 can send a message having the dynamic neighbor list to a device not equipped to communicate V2X messages, or a device not currently communicating V2X messages (e.g., a vehicle that is not communicating using PC5 or cannot communicate using PC5). In some examples, each receiving vehicle 1210a - 1210j can use the information contained in the response message, along with other information (e.g., characteristics of other vehicles, location information associated with the location of other vehicles or scenes, weather conditions, traffic conditions, etc.), to generate a dynamic neighbor list for itself.

[0125] In some cases, the network device 1230 uses the information included in one or more information messages from the equipped vehicles 1210a to 1210j, other information (e.g., characteristics of other vehicles, location information associated with the locations of other vehicles or scenes, weather conditions, traffic conditions, etc.), the quality of service (QoS) associated with each of the receiving vehicles, and performance parameters to determine which device (e.g., a vehicle, or other devices such as a UE, RSU, network connection infrastructure, etc.) can be the receiving device to which the message is to be sent, and / or when to send a response message to the receiving vehicle or other devices. Selectively sending a message to a specific device and / or at a specific time can reduce the load on the communication network (e.g., on the Uu interface) by, for example, sending only the most relevant messages to a specific device.

[0126] In some examples, QoS is related to the level of priority that receiving vehicles 1210a - 1210j have for receiving messages, and is the level of service associated with a receiving device (e.g., equipped vehicles 1210a - 1210j and / or from other receiving devices). Thus, for example, a receiving vehicle with high QoS will have a higher priority for receiving messages before a receiving vehicle with low QoS. In some examples, the performance parameters may include an end - to - end latency threshold and / or an age - of - information threshold. The end - to - end latency threshold specifies a predetermined threshold amount of time between when a response message is sent and when it is received. The age - of - information threshold specifies a predetermined threshold amount of the age of vehicle information (e.g., related to an amount of time or “freshness” or “staleness”). In some examples, network device 1230 can determine a transmission priority based on the severity of a message. For example, if an information message or a response message includes a particular message (e.g., a do - not - pass warning (DNPW), a forward collision warning (FCW), etc.), network device 1230 can choose to prioritize the transmission of the related response message.

[0127] In some examples, the network device 1230 can determine to wait (e.g., when not urgent) to send at least a portion of one or more response messages to the receiving device (e.g., from equipped vehicles 1210a - 1210j and / or other receiving devices) in order to improve transmission efficiency. In such examples, the network device 1230 can bundle multiple response messages together and transmit them to the receiving device simultaneously. In some examples, the network device can use information included within one or more information messages from one or more equipped vehicles 1210a - 1210j, other information (e.g., characteristics of other vehicles, location information associated with other vehicles or locations related to the scene, weather conditions, traffic conditions, etc.), the QoS associated with each of the receiving devices, and performance parameters to determine whether to bundle at least a portion of the response messages for transmission. For example, the network device 1230 can bundle response messages to meet QoS requirements such as latency requirements.

[0128] In some cases, the network device 1230 may send one or more response messages to the receiving device via another network entity such as the base station 1220 or a part thereof (e.g., one or more of the DU, CU, etc. of the base station 1220), as shown in FIG. 12. In some examples, a gNB or eNB having a monolithic or non - centralized base station architecture may be employed for the base station 1220. The network device 1230 and the base station 1220 may be collocated together, or alternatively, the network device 1230 and the base station 1220 may be located apart from each other. In some techniques, the base station 1220 may be used to determine whether to bundle some of the response messages for transmission. As described above, in some cases, the equipped vehicles 1210a - 1210j may communicate directly with the network device 1230, in which case the base station 1220 may or may not be involved in the message exchange between the equipped vehicles 1210a - 1210j and the network device 1230.

[0129] FIG. 13 is a diagram showing an disclosed system 1300 for providing optimized vehicle - based messages (e.g., safety messages) to equipped vehicles 1310a, 1310b, 1310c, 1310d, 1310e, 1310f, 1310g, 1310h, 1310i, and 1310j (collectively referred to as equipped vehicles 1310a - 1310j) according to some aspects of the present disclosure. For example, the system 1300 of FIG. 13 shows an example of the operation of the system 1200 of FIG. 12. FIG. 14 is a diagram showing an example of a communication (e.g., V2X communication) exchange 1400 for sharing vehicle information (e.g., vehicle - based messages) for the system 1300 of FIG. 13, and is described in relation to the description of FIG. 13.

[0130] In FIG. 13, the system 1300 may include equipped vehicles 1310a - 1310j, a base station 1320 (e.g., eNB or gNB), and a network device 1330 (e.g., MEC device). It should be noted that the disclosed system 1300 may have more or fewer equipped vehicles 1310a - 1310j, base stations 1320, and / or network devices 1330 than those shown in FIG. 13. The equipped vehicles 1310a, 1310b, 1310c, 1310d, 1310e, 1310f, 1310g, 1310h, 1310i, and 1310j can be V2X equipped vehicles or corresponding vehicles configured to communicate using any type of sidelink communication mechanism (e.g., C-V2X, DSRC, etc.).

[0131] During the operation of the disclosed system 1300 in FIG. 13, the equipped vehicle 1210a (e.g., V2X corresponding vehicle) can transmit a first information message associated with the equipped vehicle 1210a to a base station 1320 located within the range of the equipped vehicle 1210a (e.g., transmission 1410 in FIG. 14). The base station 1320 can transmit the first information message to the network device 1330 (e.g., transmission 1410 in FIG. 14).

[0132] As shown in FIG. 13, the network device 1330 can transmit one or more response messages from the equipped vehicles 1310a to 1310d to the receiving vehicle. For example, after the network device 1330 receives a first information message from the base station 1320, the network device 1330 uses the information included in the first information message together with other information (e.g., characteristics of other vehicles, location information associated with the locations of other vehicles or scenes, weather conditions, traffic conditions, etc.) to generate one or more response messages, and determines which of the equipped vehicles 1310a to 1310j currently located within the communication range of the network device 1330 to transmit the one or more response messages including the information of vehicle 1310a. As shown in FIG. 14, the network device 1330 determines the equipped vehicles 1310b to 1310d as the vehicles (referred to herein as receiving vehicles 1310b to 1310d) to which one or more response messages will be transmitted. By doing so, the network device 1330 can generate a customized group of receiving vehicles for the response messages and also generate customized response messages for each of the receiving vehicles 1310b to 1310d.

[0133] The selected receiving vehicles 1310b to 1310d are the equipped vehicles 1310a to 1310j that the network device 1330 determines that the information related to the equipped vehicle 1310a is relevant to itself. For example, since the equipped vehicle 1310e is located too far from the equipped vehicle 1310a to find the information related to the relevant 1310a, the equipped vehicle 1310e is not determined to be one of the receiving vehicles 1310b to 1310d. Then, after the network device 1330 generates one or more response messages and determines the receiving vehicles 1310b to 1310d, the network device 1330 can transmit one or more response messages to the determined receiving vehicles 1310b to 1310d via the base station 1320 (e.g., transmission 1420 in FIG. 14).

[0134] FIG. 15 is a diagram showing data processing by a network device (e.g., MEC) 1510 of a disclosed system for generating a neighbor list for an equipped vehicle (e.g., a V2X-capable vehicle) 1530 according to some aspects of the present disclosure. During operation of the disclosed system (e.g., system 1200 of FIG. 12), the network device (e.g., MEC) 1510 can receive and analyze information received from various different sources to generate and maintain a dynamic neighbor list for each of the vehicles 1540.

[0135] In FIG. 15, in one or more examples, the network device (e.g., MEC) 1510 can receive information from a plurality of sources, including the vehicle 1530 (e.g., information received via BSMs 1550 transmitted from each of the vehicles 1530) and TMC, RSU, and / or other infrastructure (e.g., may include sensors on the infrastructure) 1520. Information from each of the vehicles 1530 can include, but is not limited to, the position of the vehicle, the accuracy of the position, the speed of the vehicle, the direction in which the vehicle is traveling, events of the vehicle (e.g., braking), and / or other information related to the vehicle. Also, information from the TMC, RSU, and / or other infrastructure 1520 can include, but is not limited to, traffic conditions (e.g., low speed and / or high density traffic, high speed traffic, information related to accidents, etc.), weather conditions (e.g., rain, snow, etc.), message types (e.g., emergency messages, non-emergency or "normal" messages), road topology (e.g., line of sight (LOS) or non-LOS (NLOS)), expected use cases (e.g., DNPW or FCW), any combination of these, and / or other information.

[0136] Once the network device 1510 receives information from different sources, the network device 1510 can use at least a portion of the received information to generate and maintain a dynamic neighbor list for each of the vehicles 1540. For example, each dynamic neighbor list can include listings of all of the vehicles 1530 located within a specific predetermined distance (or radius of distance) from the corresponding vehicle 1530.

[0137] FIG. 16 is a diagram 1600 showing data processing by a network device (e.g., MEC) of a disclosed system for providing vehicle-based messages (e.g., safety messages) optimized for equipped vehicles (e.g., V2X-capable vehicles) 1610a, 1610b, 1610c, 1640 according to some aspects of the present disclosure. In FIG. 16, equipped vehicles 1610a, 1610b, 1610c can transmit one or more information messages to the network device. After receiving the one or more information messages, the network device (e.g., MEC) can use the information (e.g., vehicle information) included in the one or more information messages (e.g., by executing ITS stack functions) to perform a relevance check 1620 on the dynamic neighbor list for each of equipped vehicles 1610a, 1610b, 1610c, 1640. The network device can then update the dynamic neighbor list for each of equipped vehicles 1610a, 1610b, 1610c, 1640 according to at least a portion of the information in the one or more information messages. For example, equipped vehicles 1610a, 1610b, 1610c can be members of the dynamic neighbor list of equipped vehicle 1640.

[0138] Next, the network device can combine a plurality of response messages (e.g., including an updated dynamic neighbor list) for each of the equipped vehicles 1610a, 1610b, 1610c, 1640, and can transmit the bundled response messages to the base station (e.g., eNB or gNB) 1630 (e.g., via the Uu interface). The network device can also specify the transmission priority of the response messages for each of the equipped vehicles 1610a, 1610b, 1610c, 1640 to the base station. The transmission priority may be related to the QoS associated with each of the equipped vehicles 1610a, 1610b, 1610c, 1640. For example, if the equipped vehicle 1640 has a higher level of QoS than the equipped vehicles 1610a, 1610b, 1610c, the base station can select to transmit the response message (e.g., including the updated dynamic neighbor list) to the equipped vehicle 1610 before transmitting one or more other response messages to the equipped vehicles 1640a, 1610b, 1610c.

[0139] FIG. 17 is a flowchart of an exemplary process 1700 for wireless communication in a network entity, according to some aspects of the present disclosure. Process 1700 may be performed by a network device (e.g., a location server such as MEC, eNB, gNB, LMF, or a portion thereof such as one or more of CU, DU, RU, quasi-RT RIC, or non-RT RIC), or by a component or system of a network device (e.g., a chipset). The operations of process 1700 may be implemented as software components that execute and operate on one or more controllers or processors (e.g., control system 452 of FIG. 4, processor 1810 of FIG. 18, or other processor(s)). Further, the transmission and reception of signals by the network entity in process 1700 may be enabled by, for example, one or more antennas and / or one or more transceivers (e.g., the wireless transceiver(s) of communication system 458 of FIG. 4, the wireless transceiver(s) of communication interface 1840 of FIG. 18, etc.).

[0140] In block 1710, a network device (or a portion thereof) can receive one or more first messages (e.g., one or more information messages as described above) from one or more vehicles that are remote from the network device. Each of the one or more first messages includes vehicle information associated with each of the one or more vehicles. In some aspects, the vehicle information includes the location of each of the one or more vehicles, the accuracy of the location, the direction of each vehicle, the speed of each vehicle, one or more capabilities of each vehicle, message filtering requirements by each vehicle, safety warnings from each vehicle, any combination thereof, and / or other information associated with the vehicle from one or more vehicles. In some cases, the one or more capabilities can include the processing capabilities of each vehicle, the thermal state of each vehicle, the health state of each vehicle, any combination thereof, and / or other capabilities. In some examples, the safety warnings are do not pass warning (DNPW), forward collision warning (FCW), and / or any other type of safety warning.

[0141] In block 1720, a network device (or a portion thereof) can determine one or more receiving vehicles with respect to one or more second messages (e.g., one or more response messages as described above) based on at least a portion of vehicle information from one or more first messages and characteristics associated with each of the one or more receiving vehicles. The one or more receiving vehicles are remote from the network device. In some aspects, the characteristics associated with each of the one or more receiving vehicles include quality of service associated with each of the one or more receiving vehicles, one or more performance parameters associated with the one or more receiving vehicles, combinations thereof, and / or other characteristics associated with each receiving vehicle. In some aspects, the quality of service includes message priority. For example, in such an example, the network device (or a portion thereof) can transmit (or output for transmission) one or more second messages to at least one of the one or more receiving vehicles having a higher level of message priority before at least one other vehicle of the one or more receiving vehicles having a lower level of message priority. In some examples, the one or more performance parameters include an end-to-end latency threshold and / or an age of information threshold. For example, as described herein, the end-to-end latency threshold specifies a threshold amount of time between when one or more second messages are transmitted and when the one or more second messages are received. As further described herein, the age of information threshold specifies a threshold amount of the age of information from each receiving vehicle.

[0142] In some cases, the characteristics associated with each receiving vehicle further include the position of each receiving vehicle, the accuracy of the position, the speed of each receiving vehicle, one or more capabilities of each receiving vehicle, the message filtering requirements by each receiving vehicle, safety warnings from each receiving vehicle (e.g., DNPW, FCW, and / or other types of safety warnings), combinations thereof, and / or other characteristics associated with each receiving vehicle. In some examples, one or more capabilities of each receiving vehicle include the processing capabilities of each receiving vehicle, the thermal state of each receiving vehicle, the health state of each receiving vehicle, any combination thereof, and / or other capabilities.

[0143] In some aspects, a network device (or a portion thereof) can determine one or more receiving vehicles with respect to one or more second messages based further on additional information associated with each receiving vehicle among one or more receiving vehicles. For example, the additional information can include weather information, traffic information, sunlight condition information, road topology information, preference information (e.g., a particular preference of a vehicle as to whether to receive information messages from other vehicles), obstacle information, any combination thereof, and / or other information.

[0144] In some aspects, a network device (or a portion thereof) can generate, for each of one or more receiving vehicles, a dynamic neighbor list (also referred to as a local dynamic map (LDM) as described above) based on at least a portion of vehicle information from one or more first messages and based on characteristics associated with the one or more receiving vehicles. In some aspects, a network device (or a portion thereof) can generate, for each of one or more vehicles, a dynamic neighbor list (or LDM) based on at least a portion of vehicle information from one or more first messages and based on characteristics associated with each respective receiving vehicle among the one or more receiving vehicles. As described above, a network device (or a portion thereof) can use the neighbor list(s) generated for one or more receiving vehicles and / or the neighbor list(s) generated for one or more vehicles that transmit one or more first messages (e.g., information messages) to determine one or more receiving vehicles with respect to one or more second messages. In one example, a network device (or a portion thereof) can determine one or more receiving vehicles with respect to one or more second messages based on at least a portion of vehicle information from one or more first messages and the dynamic neighbor list generated for each of the one or more receiving vehicles. In another example, a network device (or a portion thereof) can determine one or more receiving vehicles based on at least a portion of vehicle information and the dynamic neighbor list generated for each of the one or more receiving vehicles.

[0145] In block 1730, a network device (or a part thereof) can send (or output for sending) one or more second messages to one or more receiving vehicles. In some embodiments, the one or more first messages and the one or more second messages are vehicle-based messages. For example, the one or more first messages can include basic safety messages (BSMs), cooperative awareness messages (CAMs), sensor data sharing messages (SDSMs), any combination thereof, and / or other vehicle-based messages. In some cases, the network device (or a part thereof) can send (or output for sending) one or more second messages to one or more receiving vehicles via a network entity (e.g., via the Uu interface). The network device (or a part thereof) can also receive one or more first messages via the Uu interface. For example, the network entity can be a base station (e.g., gNB, eNB, etc.) or a part thereof (e.g., one or more of CU, DU, RU, quasi-RT RIC, or non-RT RIC). In some cases, as described herein, the network device (e.g., MEC) and the network entity (e.g., a base station or a part thereof) are remote from each other. In other cases, as described herein, the network device (e.g., MEC) and the network entity (e.g., a base station or a part thereof) are collocated with each other. For example, when the network device and the network entity are collocated, the one or more receiving vehicles are located within the communication range of the network device. In another example, when the network device and the network entity are remote from each other, the one or more receiving vehicles are located within the communication range of the network entity.

[0146] In some examples, a network device (or a portion thereof) can bundle messages from one or more second messages based on vehicle information (or a portion thereof) from one or more first messages and characteristics associated with each of one or more receiving vehicles. For example, the network device (or a portion thereof) can bundle messages from one or more second messages for transmission to a receiving vehicle based on that a plurality of messages are from at least one vehicle within a dynamic neighbor list of the receiving vehicle, based on the quality of service associated with the plurality of messages, based on the content of the plurality of messages (e.g., by bundling related messages for the same receiving vehicle), based on any combination thereof, and / or based on other factors. The network device (or a portion thereof) can transmit (or output for transmission) one or more second messages to one or more receiving vehicles by transmitting the bundled messages to one or more receiving vehicles.

[0147] As an example for the description of a device that receives one or more first messages (e.g., information messages) therefrom and a receiving device determined to receive a response message, a process 1700 using a vehicle is described. However, process 1700 also applies to other types of receiving devices (e.g., receiving RSU, receiving pedestrian device / UE, receiving network connection infrastructure device, etc.) in addition to or instead of the receiving vehicle. For example, a network device (or a part thereof) can determine one or more receiving user devices regarding one or more second messages based on at least a part of the vehicle information from one or more first messages and the characteristics associated with each of the one or more receiving user devices. The network device (or a part thereof) can send one or more second messages to one or more receiving user devices. In another example, a network device (or a part thereof) can receive one or more first messages (or other messages) from one or more user devices other than a vehicle, and each of the messages from the one or more user devices includes characteristics associated with each of the user devices.

[0148] FIG. 18 is a diagram showing an example of a system for implementing a particular aspect of the present technology. In particular, FIG. 18 shows an example of a computing system 1800 that can be any computing device, remote computing system, camera, or any component thereof that constitutes an internal computing system, and the components thereof communicate with each other using a connection 1805. The connection 1805 can be a physical connection using a bus or a direct connection to a processor 1810 in a chipset architecture, etc. The connection 1805 can also be a virtual connection, network connection, or logical connection.

[0149] In some aspects, computing system 1800 is a distributed system in which the functions described in this disclosure can be distributed among a data center, multiple data centers, a peer network, etc. In some aspects, one or more of the described system components represent many such components that each perform part or all of the functions for which the component is described. In some aspects, these components can be physical devices or virtual devices.

[0150] Exemplary system 1800 includes at least one processing unit (CPU or processor) 1810 and connection 1805 that communicatively couple various system components including system memory 1815, such as read only memory (ROM) 1820 and random access memory (RAM) 1825, to processor 1810. Computing system 1800 can include cache 1812 of high-speed memory directly connected to, proximate to, or integrated as part of processor 1810.

[0151] Processor 1810 can include any general-purpose processor, hardware services or software services, such as services 1832, 1834, and 1836 stored in storage device 1830 configured to control processor 1810, and dedicated processors in which software instructions are incorporated into the actual processor design. Processor 1810 can essentially be a fully self-contained computing system including multiple cores or processors, buses, memory controllers, caches, etc. The multi-core processor can be symmetric or asymmetric.

[0152] To enable user interaction, computing system 1800 includes an input device 1845 that can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, speech, etc. The computing system 1800 can also include an output device 1835, which can be one or more of several output mechanisms. In some cases, a multimodal system can be enabled to provide multiple types of input / output for a user to communicate with the computing system 1800.

[0153] Computing system 1800 can include a communication interface 1840, which can generally control and manage user input and system output. The communication interface can be an audio jack / plug, a microphone jack / plug, a Universal Serial Bus (USB) port / plug, an Apple® Lightning® port / plug, an Ethernet port / plug, an optical fiber port / plug, a proprietary wired port / plug, 3G, 4G, 5G, and / or other cellular data network wireless signal transmission, Bluetooth® wireless signal transmission, Bluetooth® low energy (BLE) wireless signal transmission, iBeacon® wireless signal transmission, Radio Frequency Identification (RFID) wireless signal transmission, Near Field Communication (NFC) wireless signal transmission, Dedicated Short Range Communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, Wireless Local Area Network (WLAN) signal transmission, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transmission, Public Switched Telephone Network (PSTN) signal transmission, Integrated Services Digital Network (ISDN) signal transmission, Ad Hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or any combination thereof, and may perform or facilitate the reception and / or transmission of wired communication or wireless communication using a wired and / or wireless transceiver. The communication interface 1840 may also include one or more GNSS receivers or transceivers used to determine the location of the computing system 1800 based on the reception of one or more signals from one or more satellites associated with one or more Global Navigation Satellite System (GNSS) systems.GNSS systems include, but are not limited to, the United States' Global Positioning System (GPS), Russia's Global Navigation Satellite System (GLONASS), China's BeiDou Navigation Satellite System (BDS), and the European Union's Galileo GNSS. There are no restrictions on operating with any particular hardware configuration, and thus the basic feature here is that they may be easily replaced for improved hardware or firmware configurations as they are developed.

[0154] The memory device 1830 can be a non-volatile and / or non-transitory and / or computer-readable memory device, such as a hard disk, or a magnetic cassette, a flash memory card, a solid state memory device, a digital versatile disc, a cartridge, a floppy disk, a flexible disk, a hard disk, a magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, a digital video disk (DVD) optical disc, a Blu-ray disc (BDD) optical disc, a holographic optical disc, other optical media, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick (registered trademark) card, a smart card chip, an EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, other integrated circuit (IC) chips / cards, a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a flash EPROM (FLASHEPROM), a cache memory (e.g., level 1 (L1) cache, level 2 (L2) cache, level 3 (L3) cache, level 4 (L4) cache, level 5 (L5) cache, or other (L#) cache), a resistive random-accessOther types of computer-readable media that can store data accessible by a computer, such as memory, RRAM / ReRAM, phase change memory (PCM), spin transfer torque RAM (STT-RAM), other memory chips or cartridges, and / or any combination thereof, can be used.

[0155] The memory device 1830 can include software services, servers, services, etc., and when the code defining such software is executed by the processor 1810, it causes the system to perform functions. In some aspects, the hardware services that perform a particular function can include software components stored in a computer-readable medium in relation to the necessary hardware components such as the processor 1810, the connection 1805, the output device 1835, etc. for performing that function. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media that can store, hold, or carry instructions (singular or plural) and / or data. The computer-readable medium can include non-transitory media that can store data and do not include carrier waves and / or transient electronic signals propagated wirelessly or via a wired connection. Examples of non-transitory media can include, but are not limited to, magnetic disks or tapes, optical storage media such as compact discs (CDs) or digital versatile discs (DVDs), flash memory, memory, or memory devices. The computer-readable medium can have code and / or machine-executable instructions stored thereon that can represent any combination of procedures, functions, subprograms, programs, routines, subroutines, modules, software packages, classes, or instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, transferred, or transmitted via any suitable means including, but not limited to, memory sharing, message passing, token passing, network transmission, etc.

[0156] To provide a complete understanding of the aspects and examples provided herein, specific details are given in the above description, but those skilled in the art will understand that the present application is not limited thereto. Thus, while exemplary aspects of the present application are described in detail herein, it should be understood that the inventive concept can be embodied and adopted in various other ways, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art. The various features and aspects of the present application described above can be used individually or jointly. Furthermore, the aspects can be utilized in any number of environments and applications other than those described herein without departing from the broader spirit and scope of the present specification. Accordingly, the present specification and drawings should be regarded as illustrative rather than limiting. For purposes of illustration, the methods are described in a particular order. In alternative aspects, it should be understood that the methods can be performed in an order different from that described.

[0157] For clarity of explanation, in some instances, the present technology may be presented as including individual functional blocks comprising a device, device components, and steps or routines in a method embodied in software, or a combination of hardware and software. Additional components other than those shown in the figures and / or described herein may be used. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the aspects in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail so as not to obscure the aspects.

[0158] Furthermore, those skilled in the art will understand that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0159] Individual aspects may be described above as a process or method shown as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. A flowchart may describe the operations as a sequential process, but many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but it may have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

[0160] The processes and methods according to the examples described above can be implemented using computer-executable instructions stored on or otherwise available from a computer-readable medium. Such instructions can include, for example, instructions and data that cause or configure a general-purpose computer, a special-purpose computer, or a processing device to perform a particular function or group of functions. Portions of the computer resources used can be accessible via a network. The computer-executable instructions can be, for example, binary, intermediate format instructions such as assembly language, firmware, source code, etc. Examples of computer-readable media that can be used to store the instructions, the information used, and / or the information created during the methods according to the described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, network-connected storage devices, and the like.

[0161] Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media such as compact discs (CDs) or digital versatile discs (DVDs), flash memories, memories, or memory devices. A computer-readable medium may have code and / or machine-executable instructions stored thereon that represent, for example, any combination of procedures, functions, subprograms, programs, routines, subroutines, modules, software packages, classes, or instructions, data structures, or program statements. A code segment may be coupled to another code segment or hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, transferred, or transmitted via any suitable means, including, for example, memory sharing, message passing, token passing, network transmission, etc. In some examples, a computer-readable storage device, medium, and memory can include a cable signal or wireless signal, such as a bitstream. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0162] One of ordinary skill in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips, which may be referred to throughout the above description, may in some cases be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, desired design, corresponding technology, etc.

[0163] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or executed in hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof, and may take on any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments necessary to perform the required tasks (e.g., a computer program product) may be stored within a computer-readable or machine-readable medium. A processor(s) may perform the required tasks. Examples of form factors include laptops, smartphones, cellular phones, tablet devices or other small form factor personal computers, personal digital assistants, rack-mounted devices, stand-alone devices, and the like. The functions described herein may also be embodied in a peripheral device or add-in card. Such functions may also be implemented, as a further example, on a circuit board among different chips, or on different processes executing within a single device.

[0164] Instructions, media for propagating such instructions, computing resources for executing the instructions, and other structures that support such computing resources are exemplary means for providing the functions described in this disclosure.

[0165] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices, including but not limited to general purpose computers, wireless communication device handsets, or integrated circuit devices having multiple applications including applications in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together within an integrated logic device or separately as discrete but interoperable logic devices. When implemented in software, these techniques may be realized at least in part by a computer-readable data storage medium comprising program code that includes instructions, which when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging material. The computer-readable medium may comprise a memory or data storage medium, such as random access memory (RAM), such as synchronous dynamic random access memory (SDRAM), read only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read only memory (EEPROM), FLASH memory, magnetic or optical data storage media, and the like. The techniques may alternatively or additionally be realized at least in part by a computer-readable communication medium that conveys or communicates program code in the form of instructions or data structures and that is accessed, read, and / or executed by a computer, such as a propagated signal or wave.

[0166] The program code may be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated logic circuits or discrete logic circuits. Such processors may be configured to implement any of the techniques described in this disclosure. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration. Thus, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or device suitable for implementation of the techniques described herein.

[0167] Those skilled in the art will understand that the symbols or terms "less than" ("<") and "greater than" (">") as used herein may be replaced, without departing from the scope of this specification, with the symbols "less than or equal to" ("≦") and "greater than or equal to" ("≧"), respectively.

[0168] When a component is described as being "configured to" perform a certain operation, such configuration can be achieved, for example, by designing an electronic circuit or other hardware to perform the operation, by programming a programmable electronic circuit (e.g., a microprocessor, or other suitable electronic circuit) to perform the operation, or by any combination thereof.

[0169] The phrase "coupled to" refers to any component that is physically connected, either directly or indirectly, to another component, and / or that communicates, either directly or indirectly, with another component (e.g., is connected to another component via a wired or wireless connection and / or other suitable communication interface).

[0170] The language of a claim or other language that recites "at least one" of a set and / or "one or more" of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, the language of a claim that recites "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, the language of a claim that recites "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, or A and B and C. The language "at least one" of a set and / or "one or more" of a set does not limit the set to the items enumerated in the set. For example, the language of a claim that recites "at least one of A and B" or "at least one of A or B" can mean A, B, or A and B, and can additionally include items not enumerated in the set of A and B.

[0171] Exemplary aspects of the present disclosure include the following. Aspect 1. A method for wireless communication in a network device, the method comprising: at the network device, receiving, from one or more vehicles remote from the device, one or more first messages, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles; at the network device, determining, based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective receiving vehicles of the one or more receiving vehicles, one or more receiving vehicles remote from the device, for which one or more second messages are to be transmitted; and at the network device, transmitting the one or more second messages to the one or more receiving vehicles.

[0172] Aspect 2. The method according to Aspect 1, wherein the one or more first messages and the one or more second messages are vehicle-based messages.

[0173] Aspect 3. The method according to Aspect 1 or 2, wherein the one or more first messages include at least one of a basic safety message (BSM) or a cooperative awareness message (CAM).

[0174] Aspect 4. The method according to any one of Aspects 1 to 3, wherein the network device is a multi-access edge computing (MEC) device.

[0175] Aspect 5. The method according to any one of Aspects 1 to 4, wherein the vehicle information includes at least one of a location of a respective one of the one or more vehicles, an accuracy of the location, a direction of a respective one of the one or more vehicles, a speed of a respective one of the one or more vehicles, one or more capabilities of a respective one of the one or more vehicles, a message filtering requirement by a respective one of the one or more vehicles, or a safety warning from a respective one of the one or more vehicles.

[0176] Aspect 6. The method according to aspect 5, wherein one or more capabilities include at least one of the processing capabilities of each vehicle, the thermal state of each vehicle, or the health state of each vehicle.

[0177] Aspect 7. The method according to aspect 5 or 6, wherein the safety warning includes at least one of a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW).

[0178] Aspect 8. One or more receiving vehicles for one or more second messages are determined based on additional information associated with each receiving vehicle among the one or more receiving vehicles, the additional information including at least one of weather information, traffic information, sunlight condition information, road topology information, preference information, or obstacle information, according to the method described in any one of aspects 1 to 7.

[0179] Aspect 9. Further including generating a dynamic neighbor list for each of the one or more receiving vehicles based on at least a portion of the vehicle information from the one or more first messages and based on characteristics associated with each of the one or more receiving vehicles, and determining the one or more receiving vehicles regarding the one or more second messages includes determining the one or more receiving vehicles based on at least a portion of the vehicle information from the one or more first messages and the dynamic neighbor list generated for each of the one or more receiving vehicles, according to the method described in any one of aspects 1 to 8.

[0180] Aspect 10. Further including generating a dynamic neighbor list for each of the one or more vehicles based on at least a portion of the vehicle information from the one or more first messages and based on characteristics associated with each of the one or more receiving vehicles, and determining the one or more receiving vehicles regarding the one or more second messages includes determining the one or more receiving vehicles based on at least a portion of the vehicle information and the dynamic neighbor list generated for each of the one or more receiving vehicles, according to the method described in any one of aspects 1 to 9.

[0181] Aspect 11. The method according to any one of Aspects 1 to 10, wherein the characteristic associated with each receiving vehicle among the one or more receiving vehicles includes at least one of the quality of service associated with each receiving vehicle among the one or more receiving vehicles, or at least one of one or more performance parameters associated with each receiving vehicle among the one or more receiving vehicles.

[0182] Aspect 12. The method according to Aspect 11, wherein the characteristic associated with each receiving vehicle among the one or more receiving vehicles further includes at least one of the position of each receiving vehicle, the accuracy of the position, the speed of each receiving vehicle, one or more capabilities of each receiving vehicle, the message filtering requirements by each receiving vehicle, or the safety warnings from each receiving vehicle.

[0183] Aspect 13. The method according to Aspect 12, wherein one or more capabilities of each receiving vehicle include at least one of the processing capability of each receiving vehicle, the thermal state of each receiving vehicle, or the health state of each receiving vehicle.

[0184] Aspect 14. The method according to Aspect 12 or 13, wherein the safety warning includes at least one of a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW).

[0185] Aspect 15. The method according to any one of Aspects 11 to 14, wherein the quality of service includes a message priority, and one or more second messages are transmitted to at least one of one or more receiving vehicles having a higher level of message priority before at least one of the other vehicles of one or more receiving vehicles having a lower level of message priority.

[0186] Aspect 16. The method according to any one of Aspects 11 to 15, wherein one or more performance parameters include at least one of an end-to-end latency threshold or an age of information threshold.

[0187] Aspect 17. The method according to aspect 16, wherein the end-to-end latency threshold specifies a threshold amount of time between when one or more second messages are transmitted and when one or more second messages are received.

[0188] Aspect 18. The method according to aspect 16 or 17, wherein the age of information threshold specifies a threshold amount of the age of information from each receiving vehicle.

[0189] Aspect 19. Further comprising bundling at least a portion of the second message(s) based on at least a portion of the vehicle information from the one or more first messages and the characteristics associated with each receiving vehicle among the one or more receiving vehicles, and transmitting the one or more second messages to the one or more receiving vehicles, wherein transmitting the bundled at least a portion of the one or more second messages to the one or more receiving vehicles includes transmitting the bundled at least a portion of the one or more second messages to the one or more receiving vehicles. The method according to any one of aspects 1 to 18.

[0190] Aspect 20. Bundling at least a portion of the one or more second messages includes bundling a plurality of messages from at least one of a plurality of messages from at least one vehicle within the dynamic neighbor list of the receiving vehicle, the quality of service associated with the plurality of messages, or the content of the plurality of messages, for transmission to the receiving vehicle. The method according to aspect 19.

[0191] Aspect 21. The method according to any one of aspects 1 to 20, wherein the one or more second messages are transmitted to the one or more receiving vehicles via a network entity.

[0192] Aspect 22. The method according to aspect 21, wherein the network entity is a base station.

[0193] Aspect 23. The method according to aspect 22, wherein the base station is one of a gNodeB (gNB) or an evolved NodeB (eNB).

[0194] Aspect 24. The method according to any one of Aspects 21 to 23, wherein the network device and the network entity are either remote from each other or collocated, and when the network device and the network entity are collocated, one or more receiving vehicles are located within the communication range of the network device, or when the network device and the network entity are remote from each other, one or more receiving vehicles are located within the communication range of the network entity.

[0195] Aspect 25. The method according to any one of Aspects 1 to 24, wherein one or more first messages are received via a wide area network (Uu) interface and one or more second messages are transmitted via the Uu interface.

[0196] Aspect 26. The method according to any one of Aspects 1 to 25, further comprising determining one or more receiving user devices for one or more second messages based on at least a portion of vehicle information from one or more first messages and characteristics associated with each of the one or more receiving user devices, and transmitting the one or more second messages to the one or more receiving user devices.

[0197] Aspect 27. The method according to any one of Aspects 1 to 26, further comprising receiving one or more third messages from one or more user devices, each message from the one or more user devices including characteristics associated with each of the one or more user devices.

[0198] Aspect 28. An apparatus for wireless communication, comprising at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive, from one or more vehicles remote from the apparatus, one or more first messages, each of the one or more first messages including vehicle information associated with a respective one of the one or more vehicles, determine, based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with respective receiving vehicles of the one or more receiving vehicles, one or more receiving vehicles remote from the apparatus for one or more second messages, and output one or more second messages for transmission to the one or more receiving vehicles.

[0199] Aspect 29. The apparatus according to aspect 28, wherein the one or more first messages and the one or more second messages are vehicle-based messages.

[0200] Aspect 30. The apparatus according to aspect 28 or 29, wherein the one or more first messages include at least one of a basic safety message (BSM) or a cooperative awareness message (CAM).

[0201] Aspect 31. The apparatus according to any one of aspects 28 to 30, wherein the apparatus is a multi-access edge computing (MEC) device.

[0202] Aspect 32. The apparatus according to any one of aspects 28 to 31, wherein the vehicle information includes at least one of a position of a respective one of the one or more vehicles, an accuracy of the position, a direction of a respective one of the one or more vehicles, a speed of a respective one of the one or more vehicles, one or more capabilities of a respective one of the one or more vehicles, a message filtering requirement by a respective one of the one or more vehicles, or a safety warning from a respective one of the one or more vehicles.

[0203] Aspect 33. The apparatus according to aspect 32, wherein one or more capabilities include at least one of the processing capabilities of each vehicle, the thermal state of each vehicle, or the health state of each vehicle.

[0204] Aspect 34. The apparatus according to aspect 32 or 33, wherein the safety warning includes at least one of a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW).

[0205] Aspect 35. One or more receiving vehicles for one or more second messages are determined based further on additional information associated with each of the one or more receiving vehicles, the additional information including at least one of weather information, traffic information, sunlight condition information, road topology information, preference information, or obstacle information, the apparatus according to any of aspects 28 - 34.

[0206] Aspect 36. At least one processor is configured to generate a dynamic neighbor list for each of one or more receiving vehicles based on at least a portion of vehicle information from one or more first messages and based on characteristics associated with the one or more receiving vehicles, and to determine the one or more receiving vehicles based on at least a portion of vehicle information from the one or more first messages and the dynamic neighbor list generated for each of the one or more receiving vehicles, the apparatus according to any of aspects 28 - 35.

[0207] Aspect 37. At least one processor is configured to generate a dynamic neighbor list for each of one or more vehicles based on at least a portion of vehicle information from one or more first messages and based on characteristics associated with each of the one or more receiving vehicles, and to determine the one or more receiving vehicles based on at least a portion of the vehicle information and the dynamic neighbor list generated for each of the one or more receiving vehicles, the apparatus according to any of aspects 28 - 36.

[0208] Aspect 38. The apparatus according to any one of Aspects 28 to 37, wherein the characteristic associated with each receiving vehicle among the one or more receiving vehicles includes at least one of the quality of service associated with each receiving vehicle among the one or more receiving vehicles, or at least one of one or more performance parameters associated with each receiving vehicle among the one or more receiving vehicles.

[0209] Aspect 39. The apparatus according to Aspect 38, wherein the characteristic associated with each receiving vehicle among the one or more receiving vehicles further includes at least one of the position of each receiving vehicle, the accuracy of the position, the speed of each receiving vehicle, one or more capabilities of each receiving vehicle, the message filtering requirements by each receiving vehicle, or a safety warning from each receiving vehicle.

[0210] Aspect 40. The apparatus according to Aspect 39, wherein one or more capabilities of each receiving vehicle include at least one of the processing capability of each receiving vehicle, the thermal state of each receiving vehicle, or the health state of each receiving vehicle.

[0211] Aspect 41. The apparatus according to Aspect 39 or 40, wherein the safety warning includes at least one of a Do Not Pass Warning (DNPW) or a Forward Collision Warning (FCW).

[0212] Aspect 42. The quality of service includes a message priority, and at least one processor is configured to output one or more second messages to transmit to at least one of one or more receiving vehicles having a higher level of message priority before at least one of one or more other vehicles having a lower level of message priority among the one or more receiving vehicles. The apparatus according to any one of Aspects 38 to 41.

[0213] Aspect 43. The apparatus according to any one of Aspects 38 to 42, wherein one or more performance parameters include at least one of an end-to-end latency threshold or an age of information threshold.

[0214] Aspect 44. The apparatus according to aspect 43, wherein the end-to-end latency threshold specifies a threshold amount of time between when one or more second messages are transmitted and when one or more second messages are received.

[0215] Aspect 45. The apparatus according to aspect 43 or 44, wherein the age-of-information threshold specifies a threshold amount of the age of information from each receiving vehicle.

[0216] Aspect 46. At least one processor is configured to bundle at least a portion of one or more second messages based on at least a portion of vehicle information from one or more first messages and characteristics associated with each receiving vehicle among one or more receiving vehicles, and to output at least a portion of the bundled one or more second messages for transmission to one or more receiving vehicles. The apparatus according to any one of aspects 28 to 45, wherein at least one processor is configured to output at least a portion of the bundled one or more second messages for transmission to one or more receiving vehicles.

[0217] Aspect 47. To bundle at least a portion of one or more second messages, at least one processor is configured to bundle a plurality of messages from at least one vehicle within a dynamic neighbor list of a receiving vehicle, based on the quality of service associated with the plurality of messages, or the content of the plurality of messages, from one or more second messages for transmission to the receiving vehicle. The apparatus according to aspect 46.

[0218] Aspect 48. The apparatus according to any one of aspects 28 to 47, wherein at least one processor is configured to output one or more second messages for transmission to one or more receiving vehicles via a network entity.

[0219] Aspect 49. The apparatus according to aspect 48, wherein the network entity is a base station.

[0220] Aspect 50. The apparatus according to aspect 49, wherein the base station is one of a gNodeB (gNB) or an evolved NodeB (eNB).

[0221] Aspect 51. The apparatus according to any one of aspects 48 to 50, wherein the apparatus and the network entity are either remote from each other or collocated, and when the network device and the network entity are collocated, one or more receiving vehicles are located within the communication range of the network device, or when the network device and the network entity are remote from each other, one or more receiving vehicles are located within the communication range of the network entity.

[0222] Aspect 52. The apparatus according to any one of aspects 28 to 51, wherein one or more first messages are received via a wide area network (Uu) interface and one or more second messages are transmitted via the Uu interface.

[0223] Aspect 53. The apparatus according to any one of aspects 28 to 52, wherein the apparatus is configured as a network entity and further includes a transceiver configured to receive one or more first messages and transmit one or more second messages to one or more receiving vehicles.

[0224] Aspect 54. The method according to any one of aspects 28 to 53, wherein at least one processor determines one or more receiving user devices for one or more second messages based on at least a portion of vehicle information from one or more first messages and characteristics associated with each of one or more receiving user devices, and outputs one or more second messages for transmission to the one or more receiving user devices.

[0225] Aspect 55. The method according to any one of Aspects 28 to 54, wherein at least one processor is configured to receive one or more third messages from one or more user devices, and each of the messages from the one or more user devices includes characteristics associated with each of the one or more user devices.

[0226] Aspect 56. A non-transitory computer-readable medium of a network entity storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations according to any one of Aspects 1 to 55.

[0227] Aspect 57. An apparatus for wireless communication comprising one or more means for performing the operations according to any one of Aspects 1 to 55.

[0228] The foregoing description has been provided to enable any person skilled in the art to make and use the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein but are to be accorded the widest scope consistent with the claim language and not to mean "sole and exclusive" by the singular reference to an element unless specifically stated otherwise, but rather to mean "one or more".

Claims

1. A method for wireless communication in network devices, The network device receives one or more first messages from one or more first vehicles located remotely from the network device, wherein each of the one or more first messages includes vehicle information associated with each of the one or more first vehicles. In the network device, determining one or more receiving vehicles with respect to one or more second messages based on at least a portion of the vehicle information from one or more first messages and the characteristics associated with each of the one or more receiving vehicles, wherein the one or more receiving vehicles is located remotely from the network device. The network device transmits the one or more second messages to the one or more receiving vehicles, including the one or more receiving vehicles that transmit the messages to one or more second vehicles located beyond the vehicle-to-everything (V2X) communication range of the one or more first vehicles and away from the one or more first vehicles. Methods that include...

2. The method according to claim 1, wherein the one or more first messages and the one or more second messages are vehicle-based messages.

3. The method according to claim 1, wherein the one or more first messages include at least one of a basic safety message (BSM) or a cooperative recognition message (CAM).

4. The method according to claim 1, wherein the network device is a multi-access edge computing (MEC) device.

5. The method according to claim 1, wherein the vehicle information includes at least one of the following: the position of each of the one or more vehicles, the accuracy of the position, the direction of each vehicle, the speed of each vehicle, the capability of one or more of the vehicles, a message filtering request from each vehicle, or a safety warning from each vehicle.

6. The method according to claim 5, wherein the one or more capabilities include at least one of the processing capacity of each vehicle, the thermal state of each vehicle, or the health state of each vehicle.

7. The method according to claim 5, wherein the safety warning includes at least one of a no-passing-allow-pass (DNPW) or a forward collision warning (FCW).

8. The method according to claim 1, wherein the one or more receiving vehicles relating to the one or more second messages are further determined based on additional information associated with each of the one or more receiving vehicles, the additional information includes at least one of weather information, traffic information, sunshine conditions information, road topology information, preference information, or obstacle information.

9. The method according to claim 1, further comprising generating a dynamic neighbor list for each of the one or more receiving vehicles based on at least a portion of the vehicle information from the one or more first messages and based on the characteristics associated with each of the one or more receiving vehicles, wherein determining the one or more receiving vehicles with respect to the one or more second messages includes determining the one or more receiving vehicles based on at least a portion of the vehicle information from the one or more first messages and the dynamic neighbor list generated for each of the one or more receiving vehicles.

10. The method according to claim 1, further comprising generating a dynamic neighbor list for each of the one or more vehicles based on at least a portion of the vehicle information from the one or more first messages and based on the characteristics associated with each of the one or more receiving vehicles, wherein determining the one or more receiving vehicles with respect to the one or more second messages includes determining the one or more receiving vehicles based on the at least portion of the vehicle information and the dynamic neighbor list generated for each of the one or more receiving vehicles.

11. The method according to claim 1, wherein the characteristics associated with each of the one or more receiving vehicles include at least one of the service quality associated with each of the one or more receiving vehicles, or one or more performance parameters associated with the one or more receiving vehicles.

12. The method according to claim 11, wherein the characteristics associated with each of the one or more receiving vehicles further include at least one of the following: the location of each receiving vehicle, the accuracy of the location, the speed of each receiving vehicle, the capability of one or more of the receiving vehicles, a message filtering request by each receiving vehicle, or a safety warning from each receiving vehicle, and optionally, the one or more of the capabilities of each receiving vehicle includes at least one of the following: the processing capacity of each receiving vehicle, the thermal state of each receiving vehicle, or the health state of each receiving vehicle.

13. The method according to claim 11, wherein the quality of service includes message priority, and the one or more second messages are transmitted to at least one of the one or more receiving vehicles having a higher message priority before the other one of the one or more receiving vehicles having a lower message priority.

14. The method according to claim 11, wherein the one or more performance parameters include at least one of an end-to-end latency threshold or an information age threshold, and optionally the end-to-end latency threshold specifies a threshold amount of time between when the one or more second messages are transmitted and when the one or more second messages are received, and / or the information age threshold specifies a threshold amount of the age of the information from each receiving vehicle.

15. The further includes bundling at least a portion of the one or more second messages based on at least a portion of the vehicle information from the one or more first messages and the characteristics associated with each of the one or more receiving vehicles, The method according to claim 1, wherein transmitting the one or more second messages to the one or more receiving vehicles includes transmitting at least a bundled portion of the one or more second messages to the one or more receiving vehicles.

16. Bundling at least a portion of the one or more second messages is The method according to claim 1, comprising bundling the multiple messages from one or more second messages for transmission to the receiving vehicle, based on at least one of a plurality of messages from at least one vehicle in the dynamic neighbor list of the receiving vehicle, the quality of service associated with the plurality of messages, or the content of the plurality of messages.

17. A device for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor is Receiving one or more first messages from one or more first vehicles located remotely from the device, wherein each of the one or more first messages includes vehicle information associated with each of the one or more vehicles, Determining one or more receiving vehicles with respect to one or more second messages based on at least a portion of the vehicle information from one or more first messages and the characteristics associated with each of the one or more receiving vehicles, wherein the one or more receiving vehicles is located remotely from the device. Outputting one or more second messages for transmission to one or more receiving vehicles, including one or more second vehicles located beyond the vehicle-to-everything (V2X) communication range of one or more first vehicles and away from the one or more first vehicles, A device configured to perform the following actions.

18. A computer-readable storage medium for a network entity, which stores instructions that cause one or more processors to perform the operations described in any one of claims 1 to 16 when executed by one or more processors.

Images