Geolocation of critical driver behavior and potential safety hazards

Abstract

Systems, apparatus, processes, and computer-readable media for wireless communication are disclosed. For example, an example of the process may include obtaining sensor data using one or more sensors of a vehicle. The processors may include determining, by one or more processors of the vehicle, an event based on the sensor data. The processors may also include determining, by one or more processors of the vehicle, a location of the vehicle associated with the event.

Description

Technical Field

[0001] The present disclosure generally relates to vehicle communication. For example, aspects of the present disclosure relate to the geolocation of key critical driver behavior and safety hazards. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology that is 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 the city, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to 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 can be based on the 4G Long Term Evolution (LTE) standard. Aspects of wireless communication can include direct communication between devices (such as devices in vehicle-to-everything (V2X), vehicle-to-vehicle (V2V), and / or device-to-device (D2D) communication). There is a need for further improvement in V2X, V2V, and / or D2D technologies. These improvements can also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0004] A simplified overview related to one or more aspects disclosed herein is presented below. Accordingly, the following overview should not be considered an extensive review related to all contemplated aspects, nor should the following overview be considered to identify key or critical elements related to all contemplated aspects or to depict the scope associated with any particular aspect. Accordingly, the sole purpose of the following overview is to present in a simplified form certain concepts related to one or more aspects of the mechanisms disclosed herein prior to the detailed description presented below.

[0005] Systems, apparatuses, methods, and computer-readable media for geolocating critical driver behaviors and safety hazards are disclosed. According to at least one example, a method for wireless communication is provided. The method includes: obtaining sensor data using one or more sensors of a vehicle; determining an event by one or more processors of the vehicle based on the sensor data; and determining a location of the vehicle associated with the event by one or more processors of the vehicle.

[0006] In another example, a device for processing image data is provided. The device includes at least one memory and at least one processor (e.g., implemented in a circuit) coupled to the at least one memory. The at least one processor is configured to: obtain sensor data using one or more sensors of a vehicle; determine an event based on the sensor data; and determine the location of the vehicle associated with the event.

[0007] In another example, a non-transitory computer-readable medium storing instructions is provided. The instructions, when executed by one or more processors, cause the one or more processors to: obtain sensor data using one or more sensors of a vehicle; determine an event based on the sensor data; and determine the location of the vehicle associated with the event.

[0008] In another example, a device for wireless communication is provided. The device includes: means for obtaining sensor data using one or more sensors of a vehicle; means for determining an event based on the sensor data; and means for determining the location of the vehicle associated with the event.

[0009] In some aspects, one or more of the devices described herein are a vehicle (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, a robotic device, or other devices, a part of or including these devices. In some aspects, the device includes 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 signals (e.g., at optical frequencies). In some aspects, the device includes one or more cameras for capturing one or more images. In some aspects, the device further includes a display for displaying one or more images, notifications, and / or other displayable data. In some aspects, the above-described device may include one or more sensors, and the one or more sensors may 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 not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to the entire specification of this patent, any or all of the drawings, and the appropriate portions of each claim.

[0011] Based on the drawings and the detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The illustrative aspects of the present application are described in detail below with reference to the following drawings:

[0013] Figure 1 is a diagram showing an example wireless communication system according to some aspects of the present disclosure.

[0014] Figure 2 is a diagram showing an example of a decomposed base station architecture according to some aspects of the present disclosure, which can be adopted by the disclosed system for geolocation of critical driver behaviors and safety hazards.

[0015] Figure 3 is a diagram showing examples of various user equipment (UE) communicating via a direct communication interface (e.g., a cellular-based PC5 sidelink interface, a DSRC interface defined by 802.11p, or other direct interfaces) and a wide area network (Uu) interface according to some aspects of the present disclosure.

[0016] Figure 4 is a block diagram showing an example of a computing system of a vehicle according to some aspects of the present disclosure.

[0017] Figure 5 is a block diagram showing an example of a computing system of a user equipment according to some aspects of the present disclosure.

[0018] Figure 6 is a diagram showing an example of devices involved in wireless communication (e.g., sidelink communication) according to some aspects of the present disclosure.

[0019] Figures 7A - 7D is a diagram showing an example of sensor sharing for a cooperative and automated driving system according to some aspects of the present disclosure.

[0020] Figure 8 is a diagram showing an example of sensor sharing for a cooperative and automated driving system according to some aspects of the present disclosure.

[0021] Figure 9 is a diagram showing an example of a system for sensor sharing in wireless communication (e.g., V2X communication) according to some aspects of the present disclosure.

[0022] Figure 10 A diagram showing an example of a vehicle-based message (shown as a sensor sharing message) according to some aspects of the present disclosure.

[0023] Figure 11 A diagram showing an example of a map of a system for geolocating critical driver behaviors and safety hazards according to some aspects of the present disclosure, where the map indicates the locations where driver drowsiness is sensed.

[0024] Figure 12 A diagram showing an example of a map of a system for geolocating critical driver behaviors and safety hazards according to some aspects of the present disclosure, where the map indicates the locations where driver distraction is sensed.

[0025] Figure 13 A diagram showing an example of a system for geolocating critical driver behaviors and safety hazards according to some aspects of the present disclosure.

[0026] Figure 14A and Figure 14B A table showing an example of the values and uses of data points of interest associated with an event (e.g., driver misconduct or safety hazard) according to some aspects of the present disclosure.

[0027] Figure 15A A flowchart showing an example of a process for wireless communication according to some aspects of the present disclosure.

[0028] Figure 15B A flowchart showing another example of a process for wireless communication according to some aspects of the present disclosure.

[0029] Figure 16 Shows an example computing system according to aspects of the present disclosure. Detailed Description

[0030] For illustrative purposes, certain aspects of the present disclosure are provided below. Alternative aspects may be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure. Some aspects described herein may be applied independently, and some of them may be applied in combination, which will be apparent to those skilled in the art. In the following description, for purposes of explanation, specific details are set forth in order to provide a thorough understanding of the aspects of the present application. However, it will be apparent that the aspects may be practiced without these specific details. The drawings and description are not intended to be restrictive.

[0031] The following description provides only example aspects and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the following description of example aspects will provide those skilled in the art with an enabling description for implementing the example aspects. It should be understood that various changes may be made to the functionality and arrangement of the elements without departing from the spirit and scope of the application as set forth in the appended claims.

[0032] 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 advantageous over other aspects. Similarly, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0033] Wireless communication systems are deployed to provide various telecommunication services including telephony, video, data, messaging, broadcasting, etc. Wireless communication systems have evolved through different generations. The fifth generation (5G) mobile standards require higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. The 5G standards according to the Next Generation Mobile Networks Alliance (also known as “New Radio” or “NR”) are designed to provide data rates of tens of megabits per second to each of tens of thousands of users.

[0034] A transportation vehicle is an example of a system that can include wireless communication capabilities. For example, a transportation vehicle (e.g., a motor vehicle, an autonomous vehicle, an aircraft, a marine vessel, etc.) can communicate with other transportation vehicles and / or with other devices having wireless communication capabilities. A wireless transportation vehicle communication system includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-grid (V2G) communication (e.g., data going into the power grid, such as for active management of energy in an electric transportation vehicle or other electric devices or systems), and these communications are collectively referred to as vehicle-to-everything (V2X) communication. V2X communication is a transportation vehicle communication system that supports wireless transfer of information from one transportation vehicle to other entities within a transportation system that may affect that transportation vehicle (e.g., other transportation vehicles, pedestrians with smart phones, equipped vulnerable road users (VRUs) such as bicyclists, and / or other transportation infrastructure). The main purposes of V2X technology are to improve road safety, fuel savings, and traffic efficiency.

[0035] In a V2X communication system, information is transmitted via a wireless link from vehicle sensors (and other sources) to allow the information to be communicated to other vehicles, pedestrians, VRUs, and / or traffic infrastructure. The information may be transmitted using one or more vehicle-based messages (such as cellular-vehicle-to-everything (C-V2X) messages), and the vehicle-based messages may include Sensor Data Sharing Message (SDSM), Basic Safety Message (BSM), Cooperative Awareness Message (CAM), Collective Perception Message (CPM), Decentralized Environmental Message (DENM), and / or other types of vehicle-based messages. By sharing this information with other vehicles, V2X technology improves the awareness of vehicles (and drivers) of potential hazards to help reduce collisions with other vehicles and entities. In addition, V2X technology enhances traffic efficiency by providing vehicles with traffic warnings of potential upcoming road hazards and obstacles so that the vehicles can select alternative traffic routes.

[0036] As previously described, V2X technology includes V2V communication, which can also be referred to as peer-to-peer communication. V2V communication allows vehicles to communicate wirelessly directly with each other while on the move. With V2V communication, vehicles can obtain situational awareness by receiving information about upcoming road hazards (e.g., unforeseen oncoming vehicles, accidents, and road conditions) from other vehicles.

[0037] The IEEE 802.11p standard supports the use of dedicated short-range communication (DSRC) interfaces for V2X wireless communication. The characteristics of the DSRC interface based on IEEE 802.11p include low latency and the use of the unlicensed 5.9 gigahertz (GHz) band. Cellular Vehicle-to-Everything (C-V2X) is adopted as an alternative to wireless communication using the DSRC interface based on IEEE 802.11p. The 5G Automotive 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 operation modes. One of the operation modes allows direct wireless communication between vehicles through the LTE sidelink PC5 interface. Similar to the DSRC interface based on IEEE 802.11p, the LTE C-V2X sidelink PC5 interface operates in the 5.9 GHz band. Vehicle-based messages, such as Basic Safety Messages (BSMs) and Cooperative Awareness Messages (CAMs), are designed to be wirelessly broadcast through the DSRC interface based on 802.11p and the LTE C-V2X sidelink PC5 interface.

[0038] Currently, driver misbehavior (e.g., distracted or sleepy drivers) and road safety hazards (e.g., road potholes) are the main causes of traffic accidents and fatalities. Driver misbehavior that can lead to collisions can include, but is not limited to, distraction, drowsiness, looking at an object inside the vehicle that is not related to driving, looking at an object outside the vehicle that is not related to driving, looking at a specific part of the telematics control unit (TCU) display, having both hands off the steering wheel for a predefined duration, frequent head turning, eating, drinking, smoking, texting, browsing, attempting to make a call on a mobile phone, frequent interaction with passengers in the vehicle, singing, moving to music, grooming, reaching for an object inside the vehicle, sudden braking, frequent braking, and dangerous driving. Driver distraction and road safety hazards can increase the chances of collisions with other vehicles, pedestrians, and Vulnerable Road Users (VRUs). Not only will the vehicles, pedestrians, and VRUs being hit be affected by the collision, but also the drivers of the vehicles experiencing road safety hazards and the distracted drivers themselves are at risk of being affected by a vehicle collision.

[0039] In today's industry, there are existing driver misbehavior detection systems that are designed to detect these hazards and generate alert messages regarding the detected hazards. However, these systems do not correlate driver misbehavior or road safety hazards on a map with the location of the vehicle when the driver misbehavior or road safety hazard occurs to determine trends that can be used to predict future driver misbehavior or anticipate road safety hazards to avoid future accidents. There are also other solutions available, including post-accident assessments. However, these solutions do not quantify the frequency of near-miss events (e.g., occurrences of driver distraction and / or drowsiness that could lead to an accident), and the frequency of near-miss events can be used to understand the causes of near-miss events and thus enable the prevention of potential future accidents.

[0040] Systems and techniques are provided for optimizing the situational awareness of driver misbehavior and road safety hazards that can lead to traffic collisions. The systems and techniques can provide awareness to vehicles, pedestrians with smartphones, traffic infrastructure, government municipalities, businesses, and / or other entities. For example, in one or more aspects, the systems and techniques can aggregate actionable crowdsourced data related to driver state (e.g., driver misbehavior and / or safety hazards in the environment). Government municipalities (e.g., managing traffic infrastructure) and marketing companies (e.g., insurance companies) can use trends in the aggregated crowdsourced data to understand driver misbehavior and road safety hazards on the road.

[0041] For example, driver condition data or information (e.g., driver misbehavior, such as driver distraction) can be collected via a vision-based system (e.g., including sensors such as cameras) located inside the vehicle (e.g., passenger compartment) and can be correlated with time and geolocation. The data can be normalized, structured, and analyzed (e.g., using statistical analysis and / or machine learning) to determine actionable trends. In one or more examples, a municipality (e.g., a government agency such as a department of transportation) can improve traffic infrastructure at "hotspots" (e.g., locations) that are determined to have low visibility and are thus potentially prone to vehicle accidents. In some examples, an auto insurance company can determine a driver accident risk based on the time of day, location, and driver condition (e.g., drowsiness, distraction, and / or driver body movements such as eating or drinking). In one or more examples, crowdsourced data can assist autonomous vehicles in optimizing their driving style to be more similar to that of a human driver familiar with the road conditions.

[0042] In one or more aspects, the systems and techniques can fuse the context of the driver's condition (e.g., detected by a vision-based system) with information associated with the vehicle's location (e.g., geolocation) to determine trends. For example, driver drowsiness can lead to damages (e.g., to the vehicle, other vehicles, and / or the vehicle's surroundings), accidents, and fatalities. By understanding the "hot spots" (e.g., locations) in the transportation infrastructure, preventive actions can be taken. For example, if a large number of drowsiness events occur at a particular time and location, then the transportation infrastructure can be modified to address the underlying causes of drowsiness. As another example, if highly distracting events repeatedly occur at certain intersections, actions can be taken to remove the potential objects that cause distraction (e.g., billboard advertisements).

[0043] In one or more aspects, such as during operation of a vehicle, one or more sensors of the vehicle can perform sensing to obtain sensor data. The sensors can be located inside and / or outside the vehicle. One or more processors of the vehicle can determine that an event has occurred based on the obtained sensor data. In some aspects, the event can be driver misconduct (e.g., driver distraction or drowsiness) of the vehicle's driver or a safety hazard (e.g., a safety hazard in the environment, such as the vehicle hitting an object in or around the road, e.g., a pothole). In one or more aspects, one or more processors of the vehicle can determine the location of the vehicle when the event occurs. In some aspects, one or more processors of the vehicle can determine the characteristics of the event, such as the driver's gaze angle or the type of the event (e.g., a drowsy driver). In some aspects, one or more processors of the vehicle (e.g., the vehicle's on-board unit) or another device (e.g., a user device, such as a smartphone or a server) can associate the location of the event with a location on a map. The map can include a rendering of the area surrounding the location of the event and the locations of previously occurred events. One or more processors of the vehicle (or another device) can determine similar events that have occurred around the location of the event based on the map (e.g., and the characteristics of the event). One or more processors of the vehicle (or another device) can analyze the data in the map (e.g., perform statistical analysis and / or machine learning on the data in the map) to determine trends based on the event and the determined similar events. In one or more aspects, the vehicle can send a message related to the event (e.g., an alert message, an event report, and / or a marketing message) based on the trend.

[0044] Other aspects of the present disclosure are described in more detail below.

[0045] As used herein, the terms "user equipment" (UE) and "network entity" are not intended to be specific 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, router, tablet computer, laptop computer, and / or tracking device, etc.) used by a user to communicate via a wireless communication network, wearable (e.g., a smart watch, smart glasses, wearable ring, and / or 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, motorcycle, bicycle, etc.), and / or an Internet of Things (IoT) device, etc. The UE can be mobile or can (e.g., at certain times) be stationary, and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or a variant thereof. Generally, a UE can communicate with a core network via a RAN, and through the core network, the UE can communicate with external networks (such as the Internet) and with other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as connecting to the core network and / or the Internet via a wired access network, a wireless local area network (WLAN) network (e.g., based on the IEEE 802.11 communication standard, etc.).

[0046] In some cases, a network entity may be implemented in a centralized or monolithic base station or server architecture, or alternatively, in a decomposed base station or server architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-RealTime (Near-RT) RAN Intelligent Controller (RIC), or a Non-RealTime (Non-RT) RIC. In some cases, a network entity may include a server device, such as a Multi-access Edge Compute (MEC) device. A base station or server (e.g., having a centralized / monolithic base station architecture or a decomposed base station architecture) may operate according to one of several RATs for communicating with a UE, a road side unit (RSU), and / or other devices depending on the network in which it is deployed, and may alternatively be referred to as an access point (AP), a network node, a NodeB (NB), an evolved NodeB (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 of a UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, a base station may provide edge node signaling functionality, while in other systems, it may provide additional control and / or network management functionality. A communication link through which a UE sends signals to a base station may be referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which a base station sends signals to a UE may be referred to as a downlink (DL) or a forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forward traffic channel, etc.). The term traffic channel (TCH) as used herein may refer to an uplink, reverse, or downlink and / or forward traffic channel.

[0047] The term "network entity" or "base station" (e.g., having an integrated / monolithic base station architecture or a disaggregated base station architecture) can refer to a single physical TRP, or multiple physical TRPs that may or may not be collocated. For example, where the term "network entity" or "base station" refers to a single physical TRP, that physical TRP can be an antenna of the base station corresponding to a cell (or cell sectors) of the base station. Where the term "network entity" or "base station" refers to multiple collocated physical TRPs, these physical TRPs can be an antenna array 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-collocated physical TRPs, these physical TRPs can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-collocated physical TRPs can be a serving base station that receives measurement reports from the UE and an adjacent base station whose reference radio frequency (RF) signal (or simply "reference signal") the UE is measuring. Since the TRP is the point from which the base station transmits and receives wireless signals, as used herein, a reference to transmission from the base station or reception at the base station should be understood to refer to a particular TRP of the base station.

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

[0049] A roadside unit (RSU) is one that can communicate via a communication link or interface (e.g., a cellular-based sidelink or PC5 interface, an 802.11 or WiFi-based TMA device that sends messages to and receives messages from one or more UEs, other RSUs, and / or base stations via 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 will be described in more detail below. An RSU can be located on various transportation infrastructure systems, including roads, bridges, parking lots, toll booths, and / or other infrastructure systems. In some examples, an RSU can facilitate communication between a UE (e.g., a vehicle, a pedestrian user device, and / or other UEs) and a transportation infrastructure system. In some embodiments, an RSU can communicate with a server, a base station, and / or other systems capable of performing centralized management functions.

[0050] An RSU can communicate with the communication system of a UE. For example, an intelligent transport system (ITS) of a UE (e.g., a vehicle and / or other UEs) can be used to generate messages and sign the messages for transmission to an RSU, and to verify messages received from the RSU. An RSU can communicate with vehicles traveling along roads, bridges, or other infrastructure systems (e.g., via a PC5 interface, a DSRC interface, etc.) to obtain traffic-related data (e.g., the time, speed, location, etc. of a vehicle). In some cases, in response to obtaining traffic-related data, an RSU can determine or estimate traffic congestion information (e.g., the start of traffic congestion, the end of traffic congestion, etc.), travel time, and / or other information about a specific location. In some examples, an RSU can communicate with other RSUs (e.g., via a PC5 interface, a DSRC interface, etc.) to determine traffic-related data. An RSU can 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, an RSU can broadcast or otherwise send information to any UE (e.g., a vehicle, a pedestrian UE, etc.) within the coverage area of the RSU.

[0051] A radio frequency signal or "RF signal" includes an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter can send a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through a multipath channel, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and the receiver can be referred to as a "multipath" RF signal. As used herein, an RF signal can also be referred to as a "wireless signal" or simply a "signal", where it is obvious from the context that the term "signal" refers to a wireless signal or an RF signal.

[0052] According to various aspects, Figure 1 An exemplary wireless communication system 100 is shown. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. In some aspects, the base stations 102 may also be referred to as “network entities” or “network nodes”. One or more base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more base stations 102 may be implemented 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. The base stations 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base stations may include an eNB and / or an ng-eNB where the wireless communication system 100 corresponds to a Long Term Evolution (LTE) network, or a gNB where the wireless communication system 100 corresponds to a New Radio (NR) network, or a combination of both, and the small cell base stations may include femto cells, pico cells, micro cells, etc.

[0053] The base stations 102 may together form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 122, and interface to one or more location servers 172 (which may be part of the core network 170 or may be external to the core network 170) via the core network 170. In addition to other functions, the base stations 102 may also perform functions related to one or more of transmitting 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, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., via the EPC or 5GC) via a backhaul link 134, which may be wired and / or wireless.

[0054] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage for a corresponding geographical coverage area 110. In one aspect, the base stations 102 in each coverage area 110 can support one or more cells. A "cell" is a logical communication entity used to communicate with a base station (e.g., via some frequency resources, referred to as carrier frequency, component carrier, carrier, frequency band, etc.), and can be associated with an identifier (e.g., physical cell identifier (PCI), virtual cell identifier (VCI), 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 that can provide access for different types of UEs (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), etc.). Since a cell is supported by a specific base station, depending on the context, the term "cell" can refer to one or both of the logical communication entity and the base station that supports it. In addition, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area (e.g., sector) of a base station, as long as a carrier frequency can be detected and used for communication within some parts of the geographical coverage area 110.

[0055] Although the geographical coverage areas 110 of adjacent macro cell base stations 102 can partially overlap (e.g., in handover areas), some geographical coverage areas 110 can be substantially overlapped by larger geographical coverage areas 110. For example, a small cell base station 102' can have a coverage area 110' that substantially overlaps the coverage areas 110 of one or more macro cell base stations 102. A network including both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network can also include a home eNB (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG).

[0056] The communication link 120 between the base station 102 and the UE 104 may include an uplink (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (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. The communication link 120 may pass through one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and the uplink (e.g., more or fewer carriers may be allocated for the downlink compared to the uplink).

[0057] The wireless communication system 100 may also include a WLAN AP 150 that communicates with a 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 a listen before talk (LBT) procedure before communication to determine whether the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc. using the ultra-wideband (UWB) spectrum. The range of the UWB spectrum may be from 3.1 to 10.5 GHz.

[0058] The small cell base station 102’ may operate in a licensed spectrum and / or an unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102’ may adopt LTE or NR technology and use the same 5 GHz unlicensed spectrum used by the WLAN AP 150. The adoption of LTE and / or 5G in the unlicensed spectrum by the small cell base station 102’ may enhance the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0059] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180, which may operate at mmW frequencies and / or near mmW frequencies for communicating with the UE 182. The mmW base station 180 may be implemented in an integrated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture (e.g., including one or more of a CU, DU, RU, near RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. The range of EHF is from 30 GHz to 300 GHz, and its wavelength is between 1 millimeter and 10 millimeters. The radio waves in this frequency band may be referred to as millimeter waves. Near mmW may extend down to a frequency of 3 GHz at a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW and / or near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmission and / or reception) on the mmW communication link 184 to compensate for the extremely high path loss and short distances. Additionally, it will be understood that in alternative configurations, one or more of the base stations 102 may also use mmW or near mmW and beamforming for transmission. Accordingly, it will be understood that the foregoing description is merely illustrative and should not be construed as limiting the aspects disclosed herein.

[0060] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Conventionally, when a network node or entity (e.g., a base station) broadcasts an RF signal, it broadcasts the signal omnidirectionally (in all directions). With transmit beamforming, the network node determines the location of a given target device (e.g., a UE) relative to the transmitting network node and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directivity of the RF signal during transmission, the network node may control the phase and relative amplitude of the RF signal at each of one or more transmitters that are broadcasting the RF signal. For example, the network node may use an array of antennas (referred to as a "phased array" or "antenna array") that generates a beam of RF waves that can be "manipulated" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are fed to the individual antennas in the correct phase relationship such that the radio waves from the individual antennas add together to increase the radiation in the desired direction while canceling each other out to suppress the radiation in the undesired directions.

[0061] The transmit beams can be quasi - collocated, which means that they appear to have the same parameters to the receiver (e.g., UE), regardless of whether the transmit antennas of the network node are physically collocated. In NR, there are four types of quasi - collocation (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters regarding a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

[0062] In receive beamforming, the receiver uses receive beams to amplify the RF signals detected on a given channel. For example, the receiver can increase the gain setting of the antenna array and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signals received from that direction (e.g., to increase its gain level). Thus, when the receiver is said to be beamforming in a certain direction, it means that the beam gain in that direction is higher than the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gains of other beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal - to - interference - plus - noise ratio (SINR), etc.) of the RF signals received from that direction.

[0063] The receiving beam can be spatially related. Spatially related means that the parameters of the transmission beam of the second reference signal can be derived from the information of the receiving beam of the first reference signal. For example, a UE can receive one or more reference downlink reference signals (such as positioning reference signal (PRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel state information reference signal (CSI-RS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (SSB), etc.) from a network node or entity (such as a base station) using a specific receiving beam. Then, the UE can form a transmission beam to transmit one or more uplink reference signals (such as uplink positioning reference signal (UL-PRS), sounding reference signal (SRS), demodulation reference signal (DMRS), PTRS, etc.) to the network node or entity (such as a base station) based on the parameters of the receiving beam.

[0064] Note that a "downlink" beam can be a transmission beam or a receiving beam, depending on the entity forming it. For example, if a network node or entity (such as a base station) is forming a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmission beam. However, if the UE is forming a downlink beam, it is a receiving beam for receiving downlink reference signals. Similarly, an "uplink" beam can be a transmission beam or a receiving beam, depending on the entity forming it. For example, if a network node or entity (such as a base station) is forming an uplink beam, it is an uplink receiving beam, and if the UE is forming an uplink beam, it is an uplink transmission beam.

[0065] In 5G, the spectrum in which a radio network node or entity (e.g., base station 102 / 180, UE 104 / 182) operates is divided into multiple frequency ranges, FR1 (from 450 to 6000 megahertz (MHz)), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system such as 5G, one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is the carrier that operates on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). The secondary carrier is the carrier that operates on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between the UE 104 and the anchor carrier, and the second frequency can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may only contain necessary signaling information and signals. For example, those UE-specific signaling information and signals may not exist in the secondary carrier because the primary uplink and downlink carriers are usually UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Since a "serving cell" (whether it is a PCell or an SCell) corresponds to the carrier frequency and / or component carrier on which a certain base station is communicating, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.

[0066] For example, still referring to Figure 1, one of the frequencies utilized by macro cell base station 102 can be the anchor carrier (or "PCell"), and other frequencies utilized by macro cell base station 102 and / or mmW base station 180 can be secondary carriers (SCells). In carrier aggregation, base station 102 and / or UE 104 can use up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidth per carrier for transmission in each direction, with a total spectrum of up to Yx MHz (x component carriers). The component carriers can be adjacent to each other in the spectrum or can be non - adjacent to each other. The allocation of carriers can be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers can be allocated for the downlink compared to the uplink). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, compared to what is achieved with a single 20 MHz carrier, two 20 MHz aggregated carriers in a multi - carrier system would theoretically result in a two - fold increase in data rate (i.e., 40 MHz).

[0067] To operate on multiple carrier frequencies, base station 102 and / or UE 104 are equipped with multiple receivers and / or transmitters. For example, UE 104 can have two receivers, "Receiver 1" and "Receiver 2", where "Receiver 1" is a multi - band receiver that can be tuned to frequency band (i.e., carrier frequency) "X" or frequency band "Y", and "Receiver 2" is a single - band receiver that can only be tuned to frequency band "Z". In this example, if UE 104 is being served in frequency band "X", then frequency band "X" will be referred to as the PCell or the active carrier frequency, and "Receiver 1" will need to be tuned from frequency band "X" to frequency band "Y" (SCell) in order to measure frequency band "Y" (and vice versa). In contrast, regardless of whether UE 104 is being served in frequency band "X" or frequency band "Y", due to the separate "Receiver 2", UE 104 can measure frequency band "Z" without interrupting the service on frequency band "X" or frequency band "Y".

[0068] Wireless communication system 100 can also include UE 164, which can communicate with macro cell base station 102 via communication link 120 and / or with mmW base station 180 via mmW communication link 184. For example, macro cell base station 102 can support a PCell and one or more SCells for UE 164, and mmW base station 180 can support one or more SCells for UE 164.

[0069] The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelinks"). In Figure 1 the example of, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain a cellular connection via the D2D P2P link 192) and a D2D P2P link 194 with a WLAN STA 152 connected to the WLAN AP 150 (UE 190 can indirectly obtain a WLAN-based Internet connection via the D2D P2P link 194). In one example, the D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as Long-Term Evolution Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth®, etc.

[0070] Figure 2 is a diagram illustrating an example of a decomposed base station architecture, which can be adopted by the disclosed system for geolocation of critical driver behavior and safety hazards. The deployment of a communication system (such as a 5G NR system) can utilize various components or elements arranged in various ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network devices (such as a base station (BS)), or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, AP, transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a decomposed base station.

[0071] A centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station can be configured to utilize a protocol stack that is 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 can be implemented within a RAN node, and one or more DUs can be collocated with the CU or, alternatively, can be geographically or virtually distributed among one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0073] As previously described, Figure 2A diagram illustrating an exemplary architecture of a split base station 201. The split base station 201 architecture may include one or more central units (CUs) 211, and the CU 211 may communicate directly with a core network 223 via a backhaul link, or indirectly communicate with the core network 223 through one or more split base station units (such as a near real-time (near RT) Radio Access Network (RAN) Intelligent Controller (RIC) 227 via an E2 link, or a non-real-time (non RT) RIC 217 associated with a Service Management and Orchestration (SMO) framework 207, or both). The CU 211 may communicate with one or more distributed units (DUs) 231 via corresponding midhaul links (such as an F1 interface). The DU 231 may communicate with one or more radio units (RUs) 241 via corresponding fronthaul links. The RU 241 may communicate with a corresponding UE 221 via one or more RF access links. In some embodiments, the UE 221 may be served by multiple RUs 241 simultaneously.

[0074] Each unit (i.e., CU 211, DU 231, RU 241) and the near RT RIC 227, non RT RIC 217, and SMO framework 207 may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more other units via the transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals via a wired transmission medium to one or more other units. Additionally, a unit may include a wireless interface configured to receive or transmit signals or both receive and transmit signals via a wireless transmission medium to one or more other units, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver).

[0075] In some aspects, the CU 211 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 with an interface configured to communicate signals with other control functions hosted by the CU 211. The CU 211 may be configured to handle user plane functions (i.e., Central Unit – User Plane (CU-UP)), control plane functions (i.e., Central Unit – Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 211 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as the E1 interface when implemented in an O-RAN configuration). The CU 211 may be implemented to communicate with the DU 131 when necessary for network control and signaling.

[0076] The DU 231 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 241. In some aspects, the DU 231 may host one or more of the Radio Link Control (RLC) layer, 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.) (such as those defined by the 3rd Generation Partnership Project (3GPP)), at least partially depending on the functional split. In some aspects, the DU 231 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 231 or with control functions hosted by the CU 211.

[0077] Lower layer functions can be implemented by one or more RUs 241. In some deployments, the RUs 241 controlled by the DU 231 can correspond to logical nodes that host 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, at least partially based on function splitting, such as lower layer function splitting. In such an architecture, the (multiple) RUs 241 can be implemented to handle over-the-air (OTA) communication with one or more UEs 221. In some embodiments, the real-time and non-real-time aspects of control and user plane communication with the (multiple) RUs 241 can be controlled by the corresponding DU 231. In some scenarios, such a configuration can enable the (multiple) DUs 231 and CU 211 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0078] The SMO framework 207 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 207 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface, such as the O1 interface. For virtualized network elements, the SMO framework 207 can be configured to interact with a cloud computing platform, such as the Open Cloud (O-Cloud) 291, to perform network element lifecycle management (such as instantiating virtualized network element instances) via a cloud computing platform interface, such as the O2 interface. Such virtualized network elements can include, but are not limited to, the CU 211, DU 231, RU 241, and near RT RIC 227. In some embodiments, the SMO framework 207 can communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 213, via the O1 interface. Additionally, in some embodiments, the SMO framework 207 can communicate directly with one or more RUs 241 via the O1 interface. The SMO framework 207 can also include a non-RT RIC 217 configured to support the functions of the SMO framework 207.

[0079] The non-RT RIC 217 can be configured to include logic functions that implement 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 227. The non-RT RIC 217 can be coupled to or communicate with the near-RT RIC 227 (such as via the A1 interface). The near-RT RIC 227 can be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources through data collection and actions on an interface (such as via the E2 interface) that connects one or more CUs 211, one or more DUs 231, or both, and the O-eNB 213 to the near-RT RIC 227.

[0080] In some embodiments, to generate an AI / ML model to be deployed in the near-RT RIC 227, the non-RT RIC 217 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 227 and can be received from non-network data sources or from network functions at the SMO framework 207 or at the non-RT RIC 217. In some examples, the non-RT RIC 217 or the near-RT RIC 227 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 217 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 207 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0081] Figure 3 Examples of different communication mechanisms used by various UEs are shown. In one example of sidelink communication, Figure 3 Vehicles 304, 305, and RSU 303 that communicate with each other using PC5, DSRC, or other device-to-device direct signaling interfaces are shown. Additionally, vehicles 304 and 305 can communicate with a base station 302 (shown as BS 302) using a network (Uu) interface. In some examples, the base station 302 can include a gNB. Figure 3User equipment 307 that communicates with base station 302 using the network (Uu) interface is also shown. As described below, functions can be transferred from a vehicle (e.g., vehicle 304) to user equipment (e.g., user equipment 307) based on one or more characteristics or factors (e.g., temperature, humidity, etc.). In an illustrative example, V2X functionality can be transferred from vehicle 304 to user equipment 307, after which user equipment 307 can communicate with other vehicles (e.g., vehicle 305) via the PC5 interface (or other device-to-device direct interface such as the DSRC interface), as Figure 3 shown.

[0082] Although Figure 3 a specific number of vehicles (e.g., two vehicles 304 and 305) are shown communicating with each other and / or with RSU 303, BS 302, and / or user equipment 307, the present disclosure is not limited thereto. For example, dozens or hundreds of such vehicles can communicate 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 can send various types of information as messages to other nearby vehicles, resulting in each vehicle (e.g., vehicle 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.

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

[0084] Figure 4FIG. 0 is a block diagram illustrating an example vehicle computing system 450 of a vehicle 404. The vehicle 404 is an example of a UE that may communicate with a network (e.g., an eNB, a gNB, a positioning beacon, a location measurement unit, and / or other network entities) via a Uu interface and communicate with other UEs using V2X communication via a PC5 interface (or other device-to-device direct interface such as a DSRC interface). As shown, the vehicle computing system 450 may at least include a power management system 451, a control system 452, an infotainment system 454, an intelligent transportation system (ITS) 455, one or more sensor systems 456, and a communication system 458. In some cases, the vehicle computing system 450 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), communication processors (APs), graphics processing units (GPUs), vision processing units (VPUs), neural network signal processors (NSPs), microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems.

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

[0086] The vehicle computing system 450 further includes a power management system 451. In some embodiments, 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 to the computing system 450 and / or other parts of the vehicle. For example, in view of power fluctuations, such as based on starting the vehicle's engine, the power management system 451 may provide a stable power supply. In another example, the power management system 451 may perform thermal monitoring operations (such as by checking the environment and / or the transistor junction temperature). In another example, the power management system 451 may perform certain functions 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 functions of the vehicle computing system 450 (e.g., restricting the infotainment system 454 (such as by turning off one or more displays, disconnecting from a wireless network, etc.)), and other functions.

[0087] The vehicle computing system 450 further includes a communication system 458. The communication system 458 may include software and hardware components for sending signals to a network (e.g., a gNB on the Uu interface or other network entity) and receiving signals from the network and / or for sending signals to other UEs (e.g., to another vehicle or UE via the PC5 interface, a WiFi interface (e.g., DSRC), a Bluetooth TM interface, and / or other wireless and / or wired interfaces) and receiving signals from other UEs. For example, the communication system 458 is configured to communicate via any suitable wireless network (e.g., a 3G network, a 4G network, a 5G network, a WiFi network, Bluetooth TMWirelessly send and receive information over a network and / or other networks. The communication system 458 includes various components or devices for performing wireless communication functions, 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. The SIM 460 can include a hardware SIM, a software-based SIM (or eSIM) (e.g., a programmable SIM card), any combination thereof, and / or other types of SIMs. Although the vehicle computing system 450 is shown as having two SIMs and one modem, in some embodiments, 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).

[0088] A SIM is a device (e.g., an integrated circuit) capable of securely storing the international mobile subscriber identity (IMSI) number and associated keys (e.g., encryption-decryption keys) of a specific subscriber or user. The IMSI and keys can be used to identify and authenticate the subscriber on a specific UE. The communication system 458 can use the OEM SIM 460 to establish a wireless connection for vehicle-based operations, such as for performing an emergency call (eCall) function, communicating with the communication system of the vehicle manufacturer (e.g., for software updates, etc.), and other operations. The OEM SIM 460 may be important for OEM SIM support of critical services, such as eCall for making an emergency call in the event of a car crash or other emergency. For example, eCall can include a service that automatically dials 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 communicates the location of the vehicle to emergency services (such as the police department, fire department, etc.).

[0089] The communication system 458 can use the user SIM 462 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 equipment can be connected through an interface (e.g., through PC5, Bluetooth TM , WiFI TM(e.g., DSRC), a universal serial bus (USB) port, and / or other wireless or wired interfaces) to the vehicle computing system 450. Once connected, the user device can transfer the wireless network access function from the user device to the vehicle's communication system 458, in which case the user device can stop performing the wireless network access function (e.g., during the period in which the communication system 458 performs the wireless access function). The communication system 458 can start interacting with a 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 this case, other components of the vehicle computing system 450 can be used to output the data received by the communication system 458. For example, the infotainment system 454 (described below) can display the video received by the communication system 458 on one or more displays, and / or can output the audio received by the communication system 458 using one or more speakers.

[0090] 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. The modem 464 (and / or one or more other modems of the communication system 458) can be used for the communication of data of the OEM SIM 460 and / or the user SIM 462. In some examples, the modem 464 can include a 4G (or LTE) modem, and another modem (not shown) of the communication system 458 can include a 5G (or NR) modem. In some examples, the communication system 458 can include one or more Bluetooth TM modems (e.g., for Bluetooth TM Low Energy (Bluetooth TM Low Energy, BLE) or other types of Bluetooth communication), one or more WiFi TM modems (e.g., for DSRC communication and / or other WiFi communication), broadband modems (e.g., ultra-wideband (UWB) modems), any combination thereof, and / or other types of modems.

[0091] In some cases, the modem 464 (and / or one or more other modems of the communication system 458) can be used to perform V2X communications (e.g., vehicle-to-vehicle (V2V) communications with other vehicles, device-to-device (D2D) communications with other devices, vehicle-to-infrastructure (V2I) communications with infrastructure systems, vehicle-to-pedestrian (V2P) communications with pedestrian UEs, etc.). In some examples, the communication system 458 can 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 can be separated from one or more modems for wireless network access functions (e.g., network communications via a network / Uu interface and / or sidelink communications other than V2X communications).

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

[0093] In some cases, the communication system 458 can 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., a serial interface (such as a Universal Serial Bus (USB) input), a lighting connector, and / or other wired interfaces), and / or other components that can allow the vehicle 404 to communicate with the network and / or other UEs.

[0094] 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. The 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 haptic feedback devices (e.g., one or more devices configured to vibrate a seat, a steering wheel, and / or other parts of the vehicle 404), and / or other output devices.

[0095] In some examples, the computing system 450 may include an intelligent transportation system (ITS) 455. In some examples, the ITS 455 may be used to implement V2X communication. For example, the ITS stack of the ITS 455 may generate V2X messages based on information from the application layer of the ITS. In some cases, the application layer may determine whether certain conditions have been met for generating messages for use by the ITS 455 and / or generating messages to be sent to other vehicles (for V2V communication), pedestrian UEs (for V2P communication), and / or infrastructure systems (for V2I communication). In some cases, the communication system 458 and / or the ITS 455 may obtain CAN information (e.g., from other components of the vehicle via a car access network (CAN) bus). In some examples, the communication system 458 (e.g., TCU NAD) may obtain CAN information via the CAN bus and may send the CAN information to the PHY / MAC layer of the ITS 455. The ITS 455 may provide the CAN information to the ITS stack of the ITS 455. The CAN information may include vehicle-related information, such as the forward direction of the vehicle, the speed of the vehicle, braking information, and other information. The CAN information may be provided to the ITS 455 continuously or periodically (e.g., every 1 millisecond (ms), every 10 ms, etc.).

[0096] CAN information can be used to determine conditions for determining whether to generate a message, based on safety-related applications and / or other applications (including applications related to road safety, traffic efficiency, infotainment, enterprise, and / or other applications). In an illustrative example, the ITS 455 can perform lane change assistance or negotiation. For example, using CAN information, the ITS 455 can determine that the driver of the vehicle 404 is attempting to change lanes from the current lane to an adjacent lane (e.g., based on the turn signals being activated, based on the user steering or turning into the adjacent lane, etc.). Based on determining that the vehicle 404 is attempting to change lanes, the ITS 455 can determine that the lane change conditions associated with a message to be sent to other vehicles in the adjacent lane near the vehicle have been met. The ITS 455 can trigger the ITS stack to generate one or more messages for transmission to other vehicles, and the one or more messages can be used to negotiate a lane change 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.

[0097] The ITS 455 can use any suitable protocol to generate messages (e.g., V2X messages). Examples of protocols that the ITS 455 can use include one or more Society of Automotive Engineering (SAE) standards, such as SAE J2735, SAE J2945, SAE J3161, and / or other standards, the entire contents of which are incorporated herein by reference and used for all purposes.

[0098] The security layer of ITS 455 can be used to securely sign messages from the ITS stack, and the messages from the ITS stack are sent to other UEs (such as other vehicles, pedestrian UEs, and / or infrastructure systems) configured for V2X communication and verified by the other UEs. The security layer can also verify messages received from these other UEs. In some embodiments, the signing and verification processes can be based on the security context of the vehicle. In some examples, the security context can include one or more encryption - decryption algorithms, public and / or private keys for generating signatures using the 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 the public key and the encryption - decryption algorithm. The vehicle, pedestrian UE, and / or infrastructure system receiving the signed message can verify the signature to ensure that the message is from an authorized vehicle. In some examples, one or more encryption - decryption algorithms can include one or more symmetric encryption algorithms (e.g., advanced encryption standard (AES), data encryption standard (DES), and / or other symmetric encryption algorithms), one or more asymmetric encryption algorithms using public and private keys (e.g., RSA (Rivest–Shamir–Adleman) and / or other asymmetric encryption algorithms), and / or other encryption - decryption algorithms.

[0099] In some examples, the ITS 455 can determine certain operations to perform (e.g., V2X-based operations) based on messages received from other UEs. The operations can include safety-related operations and / or other operations, such as operations for road safety, traffic efficiency, infotainment, enterprise, and / or other applications. In some examples, the operations can include causing a vehicle (e.g., the control system 452) to perform an automated function, such as automated braking, automated steering (e.g., to maintain a forward direction in a specific lane), automated lane change negotiation with other vehicles, and other automated functions. In an illustrative example, the communication system 458 can 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 suddenly stop. In response to receiving the message, the ITS stack can generate a message or an instruction and can send the message or the instruction to the control system 452, which can cause the control system 452 to automatically brake the vehicle 404 so that it stops before having an impact on the other vehicle. In other illustrative examples, the operations can include triggering a message to warn the driver that another vehicle is in the lane next to the vehicle, a message to warn the driver to stop the vehicle, a message to warn the driver that a pedestrian is at an upcoming crosswalk, a message to warn the driver that a toll booth is within a specific distance (e.g., within 1 mile) of the vehicle, etc.

[0100] In some examples, the ITS 455 can receive a large number of messages from other UEs (e.g., vehicles, RSUs, etc.), in which case the ITS 455 will authenticate (e.g., decode and decrypt) each message and / or determine which operations to perform. Such a large number of messages can result in a large computational load on the vehicle computing system 450. In some cases, the large computational load can cause the temperature of the computing system 450 to increase. The temperature rise of the components of the computing system 450 can adversely affect the ability of the computing system 450 to process a large number of incoming messages. Based on the temperature of the vehicle computing system 450 (or its components) exceeding or approaching one or more thermal levels, one or more functions can be shifted from the vehicle 404 to another device (e.g., a user device, an RSU, etc.). Shifting one or more functions can reduce the computational load on the vehicle 404, thereby helping to reduce the temperature of the components. A thermal load balancer can be provided, which 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 capabilities of the vehicle computing system 450.

[0101] The computing system 450 also includes one or more sensor systems 456 (e.g., a first sensor system through an Nth sensor system, where N is a value equal to or greater than 0). When multiple sensor systems are included, the (multiple) sensor systems 456 can include different types of sensor systems that can be disposed on or in different parts of the vehicle 404. The (multiple) sensor systems 456 can include one or more camera sensor systems, LIDAR sensor systems, radio detection and ranging (RADAR) sensor systems, electromagnetic detection and ranging (EmDAR) sensor systems, sound navigation and ranging (SONAR) sensor systems, sound detection and ranging (SODAR) sensor systems, global navigation satellite system (GNSS) receiver systems (e.g., one or more global positioning system (GPS) receiver systems), accelerometers, gyroscopes, inertial measurement units (IMUs), infrared sensor systems, laser rangefinder systems, ultrasonic sensor systems, infrasonic sensor systems, microphones, any combination thereof, and / or other sensor systems. It should be understood that any number of sensors or sensor systems can be included as part of the computing system 450 of the vehicle 404.

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

[0103] Figure 5 An example of a computing system 570 of a user device 507 is shown. 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 smartwatch, glasses, an XR device, etc.), an Internet of Things (IoT) device, and / or other devices that a user uses to communicate via a wireless communication network. The computing system 570 includes software and hardware components that may be electrically coupled or communicatively coupled (or may communicate in other ways as appropriate) via a bus 589. 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, specialized hardware, any combination thereof, and / or other processing devices or systems. The one or more processors 584 may use the bus 589 to communicate between cores and / or with one or more memory devices 586.

[0104] 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., cameras, mice, keyboards, touch-sensitive screens, touchpads, keypads, microphones, etc.), and one or more output devices 580 (e.g., displays, speakers, printers, etc.).

[0105] One or more wireless transceivers 578 may receive wireless signals (e.g., signal 588) from one or more other devices (such as other user devices, vehicles (e.g., the vehicle 404 described above), network devices (e.g., base stations (such as eNBs and / or gNBs), WiFi routers, etc.), cloud networks, etc.) via the antenna 587. Figure 4 In some examples, the computing system 570 may include multiple antennas. The wireless signal 588 may be transmitted via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a WiFi network), a Bluetooth 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 amplifiers, mixers for signal downconversion (also referred to as signal multipliers), frequency synthesizers (also referred to as oscillators) that supply signals to the mixers, baseband filters, analog-to-digital converters (ADCs), one or more power amplifiers, and other components. The RF front end may generally handle the selection of the wireless signal 588 and the conversion of the wireless signal 588 to baseband or intermediate frequency, and may convert the RF signal to the digital domain.

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

[0107] One or more SIMs 574 may each securely store the IMSI number and associated keys assigned to the user of the user equipment 507. As described above, the IMSI and keys may be used to identify and authenticate a subscriber when accessing a network provided by a network service provider or operator associated with the one or more SIMs 574. One or more modems 576 may modulate one or more signals to encode information for transmission using one or more wireless transceivers 578. One or more modems 576 may also demodulate signals received by one or more wireless transceivers 578 in order 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 may be used to communicate data for one or more SIMs 574.

[0108] The computing system 570 may also include one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 586) (and / or communicate therewith), 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, etc. Such storage devices may be configured to implement any suitable data storage means, including but not limited to various file systems, database structures, etc.

[0109] In various aspects, the functionality may be stored as one or more computer program products (e.g., instructions or code) in the (one or more) memory devices 586 and executed by one or more processors 584 and / or one or more DSPs 582. The computing system 570 may also include software elements (e.g., located within 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 computer programs implementing the functionality provided by the various aspects, and / or may be designed to implement methods and / or configure systems as described herein).

[0110] Figure 6An example 600 of wireless communication between devices based on sidelink communication, such as V2X or other D2D communication, is shown. The communication can be based on a time-slot structure. For example, the transmitting UE 602 can send a transmission 614 (e.g., including a control channel and / or a corresponding data channel), and the transmission 614 can be received by the receiving UEs 604, 606, 608. At least one UE can include an autonomous vehicle or a drone. The control channel can include information for decoding the data channel and can also be used by the receiving device to avoid interference by suppressing transmissions on the occupied resources during data transmission. The number of TTIs and the RBs that the data transmission will occupy can be indicated in a control message from the transmitting device. In addition to operating as receiving devices, the UEs 602, 604, 606, 608 are also each capable of operating as transmitting devices. Thus, the UEs 606, 608 are shown as sending transmissions 616, 620. The transmissions 614, 616, 620 (and 618 of the RSU 607) can be broadcast or multicast to nearby devices. For example, the UE 614 can send a communication intended to be received by other UEs within the range 601 of the UE 614. Additionally / alternatively, the RSU 607 can receive the communication 618 from the UEs 602, 604, 606, 608 and / or send the communication 618 to the UEs 602, 604, 606, 608. The UEs 602, 604, 606, 608 or the RSU 607 can include a detection component. The UEs 602, 604, 606, 608 or the RSU 607 can also include a BSM or a mitigation component.

[0111] In wireless communication, such as V2X communication, V2X entities can perform sensor sharing with other V2X entities for cooperative and automated driving. For example, referring to Figure 7A Figure 700 of, the host vehicle (HV) 702 can detect multiple items in its environment. For example, at block 732, the HV 702 can detect the presence of a non-V2X entity (NV) 706. If the first remote vehicle (RV1) 704 and / or the roadside unit (RSU) 708 itself cannot detect the NV 706, the HV 702 can notify other entities such as the RV1 704 or the RSU 708 of the presence of the NV 706. The HV 702 notifying the RV1 704 and / or the RSU 708 of the NV 706 is the sharing of sensor information. Referring to Figure 7BIn FIG. 710, HV 702 can detect physical obstacles 712, such as potholes, debris, or objects that may be obstacles in the path of HV 702 and / or RV1 704 that have not been detected by RV1 704 and / or RSU 708. HV 702 can notify RV1 and / or RSU 708 of the obstacle 712 so that the obstacle 712 can be avoided. Refer to Figure 7C In FIG. 720, in the case where RSU 708 and / or RV1 704 may not be able to detect a vulnerable road user (VRU) 722, HV 702 can detect the presence of VRU 722 and can share the detection of VRU 722 with RV1 704 and RSU 708. Refer to Figure 7D In FIG. 730, when the HV detects nearby entities (e.g., NV, VRU, obstacle), it can send a sensor data sharing message (SDSM) 734 to the RV and / or RSU to share the detection of the entity. SDSM 734 can be a broadcast message so that any receiving device near the HV can receive the message. In some cases, the shared information can be relayed to other entities, such as RVs. For example, refer to Figure 8 In FIG. 800, HV 802 can detect the presence of NV 806 and / or VRU 822. HV 802 can broadcast SDSM 810 to RSU 808 to report the detection of NV 806 and / or VRU 822. RSU 808 can relay the SDSM 810 received from HV 802 to remote vehicles so that the remote vehicles know the presence of NV 806 and / or VRU 822. For example, RSU 808 can send SDSM 812 to RV1 804, where SDSM 812 includes information related to the detection of NV 806 and / or VRU 822.

[0112] Figure 9 FIG. is an example diagram showing a system 900 for sensor sharing in wireless communication (e.g., V2X communication). In Figure 9 it, system 900 is shown to include a plurality of equipped (e.g., V2X-enabled) network devices. The plurality of equipped network devices include vehicles (e.g., cars) 910a, 910b, 910c, 910d and RSU 905. Also shown are a plurality of un-equipped network devices, which include un-equipped vehicles 920, VRUs (e.g., bicyclists) 930, and pedestrians 940. System 900 can include more or fewer equipped network devices and / or more or fewer un-equipped network devices than Figure 9 shown. Additionally, system 900 can include more or fewer than Figure 9More or fewer different types of equipped network devices (e.g., which may include equipped UEs) and / or more or fewer different types of un-equipped network devices (e.g., which may include un-equipped UEs). Additionally, in one or more examples, the equipped network devices may be equipped with heterogeneous capabilities, which may include but are not limited to C-V2X / DSRC capabilities, 4G / 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, and / or LIDAR capabilities.

[0113] Multiple equipped network devices may be capable of performing V2X communication. Additionally, at least some of the equipped network devices are configured to send and receive sensing signals (e.g., RF sensing signals) for radar and / or sensing signals (e.g., optical sensing signals) for LIDAR to detect nearby vehicles and / or objects. Additionally or alternatively, in some cases, at least some of the equipped network devices are configured to use one or more cameras to detect nearby vehicles and / or objects (e.g., by processing images captured by one or more cameras to detect vehicles / objects). In one or more examples, vehicles 910a, 910b, 910c, 910d, and RSU 905 may be configured to send and receive certain sensing signals (e.g., radar and / or LIDAR sensing signals).

[0114] In some examples, some of the equipped network devices may have sensors with higher capabilities than other equipped network devices of system 900 (e.g., GPS receivers, cameras, RF antennas, and / or optical lasers and / or optical sensors). For example, vehicle 910b may be a luxury vehicle and thus have more expensive and higher-capability sensors than other vehicles that are economy vehicles. In an illustrative example, vehicle 910b may have one or more LIDAR sensors with higher capabilities than other equipped network devices in system 900 (e.g., high-capability optical lasers and optical sensors). In an illustrative example, the LIDAR of vehicle 910b may be able to detect VRUs (e.g., bicyclists) 930 and / or pedestrians 940 with a high degree of confidence (e.g., 70% confidence). In another example, vehicle 910b may have a radar with higher capabilities than other equipped network devices in system 900 (e.g., high-capability RF antennas). For example, the radar of vehicle 910b may be able to detect VRUs (e.g., bicyclists) 930 and / or pedestrians 940 with a certain degree of confidence (e.g., 85% confidence). In another example, vehicle 910b may have a camera with higher capabilities than other equipped network devices in system 900 (e.g., having higher resolution capabilities, higher frame rate capabilities, better lenses, etc.).

[0115] During operation of the system 900, equipped network devices (e.g., at least one of RSU 905 and / or vehicles 910a, 910b, 910c, 910d) may send and / or receive sensing signals (e.g., RF and / or optical signals) to sense and detect vehicles (e.g., vehicles 910a, 910b, 910c, 910d and 920) and / or objects (e.g., VRU 930 and pedestrians 940) located within and around the road. The equipped network devices (e.g., at least one of RSU 905 and / or vehicles 910a, 910b, 910c, 910d) may then use the sensing signals to determine characteristics of the detected vehicles and / or objects (e.g., movement, size, type, direction of travel, and speed). The equipped network devices (e.g., at least one of RSU905 and / or vehicles 910a, 910b, 910c, 910d) may generate at least one vehicle-based message 915 (e.g., a V2X message such as a sensor data sharing message (SDSM), a basic safety message (BSM), a cooperative awareness message (CAM), a collective perception message (CPM), and / or other types of messages) including information related to the determined characteristics of the detected vehicles and / or objects.

[0116] The vehicle-based message 915 may include information related to the detected vehicle or object (e.g., the location of the vehicle or object, the accuracy of the location, the speed of the vehicle or object, the direction in which the vehicle or object is traveling, and / or other information related to the vehicle or object), traffic conditions (e.g., low-speed and / or dense traffic, high-speed traffic, information related to an accident, etc.), weather conditions (e.g., rain, snow, etc.), message type (e.g., emergency message, non-emergency or "regular" message, etc.), road topology (line-of-sight (LOS) or non-LOS (NLOS), etc.), any combination thereof, and / or other information. In some examples, the vehicle-based message 915 may also include information about the preference of the equipped network device for receiving vehicle-based messages from certain other equipped network devices. In some cases, the vehicle-based message 915 may include the current capabilities of the equipped network device (e.g., vehicles 910a, 910b, 910c, 910d), such as the sensing capabilities of the equipped network device (which may affect the accuracy of the equipped network device in sensing vehicles and / or objects), processing capabilities, the thermal state of the equipped network device (which may affect the vehicle's ability to process data), and the state of health of the equipped network device.

[0117] In some aspects, the vehicle-based message 915 can include a dynamic neighbor list (also referred to as a Local Dynamic Map (LDM) or a dynamic surrounding map) for each equipped network device (e.g., vehicles 910a, 910b, 910c, 910d and RSU 905). For example, each dynamic neighbor list can include an enumeration of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device. In some cases, each dynamic neighbor list includes a mapping of all vehicles and / or objects located within a specific predetermined distance (or distance radius) from the corresponding equipped network device, which can include road and terrain topologies.

[0118] In some embodiments, the vehicle-based message 915 can include specific use cases or safety warnings related to the current status of the equipped network devices (e.g., vehicles 910a, 910b, 910c, 910d), such as a do-not-pass warning (DNPW) or a forward collision warning (FCW). In some examples, the vehicle-based message 915 can be in the form of a standard Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), a Collective Perception Message (CPM), a Sensor Data Sharing Message (SDSM) (e.g., SAE J3224 SDSM), and / or other formats.

[0119] Figure 10 FIG. 1000 is a diagram showing an example of a vehicle-based message (e.g., Figure 9 the vehicle-based message 915). The vehicle-based message 915 is shown as a sensor sharing message (e.g., SDSM), but can include a BSM, a CAM, a CPM, or other vehicle-based messages mentioned herein. In Figure 10In this case, the vehicle-based message 915 is shown as including Host Data 1020 and detected object data 1010a, 1010b. The Host Data 1020 of the vehicle-based message 915 may include information related to the sending device of the vehicle-based message 915 (e.g., an equipped sending network entity such as an RSU 905 or an onboard unit (OBU) on vehicles 910a, 910b, 910c, 910d). The detected object data 1010a, 1010b of the vehicle-based message 915 may include information related to the detected vehicle or object (e.g., static or dynamic characteristics related to the detected vehicle or object, and / or other information related to the detected vehicle or object). The detected object data 1010a, 1010b may specifically include detected object CommonData, detected object VehicleData, detected object VRUData, detected obstacle ObstacleData, and detected object MisbehavingVehicleDat.

[0120] These vehicle-based messages 915 are beneficial because they can provide equipped network devices (e.g., Figure 9 vehicles 910a, 910b, 910c, 910d) with awareness and understanding of upcoming potential road hazards (e.g., unforeseen oncoming vehicles, accidents, and road conditions).

[0121] As mentioned above, driver misbehavior (e.g., distracted or sleepy drivers) and road safety hazards (e.g., road potholes) are both major causes of traffic accidents and deaths. Driver misbehavior that may lead to a collision may include, but is not limited to, distraction, drowsiness, looking at objects inside the vehicle unrelated to driving, looking at objects outside the vehicle unrelated to driving, looking at a specific part of the telematics control unit (TCU) display, having (both) hands off the steering wheel for a predefined duration, frequent head turning, eating, drinking, smoking, texting, browsing, attempting to make a call on a mobile phone, frequent interaction with passengers in the vehicle, singing, moving to music, grooming, reaching for objects inside the vehicle, sudden braking, frequent braking, and / or dangerous driving. Driver distraction and road safety hazards may increase the chance of a collision with other vehicles, pedestrians, and / or VRUs. Not only the vehicles, pedestrians, and VRUs being hit may be affected by the collision, but also the drivers of the vehicles experiencing road safety hazards and the distracted drivers themselves may be affected by the vehicle collision.

[0122] In today's industry, there are existing driver misbehavior detection systems designed to detect these hazards and generate alert messages regarding the detected hazards. However, these systems do not associate driver misbehavior or road safety hazards on a map with the location of the vehicle when the driver misbehavior or road safety hazard occurred to determine trends that can be used to predict future driver misbehavior and / or anticipate road safety hazards to prevent future accidents. There are also other solutions for performing post-accident assessments. However, these solutions do not quantify the frequency of near-miss events (e.g., occurrences of driver distraction and / or drowsiness that could lead to an accident), and the frequency of near-miss events can be used to understand the causes of near-miss events, thereby enabling the prevention of potential future accidents.

[0123] Disclosed are systems and techniques for optimizing the situational awareness of driver misbehavior and road safety hazards that can lead to traffic collisions. The systems and techniques can provide awareness to vehicles, pedestrians with smart phones, traffic infrastructure, government municipal agencies, and local businesses. In one or more examples, the systems and techniques can involve detecting events (e.g., driver misbehavior and / or drowsiness) by using a vehicle sensor system. The location of the detected events (e.g., driver misbehavior and / or drowsiness) can be mapped on a map for trends in the event data. The event data on the map can be analyzed (e.g., using statistical analysis and / or machine learning) to determine trends in the data. Based on the determined data trends, various different types of messages (e.g., alert messages, event reports, and / or marketing messages) can be sent to various different entities (e.g., other vehicles, government municipal agencies, and / or businesses) to provide awareness of the events and effect possible changes to prevent future accidents.

[0124] In some cases, the systems and techniques can monitor and / or collect behavioral data associated with one or more devices (e.g., XR devices, mobile devices, etc.). One or more entities (e.g., other vehicles, government municipal agencies, and / or businesses) can use the behavioral data to provide further safety (such as for VRUs and pedestrians, insurance companies, etc.).

[0125] Figure 11 and Figure 12 Examples of maps 1100, 1200 of a system including detected events are shown. In particular, Figure 11 map 1100 shows the plotting of a detected event as a driver drowsiness event (e.g., driver misbehavior), and Figure 12 map 1200 shows the plotting of a detected event as a driver distraction event (e.g., driver misbehavior).

[0126] Figure 11 FIG. 1 is a diagram showing an example of a map 1100 that shows a system for geolocating critical driver behaviors and safety hazards, where the map 1100 indicates the locations where driver drowsiness (e.g., driver misconduct) is sensed. In Figure 11 , the map 1100 shows that the system can include a plurality of equipped (e.g., communication-enabled (such as via V2X communication)) network devices. The plurality of equipped network devices can be in the form of vehicles 1110a, 1110b, 1110c, 1110d, 1110e (e.g., cars) marked as circles in the map 1100. The system can also include a plurality of equipped traffic structures. The traffic structures can include roadside units 1120a, 1120b, 1120c, 1120d and equipped traffic lights 1130a, 1130b, 1130c, 1130d. The system can also include base stations 1140a, 1140b that can be in the form of gNBs.

[0127] The system can include more or fewer equipped network devices, more or fewer traffic structures, and / or more or fewer base stations than Figure 11 shown. Additionally, compared to Figure 11 shown, the disclosed system can include more or fewer different types of equipped network devices (e.g., smartphones), more or fewer different types of traffic structures, and / or more or fewer different types of base stations. Further, in one or more examples, the equipped network devices, equipped traffic structures, and base stations can be equipped with heterogeneous capabilities, which can include but are not limited to C-V2X / DSRC capabilities, 4G / 5G cellular connectivity, radar capabilities, and / or LIDAR capabilities. In one or more examples, the vehicles 1110a, 1110b, 1110c, 1110d, 1110e can include components (e.g., GPS receivers) for obtaining their locations (e.g., by performing their own geolocation).

[0128] In one or more examples, each of the vehicles 1110a, 1110b, 1110c, 1110d, 1110e can employ sensors located outside the vehicle (e.g., outside the passenger compartment) to detect any potential road safety hazards (e.g., potholes in the road). In some examples, the sensors can include but are not limited to accelerometers and / or stability control monitoring units.

[0129] In one or more examples, each vehicle 1110a, 1110b, 1110c, 1110d, 1110e can employ sensors located inside the vehicle (e.g., the passenger compartment) to detect any possible driver misconduct. In one or more examples, the sensors can include, but are not limited to, cameras, LIDAR, infrared sensors, and / or radar sensors. In some examples, the sensors may be able to obtain the driver's gaze angle. The driver's gaze angle (e.g., the angle at which the driver's eyes are looking or how the driver's head is oriented to view) can be used to determine the occurrence of driver distraction (e.g., this can be determined by the driver gazing at an object (e.g., at a particular gaze angle) other than the road for more than a predetermined amount of time).

[0130] For example, sensors (e.g., one or more cameras, LIDAR sensors, infrared sensors, radar sensors, etc.) can be mounted on the vehicle's steering wheel, and / or sensors (e.g., cameras, LIDAR sensors, infrared sensors, radar sensors, etc.) can be mounted at one or more other locations inside the vehicle's passenger compartment (e.g., on the dashboard, on one or more doors, on the entertainment console, and / or other locations). Driver misconduct that can potentially lead to a collision and can be detected by these sensors can include, but is not limited to, distraction, drowsiness, gazing at objects inside the vehicle that are not related to driving, gazing at objects outside the vehicle that are not related to driving, gazing at a specific part of the telematics control unit (TCU) display (e.g., the screen, a specific interface page, etc., such as pages related to music, maps, settings, etc.), (both) hands not on the steering wheel for a predefined duration, frequent head turning, eating, drinking, smoking, texting, browsing, attempting to make a call on a mobile phone, frequent interaction with a passenger in the vehicle, singing, moving to music, grooming, reaching for an object inside the vehicle, sudden braking, frequent braking, and / or dangerous driving.

[0131] Sensors (e.g., internal sensors and / or external sensors) can be connected to an in-vehicle unit (e.g., located inside vehicles 1110a, 1110b, 1110c, 1110d, 1110e), such as an in-vehicle telematics unit (e.g., including at least one processor, such as Figure 16 processor 1610), and the in-vehicle unit can receive sensor data, plot the sensor data on a map (e.g., map 1100), and analyze the sensor data on the map (e.g., analyze patterns in the sensor data on the map, such as observing clusters of the sensor data on the map) to determine trends in the sensor data. In some examples, the in-vehicle unit can utilize statistical analysis and / or pre-trained deep learning models (e.g., such as artificial intelligence (AI) and machine learning (ML) algorithms) to analyze the sensor data to determine trends in the sensor data.

[0132] After the in-vehicle unit determines the trend of the sensor data, the in-vehicle unit may generate a message that includes information about the detected driver misconduct or safety hazard trends. The message may include information about the specific type of detected driver misconduct (e.g., driver drowsiness or driver distraction) or safety hazard (e.g., pothole) and the location of the detected driver misconduct or safety hazard. In one or more examples, the message may be an alert message, an event report, or a marketing message. In some examples, the message may be incorporated into a BSM, CAM, CPM, SDSM, or DENM. In one or more examples, the message itself may include an event flag that may indicate the specific type of driver misconduct or safety hazard that has occurred.

[0133] After the in-vehicle unit has generated the message, the in-vehicle units of vehicles 1110a, 1110b, 1110c, 1110d, 1110e may send an alert message (e.g., via an IEEE 802.11p-based DSRC interface and / or an LTE C-V2X side-link PC5 interface) to other vehicles 1110a, 1110b, 1110c, 1110d, 1110e, pedestrians with smart phones, equipped VRUs (e.g., bicyclists with smart phones), RSUs 1120a, 1120a, 1120c, 1120d, equipped traffic lights 1130a, 1130b, 1130c, 1130b, and / or base stations 1140a, 1140b located within the communication range to notify (e.g., warn) of the detected safety hazard or driver misconduct trend.

[0134] In one or more examples, during the operation of the Figure 11 system shown, one or more sensors of a vehicle (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e) may perform sensing to obtain sensor data. The sensors may be located inside and / or outside the vehicle (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e). The sensors may include cameras, LIDAR, infrared sensors, and / or radar sensors. One or more processors of the vehicle (e.g., the in-vehicle unit of the vehicle) may determine that an event has occurred based on the obtained sensor data.

[0135] In some aspects, an event can be driver misconduct or a safety hazard (e.g., a pothole) of a driver of a vehicle. One or more processors of the vehicle (e.g., an in-vehicle unit of the vehicle) can determine the location of the vehicle at the time the event occurs. In some examples, one or more processors of the vehicle (e.g., an in-vehicle unit of the vehicle) can determine characteristics of the event, such as the driver's gaze angle or the type of event (e.g., a sleepy driver).

[0136] In some examples, one or more processors of the vehicle (e.g., in an in-vehicle unit of the vehicle) or another vehicle or device (e.g., a user equipment (such as Figure 13 smartphone 1360) or a server (such as Figure 13 server 1330)) can associate the location of the event with a location on a map (e.g., create a plot of the event). The map (e.g., map 1100) can include plots of the location of the event and the surrounding area of the locations of events that have previously occurred. For example, map 1100 shows vehicles 1110a, 1110b, 1110c, 1110d, 1110e that have been detected as having sleepy drivers, marked by circles. Map 1100 also shows a cluster area 1160 that contains a cluster of detected events that are closely located together at approximately the same location.

[0137] One or more processors of the vehicle (or another device) can determine similar events that have occurred around the location of the event based on the map (e.g., and characteristics of the event). One or more processors of the vehicle (or another device) can analyze the data in the map (e.g., map 1100) (e.g., by using statistical analysis or machine learning) to determine a trend (e.g., determine a cluster area 1150) based on the event and the determined similar events.

[0138] In one or more examples, a vehicle (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e) can send a message related to the event (e.g., a sleepy driver) based on the trend (e.g., cluster area 1150). In some examples, for instance, in the case of a detected trend of sleepy drivers, the message can be a marketing message. The marketing message can be sent to businesses related to the characteristics (e.g., sleepiness) of the event (e.g., a sleepy driver) (e.g., Figure 13 business 1340) and businesses around the location of the event. For example, the marketing message can include an indication of a specific location (e.g., the location of cluster area 1150) where sleepy drivers often occur, and thus, a coffee business might want to open a coffee shop near that location.

[0139] In some examples, such as in the case of a detected trend of driver misconduct (such as driver distraction), the message can be an alert message. The alert message can be sent to other vehicles (e.g., vehicles 1110a, 1110b, 1110c, 1110d, 1110e), users with smartphones (e.g., Figure 13 smartphone 1365), equipped VRUs (e.g., Figure 13 equipped bicyclist 1380), base stations 1140a, 1140b, government municipal agencies (e.g., Figure 13 government agency 1310), servers (e.g., Figure 13 server 1330) and / or traffic structures (such as roadside units 1120a, 1120b, 1120c, 1120d and / or equipped traffic lights 1130a, 1130b, 1130c, 1130d). For example, the alert message can be a warning to a distracted driver of a vehicle.

[0140] In some examples, such as in the case of a detected trend of a safety hazard (e.g., a pothole), the message can be an incident report. The incident report can be sent to a government municipal agency (e.g., a traffic zoning agency, such as Figure 13 government agency 1310) associated with the characteristics of the incident (e.g., road damage) and associated with the area around the location of the incident. For example, the incident report can include an indication of the location of the pothole in the road for the traffic zoning agency to repair the road.

[0141] Figure 12 is a diagram showing an example of a map 1200 that shows a system for geolocating critical driver behavior and safety hazards, where the map 1200 marks the location of sensed driver distraction (e.g., driver misconduct). Similar to Figure 11 map 1100, Figure 12 map 1200 shows that the system can include multiple equipped (e.g., communication-enabled) network devices. The equipped network devices can be in the form of vehicles 1210a, 1210b, 1210c (e.g., cars) marked as circles in the map 1200. The system can also include multiple equipped traffic structures, such as roadside units 1220a, 1220b, 1220c, 1220d and equipped traffic lights 1230a, 1230b, 1230c, 1230d. The system can also include base stations 1240a, 1240b (e.g., gNB).

[0142] The system can include more than Figure 12more or fewer equipped network devices, more or less traffic infrastructure, and / or more or less base stations shown. Additionally, compared to Figure 12 that shown, the disclosed system may include more or fewer different types of equipped network devices (e.g., smart phones), more or less different types of traffic infrastructure, and / or more or less different types of base stations. In one or more examples, the equipped network devices, equipped traffic infrastructure, and base stations may be equipped with heterogeneous capabilities that may include, but are not limited to, C-V2X / DSRC capabilities, 4G / 5G cellular connectivity, radar capabilities, and / or LIDAR capabilities. Vehicles 1210a, 1210b, 1210c may include components (e.g., GPS receivers) for obtaining their location (e.g., by performing their own geolocation).

[0143] Each vehicle 1210a, 1210b, 1210c may employ sensors located outside the vehicle (e.g., outside the passenger compartment) to detect any potential road safety hazards (e.g., potholes in the road). The sensors may include accelerometers and / or stability control monitoring units.

[0144] Each vehicle 1210a, 1210b, 1210c may employ sensors located inside the vehicle (e.g., in the passenger compartment) to detect any potential driver misconduct (e.g., driver distraction). In one or more examples, the sensors may include cameras, LIDAR, infrared sensors, and / or radar sensors. The sensors may be capable of obtaining the driver's gaze angle (e.g., as shown by gaze angles 1250a, 1250b, 1250c in map 1200). The driver's gaze angle may be used to determine the occurrence of driver distraction (e.g., the time spent looking at billboard 1270 is greater than a predetermined amount of time).

[0145] In one or more examples, during the operation of the Figure 12 system shown, one or more sensors of a vehicle (e.g., vehicles 1210a, 1210b, 1210c) may perform sensing to obtain sensor data. The sensors may be located inside and / or outside the vehicle (e.g., vehicles 1210a, 1210b, 1210c). The sensors may include cameras, LIDAR, infrared sensors, and / or radar sensors. One or more processors of the vehicle (e.g., the in-vehicle unit of the vehicle) may determine that an event has occurred based on the obtained sensor data.

[0146] In some aspects, an event can be driver misbehavior (e.g., driver distraction) or a safety hazard (e.g., a pothole) of a vehicle operator. One or more processors of a vehicle (e.g., an in-vehicle unit of the vehicle) can determine the location of the vehicle at the time of the event. In some examples, one or more processors of a vehicle (e.g., an in-vehicle unit of the vehicle) can determine characteristics of the event, such as the gaze angle of the driver (e.g., gaze angles 1250a, 1250b, 1250c) or the type of the event (e.g., a distracted driver).

[0147] In some examples, one or more processors of a vehicle (e.g., in an in-vehicle unit of the vehicle) or another vehicle or device (e.g., a user device (such as Figure 13 a smart phone 1360) or a server (such as Figure 13 a server 1330)) can associate the location of the event with a location on a map (e.g., create a plot of the event). The map (e.g., map 1200) can include plots of the location of the event and the surrounding area of the locations of events that have occurred previously. For example, map 1200 shows vehicles 1210a, 1210b, 1210c for which driver distraction has been detected, marked by circles. The detected gaze angles 1250a, 1250b, 1250c of the respective drivers of vehicles 1210a, 1210b, 1210c are also shown in map 1200. Map 1200 also shows a cluster area 1260 that includes a cluster of detected events (e.g., driver distractions) that are closely located together at approximately the same location. For example, in map 1200, the gaze angles of the drivers of the vehicles located inside cluster area 1260 are shown as pointing to a billboard 1270, and thus, the drivers of the vehicles inside cluster area 1260 appear to be distracted by billboard 1270.

[0148] One or more processors of a vehicle (or another device) can determine similar events that have occurred around the location of the event based on the map (e.g., and characteristics of the event). One or more processors of a vehicle (or another device) can analyze data in the map (e.g., map 1200) (e.g., by using statistical analysis or machine learning) to determine a trend (e.g., determine cluster area 1260) based on the event and the determined similar events.

[0149] A vehicle (e.g., vehicle 1210a, 1210b, 1210c) can send messages related to an event (e.g., driver distraction) based on a trend (e.g., clustered area 1260). For example, in the case of a trend of detected driver misbehavior such as driver distraction shown in map 1200, the message can be an alert message. The alert message can be sent to other vehicles (e.g., vehicle 1210a, 1210b, 1210c), users with a smart phone (e.g., Figure 13 smart phone 1360), an equipped VRU (e.g., Figure 13 equipped bicyclist 1380), base stations 1240a, 1240b, government municipal agencies (e.g., Figure 13 government agency 1310), a server (e.g., Figure 13 server 1330) and / or traffic structures such as roadside units 1220a, 1220b, 1220c, 1220d and / or equipped traffic lights 1230a, 1230b, 1230c, 1230d. For example, the alert message can be a warning to a distracted driver of a vehicle.

[0150] Figure 13 FIG. shows an example of a system 1300 of a vehicle that sends messages (e.g., alert messages, event reports, and / or marketing messages) to various different types of devices. In particular, Figure 13 is a diagram showing an example of a system 1300 for geolocating critical important driver behaviors and safety hazards. In Figure 13 , the system 1300 is shown to include network devices in the form of vehicles 1305, 1370 that are equipped (e.g., communication-enabled). The system 1300 can also include equipped traffic structures such as roadside units 1390 and / or equipped traffic lights 1350. The system can also include base stations 1320 (such as gNB) and / or a server 1330. The system 1300 can also include a smart phone 1360 that can be associated with a user (e.g., a pedestrian) and / or an equipped VRU 1380 (e.g., an equipped bicyclist). In some examples, the system 1300 can also include a government agency 1310 and / or an enterprise 1340.

[0151] During operation of system 1300, after vehicle 1305 has determined a trend of a detected event (e.g., detected driver misconduct or safety hazard), the vehicle may send (e.g., via signals 1315, 1325, 1335, 1345, 1355, 1365, 1375, 1385, 1395) a message (e.g., alert information, event report, and / or marketing information) to devices (e.g., government agency 1310, base station 1320, server 1330, enterprise 1340, traffic light 1350, smartphone 1360, other vehicle 1370, equipped VRU 1380, roadside unit 1390) to notify the devices of the determined trend of the detected event.

[0152] Figure 14A and Figure 14B are Tables 1400, 1450 showing example values and uses of data points of interest associated with events (e.g., driver misconduct or safety hazard). In particular, Figure 14A and Figure 14B Tables 1400, 1450 include data columns corresponding to data points of interest (DPOIs) 1410, geolocation points 1420, values of the data 1430, and customer potential 1440 associated with the data.

[0153] In one or more examples, as shown in Tables 1400, 1450, data associated with data point of interest 1410 may include, but is not limited to, crash (e.g., airbag deployment) data, seatbelt tightening (e.g., for vehicles equipped with seatbelt tightening) data, seatbelt usage data, drowsiness data, distracted behavior data (e.g., saccade values of the driver looking at an object other than the road being greater than the driver looking at the road), age and gender data of the driver, automatic emergency braking (AEB) and / or lane-keeping assist (LKA) activation event data, data of animals and / or pedestrians on the road, road condition rating data, and / or high-occupancy vehicle (HOV) eligibility and / or data of the occupants within the vehicle.

[0154] In one or more examples, data associated with the geolocation point 1420 can include, but is not limited to: the location of a crash event collected using time-based data; the activation location of deactivated AEB and / or LKA; geolocation and potentially establishing a relationship with information in Crash Deployment; aspects related to the geolocation point at the time of an event (e.g., temperature, weather conditions, drowsy events, time of day, and / or specific location); geolocation of distractions and / or severity, speed traffic information, and / or pedestrian information; data values stored with other events; geolocation, time, and / or date; and / or determining HOV eligibility and / or passengers in a vehicle.

[0155] Data associated with the data value 1430 can include, but is not limited to: understanding a crash event and the location of the crash event, which may or may not be recorded in a police report; understanding situations where the accelerometer value of a vehicle is greater than the accelerometer threshold defined for the vehicle; statistics on seat belt use, understanding driver drowsiness to determine key metrics to support infrastructure changes and / or improvements; understanding the reasons for distracted routes; the context of data for other data points of interest; determining whether there is a trend to activate points of interest (POIs), road safety statistics, marking the location of poor road conditions, or creating a rating for a road segment, and / or understanding the reasons for distracted routes.

[0156] In one or more examples, data associated with the customer potential 1440 of the data can include, but is not limited to: statistical analysis (and / or machine learning) of time of day and location for use in improved traffic design (e.g., speed limit changes) and / or improved road safety (e.g., guardrails, etc.); for locations where drivers become aggressive, determining and understanding whether road design (e.g., speed limit changes, addition of roundabouts, removal or addition of stop signs, etc.) can adapt; feedback from original equipment manufacturers (OEMs) on seat belt use, statistics on seat belt use, and / or determining whether there is any link between seat belt use and location; gas stations, food (e.g., coffee) locations, department of transportation (DOT), to support business opportunities for increasing driver engagement; improving driver attention by companies reducing location and regulatory distractions (e.g., by the government) and / or by the DOT improving infrastructure in areas such as intersections; statistical values of events; improving infrastructure; and / or supporting on-site understanding of key road conditions and future opportunities and / or the cost of improvements.

[0157] Figure 15A is a flowchart showing an example of a process 1500 for wireless communication. Process 1500 can be performed by a vehicle (e.g.,Figure 4 of the vehicle 404) or by components, systems or devices of the vehicle (e.g., Figure 4 the vehicle computing system 450, the on-board unit (OBU) of the vehicle, the chipset of the vehicle, one or more processors of the vehicle, one or more processors of the OBU of the vehicle, or other components or systems of the vehicle). The operations of process 1500 can be implemented as software components that execute and run on one or more processors of the vehicle (e.g., Figure 16 processor 1610 or other processor(s)). Additionally, the sending and receiving of signals by the wireless communication device in process 1500 can be implemented, for example, by one or more antennas and / or one or more transceivers of the vehicle (e.g., wireless transceiver(s)).

[0158] At block 1510, the vehicle (or its components, systems or devices) can receive sensor data obtained using one or more sensors of the vehicle. For example, one or more sensors can include one or more cameras, one or more LIDAR sensors, one or more infrared sensors, one or more radar sensors, any combination thereof and / or other sensors. In some cases, one or more sensors are located inside and / or outside the vehicle.

[0159] At block 1520, the vehicle (or its components, systems or devices) can determine an event based on the sensor data. In some cases, the event is driver misconduct of the driver of the vehicle. The driver's misconduct can be drowsiness, distraction, the driver looking at an object inside the vehicle that is not related to driving, the driver looking at an object outside the vehicle that is not related to driving, the driver looking at a specific part of the telematics control unit (TCU) display, the driver's hands not on the steering wheel for a predefined duration, the driver frequently turning their head, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver frequently interacting with a passenger in the vehicle, the driver singing, the driver moving to music, the driver grooming, the driver reaching for an object inside the vehicle, sudden braking, frequent braking, frequent lane departure, any combination thereof and / or other behaviors. In some cases, the sensor data includes the driver's gaze angle.

[0160] In some aspects, the event is a safety hazard in the environment of the vehicle. For example, the safety hazard can be one or more objects in the road on which the vehicle is driving (e.g., one or more potholes, one or more other vehicles (e.g., a stalled vehicle), one or more traffic cones, ice, snow, etc.).

[0161] At block 1530, a vehicle (or its component, system, or device) can determine the location of the vehicle associated with an event. In some aspects, the vehicle (or its component, system, or device) can send the event and the location to one or more devices (e.g., one or more user equipment (UEs), one or more servers, etc.). In some aspects, the vehicle (or its component, system, or device) can associate the event with the location on a map. In some cases, the vehicle (or its component, system, or device) can determine, based on the map, one or more events similar to the event that have occurred corresponding to the location. In some aspects, the vehicle (or its component, system, or device) can use at least one of statistical analysis or machine learning to determine a trend associated with the event based on the event and the one or more events. In some examples, the vehicle (or its component, system, or device) can send a message related to the event based on the trend. In some cases, the message is an alert message. The alert message can be sent to traffic infrastructure, other vehicles, and / or other entities around the location. In some cases, the message is an event report. The event report can be sent to entities such as government municipal agencies related to the characteristics of the event and associated with the area around the location. In some cases, the message is a marketing message. The marketing message can be sent to entities such as one or more enterprises related to the characteristics of the event and around the location.

[0162] Figure 15B is a flowchart illustrating an example of process 1550 for wireless communication. Process 1550 can be performed by a device or by a component, system, or device of the device (e.g., the chipset of the device, one or more processors of the device, or other components or systems of the device). The device can be a user equipment (UE) (e.g., Figure 5 user equipment 507, a base station (e.g., Figure 1 base station 102, Figure 2 decomposed base station 201, etc.), a vehicle (e.g., Figure 4 vehicle 404), a server, or other device. The operations of process 1550 can be implemented as software components executed and run on one or more processors of the vehicle (e.g., Figure 16 processor 1610 or other processors) of the vehicle. Additionally, for example, the sending and receiving of signals by the wireless communication device in process 1550 can be implemented by one or more antennas and / or one or more transceivers (e.g., (multiple) wireless transceivers) of the vehicle.

[0163] At block 1555, the device (or its component) may receive information corresponding to an event associated with a vehicle. In some cases, the event is driver misconduct of a driver of the vehicle. The driver's misconduct may be drowsiness, distraction, the driver looking at an object inside the vehicle that is not related to driving, the driver looking at an object outside the vehicle that is not related to driving, the driver looking at a specific part of a telematics control unit (TCU) display, the driver's hands not being on the steering wheel for a predefined duration, the driver frequently turning their head, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver frequently interacting with a passenger in the vehicle, the driver singing, the driver moving to music, the driver grooming, the driver reaching for an object inside the vehicle, sudden braking, frequent braking, frequent lane departure, any combination thereof, and / or other behaviors. In some cases, the sensor data includes the driver's gaze angle.

[0164] In some aspects, the event is a safety hazard in the environment of the vehicle. For example, the safety hazard may be one or more objects in the road on which the vehicle is being driven (e.g., one or more potholes, one or more other vehicles (e.g., a vehicle that has stalled), one or more traffic cones, ice, snow, etc.).

[0165] At block 1560, the device (or its component) may receive the location of the vehicle associated with the event. At block 1565, the device (or its component) may associate the event with the location on a map. At block 1570, the device (or its component) may determine, based on the map, one or more events similar to the event that have occurred corresponding to the location. At block 1575, the device (or its component) may determine a trend associated with the event, using at least one of statistical analysis or machine learning, based on the event and the one or more events.

[0166] At block 1580, the device (or its component) may send a message related to the event based on the trend. In some cases, the message is an alert message. The alert message may be sent to traffic infrastructure, other vehicles, and / or other entities around the location. In some cases, the message is an event report. The event report may be sent to an entity, such as a government municipality that is related to the characteristics of the event and associated with the area around the location. In some cases, the message is a marketing message. The marketing message may be sent to an entity, such as one or more businesses that are related to the characteristics of the event and around the location.

[0167] Figure 16FIG. 0 is a block diagram showing an example of a computing system 1600, which can be employed by the disclosed system for geolocating critical driver behaviors and safety hazards. In particular, Figure 16 FIG. 2 shows an example of a computing system 1600, which can be any computing device, such as one that constitutes an internal computing system, a remote computing system, a camera, or any component thereof, where the components of the system communicate with each other using connections 1605. The connections 1605 can be physical connections using a bus or direct connections into a processor 1610 (such as in a chipset architecture). The connections 1605 can also be virtual connections, networked connections, or logical connections.

[0168] In some aspects, the computing system 1600 is a distributed system, where the functions described in this disclosure can 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 many such components, each component performing some or all of the functions of the described component. In some aspects, the components can be physical or virtual devices.

[0169] The example system 1600 includes at least one processing unit (CPU or processor) 1610 and connections 1605 that communicatively couple various system components, including a system memory 1615 (such as a read-only memory (ROM) 1620 and a random access memory (RAM) 1625), to the processor 1610. The computing system 1600 can include a cache 1612 of high-speed memory that is directly connected to, adjacent to, or integrated as part of the processor 1610.

[0170] The processor 1610 can include any general-purpose processor and dedicated processors in which software instructions are incorporated into the actual processor design, as well as hardware services or software services (such as services 1632, 1634, and 1636 stored in a storage device 1630) configured to control the processor 1610. The processor 1610 can essentially be a fully self-contained computing system, containing multiple cores or processors, buses, memory controllers, caches, etc. The multi-core processor can be symmetric or asymmetric.

[0171] To enable user interaction, the computing system 1600 includes an input device 1645, which 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 1600 can also include an output device 1635, which can be one or more of a plurality of output mechanisms. In some cases, a multimodal system can enable a user to provide multiple types of input / output to communicate with the computing system 1600.

[0172] The computing system 1600 may include a communication interface 1640, which may generally control and manage user input and system output. The communication interface may use wired and / or wireless transceivers to perform or facilitate the reception and / or transmission of wired and / or wireless communications, including those utilizing: audio jack / plug, microphone jack / plug, universal serial bus (USB) port / plug, Apple TM Lightning TM port / plug, Ethernet port / plug, fiber optic port / plug, proprietary wired port / plug, 3G, 4G, 5G, and / or other cellular data network wireless signaling, Bluetooth TM wireless signaling, Bluetooth TM Low Energy (BLE) wireless signaling, iBeacon TM wireless 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.

[0173] The communication interface 1640 may also include one or more distance sensors (e.g., LIDAR sensors, laser rangefinders, RF radars, ultrasonic sensors, and infrared (IR) sensors) configured to collect data and provide measurements to the processor 1610, whereby the processor 1610 may be configured to perform the determinations and calculations required to obtain the various measurements of the one or more distance sensors. In some examples, the measurements may include time-of-flight, wavelength, azimuth, elevation, distance, linear velocity, and / or angular velocity, or any combination thereof. The communication interface 1640 may also include one or more GNSS receivers or transceivers for determining the location of the computing system 1600 based on one or more signals received from one or more satellites associated with one or more global navigation satellite system (GNSS) systems. GNSS systems include, but are not limited to, the US-based GPS, the Russian-based Global Navigation Satellite System (GLONASS), the Chinese-based BeiDou Navigation Satellite System (BDS), and the European-based Galileo GNSS. There is no limitation on operation on any particular hardware arrangement, so the basic features here can easily be replaced with improved hardware or firmware configurations as development proceeds.

[0174] The storage device 1630 can be a non-volatile and / or non-transitory and / or computer-readable memory device and can be a hard disk or other types of computer-readable media capable of storing computer-accessible data, such as a magnetic tape cartridge, a flash memory card, a solid-state memory device, a digital versatile disc, a cassette tape, a floppy disk, a flexible disk, a hard disk, a magnetic tape, a magnetic disk / magnetic stripe, any other magnetic storage media, flash memory, memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, a digital video disk (DVD) optical disc, a Blu-ray disc (BDD) optical disc, a holographic optical disc, another optical media, a secure digital (SD) card, a micro secure digital (micro SD) card, a Memory Stick® 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 (dynamic RAM, DRAM), a read-only memory (ROM), a programmable read-only memory (programmable read-only memory, PROM), an erasable programmable read-only memory (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 level 1 (L1) cache, a level 2 (L2) cache, a level 3 (L3) cache, a level 4 (L4) cache, a level 5 (L5) cache or other (L#) cache), a resistive random-access memory (resistive random-access memory, RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (spin transfer torque RAM, STT-RAM), another memory chip or cassette tape, and / or a combination thereof.

[0175] The storage device 1630 may include software services, servers, services, etc. When the processor 1610 executes the code that defines such software, it causes the system to perform functions. In some aspects, the hardware services that perform specific functions may include software components stored in a computer-readable medium, which are combined with necessary hardware components such as the processor 1610, the connection 1605, the output device 1635, etc. to perform functions. 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. The computer-readable medium may include a non-transitory medium in which data can be stored and which does not include carrier waves and / or transient electronic signals propagated wirelessly or via a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media (such as compact discs (CDs) or digital versatile discs (DVDs)), flash memories, memories, or memory devices. The computer-readable medium may store code and / or machine-executable instructions thereon, which may represent a process, a function, a subroutine, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. By passing and / or receiving information, data, arguments, parameters, or memory contents, a code segment may be coupled to another code segment or a hardware circuit. The information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means, including memory sharing, message passing, token passing, network transmission, etc.

[0176] Specific details are provided in the above description to provide a thorough understanding of the aspects and examples provided herein, but those skilled in the art will recognize that the present application is not limited thereto. Thus, although the illustrative aspects of the present application have been described in detail herein, it should be understood that the inventive concept may be embodied and employed differently in other ways, and the appended claims are intended to be construed to include such variations, except as limited by the prior art. The various features and aspects of the above application may be used separately or jointly. In addition, the aspects may be used in any number of environments and applications other than those described herein, without departing from the broader scope of this specification. Accordingly, the specification and the drawings should be regarded as illustrative rather than restrictive. For purposes of illustration, the methods are described in a particular order. It should be understood that in alternative aspects, the methods may be performed in a different order than that described.

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

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

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

[0180] The processes and methods according to the above examples may be implemented using computer-executable instructions stored in or otherwise obtained from a computer-readable medium. Such 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 particular function or a group of functions. Portions of the computer resources used may be accessed via a network. The computer-executable instructions may be, for example, binary numbers, intermediate format instructions (such as assembly language), firmware, source code. Examples of computer-readable media that may be used to store the instructions, information, and / or the information created during the methods according to the described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and the like.

[0181] In some aspects, a computer-readable storage device, medium, and memory can include wired or wireless signals such as a bitstream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0182] Those skilled in the art will understand that any of a variety of different technologies and techniques can be used to represent information and signals. For example, in some cases, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc., data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0183] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or executed using hardware, software, firmware, middleware, microcode, a hardware description language, or any combination thereof, and can be in any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments (e.g., a computer program product) for performing the necessary tasks can be stored in a computer-readable or machine-readable medium. One or more processors can perform the necessary tasks. Examples of form factors include laptop computers, smart phones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, stand-alone devices, etc. The functions described herein can also be embodied in a peripheral device or an add-on card. By way of further example, such functions can also be implemented on a circuit board among different chips or different processes executed in a single device.

[0184] Instructions, the media for conveying such instructions, the computing resources for executing them, and other structures for supporting such computing resources are example components for providing the functions described in this disclosure.

[0185] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices, such as a general purpose computer, a wireless communication device such as a cellular phone, or an integrated circuit device having multiple uses including applications in wireless communication devices such as cellular 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, these techniques may be implemented at least in part by a computer-readable data storage medium comprising program code, the program code including instructions that, when executed, perform one or more of the above-described methods, algorithms, and / or operations. The computer-readable data storage medium may form part of a computer program product, which may include packaging material. The computer-readable medium may include a memory or data storage medium, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, and the like. Additionally or alternatively, these techniques may be implemented at least in part by a computer-readable communication medium, such as a propagated signal or wave, that carries or communicates instructions or data structures in the form of program code that can be accessed, read, and / or executed by a computer.

[0186] 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 circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure. A general purpose processor may be a microprocessor; however, in the 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 in conjunction with a DSP core, or any other such configuration. Accordingly, as used herein, the term “processor” may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or device suitable for implementing the techniques described herein.

[0187] One of ordinary skill in the art will appreciate that the less than (“<”) and greater than (“>”) symbols or terms used herein may be replaced, respectively, with less than or equal to (“ ”) and greater than or equal to (“ ”) symbols without departing from the scope of this description.

[0188] Where a component is described as “configured to” perform certain operations, such configuration can be implemented, for example, by designing an electronic circuit or other hardware to perform the operations, by programming a programmable electronic circuit (e.g., a microprocessor or other suitable electronic circuit) to perform the operations, or any combination thereof.

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

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

[0191] Exemplary aspects of the present disclosure include:

[0192] Aspect 1: A device for wireless communication, the device comprising: at least one memory; and at least one processor, coupled to the at least one memory and configured to: obtain sensor data using one or more sensors of a vehicle; determine an event based on the sensor data; and determine a location of the vehicle associated with the event.

[0193] Aspect 2: The device according to aspect 1, wherein at least one of the one or more sensors is located inside or outside the vehicle.

[0194] Aspect 3: The device according to any one of aspects 1 or 2, wherein at least one of the one or more sensors comprises at least one of a camera, a light detection and ranging (LIDAR) sensor, an infrared sensor, or a radar sensor.

[0195] Aspect 4: The apparatus according to any one of Aspects 1 to 3, wherein the event is driver misconduct of a driver of a vehicle.

[0196] Aspect 5: The apparatus according to Aspect 4, wherein the driver misconduct is at least one of drowsiness, distraction, the driver looking at an object inside the vehicle that is not related to driving, the driver looking at an object outside the vehicle that is not related to driving, the driver looking at a specific part of a telematics control unit (TCU) display, the driver's hand not being on the steering wheel for a predefined duration, the driver frequently turning their head, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver frequently interacting with a passenger in the vehicle, the driver singing, the driver moving along with music, the driver grooming, the driver reaching for an object inside the vehicle, sudden braking, frequent braking, or frequent lane departure.

[0197] Aspect 6: The apparatus according to any one of Aspects 4 or 5, wherein the sensor data includes the driver's gaze angle.

[0198] Aspect 7: The apparatus according to any one of Aspects 1 to 6, wherein the event is a safety hazard in the environment of the vehicle.

[0199] Aspect 8: The apparatus according to Aspect 7, wherein the safety hazard is an object in the road on which the vehicle is being driven.

[0200] Aspect 9: The apparatus according to any one of Aspects 1 to 8, wherein the at least one processor is configured to associate the event with a location on a map.

[0201] Aspect 10: The apparatus according to Aspect 9, wherein the at least one processor is configured to determine, based on the map, one or more events similar to the event that have occurred corresponding to the location.

[0202] Aspect 11: The apparatus according to Aspect 10, wherein the at least one processor is configured to determine a trend associated with the event, using at least one of statistical analysis or machine learning, based on the event and the one or more events.

[0203] Aspect 12: The apparatus according to Aspect 11, wherein the at least one processor is configured to output a message related to the event based on the trend.

[0204] Aspect 13: The apparatus according to Aspect 12, wherein the message is an alert message, and wherein the at least one processor is configured to output the alert message for transmission to at least one of other vehicles or traffic infrastructure around the location.

[0205] Aspect 14: The apparatus according to aspect 12, wherein the message is an event report, and wherein the event report is sent to a government municipality associated with the characteristics of the event and with the area surrounding the location.

[0206] Aspect 15: The apparatus according to aspect 12, wherein the message is a marketing message, and wherein the marketing message is sent to one or more enterprises associated with the characteristics of the event and around the location.

[0207] Aspect 16: The apparatus according to any one of aspects 1 to 15, wherein the at least one processor is configured to output the event and the location for transmission to one or more devices, wherein each of the one or more devices is one of a user equipment (UE) or a server.

[0208] Aspect 17: The apparatus according to any one of aspects 1 to 16, wherein the apparatus is an on-board unit (OBU) of a vehicle.

[0209] Aspect 18: The apparatus according to any one of aspects 1 to 17, wherein the apparatus is a vehicle.

[0210] Aspect 19: The apparatus according to any one of aspects 1 to 18, further comprising the one or more sensors.

[0211] Aspect 20: A method for wireless communication, the method comprising: obtaining sensor data using one or more sensors of a vehicle; determining an event by one or more processors of the vehicle based on the sensor data; and determining a location of the vehicle associated with the event by the one or more processors of the vehicle.

[0212] Aspect 21: The method according to aspect 20, wherein the one or more sensors are located in at least one of inside or outside the vehicle.

[0213] Aspect 22: The method according to any one of aspects 20 or 21, wherein the one or more sensors comprise at least one of a camera, a light detection and ranging (LIDAR) sensor, an infrared sensor, or a radar sensor.

[0214] Aspect 23: The method according to any one of aspects 20 to 22, wherein the event is improper driving behavior of a driver of the vehicle.

[0215] Aspect 24: The method according to aspect 23, wherein the driver misbehavior is at least one of drowsiness, distraction, the driver looking at an object within the vehicle that is not related to driving, the driver looking at an object outside the vehicle that is not related to driving, the driver looking at a specific part of the telematics control unit (TCU) display, the driver's hand not being on the steering wheel for a predefined duration, the driver frequently turning their head, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver frequently interacting with a passenger in the vehicle, the driver singing, the driver moving along with music, the driver grooming, the driver reaching for an object within the vehicle, sudden braking, frequent braking, or frequent lane departure.

[0216] Aspect 25: The method according to any one of aspects 23 or 24, wherein the sensor data includes the driver's gaze angle.

[0217] Aspect 26: The method according to any one of aspects 20 to 25, wherein the event is a safety hazard in the environment of the vehicle.

[0218] Aspect 27: The method according to aspect 26, wherein the safety hazard is an object in the road on which the vehicle is traveling.

[0219] Aspect 28: The method according to any one of aspects 20 to 27, further comprising associating the event with a location on a map by one or more processors of the vehicle.

[0220] Aspect 29: The method according to aspect 28, further comprising determining, by one or more processors of the vehicle, one or more events similar to the event that have occurred corresponding to the location based on the map.

[0221] Aspect 30: The method according to aspect 29, further comprising determining, by one or more processors of the vehicle, a trend associated with the event based on the event and the one or more events, using at least one of statistical analysis or machine learning.

[0222] Aspect 31: The method according to aspect 30, further comprising sending, by the vehicle, a message related to the event based on the trend.

[0223] Aspect 32: The method according to aspect 31, wherein the message is an alert message, and wherein the alert message is sent to at least one of other vehicles or traffic infrastructure around the location.

[0224] Aspect 33: The method according to aspect 31, wherein the message is an event report, and wherein the event report is sent to a government municipality that is related to the characteristics of the event and is associated with the area around the location.

[0225] Aspect 34: The method according to aspect 31, wherein the message is a marketing message, and wherein the marketing message is sent to one or more enterprises that are related to the characteristics of the event and are around the location.

[0226] Aspect 35: The method according to any one of aspects 20 to 34, further comprising sending an event and a location from a vehicle to one or more devices, wherein each of the one or more devices is one of a user equipment (UE) or a server.

[0227] Aspect 36: The method according to any one of aspects 20 to 35, wherein an on-board unit (OBU) of the vehicle includes the one or more processors.

[0228] Aspect 37: An apparatus for wireless communication, the apparatus comprising: at least one memory; and at least one processor, coupled to the at least one memory and configured to: receive information corresponding to an event associated with a vehicle; receive a location of the vehicle associated with the event; associate the event with the location on a map; determine, based on the map, one or more events similar to the event that have occurred corresponding to the location; determine a trend associated with the event using at least one of statistical analysis or machine learning based on the event and the one or more events; and output a message related to the event for transmission based on the trend.

[0229] Aspect 38: The apparatus according to aspect 37, wherein the apparatus is one of a user equipment (UE) or a server.

[0230] Aspect 39: A method for wireless communication, the method comprising: receiving, by a device, information corresponding to an event associated with a vehicle; receiving, by the device, a location of the vehicle associated with the event; associating, by the device, the event with the location on a map; determining, by the device, one or more events similar to the event that have occurred corresponding to the location based on the map; determining, by the device, a trend associated with the event using at least one of statistical analysis or machine learning based on the event and the one or more events; and sending, by the device, a message related to the event based on the trend.

[0231] Aspect 40: The method according to aspect 39, wherein the device is one of a user equipment (UE) or a server.

[0232] Aspect 41: A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform any of the operations described in any of Aspects 20 to 36.

[0233] Aspect 42: An apparatus comprising one or more components for performing any of the operations described in any of Aspects 20 to 36.

[0234] Aspect 43: A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform any of the operations described in any of Aspects 39 and / or 40.

[0235] Aspect 44: An apparatus comprising one or more components for performing any of the operations described in any of Aspects 39 and / or 40.

[0236] The foregoing description is provided to enable any person skilled in the art to practice the aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, where the singular forms of elements are not intended to mean "one and only one" but rather "one or more" unless specifically stated otherwise.

Claims

1. A device for wireless communication, the device comprising: at least one memory; and at least one processor, coupled to the at least one memory and configured to: obtain sensor data using one or more sensors of a vehicle; determine an event based on the sensor data; and determine the location of the vehicle associated with the event.

2. The device according to claim 1, wherein, The one or more sensors are located in at least one of inside or outside the vehicle.

3. The device according to claim 1, wherein The one or more sensors include at least one of a camera, a light detection and ranging (LIDAR) sensor, an infrared sensor, or a radar sensor.

4. The device according to claim 1, wherein The event is improper behavior of a driver of the vehicle.

5. The device according to claim 4, wherein The improper driver behavior is at least one of drowsiness, distraction, the driver gazing at an object inside the vehicle that is not related to driving, the driver gazing at an object outside the vehicle that is not related to driving, the driver gazing at a specific part of a telematics control unit (TCU) display, the driver's hand not being on the steering wheel for a predefined duration, the driver frequently turning their head, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver frequently interacting with a passenger in the vehicle, the driver singing, the driver moving along with music, the driver grooming, the driver reaching for an object inside the vehicle, sudden braking, frequent braking, or frequent lane departure.

6. The apparatus according to claim 4, wherein The sensor data includes the gaze angle of the driver.

7. The device according to claim 1, wherein the event is a safety hazard in the environment of the vehicle.

8. The apparatus according to claim 7, wherein The safety hazard is an object in the road on which the vehicle is being driven.

9. The device according to claim 1, wherein The at least one processor is configured to associate the event with the location on a map.

10. The device according to claim 9, wherein, The at least one processor is configured to determine one or more events similar to the event that have occurred corresponding to the location based on the map.

11. The device according to claim 10, wherein, The at least one processor is configured to determine a trend associated with the event using at least one of statistical analysis or machine learning based on the event and the one or more events.

12. The apparatus according to claim 11, wherein, The at least one processor is configured to output a message related to the event based on the trend.

13. The device according to claim 12, wherein, The message is an alert message, and wherein the at least one processor is configured to output the alert message for transmission to at least one of other vehicles or traffic infrastructure around the location.

14. The apparatus according to claim 12, wherein, The message is an event report, and wherein the event report is sent to a government municipal agency related to the characteristics of the event and associated with the area around the location.

15. The device according to claim 12, wherein, The message is a marketing message, and wherein the marketing message is sent to one or more enterprises related to the characteristics of the event and around the location.

16. The apparatus according to claim 1, wherein, The at least one processor is configured to output the event and the location for transmission to one or more devices, where each of the one or more devices is one of a user equipment (UE) or a server.

17. The apparatus according to claim 1, wherein The device is an on-board unit (OBU) of the vehicle.

18. The apparatus according to claim 1, wherein The device is the vehicle.

19. The device according to claim 1, further comprising the one or more sensors.

20. A method for wireless communication, the method comprising: Obtaining sensor data using one or more sensors of a vehicle; Determining an event by one or more processors of the vehicle based on the sensor data; And Determining, by one or more processors of the vehicle, a location of the vehicle associated with the event.

21. The method according to claim 20, wherein, The one or more sensors are located in at least one of inside or outside the vehicle.

22. The method according to claim 20, wherein The one or more sensors include at least one of a camera, a light detection and ranging (LIDAR) sensor, an infrared sensor, or a radar sensor.

23. The method according to claim 20, wherein, The event is improper behavior of a driver of the vehicle.

24. The method according to claim 23, wherein, The improper behavior of the driver is at least one of drowsiness, distraction, the driver looking at an object inside the vehicle that is not related to driving, the driver looking at an object outside the vehicle that is not related to driving, the driver looking at a specific part of a telematics control unit (TCU) display, the driver's hand not being on the steering wheel for a predefined duration, the driver turning their head frequently, the driver eating, the driver drinking, the driver smoking, the driver operating a computing device, the driver attempting to make one or more calls on a mobile phone, the driver interacting frequently with a passenger in the vehicle, the driver singing, the driver moving to music, the driver grooming, the driver reaching for an object inside the vehicle, sudden braking, frequent braking, or frequent lane departure.

25. The method according to claim 23, wherein The sensor data includes the gaze angle of the driver.

26. The method according to claim 20, wherein the event is a safety hazard in the environment of the vehicle.

27. The method according to claim 26, wherein, The safety hazard is an object in the road on which the vehicle is being driven.

28. The method according to claim 20, further comprising associating, by one or more processors of the vehicle, the event with the location on a map.

29. The method according to claim 28, further comprising determining, by one or more processors of the vehicle, one or more events similar to the event that have occurred corresponding to the location based on the map.

30. The method according to claim 29, further comprising determining, by one or more processors of the vehicle, a trend associated with the event using at least one of statistical analysis or machine learning based on the event and the one or more events.

31. The method according to claim 30, further comprising sending, by the vehicle, a message related to the event based on the trend.

32. The method according to claim 31, wherein, The message is an alert message, and wherein the alert message is sent to at least one of other vehicles or traffic infrastructure around the location.

33. The method according to claim 31, wherein, The message is an event report, and wherein the event report is sent to a government municipal agency related to the characteristics of the event and associated with the area around the location.

34. The method according to claim 31, wherein, The message is a marketing message, and wherein the marketing message is sent to one or more enterprises related to the characteristics of the event and around the location.

35. The method according to claim 20, further comprising sending, by the vehicle, the event and the location to one or more devices, wherein, Each of the one or more devices is one of a user equipment (UE) or a server.

36. The method according to claim 20, wherein, The on-board unit (OBU) of the vehicle includes the one or more processors.

Images