Sharing sensor data for automotive vehicles

Abstract

According to various aspects, a system and method for sharing data related to an object, the mobile device comprises a memory, a sensor that detects the object and generates data related to the object, and at least one processor communicatively coupled to the memory, the at least one processor configured to receive the data from the sensor, determine a relevance of the data, and select an interface for transmitting the data based on the relevance.

Description

[Technical field]

[0001] 1. Field of disclosure Aspects of the present disclosure generally relate to sensor data sharing for automotive vehicles. [Background technology]

[0002] 2. Description of Related Technology Recently, many vehicles have adopted vehicle-to-everything (V2X) technology, which allows the vehicle to communicate with various components in the transportation system that may affect or be affected by the vehicle. V2X has various types of communication such as V2I (Vehicle-to-Infrastructure), V2N (Vehicle-to-Network), V2V (Vehicle-to-Vehicle), V2P (Vehicle-to-Pedestrian), V2D (Vehicle-to-Device), and V2G (Vehicle-to-Grid).

[0003]

[0003] V2X technology facilitates smoother operation of traffic by increasing safety and preventing collisions. For example, vehicles equipped with V2X technology can inform the vehicle driver about weather, nearby accidents, road conditions, and other activities that may affect the safety of the vehicle. Furthermore, V2X can be used in autonomous driving systems to safely steer the vehicle. Therefore, the V2X system on the vehicle needs to constantly communicate with many other entities and objects in the traffic, such as other vehicles, roadside objects, cyclists, and pedestrians.

[0004]

[0004] Therefore, there is a need for a more efficient way for vehicles with V2X systems to communicate with other entities and objects in traffic. Summary of the Invention

[0005]

[0005] The following provides a simplified summary relating to one or more aspects disclosed herein. Therefore, the following summary should not be considered as an extensive overview of all contemplated aspects, nor should the following summary be considered as identifying key or critical elements of all contemplated aspects or defining the scope relating to any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0006]

[0006] In one aspect, a method for sharing data about an object includes detecting the object using a sensor, generating data about the object based on the detection, receiving the data from the sensor, determining a relevance of the data, and selecting an interface for transmitting the data based on the relevance.

[0007]

[0007] In one aspect, a mobile device includes a memory, a sensor that detects an object and generates data regarding the object, and at least one processor communicatively coupled to the memory, where the at least one processor is configured to receive data from the sensor, determine a relevance of the data, and select an interface for transmitting the data based on the relevance.

[0008]

[0008] In one aspect, the mobile device includes means for detecting an object using a sensor, means for generating data regarding the object based on the detection, means for receiving the data from the sensor, means for determining relevance of the data, and means for selecting an interface for transmitting the data based on the relevance.

[0009]

[0009] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processor, cause the processor to receive data regarding an object from a sensor, determine relevance of the data, and select an interface for transmitting the data based on the relevance.

[0010]

[0010] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief description of the drawings]

[0011]

[0011] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate the aspects and not to limit the aspects.

[0012] [Figure 1]

[0012] FIG. 1 illustrates an exemplary wireless communication system according to an aspect of the present disclosure. [Figure 2A]

[0013] FIG. 1 is a top view of a vehicle and an object employing V2X technology, in accordance with various aspects. [Figure 2B]

[0014] FIG. 1 illustrates an on-board computer architecture, in accordance with various aspects. [Diagram 3]

[0015] 1 illustrates an example method for sharing data about an object, according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013]

[0016] Aspects of the present disclosure are provided in the following description and associated drawings directed to various examples provided for illustrative purposes. Alternative aspects may be devised 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.

[0014]

[0017] The words "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. Likewise, the term "aspects of the present disclosure" does not require that all aspects of the present disclosure include the discussed feature, advantage or mode of operation.

[0015]

[0018] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, desired design, corresponding technology, etc.

[0016]

[0019] Further, many aspects are described in terms of a sequence of operations to be performed by, for example, elements of a computing device. It will be appreciated that various operations described herein may be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. In addition, a sequence of operations described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, when executed, cause or instruct an associated processor of a device to perform the functions described herein. Thus, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspect may be described herein, for example, as "logic configured to" perform the described operations.

[0017]

[0020] The terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" as used herein are not intended to be specific or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE may be any wireless communication device (e.g., a vehicle-mounted computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset positioning device, a wearable (e.g., a smart watch, a smart glass, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as a "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," or variations thereof.

[0018]

[0021] A V-UE is a type of UE and may be any in-vehicle wireless communication device, such as a navigation system, a warning system, a heads-up display (HUD), an on-board computer, an in-vehicle infotainment system, an automated driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, a V-UE may be a portable wireless communication device (e.g., a mobile phone, a tablet computer, etc.) carried by the driver of the vehicle or a passenger in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and may be a portable wireless communication device carried by a pedestrian (i.e., a user not driving or riding in the vehicle). In general, a UE may communicate with a core network via a RAN, through which the UE may be connected to external networks, such as the Internet, and to other UEs. Of course, other mechanisms for a UE to connect to the core network and / or the Internet are possible, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), etc.

[0019]

[0022] Depending on the network in which the base station is deployed, the base station may operate according to one of several RATs in communication with the UE and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNode B), etc. The base station may be used primarily to support wireless access by the UE, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, the base station may provide only edge node signaling functions, while in other systems the base station may provide additional control and / or network management functions. The communication link through which the UE can send signals to the base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either a UL / reverse traffic channel or a DL / forward traffic channel.

[0020]

[0023] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station that corresponds to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be serving base stations that receive measurement reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0021]

[0024] In some implementations that support positioning of UEs, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may transmit reference RF signals to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when it transmits RF signals to the UE) and / or a location measurement unit (e.g., when it receives and measures RF signals from the UE).

[0022]

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

[0023]

[0026] 1 illustrates an example wireless communication system 100 according to an aspect of the disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In an aspect, the macrocell base stations 102 may include eNBs and / or ng-eNBs where the wireless communication system 100 supports an LTE network, or gNBs where the wireless communication system 100 supports an NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0024]

[0027] The base stations 102 may collectively form a RAN and may interface with a core network 174 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul links 122 and to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) via the core network 174. The location server(s) 172 may be part of the core network 174 or may be external to the core network 174. In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0025]

[0028] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. In an aspect, one or more cells can be supported by the base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resources, referred to as a carrier frequency, component carrier, carrier, band, etc.) and can be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because cells are supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity supporting the cell and the base station, depending on the context. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, so long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0026]

[0029] While the geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions), some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" instead of "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0027]

[0030] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0028]

[0031] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a wireless local area network (WLAN) station (STA) 152 over a communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in the unlicensed frequency spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine if a channel is available.

[0029]

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

[0030]

[0033] The wireless communication system 100 may further include a mmW base station 180 that may operate at millimeter wave (mmW) and / or sub-mmW frequencies while communicating with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may range to a frequency of 3 GHz with a wavelength of 100 millimeters. The very high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter wave. Communications using the mmW / sub-mmW radio frequency bands have high propagation losses and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely high propagation losses and short distances. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Thus, it will be appreciated that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0031]

[0034] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts it in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and launches a stronger downlink RF signal in that particular direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to the receiving device(s). To vary the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. In particular, RF current from a transmitter is fed to each antenna with the proper phase relationship so that the radio waves from the separate antennas combine together to suppress and cancel radiation in undesired directions while enhancing radiation in desired directions.

[0032]

[0035] A transmit beam may be quasi-co-located, meaning that the transmit beam appears to a receiver (e.g., UE) to have the same parameters regardless of whether the network node's own transmit antenna is physically co-located or not. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a QCL relationship of a given type means that certain parameters for the second reference RF signal of the second beam can be derived from information about the source reference RF signal of the 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 a 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 spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0033]

[0036] In receive beamforming, a receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase its gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in a particular direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is the highest compared to the beam gains in that direction of all other receive 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 RF signals received from that direction.

[0034]

[0037] The transmit beam and the receive beam may be spatially related. Spatial relationship means that parameters for a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on parameters of the receive beam.

[0035]

[0038] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE forms a downlink beam, then it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms an uplink beam, then it is an uplink receive beam, and if the UE forms an uplink beam, then it is an uplink transmit beam.

[0036]

[0039] In 5G, the frequency spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (450 MHz-6000 MHz), FR2 (24250 MHz-52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). The mmW frequency band generally includes the FR2, FR3, and FR4 frequency ranges. Thus, the terms "mmW" and "FR2," "FR3," or "FR4" may generally be used interchangeably.

[0037]

[0040] In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell" and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier in a licensed frequency. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. Since both the primary uplink carrier and the primary downlink carrier are typically UE specific, the secondary carrier may include only the necessary signaling information and signals, e.g., the signaling information and signals that are UE specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to distribute the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier through which several base stations are communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency" and the like may be used interchangeably.

[0038]

[0041] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or data reception rates. For example, two 20 MHz carriers bonded together in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0039]

[0042] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. The transmitters are typically located within the SVs 112, but may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers specifically designed to receive the signals 124 from the SV 112 to derive geolocation information.

[0040]

[0043] In a satellite positioning system, the use of the signals 124 may be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enable use with one or more global and / or regional navigation satellite systems. For example, the SBAS may include an augmentation system or systems that provide integrity information, error correction, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-aided Geo-augmented Navigation, or the GPS and Geo Augmented Navigation system (GAGAN). Thus, a satellite positioning system, as used herein, may include any combination of one or more global navigation satellites and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0041]

[0044] In one aspect, the SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, the SV 112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In this way, the UE 104 may receive communication signals (e.g., signal 124) from the SV 112 instead of or in addition to communication signals from the terrestrial base station 102.

[0042]

[0045] In particular, vehicle-to-everything (V2X) communication technology is being implemented to leverage NR's increased data rates and reduced latency to support intelligent transportation systems (ITS) applications such as wireless communications between vehicles (vehicle-to-vehicle (V2V)), between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between vehicles and pedestrians (vehicle-to-pedestrian (V2P)). The goal is for vehicles to be able to sense the environment around them and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicular communications will enable safety, mobility, and environmental improvements that current technologies cannot provide. When fully implemented, the technology is expected to reduce non-faulty vehicle crashes by 80%.

[0043]

[0046] 1 , the wireless communication system 100 may include multiple V-UEs 160 that may communicate with the base station 102 over the communication link 120 (e.g., using the Uu interface). The V-UEs 160 may also communicate directly with each other over wireless sidelink 162, with roadside access points 164 (also referred to as “roadside units”) over wireless sidelink 166, or with the UE 104 over wireless sidelink 168. The wireless sidelink (or simply “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that enables direct communication between two or more UEs without the need for communication through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, V2V communications, V2X communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of a group of V-UEs 160 utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of the base station 102 or may not otherwise be able to receive transmissions from the base station 102. In some cases, a group of V-UEs 160 communicating via sidelink communications may utilize a one-to-many (1:M) system in which each V-UE 160 transmits to all other V-UEs 160 in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the V-UEs 160 without the involvement of the base station 102.

[0044]

[0047] In one aspect, the sidelinks 162, 166, 168 may operate over a target wireless communications medium, which may be shared with other vehicles and / or infrastructure access points, as well as other wireless communications between other RATs. The "medium" may be comprised of one or more time, frequency, and / or spatial communications resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs.

[0045]

[0048] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. First generation cV2X is standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, cV2X is expected to operate in licensed ITS bands in the sub-6 GHz. Other countries may allocate other bands. Thus, as a specific example, the target medium utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the sub-6 GHz licensed ITS frequency band. However, the present disclosure is not limited to this frequency band or cellular technology.

[0046]

[0049] In one aspect, the sidelinks 162, 166, 168 may be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way, short- to medium-range wireless communications protocol using the wireless access for vehicular environments (WAVE) protocol, also referred to as IEEE 802.11p, for V2V, V2I, and V2P communications. IEEE 802.11p is an approved amendment to the IEEE 802.11 standard, which operates in the licensed ITS band at 5.9 GHz (5.85 GHz to 5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 MHz to 5.905 MHz). Other bands may be allocated in other countries. The V2V communications briefly described above are typically conducted over the Safety Channel, a 10 MHz channel dedicated for safety purposes in the United States. The remainder of the DSRC band (total bandwidth of 75 MHz) is intended for other services targeted to drivers, such as road enforcement, toll collection, automated parking, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the 5.9 GHz licensed ITS frequency band.

[0047]

[0050] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for some communication systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended their operation to unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, particularly the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi". Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and various variants thereof.

[0048]

[0051] Communications between V-UEs 160 are referred to as V2V communications, communications between V-UEs 160 and one or more roadside access points 164 are referred to as V2I communications, and communications between V-UEs 160 and one or more UEs 104 (where UEs 104 are P-UEs) are referred to as V2P communications. V2V communications between V-UEs 160 may include, for example, information about the location, speed, acceleration, heading, and other vehicle data of V-UEs 160. V2I information received at V-UEs 160 from one or more roadside access points 164 may include, for example, road regulations, parking automation information, and the like. V2P communications between V-UEs 160 and UEs 104 may include, for example, information about the location, speed, acceleration, and heading of V-UEs 160, and the location, speed (e.g., when UEs 104 are carried by a user on a bicycle), and heading of UEs 104.

[0049]

[0052] It should be noted that while FIG. 1 illustrates only two of the UEs as V-UEs (V-UE 160), any of the illustrated UEs (e.g., UEs 104, 152, 182, 190) may be V-UEs. Additionally, while only V-UE 160 and a single UE 104 are illustrated as being connected via a sidelink, any of the UEs illustrated in FIG. 1, whether V-UE, P-UE, etc., may be capable of sidelink communication. Additionally, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs, including V-UE 160, may be capable of beamforming. If V-UE 160 is capable of beamforming, V-UE 160 may beamform toward each other (i.e., toward other V-UEs 160), toward roadside access point 164, toward other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0050]

[0053] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., the UE 190 may indirectly obtain cellular connectivity via link 192) and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (the UE 190 may indirectly obtain WLAN-based Internet connectivity via link 194). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc. As another example, the D2D P2P links 192 and 194 may be sidelinks such as those described above with respect to the sidelinks 162, 166, and 168.

[0051]

[0054] 2A, a vehicle 260 (referred to as an "ego vehicle" or "host vehicle") is shown including a camera sensor module 265 located within an interior compartment of the vehicle 260 behind a windshield 261. In one aspect, the camera sensor module 265 may be located anywhere within the vehicle 260. In one aspect, the vehicle 260 may be equipped with V2X technology that allows the vehicle 260 to communicate with other V2X-enabled entities, such as vehicles with on-board units (OBUs) with V2X technology, roadside units (RSUs) with V2X capabilities, and vulnerable road users (VRUs) with V2X capabilities. In one aspect, the camera sensor module 265 may include a sensor 214 with a coverage zone 270, as shown in FIGS. 2A and 2B. Camera sensor module 265 further includes camera 212 for capturing images based on light waves seen and captured through windshield 261 in horizontal coverage zone 275 (indicated by dashed line). In one aspect, camera sensor module 265 may include one or more sensors 214, such as a lidar sensor, a radar sensor, an inertial measurement unit (IMU), a speed sensor, and / or any other sensor that may assist in the operation of vehicle 260, including V2X technology.

[0052]

[0055] FIG. 2A shows an example where the sensor and camera components are co-located components in a shared housing, but it will be appreciated that they may be housed separately in different locations within the vehicle 260. For example, the camera 212 may be positioned as shown in FIG. 2A and the sensor 214 may be positioned in the grill or front bumper of the vehicle 260. Additionally, while FIG. 2A shows the camera sensor module 265 located behind the windshield 261, it may instead be located in a rooftop sensor array or elsewhere. In one aspect, FIG. 2A shows only a single camera sensor module 265, but it will be appreciated that the vehicle 260 may have multiple camera sensor modules 265 oriented in different directions (side, front, rear, etc.). The various camera sensor modules 265 may be under the "skin" of the vehicle (e.g., behind the windshield 261, door panels, bumpers, grills, etc.) or in a rooftop sensor array.

[0053]

[0056] The camera sensor module 265 may detect one or more objects (or no objects) relative to the vehicle 260. In the example of FIG. 2A, there are two objects, vehicles 280 and 285, within horizontal coverage zones 270 and 275 that the camera sensor module 265 can detect. In one aspect, the camera sensor module 265 may estimate parameters of the detected object(s), such as position, range, direction, speed, size, classification (e.g., vehicle, pedestrian, road sign, OBU, VRU, RSU, etc.). The camera sensor module 265 may be employed by the vehicle 260 for automotive safety applications, such as cruise control (ACC), forward collision warning (FCW), collision mitigation or avoidance via automatic braking, lane departure warning (LDW), etc. Furthermore, in one aspect, the camera sensor module 265 may be employed for V2X communication technology as described below.

[0054]

[0057] FIG. 2B illustrates an on-board computer (OBC) 200 of a vehicle 260 according to various aspects of the disclosure. In one aspect, the OBC 200 may be an OBU installed on a vehicle, such as the vehicle 260. In one aspect, the OBC 200 and the camera sensor module 265 may be part of the ADAS or ADS of the vehicle 260. In another aspect, the OBC 200 may communicate with other entities on the road, such as OBUs, RSUs, and VRUs, using V2X communication technology. It should be noted that in one aspect, the vehicle 260 with the OBC 200 may be similar to the V-UE 160, and the OBC 200 may be similar to the UE 104, 190, or any other UE shown in FIG. 1, and may further include one or more components known to those skilled in the art but not shown in FIG. 2B. Thus, in one aspect, the OBC 200 may be considered to be a mobile device. In some aspects, a mobile device may be considered a "handset," "UE," "V-UE," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or "UT," "mobile terminal," "mobile station," "OBC," or variations thereof. The OBC 200 includes a non-transitory computer-readable storage medium, i.e., memory 204, and one or more processors 206 in communication with the memory 204 via a data bus 208. The memory 204 includes one or more storage modules that store computer-readable instructions executable by the processor(s) 206 to perform the functions of the OBC 200 described herein. For example, the processor(s) 206, in conjunction with the memory 204, may implement various neural network architectures.

[0055]

[0058] One or more camera sensor modules 265 are coupled to the OBC 200 (only one is shown in FIG. 2 for simplicity). In some aspects, the camera sensor module 265 includes at least one camera 212 and at least one sensor 214. The sensor 214 may include one or more of a lidar sensor, a radar sensor, an inertial measurement unit (IMU), a speed sensor, and / or any other sensor that may assist in the operation of the vehicle 260. The OBC 200 also includes one or more system interfaces 210 that connect the processor 206 to the camera sensor module 265, and optionally, to other vehicle subsystems (not shown), via a data bus 208.

[0056]

[0059] The OBC 200 also includes a wireless wide area network (WWAN) transceiver 230 configured to communicate over one or more wireless communications networks (not shown), such as, at least in some cases, an NR network, an LTE network, a GSM network, etc. The WWAN transceiver 230 may be connected to one or more antennas (not shown) for communicating with other network nodes, such as other vehicular UEs, pedestrian UEs, infrastructure access points, roadside units (RSUs), base stations (e.g., eNBs, gNBs), etc., over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communications medium (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceiver 230 may be variously configured to transmit and encode signals (e.g., messages, instructions, information, etc.) and conversely, to receive and decode signals (e.g., messages, instructions, information, pilots, etc.) in accordance with the designated RAT. In one aspect, OBC 200 may use WWAN transceiver 230 to transmit and receive sensor data sharing messages (SDSMs) over a Uu interface to perform various V2X / C-V2X communications, such as V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), V2V (vehicle-to-vehicle), V2P (vehicle-to-pedestrian), V2D (vehicle-to-device), and V2G (vehicle-to-grid) communications. In another aspect, OBC 200 may use WWAN transceiver 230 to transmit and receive SDSMs over a ProSe Communication-5 (PC5) interface to perform various V2X communications, such as V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), V2V (vehicle-to-vehicle), V2P (vehicle-to-pedestrian), V2D (vehicle-to-device), and V2G (vehicle-to-grid) communications.

[0057]

[0060] OBC 200 also includes, at least in some cases, a wireless local area network (WLAN) transceiver 240. WLAN transceiver 240 may be connected to one or more antennas (not shown) for communicating with other network nodes, such as other vehicular UEs, pedestrian UEs, infrastructure access points, RSUs, etc., via at least one designated RAT (e.g., cellular vehicle-to-everything (C-V2X), IEEE 802.11p (also known as Wireless Access for Vehicular Environments (WAVE)), Dedicated Short Range Communications (DSRC), etc.) over a wireless communication medium of interest. WLAN transceiver 240 may be variously configured to transmit and encode signals (e.g., messages, instructions, information, etc.) and conversely, to receive and decode signals (e.g., messages, instructions, information, pilots, etc.) in accordance with the designated RAT. In one aspect, OBC 200 may use WLAN transceiver 240 to perform various V2X communications, such as V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), V2V (vehicle-to-vehicle), V2P (vehicle-to-pedestrian), V2D (vehicle-to-device), and V2G (vehicle-to-grid) communications, by transmitting and receiving SDSMs.

[0058]

[0061] As used herein, a "transceiver" may include a transmitter circuit, a receiver circuit, or a combination thereof, although not all designs need to provide both transmit and receive functionality. For example, in some designs, a low-function receiver circuit (e.g., a receiver chip or similar circuit that merely provides low-level sniffing) may be employed to reduce cost when it is not necessary to provide full communication.

[0059]

[0062] OBC 200 also, at least in some cases, includes a Global Positioning System (GPS) receiver 250. GPS receiver 250 may be connected to one or more antennas (not shown) for receiving satellite signals. GPS receiver 250 may include any suitable hardware and / or software for receiving and processing GPS signals. GPS receiver 250 requests information and actions from other systems as appropriate, and performs the calculations necessary to determine the position of vehicle 260 using measurements obtained by any suitable GPS algorithms.

[0060]

[0063] In one aspect, OBC 200 may utilize WWAN transceiver 230 and / or WLAN transceiver 240 to download one or more maps 202, which may then be stored in memory 204 and used for vehicle navigation. Map 202 may be one or more high definition (HD) maps, which may provide accuracy in the absolute range of 7 cm to 10 cm and a highly detailed inventory of all fixed physical assets associated with the road, such as road lanes, road edges, shoulders, medians, traffic signals, signs, paint markings, poles, and other data useful for safe navigation of roads and intersections by vehicle 260. Map(s) 202 may also provide electronic horizon predictive awareness, enabling vehicle 260 to know what is ahead.

[0061]

[0064] In one aspect, camera 212 may capture image frames (also referred to herein as camera frames) of a scene within a field of view area of ​​camera 212 (as shown in FIG. 2A as horizontal coverage zone 275) at a periodic rate to detect objects in the surrounding environment, such as vehicles 280 and 285 and RSU 290. In one aspect, OBC 200 can use sensors 214 to detect objects in the surrounding environment in addition to camera 212. As mentioned above, sensors 214 may include one or more of a lidar sensor, a radar sensor, an inertial measurement unit (IMU), a speed sensor, and / or any other sensor that may assist in the operation of vehicle 260.

[0062]

[0065] 2A , the vehicle 260 can detect objects in the surrounding environment, including two vehicles 280 and 285 and an RSU 290, by using the camera 212 and the sensor 214 in the camera sensor module 265. The processor 206 can receive data regarding the detected objects from the camera sensor module 265. The received data can include the speed of the vehicles 280 and 285, the size of the vehicles 280 and 285, the distance of the vehicles 280 and 285 from the vehicle 260, road conditions, weather, visibility, map usage, terrain, time of day, etc., and the received data can further include data regarding the RSU 290.

[0063]

[0066] Based on the received data, the processor 206 can analyze the received data to determine the relevance of the data based on distance and time span with respect to the vehicle 260 and other entities in the V2X network. In other words, the processor 206 can determine the distance relevance based on which entities or objects in the V2X network may be affected by the received data and how far away those entities and objects are from the vehicle 260. For example, in FIG. 2A, the vehicles 280 and 285 are traveling in close proximity to the vehicle 260. Therefore, the actions of the vehicles 280 and 285 are likely to affect other entities (such as OBUs, VRUs, and RSUs) that are in close proximity to the vehicle 260, such as the RSU 290. The actions of the vehicles 280 and 285 are very unlikely to affect entities that are several miles away from the vehicle 260. Thus, processor 206 may determine that the data received from camera sensor module 265 regarding vehicles 280 and 285 is associated with entities and objects that are in close proximity to vehicle 260, and not with entities that are far or remote from vehicle 260. Thus, the distance relevance of the data regarding vehicles 280 and 285 is a close proximity relevance.

[0064]

[0067] In one aspect, in addition to determining the distance relevance of the received data, the processor 206 may determine the time span relevance of the received data. The processor 206 may determine the time span relevance based on how long the data is useful or relevant. For example, data received from the camera sensor module 265 regarding the vehicles 280 and 285 may be relevant or useful in the near future and not relevant or useful in the distant future. If the vehicle 280 suddenly slows down, the data detected by the camera sensor module 265 will likely reflect the vehicle 280 slowing down. The processor 206 may receive data indicative of a slowdown and determine how long the data is useful to the vehicle 260 and other entities in the V2X network. The received data may be useful in the near future or the distant future. The processor 206 may determine that the data indicative of a slowdown may be useful in the near future and not useful in the distant future. Data regarding the actions of the vehicle 280 is unlikely to affect the behavior of the vehicle 260 or other entities in the V2X network an hour from now. Thus, the time span relevance of the data for vehicles 280 and 285 is likely to be relevant in the near future and not relevant in the distant future.

[0065]

[0068] The above example illustrates a case where the data detected by the camera sensor module 265 is determined to have a nearby distance relevance and a near future time span relevance. In an aspect, when the processor 206 determines that the data received from the camera sensor module 265 has a nearby distance relevance and a near future time span relevance, the processor 206 can use the PC5 interface to transmit SDSMs to entities in the V2X network, such as the vehicles 280 and 285 and the RSU 290. By using the PC5 interface, the vehicle 260 can quickly transmit relevant SDSMs to other nearby entities. For example, the vehicle 260 can use the PC5 interface to transmit an SDSM that alerts the vehicle 280 (assuming it has V2X technology) that the vehicle 285 is in the blind spot of the vehicle 280.

[0066]

[0069] As shown in FIG. 2A, the camera sensor module 265 can detect the RSU 290 and transmit data regarding the RSU 290 to the processor 206. In the example shown in FIG. 2A, the RSU 290 can be a fire hydrant with or without V2X technology. Based on the data from the camera sensor module 265, the processor 206 can determine, for example, that the RSU 290 is leaking a small amount of water. Based on the determination that the RSU 290 is leaking a small amount of water, the processor 206 can determine the distance relevance and time span relevance of this fact. The processor 206 may determine that a small leak from the RSU 290 affects an entity that is far from the vehicle 260, such as a local water company, and thus the distance relevance of the RSU 290 data is remote. In addition, the processor 206 can determine the time span relevance of the data to be far in the future because the small leak does not affect the behavior of the vehicle 260 or other entities in the near future. In one aspect, if the processor 206 determines that the data received from the camera sensor module 265 has a distant distance relevance and a far future time span relevance, the processor 206 may transmit the SDSM to the V2X network or other entities using a V2I interface or a V2N interface, such as a Uu interface, since such data does not have any immediate effect on nearby entities. For example, the vehicle 260 may transmit an SDSM alert to a local water company over the Uu or V2I interface to alert the water company that the RSU 290 is leaking water. In one aspect, the Uu interface may be a wireless interface connecting the UE to an eNodeB, gNB, or base station.

[0067]

[0070] As shown in FIG. 2A, the camera sensor module 265 detects the vehicles 280 and 285 using the camera sensor module 265. In the previous example, it was assumed that both the vehicles 280 and 285 are traveling in front of the vehicle 260. In this example, it is assumed that the vehicle 280 is traveling in front of the vehicle 260, but the vehicle 285 is stationary and blocking the road. The camera sensor module 265 can transmit data regarding the vehicles 280 and 285 to the processor 206, which can determine that the vehicle 280 is traveling in front of the vehicle 260, but the vehicle 285 is stationary and blocking the road. The processor 206 can determine the distance relevance and the time span relevance of the received data based on the received data. In the current example, the processor 206 can determine that the data has both close and distant distance relevance because the stationary vehicle 285 can affect the behavior of other entities close to the vehicle 260, such as the vehicle 260 and the vehicles behind the vehicle 260. Vehicles traveling behind vehicle 260 may collide with stopped vehicle 285. Additionally, vehicles far from vehicle 260 may eventually reach stopped vehicle 285 and collide with vehicle 285. Thus, data received from camera sensor module 265 regarding vehicle 285 may have relevance to vehicles close to vehicle 260 and vehicles far from vehicle 260. Thus, data received from camera sensor module 265 regarding vehicle 285 may indicate distance relevance both close and far.

[0068]

[0071] Additionally, because stationary vehicle 285 may affect the behavior of vehicle 260 and other vehicles close to vehicle 260 in the near future, as well as the behavior of vehicles far from vehicle 285 that may eventually approach vehicle 285 in the far future, processor 206 may determine that data regarding vehicle 285 has both near and far future time span relevance. Thus, data regarding vehicle 285 has relevance to vehicles approaching vehicle 285 in the near future and vehicles approaching vehicle 285 in the far future. Thus, data received from camera sensor module 265 regarding vehicle 285 has both near and far future time span relevance. In one aspect, if processor 206 determines that data received from camera sensor module 265 has both near and far distance relevance and both near and far future time span relevance, processor 206 may transmit the SDSM by using both a PC5 interface and a V2N / V2I interface, such as a Uu interface. The PC5 interface can be used to transmit SDSMs to nearby entities, and the Uu interface can be used to transmit to distant entities or to the V2X network.

[0069]

[0072] In one aspect, the processor 206 may transmit data received from the camera sensor module 265 to a network server (not shown) using a Uu interface. The network server may determine the distance and time span relevance of the received data. The network server may then instruct the processor 206 to transmit the SDSM to other entities around the vehicle 260 using an appropriate interface, such as a PC5, V2N, V2I, and / or Uu interface, based on the determination made by the network server.

[0070]

[0073] The components of the OBC 200 of FIG. 2B may be implemented in a variety of ways. In some implementations, the components of the OBC 200 may be implemented with one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide its functionality. For example, some or all of the functionality represented by blocks 202-250 in the OBC 200 may be implemented by the processor(s) and memory components of the OBC 200 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). However, it will be understood that such operations, actions, and / or functions may in fact be performed by particular components or combinations of components of the OBC 200.

[0071]

[0074] It will be appreciated that aspects include various ways of performing the processes, functions and / or algorithms disclosed herein. For example, FIG. 3 illustrates a method 300 for sharing data about an object, according to one aspect. The method may be performed by a device such as the OBC 200, the processor 206, the vehicle 260, the V-UE 160, the UE 104, 190, or other UEs shown in FIG.

[0072]

[0075] At block 310, the method detects the object using a sensor. The camera sensor module 265 on the vehicle 260 can detect the object.

[0073]

[0076] At block 320, the method generates data regarding the object. The camera sensor module 265 can generate data regarding the detected object.

[0074]

[0077] At block 330, the method receives data from the sensor. The processor 206 may receive data from the camera sensor module 265.

[0075]

[0078] At block 340, the method determines the relevance of the data. The processor 206 may determine the relevance of the data received from the camera sensor module. The relevance includes distance relevance and time span relevance. In another aspect, a network server may determine the relevance of the data.

[0076]

[0079] At block 350, the method selects an interface for transmitting the data based on the relevance. The processor 206 may select an interface for transmitting the data based on the relevance. The processor 206 may select a V2I / V2N interface, such as a PC5 interface and / or a Uu interface.

[0077]

[0080] At block 360, the method transmits the data by using the selected interface. The processor 206 may transmit the data to other entities in the V2X network by using the selected interface.

[0078]

[0081] In the above detailed description, it can be seen that various features are grouped together in each example. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the disclosure may include less than all features of each exemplary clause disclosed. Thus, the following clauses should be considered to be incorporated in the description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspect(s) of the dependent clause are not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the aspect(s) of the dependent clause with the subject matter of any other dependent clause or independent clause, or combinations of any features with other dependent clauses and independent clauses. Unless a specific combination is expressly expressed or can be easily inferred (e.g., contradictory aspects such as defining an element as both an insulator and a conductor), the various aspects disclosed herein expressly include these combinations. It is further contemplated that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0079]

[0082] The following numbered clauses describe example implementations.

[0080]

[0083] Clause 1. A method for sharing data about an object, the method comprising: detecting the object using a sensor; generating data about the object based on the detection; receiving the data from the sensor; determining relevance of the data; and selecting an interface for transmitting the data based on the relevance.

[0081]

[0084] Clause 2. The method of clause 1, wherein the relevance includes a distance relevance of the data.

[0082]

[0085] Clause 3. The method of clause 2, wherein the relevance further includes a time span relevance of the data.

[0083]

[0086] Clause 4. The method of clause 2 or 3, wherein the distance association is based on another object that is affected by the data and the distance from the another object to the sensor.

[0084]

[0087] Clause 5. The method of clause 3 or 4, wherein the time span relevance is based on how long the data is useful.

[0085]

[0088] Clause 6. The method of any of clauses 3 to 5, further comprising transmitting data using the selected interface.

[0086]

[0089] Clause 7. The method of clause 6, wherein when the distance relevance is proximity and the time span relevance is near future, the selected interface is a PC5 interface.

[0087]

[0090] Clause 8. The method of clause 6 or 7, wherein when the distance relevance is remote and the time span relevance is in the far future, the selected interface is a V2N interface or a V2I interface.

[0088]

[0091] Clause 9. A method according to any one of clauses 6 to 8, wherein when the distance relevance is both close and remote and the time span relevance is both near and far in the future, the selected interfaces are a PC5 interface and a V2N interface.

[0089]

[0092] Clause 10. A method according to any one of clauses 6 to 9, wherein the V2N interface is a Uu interface.

[0090]

[0093] Clause 11. A mobile device comprising: a memory; a sensor that detects an object and generates data regarding the object; and at least one processor communicatively coupled to the memory, wherein the at least one processor is configured to receive data from the sensor, determine a relevance of the data, and select an interface for transmitting the data based on the relevance.

[0091]

[0094] Clause 12. The mobile device of clause 11, wherein the relevance includes a distance relevance of the data.

[0092]

[0095] Clause 13. The mobile device of clause 12, wherein the relevance further comprises a time span relevance of the data.

[0093]

[0096] Clause 14. A mobile device according to clause 12 or 13, wherein the distance relevance is based on another object affected by the data and a distance from the another object to the sensor.

[0094]

[0097] Clause 15. A mobile device according to clause 13 or 14, wherein the timespan relevance is based on how long the data is useful.

[0095]

[0098] Clause 16. The mobile device of any of clauses 13 to 15, wherein the at least one processor is further configured to transmit data using the selected interface.

[0096]

[0099] Clause 17. The mobile device of clause 16, wherein when the distance relevance is proximity and the time span relevance is near future, the selected interface is a PC5 interface.

[0097]

[0100] Clause 18. A mobile device according to clause 16 or 17, wherein when the distance relevance is remote and the time span relevance is in the far future, the selected interface is a V2N interface or a V2I interface.

[0098]

[0101] Clause 19. A mobile device according to any of clauses 16 to 18, wherein when the distance relevance is both close and remote and the time span relevance is both near future and far future, the selected interfaces are a PC5 interface and a V2N interface.

[0099]

[0102] Clause 20. A mobile device according to any one of clauses 16 to 19, wherein the V2N interface is a Uu interface.

[0100]

[0103] Clause 21. A mobile device comprising: means for detecting an object using a sensor; means for generating data regarding the object based on the detection; means for receiving the data from the sensor; means for determining relevance of the data; and means for selecting an interface for transmitting the data based on the relevance.

[0101]

[0104] Clause 22. The mobile device according to clause 21, wherein the relevance includes a distance relevance of the data.

[0102]

[0105] Clause 23. The mobile device of clause 22, wherein the relevance further comprises a time span relevance of the data.

[0103]

[0106] Clause 24. A mobile device according to clause 22 or 23, wherein the distance relevance is based on another object affected by the data and a distance from the another object to the sensor.

[0104]

[0107] Clause 25. A mobile device according to clause 23 or 24, wherein the timespan relevance is based on how long the data is useful.

[0105]

[0108] Clause 26. A mobile device according to any of clauses 23 to 25, further comprising means for transmitting data using the selected interface.

[0106]

[0109] Clause 27. The mobile device of clause 26, wherein when the distance relevance is proximity and the time span relevance is near future, the selected interface is a PC5 interface.

[0107]

[0110] Clause 28. A mobile device according to clause 26 or 27, wherein when the distance relevance is remote and the time span relevance is in the far future, the selected interface is a V2N interface or a V2I interface.

[0108]

[0111] Clause 29. A mobile device according to any of clauses 26 to 28, wherein when the distance relevance is both close and remote and the time span relevance is both near future and far future, the selected interfaces are a PC5 interface and a V2N interface.

[0109]

[0112] Clause 30. A mobile device according to any one of clauses 26 to 29, wherein the V2N interface is a Uu interface.

[0110]

[0113] Clause 31. A non-transitory computer-readable medium having stored thereon computer-executable instructions that, when executed by a processor, cause the processor to receive data regarding an object from a sensor, determine a relevance of the data, and select an interface for transmitting the data based on the relevance.

[0111]

[0114] Clause 32. The non-transitory computer-readable medium of clause 31, wherein the association includes a distance association of the data.

[0112]

[0115] Clause 33. The non-transitory computer-readable medium of clause 32, wherein the association further comprises a time span association of the data.

[0113]

[0116] Clause 34. The non-transitory computer-readable medium of clause 32 or 33, wherein the distance association is based on another object affected by the data and a distance from the another object to the sensor.

[0114]

[0117] Clause 35. The non-transitory computer-readable medium of clause 33 or 34, wherein the time span relevance is based on how long the data is useful.

[0115]

[0118] Clause 36. A non-transitory computer-readable medium according to any of clauses 33 to 35, further comprising computer-executable instructions that, when executed by a processor, cause the processor to transmit data using a selected interface.

[0116]

[0119] Clause 37. The non-transitory computer-readable medium of clause 36, wherein when the distance relevance is proximity and the time span relevance is near future, the selected interface is a PC5 interface.

[0117]

[0120] Clause 38. The non-transitory computer-readable medium of any of clauses 36 or 37, wherein when the distance relevance is remote and the time span relevance is in the far future, the selected interface is a V2N interface or a V2I interface.

[0118]

[0121] Clause 39. A non-transitory computer-readable medium according to any of clauses 36 to 38, wherein when the distance relevance is both close and remote and the time span relevance is both near and far in the future, the selected interfaces are a PC5 interface and a V2N interface.

[0119]

[0122] Clause 40. A non-transitory computer-readable medium according to any one of clauses 36 to 39, wherein the V2N interface is a Uu interface.

[0120]

[0123] Clause 41. An apparatus comprising a memory, a transceiver, and a processor communicatively coupled to the memory and the transceiver, wherein the memory, the transceiver, and the processor are configured to perform a method according to any one of clauses 1 to 40.

[0121]

[0124] Clause 42. Apparatus comprising means for carrying out the method according to any one of clauses 1 to 40.

[0122]

[0125] Clause 43. A non-transitory computer readable medium having computer executable instructions stored thereon, the computer executable including at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 40.

[0123]

[0126] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0124]

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

[0125]

[0128] The various example logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0126]

[0129] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0127]

[0130] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0128]

[0131] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein do not have to be performed in any particular order. Further, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method for sharing data related to an object, comprising: detecting the object using a sensor; generating the data related to the object based on the detection; receiving the data from the sensor; determining the relevance of the data; selecting an interface for transmitting the data based on the relevance, where the relevance includes a distance relevance of the data and a time span relevance of the data, the distance relevance is based on another object affected by the data and the distance from the other object to the sensor, and the time span relevance is based on how long the data is useful; A method comprising the above steps.

2. Further comprising transmitting the data using the selected interface. The method according to claim 1. The method according to claim 1, further comprising transmitting the data using the selected interface.

3. The method according to claim 2, wherein when the distance relevance is proximity and the time span relevance is the near future, the selected interface is a ProSe Communication - 5 (PC5) interface.

4. The method according to claim 2, wherein when the distance relevance is remote and the time span relevance is the far future, the selected interface is a Vehicle-to-Network (V2N) interface or a Vehicle-to-Infrastructure (V2I) interface.

5. The method according to claim 2, wherein when the distance relevance is both proximity and remote and the time span relevance is both the near future and the far future, the selected interface is a ProSe Communication - 5 (PC5) interface and a Vehicle-to-Network (V2N) interface.

6. The method according to claim 4, wherein the V2N interface is a Uu interface.

7. A memory, a sensor for detecting an object and generating data related to the object, at least one processor communicatively coupled to the memory, wherein the at least one processor is configured to receive the data from the sensor, determine the relevance of the data, Select an interface for transmitting the data based on the relevance, where the relevance includes the distance relevance of the data and the time span relevance of the data, and the distance relevance is based on another object affected by the data and the distance from the other object to the sensor, and the time span relevance is based on how useful the data is for a certain period of time. A mobile device configured to perform the above. **Claim 8** The at least one processor is Further configured to transmit the data using the selected interface. The mobile device according to claim 7, further configured as described above. **Claim 9** When the distance relevance is proximity and the time span relevance is the near future, the selected interface is a ProSe Communication - 5 (PC5) interface. The mobile device according to claim 8. **Claim 10** When the distance relevance is remote and the time span relevance is the far future, the selected interface is a Vehicle-to-Network (V2N) interface or a Vehicle-to-Infrastructure (V2I) interface. The mobile device according to claim 8. **Claim 11** When the distance relevance is both proximity and remote, and the time span relevance is both the near future and the far future, the selected interface is a ProSe Communication - 5 (PC5) interface and a Vehicle-to-Network (V2N) interface. The mobile device according to claim 8. **Claim 12** The mobile device according to claim 10, wherein the V2N interface is a Uu interface. **Claim 13** A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a processor, cause the processor to Receive data regarding an object from a sensor, Determine the relevance of the data, Selecting an interface for transmitting the data based on the relevance, where the relevance includes a distance relevance of the data and a time span relevance of the data, the distance relevance being based on another object affected by the data and a distance from the another object to the sensor, and the time span relevance being based on how long the data is useful. A non-transitory computer-readable medium that causes the above to be performed. **Claim 14** When executed by the processor, causing the processor to transmit the data using the selected interface The non-transitory computer-readable medium according to claim 13, further comprising computer-executable instructions. **Claim 15** When the distance relevance is proximity and the time span relevance is the near future, the selected interface is a ProSe Communication-5 (PC5) interface, or When the distance relevance is remote and the time span relevance is the far future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface, and the V2N interface is preferably a Uu interface, or When the distance relevance is both proximity and remote and the time span relevance is both the near future and the far future, the selected interface is a ProSe Communication-5 (PC5) interface and a vehicle-to-network (V2N) interface. The non-transitory computer-readable medium according to claim 14.

Images