Optimized Internet of Vehicles (V2X) messaging
The use of a network device with a wide area network interface extends the range of V2X communication beyond 1 km, addressing the limitations of short-range technologies by enabling vehicles to share information about unseen hazards, thereby reducing collisions and enhancing traffic safety.
Patent Information
- Application Number
- CN202380035240.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-27
- Filing Date
- 2023-03-22
- Publication Date
- 2024-12-03
AI Technical Summary
Existing V2X communication technologies, such as IEEE 802.11p-based DSRC and LTE C-V2X sidelink PC5, are limited to short ranges (approximately 1 km), which can hinder effective information exchange between vehicles at greater distances, especially when one or both vehicles are moving at high speeds, leading to potential collisions due to unseen hazards.
Utilizing a network device, such as a multi-access edge computing (MEC) system, to relay messages between vehicles via a wide area network (Uu) interface, extending the transmission range beyond 1 km and enabling vehicles to share information about potential hazards through intelligent relaying and message bundling.
Enhances vehicle situational awareness by allowing vehicles to receive information about unseen hazards beyond their direct communication range, reducing collisions and improving traffic efficiency by providing a low-latency, high-range communication solution.
Smart Images

Figure CN119072934A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to network communications. For example, aspects of the present disclosure relate to providing optimized vehicle-to-everything (V2X) messaging. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting 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 multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is the fifth generation (5G) new radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the third generation partnership project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G long term evolution (LTE) standard. Various aspects of wireless communication may include communication between devices, such as in V2X, vehicle to vehicle (V2V), and / or device to device (D2D) communication. There is a need to further improve V2X, V2V, and / or D2D technologies. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention
[0004] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0005] Disclosed are systems, apparatus, methods, and computer-readable media for providing optimized message transmission, such as over a wide area network (e.g., Uu) interface. According to at least one example, a method for wireless communication at a network device includes: receiving one or more first messages at the network device from one or more vehicles remote from the network device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle in the one or more vehicles; determining the one or more recipient vehicles at the network device based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with a corresponding recipient vehicle in one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being remote from the network device; and sending the one or more second messages at the network device to the one or more recipient vehicles.
[0006] In another example, a device for wireless communication is provided, the device including at least one memory (e.g., configured to store data, such as virtual content data, one or more images, etc.) and at least one processor coupled to the at least one memory (e.g., implemented in a circuit system). The at least one processor is configured to and can perform the following operations: receive one or more first messages from one or more vehicles away from the device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle in the one or more vehicles; determine the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with a corresponding recipient vehicle in one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being away from the device; and output the one or more second messages for transmission to the one or more recipient vehicles.
[0007] In another example, a non-transitory computer-readable medium of a network device having instructions stored thereon is provided, which, when executed by one or more processors, causes the one or more processors to: receive one or more first messages from one or more vehicles remote from the network device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle among the one or more vehicles; determine the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with a corresponding recipient vehicle among one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being remote from the network device; and output the one or more second messages for sending to the one or more recipient vehicles.
[0008] In another example, a device for wireless communication is provided. The device includes: a component for receiving one or more first messages from one or more vehicles remote from the device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle in the one or more vehicles; a component for performing the following operations: determining the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with a corresponding recipient vehicle in one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being remote from the device; and a component for sending the one or more second messages to the one or more recipient vehicles.
[0009] In some aspects, the device (apparatus) is a network device, or a portion thereof (e.g., a multi-access edge computing (MEC) device, a gNodeB (gNB), an evolved B node (eNB), a location server (such as a location management function (LMF), or a portion thereof), or is provided by a component or system (e.g., a chipset) of the network device. In other cases, the device (apparatus) can be a vehicle or a portion thereof (e.g., a car, a truck, etc. or a component or system of a car, 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, Robotic device, or other device or part thereof. In some aspects, the device includes a radio detection and ranging (radar) for capturing radio frequency (RF) signals. In some aspects, the device includes one or more light detection and ranging (LIDAR) sensors, radar sensors, or other light-based sensors for capturing light-based (e.g., light frequency) signals. In some aspects, the device includes a camera or multiple cameras for capturing one or more images. In some aspects, the device also includes a display for displaying one or more images, notifications, and / or other displayable data. In some aspects, the above-mentioned device may include one or more sensors that can be used to determine the location of the device, the state of the device (e.g., temperature, humidity level, and / or other states), and / or for other purposes.
[0010] This summary is neither intended to identify key features 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 appropriate portions of the entire specification of this patent, any or all drawings, and each claim.
[0011] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.
[0013] Figure 1 is a diagram illustrating an example of a wireless communication system and access network according to some aspects of the present disclosure.
[0014] Figure 2A is a diagram illustrating an example of a first device and a second device involved in wireless communications (eg, V2V communications, V2X communications, and / or other device-to-device communications) according to some aspects of the present disclosure.
[0015] Figure 2B is a diagram illustrating an example of a disaggregated base station architecture that may be used by the disclosed system to provide optimized vehicle-based messages (e.g., safety messages) to equipped vehicles (e.g., V2X-enabled vehicles) according to some examples.
[0016] Figure 3 is a diagram illustrating examples of various user equipment (UE) communicating over a direct communication interface (e.g., a cellular-based PC5 sidelink interface, a dedicated short-range communication (DSRC) interface defined in 802.11p, or other direct interfaces) and a wide area network (Uu) interface according to some aspects of the present disclosure.
[0017] Figure 4 is a block diagram illustrating an example of a computing system for a vehicle according to some aspects of the present disclosure.
[0018] Figure 5 is a block diagram illustrating an example of a computing system of a user device according to some aspects of the present disclosure.
[0019] Figure 6 is a diagram illustrating an example of devices involved in wireless communications (eg, sidelink communications) according to some aspects of the present disclosure.
[0020] 7A to 7D is a diagram illustrating an example of sensor sharing for cooperative and autonomous driving systems according to some aspects of the present disclosure.
[0021] Figure 8 is a diagram illustrating an example of sensor sharing for cooperative and autonomous driving systems according to some aspects of the present disclosure.
[0022] Fig.9A and Fig. 9Bis a diagram illustrating example ranges of a V2X-enabled vehicle according to some aspects of the present disclosure.
[0023] Fig.10 is a diagram illustrating an example system including a network entity broadcasting messages to V2X-enabled vehicles in accordance with some aspects of the present disclosure.
[0024] Fig.11 is a diagram illustrating an example of a scene including an obstructing vehicle according to some aspects of the present disclosure.
[0025] Fig.12 is a diagram illustrating an example of a system for providing optimized vehicle-based messages (eg, safety messages) to equipped vehicles (eg, V2X-enabled vehicles) in accordance with some aspects of the present disclosure.
[0026] Fig.13 is a diagram illustrating another example of a system for providing optimized vehicle-based messages (eg, safety messages) to equipped vehicles (eg, V2X-enabled vehicles) in accordance with some aspects of the present disclosure.
[0027] Fig.14 is an example of a method for Fig.13 00147] An illustration of an example of a system for exchanging communications (eg, V2X communications) for sharing vehicle information (eg, vehicle-based messages).
[0028] Fig.15 is a diagram illustrating an example of a network device processing data to generate a neighbor list for an equipped vehicle (e.g., a V2X-enabled vehicle) in accordance with some aspects of the present disclosure.
[0029] Fig.16 is a diagram illustrating an example of a network device processing data to provide optimized vehicle-based messages (e.g., safety messages) to equipped vehicles (e.g., V2X-enabled vehicles) in accordance with some aspects of the present disclosure.
[0030] Fig.17 is a flow chart illustrating an example of a process for wireless communications by a network entity in accordance with some aspects of the present disclosure.
[0031] Fig.18 is a block diagram illustrating an example of a computing system according to some aspects of the present disclosure. DETAILED DESCRIPTION
[0032] For illustrative purposes, some aspects of the present disclosure are provided below. Without departing from the scope of the present disclosure, alternative aspects can be designed. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted, so as not to make the relevant details of the present disclosure difficult to understand. Some aspects described in this article can be applied independently, and some of them can be applied in combination, which is obvious to those skilled in the art. In the following description, specific details are set forth for explanation purposes to provide a thorough understanding of various aspects of the application. However, it is obvious that various aspects can be practiced without these specific details. Each drawing and description are not intended to be restrictive.
[0033] The following description provides only example aspects and is not intended to limit the scope, applicability or configuration of the present disclosure. On the contrary, the following description of the example aspects will provide a description that can be used to implement the example aspects to those skilled in the art. It should be understood that various changes may be made to the function and arrangement of the elements without departing from the essence and scope of the present application as set forth in the appended claims.
[0034] 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" is not necessarily to be construed as preferred or superior to other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0035] Wireless communication systems are deployed to provide a variety of telecommunication services including telephony, video, data, messaging, broadcasting, etc. Wireless communication systems have evolved over several generations. The 5G mobile standard calls for higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard (also known as "New Radio" or "NR") is designed to provide data rates of tens of megabits per second to each of tens of thousands of users.
[0036] Vehicles are examples of systems that may include wireless communication capabilities. For example, vehicles (e.g., motor vehicles, autonomous vehicles, aircraft, marine vessels, etc.) may communicate with other vehicles and / or other devices that have wireless communication capabilities. Wireless vehicle communication systems include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P) communications, which are collectively referred to as vehicle-to-everything (V2X) communications. V2X communications are vehicle communication systems that support the wireless transmission of information from a vehicle to other entities located within a traffic system that may affect the vehicle (e.g., other vehicles, pedestrians with smartphones, and / or other traffic infrastructure). The main purpose of V2X technology is to improve road safety, fuel savings, and traffic efficiency.
[0037] In a V2X communication system, information is sent from vehicle sensors (and other sources) over wireless links to allow the information to be communicated to other vehicles, pedestrians, and / or traffic infrastructure. By sharing this information with other vehicles, V2X technology improves the perception of potential hazards by the vehicle (and driver), thereby helping to reduce collisions with other vehicles and entities. In addition, V2X technology improves traffic efficiency by providing vehicles with traffic warnings about upcoming potential road hazards and obstacles so that the vehicle can choose an alternative traffic route.
[0038] As previously mentioned, V2X technology includes V2V communication, which may also be referred to as peer-to-peer communication. V2V communication allows vehicles to communicate wirelessly directly with each other while on the road. Using V2V communication, vehicles can gain situational awareness by receiving information about upcoming road hazards (e.g., unforeseen oncoming vehicles, accidents, and road conditions) from other vehicles.
[0039] The IEEE 802.11p standard supports a dedicated short-range communication (DSRC) interface for V2X wireless communications. Features of the DSRC interface based on IEEE 802.11p include low latency and use of the unlicensed 5.9 gigahertz (GHz) band. However, the DSRC interface based on IEEE 802.11p has the disadvantage of being short-range (e.g., below about one (1) kilometer (km)).
[0040] Cellular V2X (C-V2X) is adopted as an alternative to using the DSRC interface based on IEEE 802.11p for wireless communication. The 5G Automobile Association (5GAA) supports the use of C-V2X technology. In some cases, C-V2X technology uses Long Term Evolution (LTE) as the underlying technology, and C-V2X functionality is based on LTE technology. C-V2X includes multiple operating modes. One operating mode allows wireless communication directly between vehicles through the LTE side link PC5 interface. Similar to the DSRC interface based on IEEE802.11p, the LTE C-V2X side link PC5 interface operates on the 5.9GHz band. The LTE C-V2X side link PC5 interface and the DSRC interface also have the disadvantage of short range (e.g., about 1km or less).
[0041] Since both the IEEE 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface are range-limited (e.g., approximately 1 km), these wireless technologies have the disadvantage of not allowing wireless exchange of information between vehicles located more than a limited range apart (e.g., 1 km or more apart in distance). In some situations, such as when at least one of the vehicles is traveling at a high speed, the vehicles may have to receive information (such as a do not pass warning (DNPW)) from each other at a distance greater than 1 km to prevent a collision. As such, there is a need for an improved V2X wireless technology that allows for longer range information transmission.
[0042] Provided herein are systems, apparatus, processes (also referred to as methods) and computer-readable media (collectively referred to as "systems and techniques") for optimizing vehicle situational awareness, such as awareness of upcoming road hazards (e.g., unforeseen oncoming vehicles, accidents, road conditions) by effectively increasing the range of information exchange between vehicles. These systems and techniques provide the ability for vehicles or other devices (e.g., roadside units (RSUs), pedestrian devices / UEs (such as mobile phones), networked infrastructure devices (such as networked traffic lights, etc.) to receive information messages from each other even when these vehicles and / or other devices are located at a distance from each other that exceeds the limited range of the V2X wireless technology used for V2X communication by these vehicles and / or other devices (e.g., greater than 1 km from each other). These systems and techniques provide the ability for vehicles and / or other devices to become aware of unforeseen potential road hazards that are not within their field of view (e.g., due to obstacles in their field of view (e.g., obstructing vehicles, structures and / or objects)). In this way, these systems and techniques can provide vehicles and / or other devices (e.g., essentially "seeing through" obstacles by becoming aware of the obstructed road hazards).
[0043] The disclosed systems and technologies operate by using a network device as an intelligent relay for messages sent between vehicles. The network device has the advantages of providing low latency and high transmission range (e.g., a transmission range greater than 1 km). In some examples, a multi-access edge computing (MEC) device (e.g., a 5G MEC device) may be used as a network device. In some cases, a network device (e.g., MEC) may be co-located with a network entity, such as a cellular base station (e.g., a 3G, 4G, 5G base station, such as a gNodeB (gNB)), an evolved B node (eNB), etc.) or a portion of a cellular base station (e.g., a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or one or more of a non-real-time (non-RT) RIC, as described in more detail below). The wide area network (Uu) interface of a network entity (e.g., a base station or a portion thereof) may be used as an air interface for transmission between a vehicle and a network device (e.g., MEC). The range of the Uu interface is higher than that of C-V2X and DSRC. For example, using the Uu interface, a network entity (e.g., a base station or part thereof) may have a transmission range of at least several kilometers (km).
[0044] In some aspects, the network device may receive one or more information messages (e.g., messages based on the vehicle) from one or more vehicles (e.g., receiving a first information message from a first vehicle, receiving a second information message from a second vehicle, etc.). The information message from the vehicle may include information or characteristics related to the vehicle (e.g., the location of the vehicle, the accuracy of the location, the speed of the vehicle, the direction in which the vehicle is traveling, and / or other information related to the vehicle), traffic conditions (e.g., low-speed and / or dense 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 "regular" messages, etc.), road topology (line of sight (LOS) or non-LOS (NLOS), etc.), any combination thereof, and / or other information. In some examples, the information message may also include information about the vehicle's preference for receiving information messages from certain other specific vehicles. In some cases, the informational message may include the current capabilities of the vehicle, such as the vehicle's processing capabilities, the vehicle's thermal state (which may affect the vehicle's ability to process data), and the vehicle's health status. In some implementations, the informational message may include a specific use case or safety warning related to the current condition of the vehicle, such as a Direct National Park Warning (DNPW) or a Forward Collision Warning (FCW). In some examples, the informational message may be in the form of a standard Basic Safety Message (BSM), a Collaborative Awareness Message (CAM), a Sensor Data Sharing Message (SDSM), and / or other formats.
[0045] After a network device receives one or more informational messages from one or more vehicles, the network device may use the information contained in the informational messages together with other information (e.g., characteristics of the other vehicles, location information associated with the location or scene of the other vehicles, weather conditions, traffic conditions, etc.) to determine which other vehicles and / or other devices (including vehicles and other V2X-enabled devices within the communication range of the network device) currently located in the traffic system (e.g., pedestrian devices / UEs (such as mobile phones), networked infrastructure devices (such as networked traffic lights, etc.)) are to send one (or more) response messages containing information from the one or more vehicles from which the informational messages were received. The vehicles and / or other devices determined to receive the response messages are referred to herein as receiving vehicles or receiving devices. Although the examples are described herein using receiving vehicles as illustrative examples of devices determined to receive response messages, the techniques described herein are applicable to other types of receiving devices (e.g., receiving RSUs, receiving pedestrian devices / UEs, receiving networked infrastructure devices, etc.).
[0046] In some aspects, the response message transmitted to the recipient's vehicle or other equipment may include an informational message received by the network device from a specific vehicle. For example, the network device may forward the informational message received from the vehicle to the recipient's vehicle. In some examples, other information used by the network entity to determine which other vehicles and / or other devices to send a response message to may include the characteristics of other vehicles, location information associated with the location or scene of other vehicles, current weather conditions, traffic conditions, lighting conditions (e.g., lighting conditions at the time of the day), road topology conditions, obstacle conditions, any combination thereof, and / or other information related to some or all vehicles located in the traffic system. In some examples, other information may include the characteristics of a specific recipient's vehicle, such as the quality of service (QoS) associated with the recipient's vehicle, performance parameters (e.g., thermal characteristics or requirements of the recipient's vehicle, the processing capacity of the recipient's vehicle, the health status of the recipient's vehicle, etc.).
[0047] In some aspects, the network device may use the information contained in the informational message from the vehicle together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, 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. A dynamic neighbor list may also be referred to as a local dynamic map (LDM). For example, each dynamic neighbor list may include a list of all vehicles located within a specific predetermined distance (or distance radius) away from the corresponding receiving vehicle. In some cases, each dynamic neighbor list includes a mapping of all vehicles located within a specific predetermined distance (or distance radius) away from the corresponding receiving vehicle, which may include roads and terrain topology. In some examples, each receiving vehicle may use the information contained in the response message together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.) to generate a dynamic neighbor list for itself.
[0048] In some cases, the network device may use information contained in the informational message from the vehicle, the QoS associated with each of the receiving vehicles, the performance parameters of each of the receiving vehicles, and / or the other information or characteristics described above to determine which vehicles may be the receiving vehicles to which one or more response messages are to be transmitted and / or when one or more response messages are to be sent to the receiving vehicles and / or other devices. In some examples, QoS is a service level associated with the receiving vehicle, which is related to the priority level at which the receiving vehicle must receive the message. Thus, for example, a receiving vehicle with a high QoS will have priority to receive the response message before a receiving vehicle with a low QoS. In some examples, the performance parameters may include an end-to-end delay threshold and / or an information age threshold. The end-to-end delay threshold specifies a predetermined threshold time amount between the time when the response message is sent and the time when the response message is received. The information age threshold specifies a predetermined threshold age amount (e.g., related to the amount of time or freshness or staleness) of the vehicle information.
[0049] In some examples, the network device may determine (e.g., when the network device is not urgent, such as in a non-emergency scenario) to wait to transmit at least some of the response messages to the recipient vehicle and / or other device to improve transmission efficiency. In such examples, the network device may bundle multiple response messages together and send them to the recipient vehicle and / or other device simultaneously. In some cases, the network device may use information contained in the informational message from the vehicle, other information (e.g., characteristics of the other vehicles, location information associated with the location or scene of the other vehicles, weather conditions, traffic conditions, etc.), QoS associated with each of the recipient vehicles, and performance parameters associated with each of the recipient vehicles to determine whether to bundle at least some of the response messages for transmission.
[0050] In some cases, the network device may send the response message to the recipient vehicle via a network entity (such as a base station or a portion thereof). In some examples, a gNodeB (gNB) or an evolved NodeB (eNB) may be used for the network entity. As noted above, the network device and the network entity may be co-located together (e.g., the MEC is co-located with the gNB or eNB), or alternatively, the network device and the network entity may be remote from each other (e.g., the MEC is remote from the gNB or eNB). In some techniques, the network entity may be used to determine whether to bundle some of the response messages for transmission.
[0051] Additional aspects of the disclosure are described in more detail below.
[0052] As used herein, the terms "user equipment" (UE) and "network entity" are not intended to be exclusive to or otherwise 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, a router, a tablet computer, a laptop computer, and / or a tracking device, etc.), a wearable device (e.g., a smart watch, smart glasses, a wearable ring, and / or an extended reality (XR) device (such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset)), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), and / or an Internet of Things (IoT) device, etc., for a user to communicate on a wireless communication network. A UE can be mobile or (e.g., at certain times) can be fixed and can communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT," a "client device," a "wireless device," a "subscriber device," a "subscriber terminal," a "subscriber station," a "user terminal" or "UT," a "mobile device," a "mobile terminal," a "mobile station," or variations thereof. In general, a UE may communicate with a core network via the RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on IEEE 802.11 communication standards, etc.), and the like.
[0053] The network entity may be implemented in a converged or monolithic base station architecture, or alternatively, in a disaggregated 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. A base station or server (e.g., having a converged / monolithic base station architecture or a disaggregated base station architecture) may operate according to one of several RATs to communicate with UEs, roadside units (RSUs), and / or other devices depending on the network in which the base station is deployed, and may alternatively 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. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems, a base station may provide edge node signaling functions, while in other systems, a base station may provide additional control and / or network management functions. The communication link by which a UE can transmit signals to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station can transmit signals to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink, a reverse or downlink, and / or a forward traffic channel.
[0054] The term "network entity" or "base station" (e.g., having an aggregated / monolithic base station architecture or a disaggregated base station architecture) may refer to a single physical TRP or multiple physical TRPs, which may or may not be co-located. For example, where the term "network entity" or "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. Where the term "network entity" or "base station" refers to multiple co-located physical TRPs, these physical TRPs may be antenna arrays of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be a serving base station that receives measurement reports from a UE and a neighbor base station whose reference radio frequency (RF) signal (or "reference signal" for short) the UE is measuring. Because as used herein, a TRP is the point through which a base station transmits and receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to the specific TRP of a base station.
[0055] In some specific implementations of supporting UE positioning, a network entity or base station may not support wireless access for a UE (e.g., may not support data, voice, and / or signaling connections with respect to the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).
[0056] A roadside unit (RSU) is a device that can communicate with a network through a communication link or interface (e.g., a cellular-based sidelink or PC5 interface, an 802.11-based or WiFi-based TM A device that sends and receives messages to and from one or more UEs, other RSUs, and / or base stations (using a 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. The RSU may be located on various transportation infrastructure systems, including roads, bridges, parking lots, toll booths, and / or other infrastructure systems. In some examples, the RSU may facilitate communications between UEs (e.g., vehicles, pedestrian devices, and / or other UEs) and transportation infrastructure systems. In some implementations, the RSU may communicate with a server, a base station, and / or other systems that may perform centralized management functions.
[0057] The RSU may communicate with the communication system of the UE. For example, the intelligent transportation system (ITS) of the UE (e.g., a vehicle and / or other UE) may be used to generate and sign messages for sending to the RSU and verify messages received from the RSU. The RSU may communicate (e.g., via a PC5 interface, a DSRC interface, etc.) with vehicles traveling along a road, bridge, or other infrastructure system to obtain traffic-related data (e.g., the time, speed, location, etc. of the vehicle). In some cases, in response to obtaining traffic-related data, the RSU may determine or estimate traffic congestion information (e.g., the start of a traffic congestion, the end of a traffic congestion, etc.), travel time, and / or other information of a specific location. In some examples, the RSU may communicate with other RSUs (e.g., via a PC5 interface, a DSRC interface, etc.) to determine traffic-related data. The RSU may send 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 may broadcast or otherwise send information to any UE (eg, vehicles, pedestrian UEs, etc.) within the coverage area of the RSU.
[0058] Radio frequency signals or "RF signals" include electromagnetic waves of a given frequency that transmit information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a 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" where it is clear from the context that the term "signal" refers to either a wireless signal or an RF signal.
[0059] According to various aspects, Figure 11 is a diagram illustrating an example of a wireless communication system and an access network 100. 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 (a high-power cellular base station) and / or a small cell (a low-power cellular base station). The macro cell includes a 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 aggregated or monolithic base station architecture. Additionally or alternatively, one or more of the base stations 102 may be implemented in a decomposed 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.
[0060] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a backhaul link 184. Base stations 102 may perform one or more of the following functions, among other functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (eg, through EPC 160 or core network 190) over backhaul links 134 (eg, X2 interfaces). Backhaul links 134 may be wired or wireless.
[0061] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. In one aspect, base station 102 in each coverage area 110 can support one or more cells. A "cell" is a logical communication entity for communicating with a base station (e.g., on a certain frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and can be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) to distinguish 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 other protocol types) that can provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" can refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, in the sense that a carrier frequency may be detected and used for communications within a portion of the geographic coverage area of the base station.
[0062] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage area 110. For example, a small cell base station 102′ may have a coverage area 110′ that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).
[0063] The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a 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. These communication links may be through one or more frequencies (e.g., carriers or subcarriers). For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). The component carrier 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 referred to as a secondary cell (SCell).
[0064] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PS SCH), and a 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 IEEE 802.11 standards, LTE, or NR.
[0065] The wireless communication system may also include a Wi-Fi or WLAN access point (AP) 150 in communication with a Wi-Fi or WLAN station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 gigahertz (GHz)). When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine whether the channel is available. In some examples, the wireless communication system 100 may include a device (e.g., UE, etc.) that communicates with one or more UEs 104, base stations 102, APs 150, etc. using an ultra-wideband (UWB) spectrum. The UWB spectrum may range from 3.1 GHz to 10.5 GHz.
[0066] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE and / or 5G in the unlicensed spectrum can boost the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.
[0067] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. The mmW base station 180 can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of CU, DU, RU, near RT RIC, or non-RT RIC). Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, and the wavelength is between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to a frequency of 3 GHz, where the wavelength is 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW and / or near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it should be understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.
[0068] Devices can use beamforming to send and receive communications. For example, Figure 1It is illustrated that the base station 180 can transmit beamformed signals to the UE 104 in one or more transmission directions 182'. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182″. The UE 104 may also send beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction of the base station 180 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same. Although the beamformed signals are illustrated between the UE 104 and the base station 102 / 180, various aspects of beamforming may be similarly applied by the UE 104 or RSU 107 to communicate with another UE 104 or RSU 107, such as based on sidelink communication (such as V2X or D2D communication).
[0069] 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 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.
[0070] The core network 190 may include an access and mobility management function unit (AMF) 192, other AMFs 193, a session management function unit (SMF) 194, and a user plane function unit (UPF) 195. AMF 192 may communicate with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.
[0071] Base station 102 may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive 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 a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
[0072] Some wireless communication networks may include vehicle-based communication devices that may communicate and / or communicate with other devices in accordance with: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node, such as an 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, which may be collectively referred to as vehicle-to-everything (V2X) communications. Again, referring to Figure 1 In some aspects, a UE 104 (e.g., a transmitting vehicle user equipment (VUE) or other UE) may be configured to send messages directly to another UE 104. The communication may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. Communications based on V2X and / or D2D communications may also be sent and received by other transmitting and receiving devices (such as RSU 107, etc.). Aspects of the communication may be based on PC5 or sidelink communications, for example, as combined with Figure 2A Although the following description may provide examples of V2X / D2D communications related to 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
[0073] Figure 2A 2 is a block diagram 200 of a first wireless communication device 210 in communication with a second wireless communication device 250, e.g., via V2V / V2X / other communications. The device 210 may include a transmitting device that communicates with a receiving device (e.g., device 250). The communication may be, for example, sidelink-based. The transmitting device 210 may include a UE, an RSU, etc. The receiving device may include a UE, an RSU, etc. The packets may be provided to a controller / processor 275 that implements layer 3 and layer 2 functionality. 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.
[0074] The transmit (TX) processor 216 and receive (RX) processor 270 implement layer 1 functionality 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) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from channel estimator 274 can be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel condition feedback sent by device 250. 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 a corresponding spatial stream for transmission.
[0075] At the device 250, each receiver 254RX receives a signal through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 can perform spatial processing on the information to recover any spatial stream destined for the device 250. If the destination of multiple spatial streams is the device 250, the RX processor 256 can combine them into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the device 210. These soft decisions can 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 sent on the physical channel by device 210. The data and control signals are then provided to controller / processor 259 which implements layer 3 and layer 2 functionality.
[0076] The controller / processor 259 may be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. The controller / processor 259 may provide demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 259 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0077] Similar to the functions described in conjunction with the transmission performed by the device 210, the controller / processor 259 may provide RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and 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.
[0078] Channel estimates derived by the channel estimator 258 from a reference signal or feedback transmitted by the device 210 may be used by the TX processor 268 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antennas 252 via corresponding transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a corresponding spatial stream for transmission.
[0079] The transmission is processed at device 210 in a manner similar to that described in conjunction with the receiver functionality at device 250. Each receiver 218RX receives a signal through its respective antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides the information to a RX processor 270.
[0080] The controller / processor 275 may be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer-readable medium. The controller / processor 275 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing. The controller / processor 275 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0081] At least one of the TX processor 268, RX processor 256, or controller / processor 259 or TX 216, RX processor 270, or controller / processor 275 of device 250 may be configured to perform a combined Figure 1 All aspects of the description of 298 or 299.
[0082] Figure 2B It is a diagram illustrating an example of a decomposed base station 2200 architecture that can be used by the disclosed system to provide optimized vehicle-based messages (e.g., safety messages) to equipped vehicles (e.g., V2X-enabled vehicles) according to some examples. The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an AP, a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.
[0083] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0084] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0085] As mentioned earlier, Figure 2B A diagram illustrating an example decomposed base station 2200 architecture is shown. The decomposed base station 2200 architecture may include one or more central units (CUs) 2210 that may communicate directly with a core network 2220 via a backhaul link, or indirectly with the core network 2220 through one or more decomposed base station units, such as 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 may communicate with one or more distributed units (DUs) 2230 via respective midhaul links, such as an F1 interface. The DU 2230 may communicate with one or more radio units (RUs) 2240 via respective fronthaul links. The RU 2240 may communicate with respective UEs 2220 via one or more RF access links. In some implementations, a UE 2220 may be served simultaneously by multiple RUs 2240.
[0086] Each of the units (i.e., CU 2210, DU 2230, RU 2240, and near-RT RIC 2225, non-RT RIC 2215, and SMO framework 2205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.
[0087] In some aspects, CU 2210 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 2210. CU2210 may be configured to control user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 2210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 2210 may be implemented to communicate with DU 2230 for network control and signaling.
[0088] DU 2230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 2240. In some aspects, DU 2230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 2230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 2230 or with control functions hosted by CU 2210.
[0089] Lower layer functionality may be implemented by one or more RUs 2240. In some deployments, a RU 2240 controlled by a DU 2230 may correspond to a logical node that hosts RF processing functions or low 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, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 2240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 2220. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 2240 may be controlled by the corresponding DU 2230. In some scenarios, this configuration may enable the implementation of the DU 2230 and the CU 2210 in a cloud-based RAN architecture (such as a vRAN architecture).
[0090] The SMO framework 2205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 2205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 2205 may be configured to interact with a cloud computing platform (such as an 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 may include, but are not limited to, CU 2210, DU 2230, RU 2240, and near-RT RIC 2225. In some specific implementations, the SMO framework 2205 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 2211, via the O1 interface. Additionally, in some implementations, the SMO framework 2205 can communicate directly with one or more RUs 2240 via an O1 interface. The SMO framework 2205 can also include a non-RT RIC 2215 configured to support the functionality of the SMO framework 2205.
[0091] The non-RT RIC 2215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 2225. The non-RT RIC 2215 may be coupled to or communicate with the near-RT RIC 2225 (such as via an A1 interface). The near-RT RIC 2225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 2210, one or more DUs 2230, or both, and the O-eNB with the near-RT RIC 2225.
[0092] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 2225, the non-RT RIC 2215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 2225 and may be received from a non-network data source or from a network function at the SMO framework 2205 or the non-RT RIC 2215. In some examples, the non-RT RIC 2215 or the near-RT RIC 2225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 2215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 2205 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0093] Figure 3 Examples of different communication mechanisms used by various UEs are illustrated. In one example of sidelink communication, Figure 3 The examples illustrate that vehicles 304, 305, and RSU 303 communicate with each other using PC5, DSRC, or other device-to-device direct signaling interfaces. In addition, vehicles 304 and 305 can communicate with 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 illustrated is that the user equipment 307 uses a network (Uu) interface to communicate with the base station 302. As described below, functionality can be transferred from a vehicle (e.g., vehicle 304) to a user equipment (e.g., user equipment 307) based on one or more characteristics or factors (e.g., temperature, humidity, etc.). In an illustrative example, the V2X functionality can be transferred from the vehicle 304 to the user equipment 307, which can then communicate with other vehicles (e.g., vehicle 305) via a PC5 interface (or other device-to-device direct interface, such as a DSRC interface), as described below. Figure 3 shown.
[0094] Although Figure 3A specific number of vehicles (e.g., two vehicles 304 and 305) are illustrated as communicating with each other and / or with RSU 303, BS 302, and / or user equipment 307, but the present disclosure is not limited thereto. For example, dozens or hundreds of such vehicles may be communicating with each other and / or with RSU 303, BS 302, and / or user equipment 307. At any given point in time, each such vehicle, RSU 303, BS 302, and / or user equipment 307 may send various types of information as messages to other nearby vehicles, resulting in each vehicle (e.g., vehicles 304 and / or 305), RSU 303, BS 302, and / or user equipment 307 receiving hundreds or thousands of messages per second from other nearby vehicles, RSUs, base stations, and / or other UEs.
[0095] Although in Figure 3 The PC5 interface is shown in FIG. 1 , but various UEs (eg, vehicles, user equipment, etc.) and RSUs may use any suitable type of direct interface (eg, 802.11 DSRC interface, Bluetooth TM For example, a vehicle may communicate with a user equipment through a direct communication interface (e.g., using PC5 and / or DSRC), a vehicle may communicate with another vehicle through a direct communication interface, a user equipment may communicate with another user equipment through a direct communication interface, a UE (e.g., a vehicle, a user equipment, etc.) may communicate with an RSU through a direct communication interface, an RSU may communicate with another RSU through a direct communication interface, and so on.
[0096] Figure 44 is a block diagram of an example of a vehicle computing system 450 for an example vehicle 404. Vehicle 404 is an example of a UE that can communicate with a network (e.g., eNB, gNB, location beacon, position measurement unit, and / or other network entities) over a Uu interface and can communicate with other UEs using V2X communication over a PC5 interface (or other device-to-device direct interface, such as a DSRC interface). As shown, the vehicle computing system 450 may include at least a power management system 451, a control system 452, an infotainment system 454, an intelligent transport system (ITS) 455, one or more sensor systems 456, and a communication system 458. In some cases, the vehicle computing system 450 may include or may be implemented using 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), visual processing units (VPUs), neural network signal processors (NSPs), microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems.
[0097] The control system 452 may 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 may include one or more electronic control units (ECUs). The ECUs may control one or more electrical systems or subsystems in the vehicle. Examples of specific ECUs that may be included as part of the control system 452 include 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), a central timing module (CTM), and the like. In some cases, the control system 452 may receive sensor signals from one or more sensor systems 456 and may communicate with other systems of the vehicle computing system 450 to operate the vehicle 404.
[0098] The vehicle computing system 450 also includes a power management system 451. In some implementations, the power management system 451 may include a power management integrated circuit (PMIC), a backup battery, and / or other components. In some cases, other systems of the vehicle computing system 450 may include one or more PMICs, batteries, and / or other components. The power management system 451 may perform power management functions for the vehicle 404, such as managing the power supply of the computing system 450 and / or other parts of the vehicle. For example, the power management system 451 may provide a stable power supply in view of power fluctuations (such as based on starting the engine of the vehicle). In another example, the power management system 451 may perform thermal monitoring operations, such as by checking the ambient and / or transistor junction temperature. In another example, the power management system 451 may perform a function based on detecting a certain temperature level, such as causing a cooling system (e.g., one or more fans, an air conditioning system, etc.) to cool certain components of the vehicle computing system 450 (e.g., the control system 452, such as one or more ECUs), shutting down certain functionality of the vehicle computing system 450 (e.g., limiting the infotainment system 454, such as by turning off one or more displays, disconnecting from a wireless network, etc.), and other functions.
[0099] The vehicle computing system 450 also includes a communication system 458. The communication system 458 may include a device for communicating with the network (e.g., a gNB or other network entity via a Uu interface) and / or with other UEs (e.g., via a PC5 interface, a WiFi interface (e.g., DSRC), a Bluetooth TM interface and / or other wireless and / or wired interfaces to another vehicle or UE) and to receive signals from the network (e.g., gNB or other network entity via Uu interface) and / or from other UEs (e.g., via PC5 interface, WiFi interface (e.g., DSRC), Bluetooth TM For example, the communication system 458 is configured to communicate with the user via any suitable wireless network (e.g., 3G network, 4G network, 5G network, WiFi network, Bluetooth network, etc.). TMThe communication system 458 includes various components or devices for performing wireless communication functionality, including an original equipment manufacturer (OEM) subscriber identity module (referred to as a SIM or SIM card) 460, 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 more than two SIMs) and any number of modems (e.g., one modem, two modems, or more than two modems).
[0100] A SIM is a device (e.g., an integrated circuit) that can securely store an International Mobile Subscriber Identity (IMSI) number and associated keys (e.g., encryption-decryption keys) for a particular subscriber or user. The IMSI and keys can be used to identify and authenticate a subscriber on a particular UE. The OEM SIM 460 can be used by the communication system 458 to establish a wireless connection for vehicle-based operations, such as for emergency call (eCall) functions, for communicating with the vehicle manufacturer's communication system (e.g., for software updates, etc.), and other operations. The OEM SIM 460 can be very important for the OEM SIM to support critical 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 dial an emergency number (e.g., "9-1-1" in the United States, "1-1-2" in Europe, etc.) in the event of a vehicle accident, and communicate the location of the vehicle to emergency services such as the police, fire department, etc.
[0101] User SIM 462 may be used by communication system 458 to perform wireless network access functions to support user data connections (e.g., for making phone calls, messaging, infotainment-related services, etc.). In some cases, the user's user device may be connected to the user's wireless network through an interface (e.g., via PC5, Bluetooth TM , Wi-Fi TMThe user device may be connected to the vehicle computing system 450 by a wireless communication system (e.g., DSRC), a universal serial bus (USB) port, and / or other wireless or wired interface. Once connected, the user device may transfer the wireless network access functionality from the user device to the communication system 458 of the vehicle, in which case the user device may stop performing the wireless network access functionality (e.g., during the time period when the communication system 458 is performing the wireless access functionality). The communication system 458 may begin interacting with the base station to perform one or more wireless communication operations, such as facilitating a phone call, sending and / or receiving data (e.g., messaging, video, audio, etc.), and other operations. In such a case, other components of the vehicle computing system 450 may be used to output data received by the communication system 458. For example, the infotainment system 454 (described below) may display video received by the communication system 458 on one or more displays, and / or may use one or more speakers to output audio received by the communication system 458.
[0102] A modem is a device that modulates one or more carrier signals to encode digital information for transmission, and demodulates the signals to decode the transmitted information. Modem 464 (and / or one or more other modems of communication system 458) may be used for data communication of OEM SIM 460 and / or user SIM 462. In some examples, modem 464 may include a 4G (or LTE) modem, and another modem (not shown) of communication system 458 may include a 5G (or NR) modem. In some examples, communication system 458 may include one or more Bluetooth TM Modem (e.g. for Bluetooth TM Low Energy (BLE) or other types of Bluetooth communication), one or more WiFi TM modems (e.g., for DSRC communications and / or other WiFi communications), broadband modems (e.g., ultra-wideband (UWB) modems), any combination thereof, and / or other types of modems.
[0103] In some cases, modem 464 (and / or one or more other modems of communication system 458) may be used to perform V2X communications (e.g., with other vehicles for V2V communications, with other devices for D2D communications, with infrastructure systems for V2I communications, with pedestrian UEs for V2P communications, etc.). In some examples, communication system 458 may include a V2X modem for performing V2X communications (e.g., sidelink communications via a PC5 interface or a DSRC interface), in which case the V2X modem may be separate from one or more modems used for wireless network access functions (e.g., for network communications via a network / Uu interface and / or sidelink communications in addition to V2X communications).
[0104] In some examples, the communication system 458 may be or may include a telematics control unit (TCU). In some implementations, the TCU may include a network access device (NAD) (also referred to as a network control unit or NCU in some cases). The NAD may include a modem 464, Figure 4 460, user SIM 462, and / or other components for wireless communication not shown in the figure. In some examples, communication system 458 may include a global navigation satellite system (GNSS). In some cases, GNSS may be part of one or more sensor systems 456, as described below. GNSS may provide vehicle computing system 450 with the ability to perform one or more location services, navigation services, and / or other services that may utilize GNSS functionality.
[0105] In some cases, the communication system 458 may also include one or more wireless interfaces for sending and receiving wireless communications (e.g., including one or more transceivers and one or more baseband processors for each wireless interface), one or more wired interfaces for performing communications via one or more hardwired connections (e.g., serial interfaces such as universal serial bus (USB) inputs, lighting connectors, and / or other wired interfaces), and / or other components that may allow the vehicle 404 to communicate with a network and / or other UEs.
[0106] The vehicle computing system 450 may 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 content. The infotainment system 454 may also be referred to as an in-vehicle infotainment (IVI) system or an in-car entertainment (ICE) system. The content may include navigation content, media content (e.g., video content, music or other audio content, and / or other media content), and other content. One or more output devices may 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 tactile feedback devices (e.g., one or more devices configured to vibrate seats, steering wheels and / or other parts of the vehicle 404) and / or other output devices.
[0107] In some examples, computing system 450 may include intelligent transport system (ITS) 455. In some examples, ITS 455 may be used to implement V2X communication. For example, an ITS stack of ITS 455 may generate V2X messages based on information from an application layer of the ITS. In some cases, the application layer may determine whether certain conditions have been met to generate messages for use by ITS 455 and / or generate messages to be transmitted to other vehicles (for V2V communication), pedestrian UEs (for V2P communication), and / or infrastructure systems (for V2I communication). In some cases, communication system 458 and / or ITS 455 may obtain vehicle access 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) may obtain CAN information via a CAN bus and may transmit the CAN information to the PHY / MAC layer of ITS 455. ITS 455 may provide CAN information to the ITS stack of ITS 455. The CAN information may include vehicle-related information, such as the vehicle's heading, the vehicle's speed, braking information, and other information. The CAN information may be provided to the ITS 455 continuously or periodically (eg, every 1 millisecond (ms), every 10 ms, etc.).
[0108] The conditions for determining whether to generate a message may be determined using CAN information based on safety-related applications and / or other applications (including applications related to road safety, traffic efficiency, infotainment, business, and / or other applications). In an illustrative example, ITS 455 may perform lane change assistance or negotiation. For example, using CAN information, ITS 455 may determine that the driver of vehicle 404 is attempting to change lanes from the current lane to an adjacent lane (e.g., based on flashing lights being activated, based on the user turning or turning to an adjacent lane, etc.). Based on determining that vehicle 404 is attempting to change lanes, ITS 455 may determine that a lane change condition has been met, which is associated with a message to be transmitted to other vehicles near the vehicle in the adjacent lane. ITS 455 may trigger the ITS stack to generate one or more messages to send to other vehicles, which may be used to negotiate lane changes with other vehicles. Other examples of applications include forward collision warning, automatic emergency braking, lane departure warning, pedestrian avoidance or protection (e.g., when a pedestrian is detected near the vehicle 404, such as based on V2P communication with the user's UE), traffic sign recognition, etc.
[0109] The ITS 455 may generate messages (e.g., V2X messages) using any suitable protocol. Examples of protocols that the ITS 455 may use include one or more Society of Automotive Engineers (SAE) standards (such as SAE J2735, SAE J2945, SAE J3161, and / or other standards), which are hereby incorporated by reference in their entirety and for all purposes.
[0110] The security layer of ITS 455 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 specific implementations, the signing and verification process can be based on the security context of the vehicle. In some examples, the security context may include one or more encryption-decryption algorithms, public and / or private keys used to generate signatures using encryption-decryption algorithms, and / or other information. For example, each ITS message generated by ITS 455 can be signed by the security layer of ITS 455. The signature can be derived using a public key and an encryption-decryption algorithm. The vehicle, pedestrian UE, and / or infrastructure system that receives the signed message can verify the signature to ensure that the message comes from an authorized vehicle. In some examples, one or more encryption-decryption algorithms may 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 using public and private keys (e.g., Levitt-Shamir-Adleman (RSA) and / or other asymmetric encryption algorithms), and / or other encryption-decryption algorithms.
[0111] In some examples, the ITS 455 may determine certain operations to be performed (e.g., V2X-based operations) based on messages received from other UEs. These operations may include safety-related and / or other operations, such as operations for road safety, traffic efficiency, infotainment, business, and / or other applications. In some examples, these operations may include causing the vehicle (e.g., the control system 452) to perform automatic functions, such as automatic braking, automatic steering (e.g., maintaining a forward direction in a particular lane), automatic lane change negotiation with other vehicles, and other automatic functions. In an illustrative example, the communication system 458 may receive a message from another vehicle (e.g., via a PC5 interface, a DSRC interface, or other device-to-device direct interface) indicating that the other vehicle is about to stop suddenly. In response to receiving the message, the ITS stack may generate a message or instruction, and may transmit the message or instruction to the control system 452, which may cause the control system 452 to automatically brake the vehicle 404 so that it stops before colliding with the other vehicle. In other illustrative examples, these operations may include triggering the display of a message warning the driver that another vehicle is in a lane adjacent to the vehicle, a message warning the driver to stop the vehicle, a message warning the driver that pedestrians are at an upcoming intersection, a message warning the driver that a toll booth is within a certain distance of the vehicle (e.g., within 1 mile), and the like.
[0112] In some examples, ITS 455 may receive a large number of messages from other UEs (e.g., vehicles, RSUs, etc.), in which case ITS 455 will authenticate (e.g., decode and decrypt) each of the messages and / or determine which operations to perform. This large number of messages may result in a large computational load on the vehicle computing system 450. In some cases, the large computational load may result in an increase in the temperature of the computing system 450. The increase in the temperature of the components of the computing system 450 may adversely affect the ability of the computing system 450 to handle a large number of incoming messages. One or more functionalities may be transferred from the vehicle 404 to another device (e.g., user equipment, RSU, etc.) based on the temperature of the vehicle computing system 450 (or its components) exceeding or approaching one or more thermal levels. Transferring one or more functionalities may reduce the computational load on the vehicle 404, helping to reduce the temperature of the components. A thermal load balancer may be provided that enables the vehicle computing system 450 to perform thermal-based load balancing to control the processing load, depending on the temperature of the computing system 450 and the processing power of the vehicle computing system 450.
[0113] The computing system 450 also includes one or more sensor systems 456 (e.g., a first sensor system to an Nth sensor system, where N is a value equal to or greater than 0). When multiple sensor systems are included, the sensor systems 456 may include different types of sensor systems that may be arranged on or in different parts of the vehicle 404. The sensor systems 456 may 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 systems (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, infrasound sensor systems, microphones, any combination thereof, and / or other sensor systems. It should be understood that any number of sensors or sensor systems may be included as part of the computing system 450 of the vehicle 404.
[0114] Although the vehicle computing system 450 is shown as including certain components and / or systems, one of ordinary skill in the art will appreciate that the vehicle computing system 450 may include more than Figure 4The vehicle computing system 450 may include more or fewer components than those shown. For example, the vehicle computing system 450 may also include one or more input devices and one or more output devices (not shown). In some specific implementations, the vehicle computing system 450 may also include (for example, as part of or separate from the control system 452, the infotainment system 454, the communication system 458 and / or the sensor system 456) at least one processor and at least one memory having computer executable instructions executed by the at least one processor. At least one processor communicates with at least one memory and / or is electrically connected to (referred to as "coupled to" or "communicatively coupled to") at least one memory. 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 (for example, for running or executing one or more software applications) and / or other processors. At least one memory may include, for example, a read-only memory (ROM), a random access memory (RAM) (for example, a static RAM (SRAM)), an electrically erasable programmable read-only memory (EEPROM), a flash memory, one or more buffers, one or more databases and / or other memories. Computer-executable instructions stored in or on at least the memory may be executed to perform one or more functions or operations described herein.
[0115] Figure 5 An example of a computing system 570 of a user device 507 is illustrated. The user device 507 is an example of a UE that can be used by an end user. For example, the user device 507 may include a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smart watch, glasses, XR devices, etc.), an Internet of Things (IoT) device, and / or other devices used by the user to communicate through a wireless communication network. The computing system 570 includes software and hardware components that can be electrically coupled or communicatively coupled via a bus 589 (or can communicate in other ways, as the case may be). For example, the computing system 570 includes one or more processors 584. The one or more processors 584 may 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 may be used by one or more processors 584 to communicate between cores and / or with one or more memory devices 586.
[0116] 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 touchpad, a keypad, a microphone, etc.), and one or more output devices 580 (e.g., a display, a speaker, a printer, etc.).
[0117] The one or more wireless transceivers 578 can receive data from one or more other devices (such as other user devices, vehicles (e.g., the above-mentioned Figure 4 The computing system 570 may include multiple antennas. The wireless signal 588 may be sent via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunication network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a WiFi network), a Bluetooth network, etc. TM network and / or other networks. In some examples, one or more wireless transceivers 578 may include an RF front end that includes one or more components such as an amplifier, a mixer for down-converting a signal (also referred to as a signal multiplier), a frequency synthesizer (also referred to as an oscillator) that provides a signal to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, and other components. The RF front end generally handles the selection of the wireless signal 588 and the conversion of the wireless signal to baseband or intermediate frequency, and may convert the RF signal to the digital domain.
[0118] In some cases, computing system 570 may include a coding-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 may include an encryption-decryption device or component configured to encrypt and / or decrypt (e.g., in accordance with the AES and / or DES standards) data transmitted and / or received by one or more wireless transceivers 578.
[0119] One or more SIMs 574 can each securely store an IMSI number and associated keys assigned to a user of the user device 507. As noted above, the IMSI and keys can be used to identify and authenticate a subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 574. One or more modems 576 can modulate one or more signals to encode information for transmission using one or more wireless transceivers 578. One or more modems 576 can also demodulate signals received by one or more wireless transceivers 578 to decode the transmitted information. In some examples, one or more modems 576 may include a 4G (or LTE) modem, a 5G (or NR) modem, a modem configured for V2X communication, and / or other types of modems. One or more modems 576 and one or more wireless transceivers 578 can be used to communicate data of one or more SIMs 574.
[0120] The computing system 570 may 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 may include, but are not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, and / or the like.
[0121] In various aspects, the functionality may be stored as one or more computer program products (e.g., instructions or code) in the memory device 586 and executed by the one or more processors 584 and / or the one or more DSPs 582. The computing system 570 may also include software elements (e.g., located within the one or more memory devices 586) including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more applications, which may include a computer program that implements the functionality provided by various aspects, and / or may be designed to implement methods and / or configure systems, as described herein.
[0122] Figure 6An example 600 of wireless communication between devices based on sidelink communication (such as V2X or other D2D communication) is illustrated. The communication may be based on a time slot structure, for example. For example, a transmitting UE 602 may transmit a transmission 614 that may be received by a receiving UE 604, 606, 608, which may include, for example, a control channel and / or a corresponding data channel. At least one UE may include an autonomous vehicle or an unmanned aerial vehicle. The control channel may include information for decoding the data channel and may also be used by the receiving device to avoid interference by avoiding transmission on the occupied resources during data transmission. The number of TTIs and RBs occupied by the data transmission may be indicated in a control message from the transmitting device. In addition to operating as a receiving device, each of the UEs 602, 604, 606, 608 may also be capable of operating as a transmitting device. Therefore, the UEs 606 and 608 are illustrated as transmitting transmissions 616 and 620, respectively. The transmissions 614, 616, 620 (and 618 via the RSU 607) may be broadcast or multicast to nearby devices. For example, the UE 614 may transmit communications intended to be received by other UEs within range 601 of the UE 614. Additionally / alternatively, the RSU 607 may receive communications 618 from and / or transmit communications to the UEs 602, 604, 606, 608.
[0123] In wireless communications (such as V2X communications), a V2X entity may perform sensor sharing with other V2X entities to achieve collaboration and autonomous driving. Fig. 7A 700, a host vehicle (HV) 702 may detect multiple items within its environment. For example, at block 732, the HV 702 may detect the presence of a non-V2X entity (NV) 706. The HV 702 may notify other entities (such as a first remote vehicle (RV1) 704 or an RSU 708) about the presence of the NV 706 if the RV1 704 and / or the RSU 708 themselves are unable to detect the NV 706. The HV 702 notifies the RV1 704 and / or the RSU 708 that the NV 706 is a sharing of sensor information. Figure 7B 710, HV 702 may detect a physical obstacle 712 (such as a pothole, debris, or an object that may be an obstacle in the path of HV 702 and / or RV1 704 that has not yet been detected by RV1 704 and / or RSU 708). HV 702 may notify RV1 and / or RSU 708 of the obstacle 712 so that the obstacle 712 may be avoided. Figure 7C720 , 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 in instances where the RSU 708 and / or the RV1 704 may not be able to detect the VRU 722. Fig.7D 730, the HV, upon detecting a nearby entity (e.g., NV, VRU, obstacle), may send a sensor data sharing message (SDSM) 734 to the RV and / or RSU to share the detection of the entity. The SDSM 734 may be a broadcast message so that any receiving device (e.g., vehicle, pedestrian device, RSU, etc.) near the HV may receive the message. In some instances, the shared information may be relayed to other entities, such as the RV. For example, referring to Figure 8 800, the HV 802 may detect the presence of the NV 806 and / or the VRU 822. The HV 802 may broadcast the SDSM 810 to the RSU 808 to report the detection of the NV 806 and / or the VRU 822. The RSU 808 may relay the SDSM 810 received from the HV 802 to the remote vehicle so that the remote vehicle is aware of the presence of the NV 806 and / or the VRU 822. For example, the RSU 808 may send the SDSM 812 to the RV1 804, wherein the SDSM 812 includes information related to the detection of the NV 806 and / or the VRU 822.
[0124] Fig.9A and Fig. 9B is a diagram illustrating example ranges of V2X-enabled vehicles (which may be, for example, C-V2X-enabled vehicles) according to aspects of the present disclosure. As previously mentioned, V2X communications may employ a DSRC interface based on IEEE 802.11p, an LTE C-V2X sidelink PC5 interface, or other device-to-device communication interfaces. In V2X communications, these interfaces may be used to communicate safety messages, such as Basic Safety Messages (BSMs) and / or Collaborative Awareness Messages (CAMs), between V2X-enabled vehicles in an Intelligent Transportation System (ITS). Examples of key performance parameters (KPIs) for these safety messages may include end-to-end latency and information age (e.g., the amount of time since the information was acquired or determined).
[0125] Safety messages (e.g., BSM and CAM) may be broadcast over these interfaces to all V2X-enabled vehicles within range. Communication over these interfaces is on the physical layer, with the broadcasts essentially being sidelinks between V2X-enabled vehicles. The delivery of messages is range-limited because UEs (e.g., V2X-enabled vehicles) have a range that is bounded by certain device characteristics, such as maximum transmit power. Range may be defined as the distance at which a message is received with at least ninety (90%) percent accuracy.
[0126] Since both the IEEE 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface are range-limited (e.g., approximately 1 km), a disadvantage of these wireless technologies is that they do not allow for wireless exchange of information between vehicles that are located more than a limited range apart (e.g., 1 km or more apart in distance). This range limitation implicitly controls the effective "neighbor list" for each of the V2X-enabled vehicles.
[0127] for Fig.9A and Fig. 9B For example, each V2X-enabled vehicle (e.g., a transmitter / receiver vehicle) may have a communication range that enables the V2X-enabled vehicle (e.g., a transmitter / receiver vehicle) to only send and / or receive messages from V2X-enabled vehicles that are within a distance (in any direction) of three V2X-enabled vehicles from the V2X-enabled vehicle (e.g., a transmitter / receiver vehicle). Fig.9A or Fig. 9B In order to determine the location of a particular V2X-enabled vehicle (e.g., a transmitter / receiver vehicle) in a communication range, the V2X-enabled vehicle (e.g., a transmitter / receiver vehicle) may only receive messages from a maximum number (six) of V2X-enabled vehicles (e.g., a "neighbor list" of a V2X-enabled vehicle may contain up to six V2X-enabled vehicles). The number of V2X-enabled vehicles within communication range will vary based on range and traffic density.
[0128] For example, in Fig.9A In the example road configuration 900 including V2X vehicles 910a, 910b, 910c, 910d, 910e, 910f, 910g, 910h, 910i, and 910j (collectively referred to as V2X vehicles 910a-910j), V2X-enabled vehicle 910a can only send and / or receive messages from V2X-enabled vehicles 910b, 910c, and 910d. Fig.9AIn the example road configuration 905 including V2X vehicles 920a, 920b, 920c, 920d, 920e, 920f, 920g, 920h, 920i, and 920j (collectively referred to as V2X vehicles 920a-920j), V2X-enabled vehicle 920b can only send and / or receive messages from V2X-enabled vehicles 920a, 920c, 920d, and 920d. Fig.9A In the example road configuration 915 including V2X vehicles 930a, 930b, 930c, 930d, 930e, 930f, 930g, 930h, 930i and 930j (collectively referred to as V2X vehicles 930a-930j), V2X-enabled vehicle 930c can only send and / or receive messages from V2X-enabled vehicles 930a, 930b, 930d, 930e and 930f.
[0129] In addition, Fig. 9B In the example road configuration 925 including V2X vehicles 940a, 940b, 940c, 940d, 940e, 940f, 940g, 940h, 940i, and 940j (collectively referred to as V2X vehicles 940a-940j), V2X-enabled vehicle 940d can only send and / or receive messages from V2X-enabled vehicles 940a, 940b, 940c, 940e, 940f, and 940g. Fig. 9B In the example road configuration 935 including V2X vehicles 950a, 950b, 950c, 950d, 950e, 950f, 950g, 950h, 950i, and 950j (collectively referred to as V2X vehicles 950a-950j), V2X-enabled vehicle 950e can only send and / or receive messages from V2X-enabled vehicles 950b, 950c, 950d, 950f, 950g, and 950h. Fig. 9B In the example road configuration 945 including V2X vehicles 960a, 960b, 960c, 960d, 960e, 960f, 960g, 960h, 960i and 960j (collectively referred to as V2X vehicles 960a-960j), V2X-enabled vehicle 960f can only send and / or receive messages from V2X-enabled vehicles 960c, 960d, 960e, 960g, 960h and 960i.
[0130] As previously mentioned, both the IEEE 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface are range-limited (e.g., approximately 1 km), and as such, these wireless technologies do not allow for wireless exchange of information between vehicles located more than a limited range apart (e.g., 1 km or more apart in distance). In some wireless systems (such as LTE, 5G, etc.), messages may be communicated with a network entity (e.g., a base station, multi-access edge computing (MEC) or a portion thereof, etc.) to increase the communication range between V2X-enabled vehicles.
[0131] Fig.10 1 is a diagram illustrating an example system 1000 that includes a network entity 1020 broadcasting 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 an MEC, a base station, or a portion thereof (e.g., 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 of the base station). Fig.10 In the embodiment of the present invention, the V2X-enabled vehicles 1010a-1010j may communicate vehicle information (e.g., safety messages, such as BSM and / or CAM) to the network entity 1020, which is within the range of each of the V2X-enabled vehicles 1010a-1010j. The network entity 1020 may then broadcast all received vehicle information to each of the V2X-enabled vehicles 1010a-1010j within its range. It should be noted that the network entity 1020 does not have any intelligence or inherent control regarding sending specific vehicle information to a specific V2X-enabled vehicle 1010a-1010j. As such, the network entity 1020 may only send a group broadcast containing all received vehicle information to all V2X-enabled vehicles 1010a-1010j within the range. When flooding the air interface with group broadcasts, the network entity 1020 does not efficiently use transmit power and / or frequency bandwidth.
[0132] It should be noted that the range limitations of the IEEE 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface may cause problems in overtaking scenarios, for example, a vehicle is attempting to overtake (pass) an obstructing vehicle (e.g., a truck) that is in front of the vehicle and is blocking the vehicle's view of oncoming vehicles. For these scenarios, when the vehicle is traveling at high speeds, a much larger range is required to receive safety messages (such as Direct Passing Warning (DNPW)) in a timely enough manner to prevent a collision.
[0133] Fig.11 is a diagram illustrating an example of a vehicle configuration 1100 (eg, a passing scenario) with an obstructing vehicle 1102 in accordance with some aspects of the present disclosure. Fig.11 The vehicle configuration 1100 in FIG. 1 depicts an example of a “perspective use case”. Specifically, in Fig.11 , vehicle 1104 is shown traveling behind an obstructing vehicle (e.g., a truck) 1102. Vehicle 1104 (or the driver of the vehicle) desires to overtake (pass) obstructing vehicle 1102. However, obstructing vehicle 1102 is obstructing the field of view (FOV) of vehicle 1104, and as such, vehicle 1104 is unaware of oncoming vehicle 1106 located in the opposing lane and traveling in the opposite direction of vehicle 1104 because vehicle 1104 is unable to see (or sense) oncoming vehicle 1106 through obstructing vehicle 1102. It should be noted that, in general, a "see-through use case" relates to a vehicle configuration in which at least one obstacle (e.g., an obstructing vehicle (such as obstructing vehicle 1102), or other obstructing structure or object) is blocking the vehicle's FOV with respect to at least one upcoming road hazard. As used herein, the FOV of a vehicle refers to the corresponding FOV of one or more sensors of the vehicle (e.g., camera, radar, LIDAR, any combination thereof, and / or other sensors). In addition, references herein to a vehicle "seeing" or "not seeing" another object (such as another vehicle, a pedestrian, etc.) refers to whether the other object is within the FOV of the one or more sensors of the vehicle.
[0134] In order to effectively increase the range of information exchange between equipped vehicles (e.g., V2X-enabled vehicles), the system of the present disclosure uses a central network device to orchestrate and manage the sharing of vehicle information (e.g., vehicle-based messages, such as safety information, including BSM and CAM) between equipped vehicles. Communications and computing are concentrated at a single network device, thereby providing efficient use of bandwidth and power and supporting ultra-low latency. The network device has the advantages of providing low latency and a high transmission range (e.g., a transmission range greater than 1km). In one or more examples, a 5G multi-access edge computing (MEC) device that may have a transmission range of at least several kilometers (km) may be used as a network device. In some examples, a wide area network (Uu) interface may be used as an air interface for transmission between equipped vehicles and network devices.
[0135] Fig.12 1 is a diagram illustrating the 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) in accordance with some aspects of the present disclosure. The equipped vehicles 1210a, 1210b, 1210c, 1210d, 1210e, 1210f, 1210g, 1210h, 1210i, and 1210j can be V2X-equipped or enabled vehicles that are configured to communicate using any type of sidelink communication mechanism (e.g., C-V2X, DSRC, etc.). Fig.12 In the embodiment of the present invention, the system 1200 may include equipped vehicles 1210a-1210j, base stations 1220 (e.g., eNBs or gNBs), and network devices 1230 (e.g., MEC devices). It should be noted that the disclosed system 1200 may have more than Fig.12 More or fewer equipped vehicles, base stations, and / or network devices are shown. In some implementations, vehicles 1210a-1210j may communicate directly with network device 1230, in which case base station 1220 may not participate in the message exchange between equipped vehicles 1210a-1210j and network device 1230.
[0136] exist Fig.12During operation of the disclosed system 1200, one or more of the equipped vehicles 1210a-1210j may send one or more informational messages (e.g., via a Uu interface or other information) to a base station 1220 (or a portion thereof, such as one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC of the base station 1220) that is within range of each of the equipped vehicles 1210a-1210j. For example, each of the equipped vehicles 1210a-1210j may send a respective informational message and information associated with each respective equipped vehicle 1210a-1210j to the base station 1220 (or a portion thereof). The one or more informational messages may include information or characteristics related to the equipped vehicles 1210a-1210j (e.g., vehicle information) (e.g., the respective position of each vehicle, the accuracy of each respective position, the speed of each respective vehicle, the direction in which each respective vehicle is traveling, events of each respective vehicle (such as braking or lane changes, and / or other information related to each respective vehicle), traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, accident-related information, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency message, or "regular" message), etc.), road topology (line of sight (LOS) or non-line of sight (NLOS), etc.), any combination thereof, and / or other information or characteristics.
[0137] The one or more informational messages may also include information about preferences or parameters of each of the equipped vehicles 1210a-1210j, indicating whether to receive informational messages from certain other specific equipped vehicles 1210a-1210j. In some cases, the one or more informational messages may include the current capabilities of each of the equipped vehicles 1210a-1210j, such as the processing capabilities of each vehicle, the thermal requirements of each vehicle, the capabilities or status (which may affect the ability of the vehicle to process data), the health status of each vehicle, etc. In some specific implementations, one or more informational messages may include information indicating specific use cases or safety warnings related to the current status of each vehicle from the equipped vehicles 1210a-1210j, such as reverse overtaking warning (DNPW) or forward collision warning (FCW). In some examples, the one or more informational messages may be in the form of standard basic safety messages (BSM), collaborative awareness messages (CAM), sensor data sharing messages (SDSM), and / or other formats. It should be noted that in one or more examples, at least some of this information may be provided by a traffic message channel (TMC) and / or an RSU (eg, provided to the network device 1230 ), rather than from one or more informational messages.
[0138] In some aspects, some or all of the equipped vehicles 1210a-1210j may send one or more values or scores associated with the above-mentioned example information or characteristics, such as instead of transmitting the actual information or characteristics. In an illustrative example, instead of sending the thermal capabilities or requirements of the vehicle 1210a, the vehicle 1210a may send a value between 0 and 10 indicating the relative level of the thermal capabilities or requirements of the vehicle 1210a. For example, a value of 0 may indicate that the vehicle 1210a has very low thermal capabilities (e.g., cannot operate at high temperatures), while a value of 10 may indicate that the vehicle 1210a has high thermal capabilities (e.g., can operate at high temperatures). In some cases, each vehicle may send a value or score for each information item or characteristic item associated with the vehicle (e.g., the vehicle's handling capabilities, the vehicle's thermal requirements or capabilities, the vehicle's health status, etc.).
[0139] The base station 1220 may send one or more informational messages to the network device 1230. After the network device 1230 receives the one or more informational messages from the base station 1220, the network device 1230 may use the information contained in the one or more informational messages together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.) to generate one or more response messages and determine which equipped devices (e.g., equipped vehicles 1210a-1210j and / or other equipped devices, such as V2X-enabled devices, including RSUs, 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) to send one or more response messages. As mentioned herein, each response message may include information associated with one or more of the equipped vehicles 1210a-1210j. As used herein, equipped vehicles 1210a - 1210j that are determined to receive one or more response messages are referred to as recipient vehicles, and other devices that are determined to receive one or more response messages are referred to as recipient devices.
[0140] In some aspects, a response message transmitted (e.g., via a Uu interface) to a recipient vehicle (e.g., any of the equipped vehicles 1210a-1210j) or other equipped devices (e.g., RSUs, pedestrian UEs, network-equipped infrastructure, etc.) may include an informational message received by the network device 1230 from a particular one of the equipped vehicles 1210a-1210j (or, in some cases, multiple informational messages received from multiple vehicles). For example, in such aspects, the network device 1230 may forward an informational message received from an equipped vehicle from the equipped vehicles 1210a-1210j to a recipient vehicle from the equipped vehicles 1210a-1210j or another network-equipped device (e.g., RSUs, pedestrian devices / UEs, network-equipped infrastructure (such as network-equipped traffic lights), etc.).
[0141] In some examples, other information used by the network device 1230 to generate one or more response messages and / or determine to which equipped devices to send one or more response messages may include: current weather conditions, traffic conditions, lighting conditions (e.g., lighting conditions at the time of day), road topology conditions, obstacle conditions, any combination thereof, and / or other information related to some or all equipped vehicles 1210a-1210j located within the transportation system. Once the network device 1230 generates one or more response messages and determines the recipient vehicle and / or other device, the network device 1230 may send the one or more response messages to the determined recipient vehicle and / or other device via the base station 1220.
[0142] In some aspects, the network device 1230 may generate a dynamic neighbor list (also referred to as a local dynamic map (LDM) or a dynamic surrounding map) for each of the vehicles 1210a-1210j (e.g., each of the receiving vehicle or the sending vehicle) using information contained in one or more informational messages from one or more equipped vehicles 1210a-1210j together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.). For example, each dynamic neighbor list may include a list of all vehicles located within a specific predetermined distance (or distance radius) away from the corresponding vehicle 1210a-1210j. In some cases, each dynamic neighbor list includes a mapping of all vehicles located within a specific predetermined distance (or distance radius) away from the corresponding vehicle 1210a-1210j, which may include road and terrain topology. In some aspects, the network device 1230 may use a dynamic neighbor list to determine which devices (e.g., recipient vehicles 1210a-1210j or other vehicles or devices) may be recipient devices to which a message is to be transmitted. In some cases, the network device 1230 may send a message with a dynamic neighbor list to a device that is not equipped to communicate V2X messages or is not currently communicating V2X messages (e.g., a vehicle that is not using PC5 for communication or cannot use PC5 for communication). In some examples, each recipient vehicle 1210a-1210j may use the information contained in the response message together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.) to generate a dynamic neighbor list for itself.
[0143] In some cases, the network device 1230 may use information contained within one or more informational messages from the equipped vehicles 1210a-1210j, other information (e.g., characteristics of the other vehicles, location information associated with the location or scene of the other vehicles, weather conditions, traffic conditions, etc.), quality of service (QoS) associated with each of the recipient vehicles, and performance parameters used to determine which devices (e.g., vehicles or other devices such as UEs, RSUs, network connectivity infrastructure, etc.) may be recipient devices to which messages are transmitted and / or when response messages are to be sent to the recipient vehicles or other devices. Selectively sending messages to certain devices and / or at certain times may reduce the load on the communication network (e.g., on the Uu interface), such as by sending only the most relevant messages to specific devices.
[0144] In some examples, QoS is a service level associated with a recipient device (e.g., from an equipped vehicle 1210a-1210j and / or other recipient devices) that is related to a priority level that the recipient vehicle 1210a-1210j has for receiving messages. Thus, for example, a recipient vehicle with a high QoS will have a higher priority for receiving a response message before a recipient vehicle with a low QoS. In some examples, the performance parameters may include an end-to-end latency threshold and / or an information age threshold. The end-to-end latency threshold specifies a predetermined threshold amount of time between the time a response message is sent and the time a response message is received. The information age threshold specifies a predetermined threshold amount of age of the vehicle information (e.g., related to an amount of time or freshness or staleness). In some examples, the network device 1230 may determine the sending priority based on the severity of the message. For example, if the informational message or the response message includes a specific message (eg, Direct National Passing Warning (DNPW), Forward Collision Warning (FCW), etc.), the network device 1230 may choose to prioritize the transmission of the associated response message.
[0145] In some examples, the network device 1230 may determine (e.g., when it is not urgent) to wait to transmit at least some of the one or more response messages to a recipient device (e.g., from the equipped vehicles 1210a-1210j and / or other recipient devices) to improve transmission efficiency. In such examples, the network device 1230 may bundle multiple response messages together and send them to the recipient device simultaneously. In some examples, the network device may use information contained in one or more informational messages from one or more equipped vehicles 1210a-1210j, other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.), QoS associated with each of the recipient devices, and performance parameters to determine whether to bundle at least some of the response messages for transmission. For example, the network device 1230 may bundle the response messages to meet QoS requirements, such as latency requirements.
[0146] In some cases, the network device 1230 may send one or more response messages to the recipient device via another network entity, such as the base station 1220 or a portion thereof (e.g., one or more of the DU, CU, etc. of the base station 1220), such as Fig.12 As shown. In some examples, a gNB or eNB having a monolithic or disaggregated base station architecture may be used for base station 1220. Network device 1230 and base station 1220 may be co-located, or alternatively, network device 1230 and base station 1220 may be remote from each other. In some techniques, base station 1220 may be used to determine whether to bundle some of the response messages for transmission. As noted above, in some cases, the equipped vehicles 1210a-1210j may communicate directly with network device 1230, in which case base station 1220 may or may not participate in the message exchange between the equipped vehicles 1210a-1210j and network device 1230.
[0147] Fig.13 is a diagram illustrating a 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, Fig.13 The system 1300 illustrates Fig.12 An example of the operation of system 1200. Fig.14 is used for Fig.13A diagram of an example of a communication (eg, V2X communication) exchange 1400 of a system 1300 for sharing vehicle information (eg, vehicle-based messages), and in conjunction with Fig.13 Description to describe.
[0148] exist Fig.13 In the embodiment of the present invention, the system 1300 may include equipped vehicles 1310a-1310j, base stations 1320 (e.g., eNBs or gNBs), and network devices 1330 (e.g., MEC devices). It should be noted that the disclosed system 1300 may have more than Fig.13 More or fewer equipped vehicles 1310a-1310j, base stations 1320, and / or network devices 1330 are shown. The equipped vehicles 1310a, 1310b, 1310c, 1310d, 1310e, 1310f, 1310g, 1310h, 1310i, and 1310j may be V2X-equipped or enabled vehicles configured to communicate using any type of sidelink communication mechanism (e.g., C-V2X, DSRC, etc.).
[0149] exist Fig.13 During operation of the disclosed system 1300, an equipped vehicle 1210a (e.g., a V2X-enabled vehicle) may transmit a signal (e.g., Fig.14 The base station 1320 may send (eg, Fig.14 Sending 1410) the first informational message.
[0150] like Fig.13 As shown, the network device 1330 may transmit one or more response messages to the receiving vehicles from the equipped vehicles 1310a-1310d. For example, after the network device 1330 receives the first informational message from the base station 1320, the network device 1330 may use the information contained in the first informational message together with other information (e.g., characteristics of other vehicles, location information associated with the location or scene of other vehicles, weather conditions, traffic conditions, etc.) to generate one or more response messages and determine which equipped vehicles 1310a-1310j currently located within the communication range of the network device 1330 are to send one or more response messages containing the information of the vehicle 1310a. Fig.14As shown, the network device 1330 determines the equipped vehicles 1310b-1310d as those vehicles to which one or more response messages will be sent (referred to herein as recipient vehicles 1310b-1310d). In doing so, the network device 1330 generates a customized group of recipient vehicles for the response message, and may also generate a customized response message for each of the recipient vehicles 1310b-1310d.
[0151] The selected recipient vehicles 1310b-1310d are the equipped vehicles 1310a-1310j that the network device 1330 determines will find information related to the equipped vehicle 1310a relevant to themselves. For example, the equipped vehicle 1310e is not determined as a recipient vehicle 1310b-1310d because the equipped vehicle 1310e is too far away from the equipped vehicle 1310a to find relevant information about 1310a. After the network device 1330 generates one or more response messages and determines the recipient vehicles 1310b-1310d, the network device 1330 may then send (e.g., via the base station 1320) to the determined recipient vehicles 1310b-1310d. Fig.14 Send 1420) one or more response messages.
[0152] Fig.15 1 is a diagram illustrating a network device (e.g., MEC) 1510 of a disclosed system processing data to generate a neighbor list for an equipped vehicle (e.g., a V2X-enabled vehicle) 1530 according to some aspects of the present disclosure. Fig.12 During operation of the system 1200 ), the network device (e.g., MEC) 1510 may receive and analyze information received from a variety of different sources to generate and maintain a dynamic neighbor list for each of the vehicles 1540 .
[0153] exist Fig.15In one or more examples, a network device (e.g., MEC) 1510 may receive information from multiple sources, which may include vehicles 1530 (e.g., information sent from each of the vehicles 1530 and received via BSM 1550) and TMCs, RSUs, and / or other infrastructure (e.g., which may include sensors on the infrastructure) 1520. The information from each vehicle 1530 may include, but is not limited to, the location of the vehicle, the accuracy of the location, the speed of the vehicle, the direction the vehicle is traveling, events of the vehicle (e.g., braking), and / or other information related to the vehicle. Furthermore, information from the TMC, RSU, and / or other infrastructure 1520 may include, but is not limited to, traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, accident-related information, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "regular" message), etc.), road topology (line of sight (LOS) or non-LOS (NLOS), etc.), intended use cases (e.g., DNPW or FCW), any combination thereof, and / or other information.
[0154] Once the network device 1510 has received information from the different sources, the network device 1510 may utilize 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 may include a list of all vehicles 1530 that are within a certain predetermined distance (or distance radius) away from the corresponding recipient vehicle 1530.
[0155] Fig.16 1600 is a diagram illustrating network devices (e.g., MEC) of the disclosed system processing data to provide optimized vehicle-based messages (e.g., safety messages) to equipped vehicles (e.g., V2X-enabled vehicles) 1610a, 1610b, 1610c, 1640 in accordance with some aspects of the present disclosure. Fig.16, the equipped vehicles 1610a, 1610b, 1610c may send one or more informational messages to the network device. After receiving the one or more informational messages, the network device (e.g., MEC) may use the information (e.g., vehicle information) contained within the one or more informational messages to perform a relevance check (e.g., by running ITS stack functionality) 1620 on the dynamic neighbor list of each of the equipped vehicles 1610a, 1610b, 1610c, 1640. The network device may then update the dynamic neighbor list of each of the equipped vehicles 1610a, 1610b, 1610c, 1640 based on at least some of the information contained in the one or more informational messages. For example, the equipped vehicles 1610a, 1610b, 1610c may be members of the dynamic neighbor list of the equipped vehicle 1640.
[0156] The network device may then combine multiple response messages (e.g., including updated dynamic neighbor lists) from the equipped vehicles 1610a, 1610b, 1610c, 1640, and may send the bundled response message (e.g., via a Uu interface) to the base station (e.g., eNB or gNB) 1630. The network device may also specify to the base station a transmission priority of the response message of each of the equipped vehicles 1610a, 1610b, 1610c, 1640. The transmission priority may be related to the QoS associated with each of the equipped vehicles 1610a, 1610b, 1610c, 1640. For example, if equipped vehicle 1640 has a higher QoS level than equipped vehicles 1610a, 1610b, 1610c, the base station may choose to send a response message (e.g., including an updated dynamic neighbor list) to equipped vehicle 1640 before sending one or more other response messages to equipped vehicles 1610a, 1610b, 1610c.
[0157] Fig.17 1700 is a flow chart of an example process 1700 for wireless communication at a network entity according to some aspects of the present disclosure. Process 1700 may be performed by a network device (e.g., MEC, eNB, gNB, location server (such as LMF) or a portion thereof (such as CU, DU, RU, near RT RIC or non-RT RIC)) or a component or system (e.g., chipset) of a network device. The operations of process 1700 may be implemented as a process on one or more controllers or processors (e.g., Figure 4 Control system 452, Fig.18In addition, the transmission and reception of signals by the network entity in process 1700 may be performed by, for example, one or more antennas and / or one or more transceivers (e.g., Figure 4 The wireless transceiver of the communication system 458, Fig.18 The communication interface 1840 may be implemented by a wireless transceiver, etc.
[0158] At box 1710, a network device (or a portion thereof) may receive one or more first messages (e.g., one or more informational messages, as described above) from one or more vehicles away from the network device. Each of the one or more first messages includes vehicle information associated with a corresponding vehicle in the one or more vehicles. In some aspects, the vehicle information includes: the positioning of each corresponding vehicle in the one or more vehicles, the accuracy of the positioning, the direction of each corresponding vehicle, the speed of each corresponding vehicle, one or more capabilities of each corresponding vehicle, a message filtering request for each corresponding vehicle, a safety warning from each corresponding vehicle, any combination thereof, and / or other information associated with a vehicle from the one or more vehicles. In some cases, the one or more capabilities may include: the processing capability of each corresponding vehicle, the thermal state of each corresponding vehicle, the health state of each corresponding vehicle, any combination thereof, and / or other capabilities. In some examples, the safety warning is a reverse overtaking warning (DNPW), a forward collision warning (FCW), and / or any other type of safety warning.
[0159] At block 1720, the network device (or a portion thereof) may determine the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with a corresponding recipient vehicle in one or more recipient vehicles of one or more second messages (e.g., one or more response messages, as described above). The one or more recipient vehicles are away from the network device. In some aspects, the characteristic associated with each corresponding recipient vehicle in the one or more recipient vehicles includes: a quality of service associated with each corresponding recipient vehicle in the one or more recipient vehicles, one or more performance parameters associated with the one or more recipient vehicles, a combination thereof, and / or other characteristics associated with each recipient vehicle. In some aspects, the quality of service includes a message priority. For example, in such an example, the network device (or a portion thereof) may send (or output for sending) one or more second messages to at least one recipient vehicle with a higher message priority level in the one or more recipient vehicles, and then send (or output for sending) one or more second messages to at least another recipient vehicle with a lower message priority level in the one or more recipient vehicles. . In some examples, the one or more performance parameters include an end-to-end latency threshold and / or a message age threshold. For example, as described herein, the end-to-end latency threshold specifies a threshold amount of time between a time when the one or more second messages are sent and a time when the one or more second messages are received. As further described herein, the message age threshold specifies a threshold amount of message age from each respective recipient vehicle.
[0160] In some cases, the characteristics associated with each respective recipient vehicle also include: the location of each respective recipient vehicle, the accuracy of the location, the speed of each respective recipient vehicle, one or more capabilities of each respective recipient vehicle, message filtering requests of each respective recipient vehicle, safety warnings from each respective recipient vehicle (e.g., DNPW, FCW, and / or other types of safety warnings), combinations thereof, and / or other characteristics associated with each respective recipient vehicle. In some examples, the one or more capabilities of each respective recipient vehicle include: the processing capabilities of each respective recipient vehicle, the thermal state of each respective recipient vehicle, the health state of each respective recipient vehicle, any combination thereof, and / or other capabilities.
[0161] In some aspects, the network device (or a portion thereof) may further determine one or more recipient vehicles of the one or more second messages based on additional information associated with each respective recipient vehicle in the one or more recipient vehicles. For example, the additional information may include weather information, traffic information, lighting condition information, road topology information, preference information (e.g., a preference of a particular vehicle on whether to receive informational messages from other vehicles), obstacle information, any combination thereof, and / or other information.
[0162] In some aspects, the network device (or a portion thereof) may generate a dynamic neighbor list (also referred to as a local dynamic map (LDM), as previously mentioned) for each of the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and based on characteristics associated with the one or more recipient vehicles. In some aspects, the network device (or a portion thereof) may generate a dynamic neighbor list (or LDM) 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 recipient vehicles. As previously described, the network device (or a portion thereof) may determine one or more recipient vehicles of one or more second messages using a neighbor list generated for one or more recipient vehicles and / or a neighbor list generated for one or more vehicles that sent one or more first messages (e.g., informational messages). In one example, the network device (or a portion thereof) may determine the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a dynamic neighbor list generated for each of the one or more recipient vehicles of the one or more second messages. In another aspect, the network device (or a portion thereof) may determine the one or more recipient vehicles based on at least a portion of the vehicle information and a dynamic neighbor list generated for each of the one or more recipient vehicles.
[0163] At box 1730, the network device (or part thereof) may send one or more second messages to (or output for) the one or more receiving vehicles. In some aspects, the one or more first messages and the one or more second messages are vehicle-based messages. For example, one or more first messages may include basic safety messages (BSM), collaborative awareness messages (CAM), sensor data sharing messages (SDSM), any combination thereof, and / or other vehicle-based messages. In some cases, the network device (or part thereof) may send one or more second messages to (or output for) the one or more receiving vehicles via a network entity (e.g., via a Uu interface). The network device (or part thereof) may also receive one or more first messages via a Uu interface. For example, the network entity may be a base station (e.g., gNB, eNB, etc.) or a part thereof (e.g., CU, DU, RU, near RT RIC or non-RT RIC). In some cases, as described herein, the network device (e.g., MEC) and the network entity (e.g., base station or part thereof) are far away 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 portion thereof) are co-located with each other. For example, where the network device and the network entity are co-located, the one or more receiving vehicles are within the communication range of the network device. In another example, where the network device and the network entity are remote from each other, the one or more receiving vehicles are within the communication range of the network entity.
[0164] In some examples, the network device (or a portion thereof) may 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 respective recipient vehicle in the one or more recipient vehicles. For example, the network device (or a portion thereof) may bundle multiple messages from one or more second messages for sending to the recipient vehicle (e.g., by bundling related messages of the same recipient vehicle) based on the multiple messages coming from at least one vehicle in the dynamic neighbor list of the recipient vehicle, based on the quality of service associated with the multiple messages, based on the content of the multiple messages, any combination thereof, and / or based on other factors. The network device (or a portion thereof) may send one or more second messages to (or output for sending to) the one or more recipient vehicles by sending the bundled messages to (or output for sending to) the one or more recipient vehicles.
[0165] Although each example is described with respect to process 1700 using a vehicle as an illustrative example of a device from which one or more first messages (e.g., informational messages) are received and a recipient device determined to receive a response message, process 1700 is also applicable to other types of recipient devices (e.g., a recipient RSU, a recipient pedestrian device / UE, a recipient networked infrastructure device, etc.) in addition to or in lieu of a recipient vehicle. For example, the network device (or a portion thereof) may determine the one or more recipient user devices based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with each of the one or more recipient user devices of the one or more second messages. The network device (or a portion thereof) may send one or more second messages to the one or more recipient user devices. In another example, the network device (or a portion thereof) may receive one or more first messages (or other messages) from one or more user devices other than a vehicle, wherein each of the messages from the one or more user devices includes a characteristic associated with each of the user devices.
[0166] Fig.18 is a diagram illustrating an example of a system for implementing certain aspects of the disclosed technology. Specifically, Fig.18 An example of a computing system 1800 is illustrated, which may be any computing device, for example, constituting an internal computing system, a remote computing system, a camera, or any components thereof, wherein the components of the system communicate with each other using a connection 1805. The connection 1805 may be a physical connection using a bus, or a direct connection into the processor 1810, such as in a chipset architecture. The connection 1805 may also be a virtual connection, a networked connection, or a logical connection.
[0167] In some aspects, computing system 1800 is a distributed system in which the functionality described in the present disclosure may be distributed within a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more of the described system components represent a number of such components that each perform some or all of the functionality that the component is described for. In some aspects, each component may be a physical or virtual device.
[0168] The example system 1800 includes at least one processing unit (CPU or processor) 1810 and connections 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 the processor 1810. The computing system 1800 may include a cache 1812 of high-speed memory directly connected to, in close proximity to, or integrated as part of the processor 1810.
[0169] Processor 1810 may include any general purpose processor and hardware or software services, such as services 1832, 1834, and 1836 stored in storage device 1830, that are configured to control processor 1810 as well as a dedicated processor where software instructions are incorporated into the actual processor design. Processor 1810 may essentially be a completely independent computing system containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.
[0170] To enable user interaction, the computing system 1800 includes an input device 1845 that can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, voice, etc. The computing system 1800 may also include an output device 1835 that can be one or more of a plurality of output mechanisms. In some examples, a multimodal system may enable a user to provide multiple types of input / output to communicate with the computing system 1800.
[0171] The computing system 1800 may include a communication interface 1840, which may generally govern and manage user input and system output. The communication interface may perform or facilitate receiving and / or sending wired or wireless communications using wired and / or wireless transceivers, including using an audio jack / plug, a microphone jack / plug, a Universal Serial Bus (USB) port / plug, an Apple TM Lightning TM Ports / plugs, Ethernet ports / plugs, Fiber optic ports / plugs, Dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal transmission, Bluetooth TM Wireless signal transmission, Bluetooth TM Low Energy (BLE) wireless signal transmission, IBEACON TMWireless signaling, radio frequency identification (RFID) wireless signaling, near field communication (NFC) wireless signaling, dedicated short range communication (DSRC) wireless signaling, 802.11 Wi-Fi wireless signaling, wireless local area network (WLAN) signaling, visible light communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), infrared (IR) communication wireless signaling, public switched telephone network (PSTN) signaling, integrated services digital network (ISDN) signaling, ad hoc network signaling, radio wave signaling, microwave signaling, infrared signaling, visible light signaling, ultraviolet light signaling, wireless signaling along the electromagnetic spectrum, or some combination thereof. The communication interface 1840 may also include one or more global navigation satellite system (GNSS) receivers or transceivers for determining the location of the computing system 1800 based on receiving one or more signals from one or more satellites associated with one or more 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 Europe's Galileo GNSS. There is no restriction to operating on any particular hardware arrangement, and thus the base features herein may be easily substituted for improved hardware or firmware arrangements as they are developed.
[0172] The storage device 1830 may be a non-volatile and / or non-transitory and / or computer-readable memory device and may be a hard disk or other type of computer-readable medium that can store data accessible by a computer, such as a magnetic cassette, a flash memory card, a solid-state memory device, a digital versatile disk, a cassette, a floppy disk, a floppy disk, a hard disk, a magnetic tape, a magnetic stripe / magnetic stripe, any other magnetic storage medium, flash memory, a memristor memory, any other solid-state memory, a compact disk-read only memory (CD-ROM) optical disk, a rewritable compact disk (CD) optical disk, a digital video disk (DVD) optical disk, a Blu-ray disc (BDD) optical disk, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Card, or a memory card. card, a smart card chip, an EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, 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 (FLASH EPROM), a cache memory (e.g., a layer 1 (L1) cache, a layer 2 (L2) cache, a layer 3 (L3) cache, a layer 4 (L4) cache, a layer 5 (L5) cache, other (L#) cache), a resistive random access memory (RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (STT-RAM), another memory chip or box, and / or a combination thereof.
[0173] Storage device 1830 may include software services, servers, services, etc., which, when the code defining such software is executed by processor 1810, causes the system to perform functions. In some aspects, hardware services that perform specific functions may include software components for performing functions stored in a computer-readable medium connected to necessary hardware components such as processor 1810, connector 1805, output device 1835, etc. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data may be stored and does not include carrier waves and / or transient electronic signals that propagate wirelessly or over a wired connection. Examples of non-transitory media may include, but are not limited to, disks or tapes, optical storage media (such as compact discs (CDs) or digital versatile discs (DVDs)), flash memory, memory, or memory devices. Computer readable media may store thereon code and / or machine executable instructions, which may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, category, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, independent variables, parameters, or memory contents. Information, independent variables, parameters, data, etc. may be passed, forwarded, or sent via any suitable means, including memory sharing, message receiving and sending, token passing, network sending, etc.
[0174] Specific details are provided in the above description to provide a thorough understanding of the various aspects and each example provided herein, but those skilled in the art will recognize that the application is not limited thereto. Therefore, although the exemplary aspects of the present application have been described in detail herein, it is to be understood that each inventive concept can be implemented and adopted in various other ways, and the appended claims are not intended to be interpreted as including these variations, unless limited by the prior art. The various features and aspects of the above-mentioned applications can be used individually or jointly. In addition, the various aspects can be utilized in any number of environments and applications beyond those described herein without departing from the broader essence and scope of this specification. Therefore, the description and the accompanying drawings should be considered as illustrative rather than restrictive. For the purpose of illustration, each method is described in a specific order. It should be appreciated that, in alternative aspects, each method can be performed in an order different from the described order.
[0175] For clarity of explanation, in some instances, the present technology may be presented as including separate functional blocks, which include devices, device components, steps or routines in the method embodied in software or a combination of hardware and software. Additional components other than those components shown in the drawings 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 to avoid confusing these aspects in unnecessary details. In other instances, known circuits, processes, algorithms, structures and techniques may be shown without unnecessary details to avoid confusing various aspects.
[0176] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits, and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits, and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed for the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0177] Individual aspects may be described above as processes or methods, which are depicted as flow charts, flow diagrams, data flow diagrams, structure diagrams, or block diagrams. Although flow charts may describe operations as sequential processes, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. The process is terminated when the operations of the process are completed, but the process may have additional steps not included in the accompanying drawings. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, the termination of the process may correspond to the function returning to the calling function or main function.
[0178] The processes and methods according to the above examples can be implemented using stored computer executable instructions or otherwise obtained from computer readable media. These instructions may include, for example, instructions and data that cause or otherwise configure a general-purpose computer, a special-purpose computer, or a processing device to perform a certain function or group of functions. Parts of the computer resources used can be accessed through a network. Computer executable instructions can be, for example, binary, intermediate format instructions such as assembly language, firmware, source code. Examples of computer readable media that can be used to store instructions, information used, and / or information created during the method according to the described examples include disks or optical disks, flash memories, USB devices with non-volatile memory, networked storage devices, etc.
[0179] Examples of non-transitory media may include, but are not limited to, disks or tapes, optical storage media (such as compact discs (CDs) or digital versatile disks (DVDs)), flash memory, memory, or memory devices. Computer-readable media may store thereon code and / or machine-executable instructions, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, categories, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, independent variables, parameters, or memory contents. Information, independent variables, parameters, data, etc. may be passed, forwarded, or sent via any suitable means, including memory sharing, message reception and transmission, token passing, network transmission, etc. In some examples, computer-readable storage devices, media, and memory may include cables or wireless signals containing bit streams, etc. However, when mentioned, non-transitory computer-readable storage media explicitly exclude media such as power consumption, carrier signals, electromagnetic waves, and the signal itself.
[0180] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof in some cases, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.
[0181] Various illustrative logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may be implemented in any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks may be stored in a computer-readable or machine-readable medium. A processor may perform the necessary tasks. Examples of form factors include: laptops, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, stand-alone devices, and the like. The functionality described herein may also be embodied in peripheral devices or add-in cards. By way of further example, such functionality may also be implemented on circuit boards in different chips or different processes executed on a single device.
[0182] The instructions, the media for conveying such instructions, the computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functionality described in this disclosure.
[0183] The technology described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such technology may be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices, or integrated circuit devices with multiple uses, including applications in wireless communication devices, mobile phones, and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the technology may be implemented at least in part by a computer-readable data storage medium including a program code, which includes instructions for executing one or more of the above-mentioned methods, algorithms, and / or operations when executed. A computer-readable data storage medium may form part of a computer program product, which may include packaging materials. A computer-readable medium may include a memory or data storage medium, such as a random access memory (RAM) (such as a synchronous dynamic random access memory (SDRAM)), a read-only memory (ROM), a non-volatile random access memory (NVRAM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic or optical data storage medium, and the like. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer, such as a propagated signal or wave.
[0184] The program code may be executed by a processor, which may include 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 or discrete logic circuits. Such a processor may be configured to perform any of the techniques described in the present disclosure. A general-purpose processor may be a microprocessor; however, in an alternative, 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, the term "processor" as used herein may refer to any of the aforementioned structures, any combination of the aforementioned structures, or any other structure or device suitable for implementing the techniques described herein.
[0185] One of ordinary skill in the art will understand that the less than ("<") and greater than (">") symbols or terms used herein may be replaced with less than or equal to ("≤") and greater than or equal to ("≥") symbols, respectively, without departing from the scope of the present specification.
[0186] Where a component is described as being “configured to” perform certain operations, such configuration may be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., a microprocessor or other suitable electronic circuits) to perform the operations, or any combination thereof.
[0187] The phrase "coupled to" means that any component is directly or indirectly physically connected to another component, and / or any component is directly or indirectly in communication with another component (e.g., connected to another component via a wired or wireless connection and / or other suitable communication interface).
[0188] Claim language or other language reciting "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) satisfies the claim. For example, claim language reciting "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, claim language reciting "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, 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 listed in the set. For example, claim language reciting "at least one of A and B" or "at least one of A or B" may mean A, B, or A and B, and may additionally include items not listed in the set of A and B.
[0189] Illustrative aspects of the present disclosure include:
[0190] Aspect 1. A method for performing wireless communications at a network device, the method comprising: receiving one or more first messages at the network device from one or more vehicles remote from a device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle among the one or more vehicles; determining at the network device the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with a corresponding recipient vehicle among one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being remote from the device; and sending the one or more second messages at the network device to the one or more recipient vehicles.
[0191] 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.
[0192] Aspect 3. The method according to any one of aspects 1 or 2, wherein the one or more first messages include at least one of the following: a basic safety message (BSM) or a collaboration awareness message (CAM).
[0193] Aspect 4. A method according to any one of Aspects 1 to 3, wherein the network device is a multi-access edge computing (MEC) device.
[0194] Aspect 5. A method according to any one of Aspects 1 to 4, wherein the vehicle information includes at least one of the following: the positioning of each corresponding vehicle among the one or more vehicles, the accuracy of the positioning, the direction of each corresponding vehicle, the speed of each corresponding vehicle, one or more capabilities of each corresponding vehicle, a message filtering request for each corresponding vehicle, or a safety warning from each corresponding vehicle.
[0195] Aspect 6. The method according to aspect 5, wherein the one or more capabilities include at least one of the following: a processing capability of each respective vehicle, a thermal state of each respective vehicle, or a health state of each respective vehicle.
[0196] Aspect 7. The method according to any one of aspects 5 or 6, wherein the safety warning comprises at least one of the following: Direct National Park Warning (DNPW) or Forward Collision Warning (FCW).
[0197] Aspect 8. A method according to any one of Aspects 1 to 7, wherein the one or more recipient vehicles of the one or more second messages are further determined based on additional information associated with each corresponding recipient vehicle among the one or more recipient vehicles, the additional information including at least one of the following: weather information, traffic information, lighting condition information, road topology information, preference information, or obstacle information.
[0198] Aspect 9. The method according to any one of Aspects 1 to 8 further includes: generating a dynamic neighbor list for each of the one or more recipient 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 the one or more recipient vehicles, wherein determining the one or more recipient vehicles of the one or more second messages includes: determining the one or more recipient vehicles based on the 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 recipient vehicles.
[0199] Aspect 10. The method according to any one of Aspects 1 to 9 further includes: 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 corresponding recipient vehicle of the one or more recipient vehicles, wherein determining the one or more recipient vehicles of the one or more second messages includes: determining the one or more recipient vehicles based on the at least a portion of the vehicle information and the dynamic neighbor list generated for each of the one or more recipient vehicles.
[0200] Aspect 11. A method according to any one of Aspects 1 to 10, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles include at least one of the following: quality of service associated with each respective recipient vehicle among the one or more recipient vehicles or one or more performance parameters associated with the one or more recipient vehicles.
[0201] Aspect 12. A method according to Aspect 11, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles also include at least one of the following: the positioning of each respective recipient vehicle, the accuracy of the positioning, the speed of each respective recipient vehicle, one or more capabilities of each respective recipient vehicle, a message filtering request made by each respective recipient vehicle, or a safety warning from each respective recipient vehicle.
[0202] Aspect 13. A method according to Aspect 12, wherein the one or more capabilities of each respective recipient vehicle include at least one of: a processing capability of each respective recipient vehicle, a thermal state of each respective recipient vehicle, or a health state of each respective recipient vehicle.
[0203] Aspect 14. The method according to any one of aspects 12 or 13, wherein the safety warning comprises at least one of the following: Direct National Park Warning (DNPW) or Forward Collision Warning (FCW).
[0204] Aspect 15. A method according to any one of Aspects 11 to 14, wherein the quality of service includes message priority, and wherein the one or more second messages are transmitted to at least one of the one or more recipient vehicles having a higher message priority level, and then transmitted to at least another of the one or more recipient vehicles having a lower message priority level.
[0205] Aspect 16. The method according to any one of aspects 11 to 15, wherein the one or more performance parameters include at least one of the following: an end-to-end delay threshold or an information age threshold.
[0206] Aspect 17. The method according to aspect 16, wherein the end-to-end latency threshold specifies a threshold amount of time between a time when the one or more second messages are sent and a time when the one or more second messages are received.
[0207] Aspect 18. A method according to any one of aspects 16 or 17, wherein the information age threshold specifies a threshold amount of information age from each respective recipient vehicle.
[0208] Aspect 19. The method according to any one of Aspects 1 to 18 further includes: bundling at least some 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 corresponding recipient vehicle among the one or more recipient vehicles; wherein sending the one or more second messages to the one or more recipient vehicles includes: sending at least some of the second messages bundled in the one or more second messages to the one or more recipient vehicles.
[0209] Aspect 20. A method according to Aspect 19, wherein bundling at least some of the one or more second messages includes: bundling multiple messages from the one or more second messages for sending to a receiving vehicle based on at least one of the following: the multiple messages are from at least one vehicle in a dynamic neighbor list of the receiving vehicle, the quality of service associated with the multiple messages, or the content of the multiple messages.
[0210] Aspect 21. The method according to any one of aspects 1 to 20, wherein the one or more second messages are sent to the one or more recipient vehicles via a network entity.
[0211] Aspect 22. The method according to aspect 21, wherein the network entity is a base station.
[0212] Aspect 23. The method according to aspect 22, wherein the base station is one of the following: a gNodeB (gNB) or an evolved NodeB (eNB).
[0213] Aspect 24. A method according to any one of Aspects 21 to 23, wherein the network device and the network entity are one of remote from each other or co-located, wherein when the network device and the network entity are co-located, the one or more receiving vehicles are within the communication range of the network device, or wherein when the network device and the network entity are remote from each other, the one or more receiving vehicles are within the communication range of the network entity.
[0214] Aspect 25. A method according to any one of Aspects 1 to 24, wherein the one or more first messages are received via a wide area network (Uu) interface, and wherein the one or more second messages are sent via the Uu interface.
[0215] Aspect 26. The method according to any one of Aspects 1 to 25 further includes: determining the one or more recipient user devices based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with each of the one or more recipient user devices of the one or more second messages; and sending the one or more second messages to the one or more recipient user devices.
[0216] Aspect 27. The method according to any one of Aspects 1 to 26 further includes: receiving one or more third messages from one or more user devices, wherein each of the messages from the one or more user devices includes characteristics associated with each of the one or more user devices.
[0217] Aspect 28. A device for wireless communication, comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and configured to: receive one or more first messages from one or more vehicles remote from the device, wherein each of the one or more first messages includes vehicle information associated with a corresponding vehicle among the one or more vehicles; determine the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with a corresponding recipient vehicle among one or more recipient vehicles of one or more second messages, the one or more recipient vehicles being remote from the device; and output the one or more second messages for sending to the one or more recipient vehicles.
[0218] 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.
[0219] Aspect 30. An apparatus according to any one of aspects 28 or 29, wherein the one or more first messages include at least one of the following: a basic safety message (BSM) or a collaboration awareness message (CAM).
[0220] Aspect 31. An apparatus according to any one of Aspects 28 to 30, wherein the apparatus is a multi-access edge computing (MEC) device.
[0221] Aspect 32. An apparatus according to any one of Aspects 28 to 31, wherein the vehicle information includes at least one of the following: the positioning of each corresponding vehicle among the one or more vehicles, the accuracy of the positioning, the direction of each corresponding vehicle, the speed of each corresponding vehicle, one or more capabilities of each corresponding vehicle, a message filtering request for each corresponding vehicle, or a safety warning from each corresponding vehicle.
[0222] Aspect 33. An apparatus according to Aspect 32, wherein the one or more capabilities include at least one of the following: a processing capability of each respective vehicle, a thermal state of each respective vehicle, or a health state of each respective vehicle.
[0223] Aspect 34. An apparatus according to any one of Aspects 32 or 33, wherein the safety warning comprises at least one of: a Direct National Passing Warning (DNPW) or a Forward Collision Warning (FCW).
[0224] Aspect 35. An apparatus according to any one of Aspects 28 to 34, wherein the one or more recipient vehicles of the one or more second messages are further determined based on additional information associated with each corresponding recipient vehicle among the one or more recipient vehicles, the additional information comprising at least one of: weather information, traffic information, lighting condition information, road topology information, preference information, or obstacle information.
[0225] Aspect 36. An apparatus according to any one of Aspects 28 to 35, wherein the at least one processor is configured to: generate a dynamic neighbor list for each of the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and based on characteristics associated with the one or more recipient vehicles; and determine the one or more recipient vehicles based on the 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 recipient vehicles.
[0226] Aspect 37. An apparatus according to any one of Aspects 28 to 36, wherein the at least one processor is configured to: generate 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 respective recipient vehicle of the one or more recipient vehicles; and determine the one or more recipient vehicles based on the at least a portion of the vehicle information and the dynamic neighbor list generated for each of the one or more recipient vehicles.
[0227] Aspect 38. An apparatus according to any one of Aspects 28 to 37, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles include at least one of the following: quality of service associated with each respective recipient vehicle among the one or more recipient vehicles or one or more performance parameters associated with the one or more recipient vehicles.
[0228] Aspect 39. An apparatus according to Aspect 38, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles also include at least one of: the positioning of each respective recipient vehicle, the accuracy of the positioning, the speed of each respective recipient vehicle, one or more capabilities of each respective recipient vehicle, a message filtering request made by each respective recipient vehicle, or a safety warning from each respective recipient vehicle.
[0229] Aspect 40. An apparatus according to Aspect 39, wherein the one or more capabilities of each respective recipient vehicle include at least one of: a processing capability of each respective recipient vehicle, a thermal state of each respective recipient vehicle, or a health state of each respective recipient vehicle.
[0230] Aspect 41. An apparatus according to any one of Aspects 39 or 40, wherein the safety warning comprises at least one of: a Direct National Passing Warning (DNPW) or a Forward Collision Warning (FCW).
[0231] Aspect 42. An apparatus according to any one of Aspects 38 or 41, wherein the quality of service includes message priority, and wherein the at least one processor is configured to output the one or more second messages for sending to at least one recipient vehicle among the one or more recipient vehicles having a higher message priority level, and then to at least another recipient vehicle among the one or more recipient vehicles having a lower message priority level.
[0232] Aspect 43. An apparatus according to any one of Aspects 38 to 42, wherein the one or more performance parameters include at least one of: an end-to-end delay threshold or an information age threshold.
[0233] Aspect 44. An apparatus according to aspect 43, wherein the end-to-end latency threshold specifies a threshold amount of time between a time at which the one or more second messages are sent and a time at which the one or more second messages are received.
[0234] Aspect 45. An apparatus according to any one of Aspects 43 or 44, wherein the information age threshold specifies a threshold amount of information age from each respective recipient vehicle.
[0235] Aspect 46. An apparatus according to any one of Aspects 28 or 45, wherein the at least one processor is configured to bundle at least some 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 corresponding recipient vehicle among the one or more recipient vehicles; wherein in order to output the one or more second messages for sending to the one or more recipient vehicles, the at least one processor is configured to output at least some of the second messages bundled in the one or more second messages for sending to the one or more recipient vehicles.
[0236] Aspect 47. An apparatus according to Aspect 46, wherein in order to bundle at least some of the one or more second messages, the at least one processor is configured to: bundle multiple messages from the one or more second messages for sending to a receiving vehicle based on at least one of the following: the multiple messages are from at least one vehicle in a dynamic neighbor list of the receiving vehicle, the quality of service associated with the multiple messages, or the content of the multiple messages.
[0237] Aspect 48. An apparatus according to any one of Aspects 28 to 47, wherein the at least one processor is configured to output the one or more second messages for transmission to the one or more recipient vehicles via a network entity.
[0238] Aspect 49. The apparatus of aspect 48, wherein the network entity is a base station.
[0239] Aspect 50. The apparatus according to aspect 49, wherein the base station is one of the following: a gNodeB (gNB) or an evolved NodeB (eNB).
[0240] Aspect 51. An apparatus according to any one of Aspects 48 to 50, wherein the apparatus and the network entity are either remote from each other or co-located, wherein when the network device and the network entity are co-located, the one or more recipient vehicles are within the communication range of the network device, or wherein when the network device and the network entity are remote from each other, the one or more recipient vehicles are within the communication range of the network entity.
[0241] Aspect 52. An apparatus according to any one of Aspects 28 to 51, wherein the one or more first messages are received via a wide area network (Uu) interface, and wherein the one or more second messages are sent via the Uu interface.
[0242] Aspect 53. An apparatus according to any one of Aspects 28 to 52, wherein the apparatus is configured as a network entity and further comprises: a transceiver configured to receive the one or more first messages and to send the one or more second messages to the one or more recipient vehicles.
[0243] Aspect 54. A method according to any one of Aspects 28 to 53, wherein the at least one processor is configured to: determine the one or more recipient user devices based on at least a portion of the vehicle information from the one or more first messages and characteristics associated with each of the one or more recipient user devices of one or more second messages; and output the one or more second messages for sending to the one or more recipient user devices.
[0244] Aspect 55. A method according to any one of Aspects 28 to 54, wherein the at least one processor is configured to: receive one or more third messages from one or more user devices, wherein each of the messages from the one or more user devices includes characteristics associated with each of the one or more user devices.
[0245] Aspect 56. A non-transitory computer-readable medium of a network entity having instructions stored thereon, the instructions, when executed by one or more processors, causing the one or more processors to perform operations according to any one of aspects 1 to 55.
[0246] Aspect 57. An apparatus for wireless communication, comprising: one or more components for performing the operations according to any one of Aspects 1 to 55.
[0247] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein elements mentioned in the singular are not intended to mean "one and only one", unless specifically stated so, but rather "one or more".
Claims
1. A method for wireless communication at a network device, the method include: receiving, at the network device, one or more first messages from one or more vehicles remote from the network device, wherein each of the one or more first messages includes vehicle information associated with a respective vehicle of the one or more vehicles; determining, at the network device, the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with each respective one of the one or more recipient vehicles of the one or more second messages, the one or more recipient vehicles being remote from the network device; as well as The one or more second messages are sent at the network device to the one or more recipient vehicles. 2 . The method of claim 1 , wherein the one or more first messages and the one or more second messages are vehicle-based messages. 3 . The method of claim 1 , wherein the one or more first messages include at least one of: a basic safety message (BSM) or a collaboration awareness message (CAM).
4. The method of claim 1, wherein the network device is a multi-access edge computing (MEC) device.
5. The method of claim 1, wherein the vehicle information comprises at least one of: the location of each respective vehicle among the one or more vehicles, the accuracy of the location, the direction of each respective vehicle, the speed of each respective vehicle, one or more capabilities of each respective vehicle, a message filtering request of each respective vehicle, or a safety warning from each respective vehicle. 6 . The method of claim 5 , wherein the one or more capabilities include at least one of: a processing capability of each respective vehicle, a thermal condition of each respective vehicle, or a health condition of each respective vehicle. 7 . The method of claim 5 , wherein the safety warning comprises at least one of: a Direct National Park Warning (DNPW) or a Forward Collision Warning (FCW).
8. The method of claim 1, wherein the one or more recipient vehicles of the one or more second messages are further determined based on additional information associated with each corresponding recipient vehicle among the one or more recipient vehicles, the additional information comprising at least one of: weather information, traffic information, lighting condition information, road topology information, preference information, or obstacle information.
9. The method according to claim 1, further comprising: include: A dynamic neighbor list is generated for each of the one or more recipient 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 respective recipient vehicle of the one or more recipient vehicles, wherein determining the one or more recipient vehicles of the one or more second messages includes: determining the one or more recipient vehicles based on the 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 recipient vehicles.
10. The method according to claim 1, further comprising: include: A dynamic neighbor list is generated 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 respective recipient vehicle of the one or more recipient vehicles, wherein determining the one or more recipient vehicles of the one or more second messages includes: determining the one or more recipient vehicles based on the at least a portion of the vehicle information and the dynamic neighbor list generated for each of the one or more recipient vehicles.
11. The method of claim 1 , wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles include at least one of: quality of service associated with each respective recipient vehicle among the one or more recipient vehicles or one or more performance parameters associated with the one or more recipient vehicles.
12. The method of claim 11, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles further include at least one of: the location of each respective recipient vehicle, the accuracy of the location, the speed of each respective recipient vehicle, one or more capabilities of each respective recipient vehicle, a message filtering request of each respective recipient vehicle, or a safety warning from each respective recipient vehicle.
13. The method of claim 12, wherein the one or more capabilities of each respective recipient vehicle include at least one of: a processing capability of each respective recipient vehicle, a thermal state of each respective recipient vehicle, or a health state of each respective recipient vehicle.
14. The method of claim 11, wherein the quality of service includes message priority, and wherein the one or more second messages are transmitted to at least one of the one or more recipient vehicles having a higher message priority level, and then transmitted to at least another of the one or more recipient vehicles having a lower message priority level.
15. The method of claim 11, wherein the one or more performance parameters include at least one of: an end-to-end delay threshold or an information age threshold.
16. The method of claim 15, wherein the end-to-end latency threshold specifies a threshold amount of time between a time at which the one or more second messages are sent and a time at which the one or more second messages are received.
17. The method of claim 15, wherein the message age threshold specifies a threshold amount of message age from each respective recipient vehicle.
18. The method according to claim 1, further comprising: include: bundling at least some 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 characteristic associated with each respective recipient vehicle of the one or more recipient vehicles; Wherein sending the one or more second messages to the one or more recipient vehicles comprises: sending at least some of the second messages bundled in the one or more second messages to the one or more recipient vehicles.
19. The method of claim 1, wherein at least some of the one or more second messages are bundled include: Multiple messages from the one or more second messages are bundled for transmission to a recipient vehicle based on at least one of: the multiple messages are from at least one vehicle in a dynamic neighbor list of the recipient vehicle, quality of service associated with the multiple messages, or content of the multiple messages.
20. The method of claim 1, wherein the one or more second messages are sent to the one or more recipient vehicles via a network entity.
21. The method of claim 20, wherein the network entity is a base station, the base station being one of: a gNodeB (gNB) or an evolved NodeB (eNB).
22. The method of claim 20, wherein the network device and the network entity are one of remote from each other or co-located, wherein in the case where the network device and the network entity are co-located, the one or more recipient vehicles are within the communication range of the network device, or wherein in the case where the network device and the network entity are remote from each other, the one or more recipient vehicles are within the communication range of the network entity.
23. The method of claim 1, wherein the one or more first messages are received over a wide area network (Uu) interface, and wherein the one or more second messages are sent over the Uu interface.
24. A device for wireless communication, the device include: at least one memory; and at least one processor coupled to the at least one memory and configured to: receiving one or more first messages from one or more vehicles remote from the apparatus, wherein each of the one or more first messages includes vehicle information associated with each respective vehicle of the one or more vehicles; determining the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and a characteristic associated with a respective one of the one or more recipient vehicles of the one or more second messages, the one or more recipient vehicles being remote from the device; as well as The one or more second messages are output for transmission to the one or more recipient vehicles.
25. The apparatus of claim 24, wherein the one or more first messages and the one or more second messages are vehicle-based messages.
26. The apparatus of claim 24, wherein the one or more first messages comprise at least one of: a basic safety message (BSM) or a collaboration awareness message (CAM).
27. The apparatus of claim 24, wherein the apparatus is a multi-access edge computing (MEC) device.
28. An apparatus according to claim 24, wherein the vehicle information includes at least one of the following: the location of each corresponding vehicle among the one or more vehicles, the accuracy of the location, the direction of each corresponding vehicle, the speed of each corresponding vehicle, one or more capabilities of each corresponding vehicle, a message filtering request for each corresponding vehicle, or a safety warning from each corresponding vehicle.
29. The apparatus of claim 28, wherein the one or more capabilities include at least one of: a processing capability of each respective vehicle, a thermal condition of each respective vehicle, or a health condition of each respective vehicle.
30. The apparatus of claim 28, wherein the safety warning comprises at least one of: a Direct National Park Warning (DNPW) or a Forward Collision Warning (FCW).
31. An apparatus according to claim 24, wherein the one or more recipient vehicles of the one or more second messages are further determined based on additional information associated with each corresponding recipient vehicle among the one or more recipient vehicles, the additional information comprising at least one of the following: weather information, traffic information, lighting condition information, road topology information, preference information, or obstacle information.
32. The apparatus of claim 24, wherein the at least one processor is configured to: generating a dynamic neighbor list for each of the one or more recipient vehicles based on at least a portion of the vehicle information from the one or more first messages and based on characteristics associated with the one or more recipient vehicles; and The one or more recipient vehicles are determined based on the 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 recipient vehicles.
33. The apparatus of claim 24, wherein the at least one processor is configured to: 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 respective recipient vehicle of the one or more recipient vehicles; and The one or more recipient vehicles are determined based on the at least a portion from the vehicle information and the dynamic neighbor list generated for each of the one or more recipient vehicles.
34. An apparatus according to claim 24, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles include at least one of the following: quality of service associated with each respective recipient vehicle among the one or more recipient vehicles or one or more performance parameters associated with the one or more recipient vehicles.
35. An apparatus according to claim 34, wherein the characteristics associated with each respective recipient vehicle among the one or more recipient vehicles also include at least one of: the positioning of each respective recipient vehicle, the accuracy of the positioning, the speed of each respective recipient vehicle, one or more capabilities of each respective recipient vehicle, a message filtering request of each respective recipient vehicle, or a safety warning from each respective recipient vehicle.
36. An apparatus according to claim 35, wherein the one or more capabilities of each respective recipient vehicle include at least one of: a processing capability of each respective recipient vehicle, a thermal state of each respective recipient vehicle, or a health state of each respective recipient vehicle.
37. An apparatus according to claim 34, wherein the quality of service includes message priority, and wherein the at least one processor is configured to output the one or more second messages for transmission to at least one of the one or more recipient vehicles having a higher message priority level, and then to at least another of the one or more recipient vehicles having a lower message priority level.
38. The apparatus of claim 34, wherein the one or more performance parameters include at least one of: an end-to-end latency threshold or an information age threshold.
39. The apparatus of claim 38, wherein the end-to-end latency threshold specifies a threshold amount of time between a time at which the one or more second messages are sent and a time at which the one or more second messages are received.
40. The apparatus of claim 38, wherein the message age threshold specifies a threshold amount of message age from each respective recipient vehicle.
41. The device according to claim 24, in: the at least one processor being configured to bundle at least some 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 characteristic associated with each respective recipient vehicle of the one or more recipient vehicles; In order to output the one or more second messages for transmission to the one or more recipient vehicles, the at least one processor is configured to output at least some of the second messages bundled in the one or more second messages for transmission to the one or more recipient vehicles.
42. The apparatus of claim 24, wherein to bundle at least some of the one or more second messages, the at least one processor is configured to: Multiple messages from the one or more second messages are bundled for transmission to a recipient vehicle based on at least one of: the multiple messages are from at least one vehicle in a dynamic neighbor list of the recipient vehicle, quality of service associated with the multiple messages, or content of the multiple messages.
43. The apparatus of claim 24, wherein the at least one processor is configured to output the one or more second messages for transmission to the one or more recipient vehicles via a network entity.
44. The apparatus of claim 43, wherein the network entity is a base station, the base station being one of: a gNodeB (gNB) or an evolved NodeB (eNB).
45. A device according to claim 43, wherein the device and the network entity are one of remote from each other or co-located, wherein when the device and the network entity are co-located, the one or more receiving vehicles are within the communication range of the device, or wherein when the device and the network entity are remote from each other, the one or more receiving vehicles are within the communication range of the network entity.
46. The apparatus of claim 24, wherein the one or more first messages are received over a wide area network (Uu) interface, and wherein the one or more second messages are sent over the Uu interface.
47. The apparatus of claim 24, wherein the apparatus is configured as a network entity, and the apparatus further include: A transceiver is configured to receive the one or more first messages and to transmit the one or more second messages to the one or more recipient vehicles.
