Sharing of sensor data for automobiles

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 the Disclosure

[0001] Aspects of the present disclosure generally relate to sensor data sharing for motor vehicles.

Background Art

[0002] 2. Description of Related Art

[0002] Recently, many vehicles employ vehicle-to-everything (V2X) technology, which enables vehicles to communicate with various components in a transportation system that may affect the vehicle or be affected by the vehicle. V2X includes 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 improving safety and preventing collisions. For example, a vehicle equipped with V2X technology can inform the vehicle's driver of weather, nearby accidents, road conditions, and other activities that may affect vehicle safety. Furthermore, V2X can be used in autonomous driving systems to safely maneuver vehicles. Accordingly, a V2X system on a vehicle needs to constantly communicate with many other entities and objects in traffic, such as other vehicles, roadside objects, cyclists, and pedestrians.

[0004]

[0004] Accordingly, there is a need for more efficient methods for vehicles having V2X systems to communicate with other entities and objects in traffic. [Overview of the Initiative]

[0005]

[0005] The following provides a simplified overview relating to one or more embodiments disclosed herein. Therefore, the following overview should not be considered a broad overview relating to all intended embodiments, nor should it be considered to identify the main or important elements relating to all intended embodiments, or to define the scope relating to any particular embodiment. Therefore, the sole purpose of the following overview is to provide, in a simplified form, certain concepts relating to one or more embodiments relating to the mechanisms disclosed herein, prior to the detailed descriptions presented below.

[0006]

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

[0007]

[0007] In one embodiment, the mobile device comprises a memory, a sensor that detects objects and generates data about the objects, 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 the relevance of the data, and select an interface for transmitting the data based on the relevance.

[0008]

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

[0009]

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

[0010]

[0010] Other purposes and advantages relating to the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief explanation of the drawing]

[0011]

[0011] The accompanying drawings are provided to aid in describing various aspects of the present disclosure and are provided only for illustrative purposes of aspects, not to limit them.

[0012] [Figure 1]

[0012] This figure shows an exemplary wireless communication system according to an aspect of the present disclosure. [Figure 2A]

[0013] These are top views of vehicles and objects employing V2X technology in various configurations. [Figure 2B]

[0014] This figure shows various configurations of onboard computer architectures. [Figure 3]

[0015] This disclosure illustrates an exemplary method for sharing data about an object. [Modes for carrying out the invention]

[0013]

[0016] The aspects of this disclosure are provided in the following description and related drawings, which cover various examples provided for illustrative purposes. Alternative embodiments may be devised without departing from the scope of this disclosure. In addition, well-known elements of this disclosure are not described in detail or are omitted so as not to obscure the relevant details of this disclosure.

[0014]

[0017] The terms “exemplary” and / or “example” are used herein to mean “to serve as an example, case, or illustration.” Any aspect described herein as “exemplary” and / or “example” should not necessarily be construed as being preferable or advantageous to any other aspect. Similarly, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the features, advantages, or modes of operation discussed.

[0015]

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

[0016]

[0019] Furthermore, many embodiments will be described, for example, with respect to a set of operations to be performed by elements of a computing device. It will be recognized that the various operations described herein may be performed by a specific circuit (e.g., an application-specific integrated circuit, ASIC), by program instructions executed by one or more processors, or a combination of both. In addition, the set of operations described herein, when executed, may be considered to be fully embodied in any form of non-temporary computer-readable storage medium storing therein a corresponding set of computer instructions that cause or instruct the relevant processor of the device to perform the functions described herein. Thus, the various embodiments of this disclosure may be embodied in several different forms, all of which are intended to fall within the scope of the claimed subject matter. In addition, for each of the embodiments described herein, any corresponding form of such embodiment may be described herein, for example, as “logic configured to perform” the operations described.

[0017]

[0020] As used herein, the terms “user equipment” (UE), “vehicle UE” (V-UE), “pedestrian UE” (P-UE), and “base station” are not intended to be specific to, or otherwise limited to, any particular radio access technology (RAT), unless otherwise noted. Generally, a UE may be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a computer mounted in a vehicle, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset positioning device, a wearable (e.g., a smartwatch, smart glasses, 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.). A UE may be mobile or stationary (e.g., for a certain period of time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as "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 that can be any in-vehicle wireless communication device, such as a navigation system, warning system, heads-up display (HUD), onboard computer, in-vehicle infotainment system, automated driving system (ADS), or advanced driver assistance system (ADAS). Alternatively, a V-UE can be a portable wireless communication device (e.g., a mobile phone, tablet computer) carried by the driver or passengers 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 that may be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding in a vehicle). Generally, a UE can communicate with the core network via the RAN, and via the core network, a UE can connect to external networks, such as the Internet, and to other UEs. Naturally, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as via wired access networks, wireless local area networks (WLANs) (for example, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.).

[0019]

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

[0020]

[0023] The term “base station” can refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs, which may or may not be colocated. For example, when the term “base station” refers to a single physical TRP, that physical TRP may be the base station’s antennas corresponding to the base station’s cells (or several cell sectors). When the term “base station” refers to multiple colocated physical TRPs, the physical TRPs may be an array of antennas of the base station (for example, in a multiple-input multiple-output (MIMO) system, or when the base station employs beamforming). When the term “base station” refers to multiple uncolocated physical TRPs, the physical TRPs 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, an uncollocated physical TRP may be a serving base station that receives measurement reports from the UE, and an adjacent base station from which the UE measures its reference radio frequency (RF) signal. Since a TRP is the 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 to refer to a specific TRP of the base station.

[0021]

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

[0022]

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

[0023]

[0026] Figure 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (indicated 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 one aspect, the macrocell base station 102 may include an eNB and / or ng-eNB on which the wireless communication system 100 is compatible with an LTE® network, or a gNB on which the wireless communication system 100 is compatible with an NR network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0024]

[0027] The base stations 102 may collectively form a RAN, and may interface via a backhaul link 122 with a core network 174 (e.g., an evolved packet core (EPC) or a 5G core (5GC)), and via the core network 174 with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The one or more location servers 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: transferring user data, wireless 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, delivery of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, 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 an EPC / 5GC) via a backhaul link 134, which may be wired or wireless.

[0025]

[0028] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage to a corresponding geographical coverage area 110. In one embodiment, one or more cells may be supported by base stations 102 within each geographical coverage area 110. A “cell” is a logical communication entity used for communication with a base station (over several frequency resources, e.g., called carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), 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 that may provide access for different types of UEs (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others). Since cells are supported by specific base stations, the term “cell” may, depending on the context, refer to either or both the logical communication entity and the base station that supports the cell. In some cases, the term “cell” may also refer to the geographical coverage area (e.g., sector) of a base station, insofar as the carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0026]

[0029] The geographical coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (for example, in the handover area), while some of the geographical coverage areas 110 may be significantly overlapped by larger geographical coverage areas 110. For example, a small cell base station 102' (indicated as "SC" instead of "small cell") may have a geographical coverage area 110' that significantly overlaps with the geographical coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations is sometimes known as a heterogeneous network. Heterogeneous networks may also include home eNBs (HeNBs) that can serve a limited group known as a closed subscriber group (CSG).

[0027]

[0030] The communication link 120 between base station 102 and UE 104 may include uplink (also called reverse link) transmission from UE 104 to base station 102, and / or downlink (DL) (also called forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be via one or more carrier frequencies. Carrier allocation may be asymmetric with respect to downlink and uplink (for example, more or fewer carriers may be allocated to downlink than to uplink).

[0028]

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

[0029]

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

[0030]

[0033] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that can operate at millimeter wave (mmW) frequencies and / or quasi-mmW frequencies while communicating with the UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths of 1 millimeter to 10 millimeters. Radio waves in this band are sometimes called millimeter waves. Quasi-mmW can extend to a frequency of 3 GHz with a wavelength of 100 millimeters. The very high frequency (SHF) band extends from 3 GHz to 30 GHz and is also called centimeter waves. Communication using the mmW / quasi-mmW radio frequency band has high propagation loss and relatively short distances. The mmW base station 180 and UE 182 may utilize beamforming (transmit and / or receive) via the mmW communication link 184 to compensate for the extremely high propagation loss and short distances. Furthermore, in alternative configurations, it will be understood that one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Therefore, it will be understood that the above examples are merely illustrative and should not be construed as limiting the various embodiments disclosed herein.

[0031]

[0034] Transmit beamforming is a technique for concentrating RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts that signal in all directions (omnidirectionally). Using transmit beamforming, a network node can determine where a given target device (e.g., a UE) is located (relative to the transmitting network node) and emit a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to one or more receiving devices. To change the directivity of an RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal in each of the one or more transmitters broadcasting the RF signal. For example, a network node may use an array of antennas (also called a "phased array" or "antenna array") that creates a beam of RF waves that can be "steered" to point in different directions without actually moving the antennas. In detail, RF current from the transmitter is supplied to individual antennas with the appropriate phase relationship, resulting in the radio waves from separate antennas combining and canceling out radiation in undesirable directions, while increasing radiation in desired directions.

[0032]

[0035] The transmitting beam may be quasi-co-located, meaning that to the receiver (e.g., UE), the transmitting beam appears to have the same parameters regardless of whether the transmitting antenna of the network node itself is physically co-located or not. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of a second reference RF signal of a 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, mean delay, and delay spread of a 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 a 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 mean 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 the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0033]

[0036] In receive beamforming, a receiver uses a received beam to amplify an RF signal detected on a given channel. For example, a receiver can amplify an RF signal received from a particular direction (e.g., increase its gain level) by increasing the gain setting of an antenna array in that direction and / or adjusting the phase setting. Therefore, 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 gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal intensity (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR)) of the RF signal received from that direction.

[0034]

[0037] The transmit beam and receive beam can 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 can 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 specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block, SSB) from a base station. The UE can then, based on the parameters of the receive beam, form a transmit beam to transmit an uplink reference signal (e.g., a sounding reference signal, SRS) to its base station.

[0035]

[0038] It should be noted that a “downlink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE forms a downlink beam, then it is a receive beam for receiving a downlink reference signal. Similarly, an “uplink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms an uplink beam, then it is an uplink receive beam, and if a 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, UE104 / 182) operate is divided into multiple frequency ranges: FR1 (450MHz to 6000MHz), FR2 (24250MHz to 52600MHz), FR3 (above 52600MHz), and FR4 (between FR1 and FR2). The mmW frequency band generally includes the FR2, FR3, and FR4 frequency ranges. Therefore, the terms "mmW" and "FR2," "FR3," or "FR4" may generally be used interchangeably.

[0037]

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

[0038]

[0041] For example, referring further to Figure 1, one of the frequencies used by the macrocell base station 102 may be the anchor carrier (or "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCell"). Simultaneous transmission and / or reception of multiple carriers allows UE 104 / 182 to significantly increase its data transmission rate and / or data reception rate. For example, two bundled 20MHz carriers in a multicarrier system would theoretically result in a doubling of the data rate (i.e., 40MHz) compared to the data rate achieved by a single 20MHz carrier.

[0039]

[0042] In the example in Figure 1, any of the illustrated UEs (shown in Figure 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 embodiment, the SVs 112 may be part of a satellite positioning system that the UEs 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) arranged to enable a receiver (e.g., UE 104) to determine its location on or above the Earth, at least in part, based on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. The transmitters are usually located within the SVs 112, but sometimes they may be located on a ground-based control station, base station 102, and / or other UEs 104. UE104 may include one or more dedicated receivers specifically designed to receive signals 124 from SV112 for deriving geolocation information.

[0040]

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

[0041]

[0044] In one embodiment, SV112 may, as an addition or alternative, be part of one or more non-terrestrial networks (NTN). In an NTN, SV112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which is then connected to an element in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in 5GC. This element then provides 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, UE104 may receive a communication signal (e.g., signal 124) from SV112 in place of, or in addition to, a communication signal from the terrestrial base station 102.

[0042]

[0045] In particular, leveraging the increased data rates and reduced latency of NR, vehicle-to-everything (V2X) communication technology is being implemented to support intelligent transportation systems (ITS) applications such as wireless communication between vehicles (V2V), between vehicles and roadside infrastructure (V2I), and between vehicles and pedestrians (V2P). The goal is for vehicles to sense their surroundings and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communication will enable improvements in safety, mobility, and the environment that current technologies cannot provide. When fully implemented, this technology is expected to reduce faulty vehicle collisions by 80%.

[0043]

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

[0044]

[0047] In one embodiment, sidelinks 162, 166, and 168 may operate on the wireless communication medium in question, which may be shared with other vehicles and / or infrastructure access points, as well as with other wireless communications between other RATs. The “medium” may consist of one or more time, frequency, and / or spatial communication 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 embodiment, side links 162, 166, and 168 may be cV2X links. The first generation of 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 range. Other countries may be allocated different bands. Therefore, as a specific example, the target medium utilized by side links 162, 166, and 168 may correspond to at least a portion of the licensed ITS frequency bands in the sub-6 GHz range. However, this disclosure is not limited to these frequency bands or cellular technologies.

[0046]

[0049] In one embodiment, sidelinks 162, 166, and 168 may be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way, short-to-medium-range wireless communication protocol that uses the Wireless Access for Vehicular Environments (WAVE) protocol, also known as IEEE 802.11p, for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification of the IEEE 802.11 standard and operates in the United States on the 5.9 GHz (5.85 GHz to 5.925 GHz) licensed ITS band. In Europe, IEEE 802.11p operates on the ITS G5A band (5.875 MHz to 5.905 MHz). Other countries may be allocated different bands. The V2V communications briefly described above are generally conducted in the United States on the Safety Channel, a 10 MHz channel dedicated to safety purposes. The remainder of the DSRC band (total bandwidth of 75 MHz) is used for other services targeting drivers, such as road regulations, toll collection, and automated parking. Therefore, as a specific example, the media used by side links 162, 166, and 168 may correspond to at least a portion of the 5.9 GHz licensed ITS frequency band.

[0047]

[0050] Alternatively, the medium in question could correspond to at least a portion of the unlicensed frequency bands shared among various RATs. While different licensed frequency bands are reserved for some communication systems (for example, 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) band, used by wireless local area network (WLAN) technology, especially IEEE 802.11x WLAN technology commonly known as "Wi-Fi." Exemplary systems of this type include various variants such as CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, and single-carrier FDMA (SC-FDMA) systems.

[0048]

[0051] Communication between V-UE160s is called V2V communication, communication between V-UE160s and one or more roadside access points 164s is called V2I communication, and communication between V-UE160s and one or more UE104s (where UE104s are P-UEs) is called V2P communication. V2V communication between V-UE160s may include information about the V-UE160s' position, speed, acceleration, direction of travel, and other vehicle data. V2I information received by V-UE160s from one or more roadside access points 164s may include information about road regulations and automated parking information. V2P communication between V-UE160s and UE104s may include information about the V-UE160s' position, speed, acceleration, and direction of travel, as well as the UE104s' position, speed (for example, if the UE104 is carried by a user on a bicycle), and direction of travel.

[0049]

[0052] Although Figure 1 only shows two UEs as V-UEs (V-UE160), it should be noted that any of the illustrated UEs (e.g., UE104, 152, 182, 190) could be V-UEs. In addition, although only V-UE160 and a single UE104 are shown as being connected via sidelinks, any of the UEs shown in Figure 1, regardless of whether they are V-UEs, P-UEs, etc., may be capable of sidelink communication. Furthermore, although only UE182 is described as being beamforming capable, any of the illustrated UEs, including V-UE160, may be beamforming capable. If V-UE160 is beamforming capable, it can beamform toward each other (i.e., toward other V-UE160s), toward roadside access point 164, toward other UEs (e.g., UE104, 152, 182, 190), etc. Therefore, in some cases, the V-UE160 may utilize beamforming on side links 162, 166, and 168.

[0050]

[0053] The wireless communication system 100 may further include one or more UEs, such as UE190, which are indirectly connected to one or more communication networks via one or more D2D peer-to-peer (P2P) links. In the example in Figure 1, UE190 has a D2D P2P link 192 with one of UE104 connected to one of base stations 102 (for example, UE190 may indirectly obtain cellular connectivity via link 192), and a D2D P2P link 194 with a WLAN STA152 connected to a WLAN AP150 (for UE190 may indirectly obtain WLAN-based internet connectivity via link 194). In one example, 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), or Bluetooth®. As another example, D2D P2P links 192 and 194 may be side links as described above with respect to side links 162, 166, and 168.

[0051]

[0054] Referring here to Figure 2A, a vehicle 260 (referred to as the “self vehicle” or “host vehicle”) is shown, which includes a camera sensor module 265 located in an internal compartment of the vehicle 260 behind the windshield 261. In one embodiment, the camera sensor module 265 may be located anywhere within the vehicle 260. In one embodiment, the vehicle 260 may be equipped with V2X technology that enables the vehicle 260 to communicate with other V2X-enabled entities, such as vehicles having on-board units (OBUs) with V2X technology, roadside units (RSUs) with V2X capability, and vulnerable road users (VRUs) with V2X capability. In one embodiment, the camera sensor module 265 may include a sensor 214 with a coverage zone 270, as shown in Figures 2A and 2B. The camera sensor module 265 is visible through the windshield 261 in a horizontal coverage zone 275 (indicated by a dashed line) and further includes a camera 212 for capturing images based on captured light waves. In one embodiment, the 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 sensors that can assist in the operation of the vehicle 260, including V2X technology.

[0052]

[0055] Figure 2A shows an example where the sensor and camera components are collated components in a shared housing, but as can be understood, they may be housed separately in different locations within the vehicle 260. For example, the camera 212 may be positioned as shown in Figure 2A, and the sensor 214 may be located in the grille or front bumper of the vehicle 260. Furthermore, Figure 2A shows a camera sensor module 265 located behind the windshield 261, but it may instead be located in a rooftop sensor array or elsewhere. In one embodiment, Figure 2A shows only a single camera sensor module 265, but as can be understood, the vehicle 260 may have multiple camera sensor modules 265 oriented in different directions (side, front, rear, etc.). Various camera sensor modules 265 may be located under the vehicle's "skin" (e.g., behind the windshield 261, door panels, bumpers, grille, etc.) or within a rooftop sensor array.

[0053]

[0056] The camera sensor module 265 can detect one or more objects (or no objects) relative to the vehicle 260. In the example in Figure 2A, there are two objects, vehicles 280 and 285, within the horizontal coverage zones 270 and 275 that the camera sensor module 265 can detect. In one embodiment, the camera sensor module 265 can estimate parameters of the detected object(s), such as position, range, direction, speed, size, and 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 adaptive cruise control (ACC), forward collision warning (FCW), collision mitigation or avoidance via automatic braking, and lane departure warning (LDW). Furthermore, in one embodiment, the camera sensor module 265 may be employed for V2X communication technology as described below.

[0054]

[0057] Figure 2B shows an onboard computer (OBC) 200 of a vehicle 260 in various embodiments of the present disclosure. In one embodiment, the OBC 200 may be an OBU installed on a vehicle such as vehicle 260. In one embodiment, the OBC 200 and camera sensor module 265 may be part of the ADAS or ADS of vehicle 260. In another embodiment, the OBC 200 may communicate with other entities on the road, such as OBUs, RSUs, and VRUs, using V2X communication technology. In one embodiment, vehicle 260 having the OBC 200 may be similar to a V-UE 160, and it should be noted that the OBC 200 may be similar to a UE 104, 190, or any other UE shown in Figure 1, and may further include one or more components known to those skilled in the art but not shown in Figure 2B. Thus, in one embodiment, the OBC 200 may be considered a mobile device. In some embodiments, 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 a variation thereof. The OBC 200 includes a non-temporary computer-readable storage medium, i.e., memory 204, and one or more processors 206 communicating with memory 204 via a data bus 208. Memory 204 includes one or more storage modules that store computer-readable instructions executable by one or more processors 206 to perform the functions of the OBC 200 described herein. For example, one or more processors 206 may work with memory 204 to 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 Figure 2 for brevity). In some embodiments, 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 the following: a lidar sensor, a radar sensor, an inertial measurement unit (IMU), a velocity sensor, and / or any other sensors that can 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 modules 265 and, optionally, to other vehicle subsystems (not shown) via a data bus 208.

[0056]

[0059] The OBC200 also includes, at least in some cases, a wireless wide area network (WWAN) transceiver 230 configured to communicate over one or more wireless communication networks (not shown), such as an NR network, an LTE network, or a GSM® network. The WWAN transceiver 230 may be connected to one or more antennas (not shown) to communicate with other network nodes, such as other vehicle UEs, pedestrian UEs, infrastructure access points, roadside units (RSUs), and base stations (e.g., eNBs, gNBs), over a wireless communication medium (e.g., some set of time / frequency resources in a particular frequency spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). The WWAN transceiver 230 may be configured in various ways 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.) according to the designated RAT. In one embodiment, the OBC 200 may use the WWAN transceiver 230 to transmit and receive sensor data sharing messages (SDSMs) via the 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 embodiment, the OBC 200 may use the WWAN transceiver 230 to transmit and receive SDSMs via the 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] The OBC200 also includes, in at least some cases, a Wireless Local Area Network (WLAN) transceiver 240. The WLAN transceiver 240 may be connected to one or more antennas (not shown) for communicating with other network nodes, such as other vehicle 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 Vehicle Environments (WAVE)), Dedicated Short-Range Communications (DSRC), etc.) over a wireless communication medium of interest. The WLAN transceiver 240 may be configured in various ways 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.) according to the designated RAT. In one embodiment, the OBC200 may use the 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 SDSM.

[0058]

[0061] As used herein, "transceiver" may include a transmitter circuit, a receiver circuit, or a combination thereof, but not all designs are required to provide both transmitting and receiving functions. For example, in some designs, when it is not necessary to provide complete communication, a low-function receiver circuit (e.g., a receiver chip or similar circuit that simply provides low-level sniffing) may be employed to reduce costs.

[0059]

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

[0060]

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

[0061]

[0064] In one embodiment, camera 212 may capture image frames (also referred to herein as camera frames) of the scene within the camera's field of view (as shown in Figure 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 embodiment, OBC 200 may use sensors 214 to detect objects in the surrounding environment in addition to camera 212. As described above, sensors 214 may include one or more of lidar sensors, radar sensors, inertial measurement units (IMUs), velocity sensors, and / or any other sensors that can assist in the operation of vehicle 260.

[0062]

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

[0063]

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

[0064]

[0067] In one embodiment, 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 can determine the time span relevance based on how long the data will be useful or relevant. For example, data received from the camera sensor module 265 regarding vehicles 280 and 285 may be relevant or useful in the near future, but irrelevant or not useful in the distant future. If vehicle 280 suddenly decelerates, the data detected by the camera sensor module 265 is likely to reflect the deceleration of vehicle 280. The processor 206 can receive data indicating deceleration and determine how long this data will be useful to vehicle 260 and other entities in the V2X network. The received data may be useful in the near or distant future. The processor 206 can determine that data indicating deceleration may be useful in the near future but not in the distant future. Data regarding the actions of vehicle 280 is unlikely to affect the actions of vehicle 260 or other entities in the V2X network one hour from now. Therefore, the time-span relevance of the data for vehicles 280 and 285 is likely to be relevant in the near future but not in the distant future.

[0065]

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

[0066]

[0069] As shown in Figure 2A, the camera sensor module 265 can detect the RSU 290 and transmit data about the RSU 290 to the processor 206. In the example shown in Figure 2A, the RSU 290 may be a fire hydrant with or without V2X technology. Based on the data from the camera sensor module 265, the processor 206 may 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 may determine the distance and time span relevance of this fact. The processor 206 may determine that the small leak from the RSU 290 will affect an entity located far from the vehicle 260, such as a local water company, and therefore the distance relevance of the RSU 290 data is remote. In addition, the processor 206 may determine that the time span relevance of the data is far future, since the small leak will not affect the actions of the vehicle 260 or other entities in the near future. In one embodiment, if the processor 206 determines that the data received from the camera sensor module 265 has a remote distance relevance and a distant future time span relevance, the processor 206 may transmit the SDSM to a V2X network or other entity using a V2I interface or V2N interface, such as a Uu interface, since such data has no immediate impact on nearby entities. For example, vehicle 260 may transmit an SDSM alert to a local water company via a Uu or V2I interface to warn the water company that the RSU 290 is leaking. In one embodiment, the Uu interface may be a radio interface connecting the UE to an enode B, gNB, or base station.

[0067]

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

[0068]

[0071] In addition, since stationary vehicle 285 can influence 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, the processor 206 may determine that the data concerning vehicle 285 has time-span relevance in both the near and far future. Thus, the data concerning vehicle 285 has relevance to vehicles that approach vehicle 285 in the near future and vehicles that approach vehicle 285 in the far future. Thus, the data received from the camera sensor module 265 concerning vehicle 285 has time-span relevance in both the near and far future. In one embodiment, if the processor 206 determines that the data received from the camera sensor module 265 has distance relevance in both proximity and distance, and time-span relevance in both the near and far future, the processor 206 may transmit the SDSM by using both the PC5 interface and a V2N / V2I interface such as the Uu interface. The PC5 interface can be used to send SDSM to nearby entities, while the Uu interface can be used to send it to distant entities or V2X networks.

[0069]

[0072] In one embodiment, 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 can determine the distance and time span relationships of the received data. Based on the decisions made by the network server, the network server can then instruct the processor 206 to transmit SDSM to other entities around the vehicle 260 using an appropriate interface such as PC5, V2N, V2I, and / or a Uu interface.

[0070]

[0073] The components of OBC200 in Figure 2B may be implemented in various ways. In some implementations, the components of OBC200 may be implemented by one or more circuits, such as one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 202-250 in OBC200 may be implemented by the processor(s) and memory components of OBC200 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor components). However, as can be understood, such operations, behaviors, and / or functions may actually be performed by specific components or combinations of components of OBC200.

[0071]

[0074] It will be understood that the embodiments include various methods for performing the processes, functions and / or algorithms disclosed herein. For example, Figure 3 shows a method 300 for sharing data about an object according to one embodiment. This method may be performed by devices such as the OBC 200, processor 206, vehicle 260, V-UE 160, UE 104, 190, or other UEs shown in Figure 1.

[0072]

[0075] In block 310, the method uses a sensor to detect an object. A camera sensor module 265 on the vehicle 260 can detect an object.

[0073]

[0076] In block 320, this method generates data about objects. The camera sensor module 265 can generate data about detected objects.

[0074]

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

[0075]

[0078] In 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 embodiment, a network server can determine the relevance of the data.

[0076]

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

[0077]

[0080] In block 360, this method transmits data by using the selected interface. Processor 206 can transmit data to other entities in the V2X network by using the selected interface.

[0078]

[0081] In the embodiments for carrying out the above invention, it will 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 explicitly stated within each clause. Rather, the various embodiments of this disclosure may contain fewer features than all the features of the individual exemplary clauses disclosed. Accordingly, the following clauses should be considered as incorporated into the description, and each clause may be valid on its own as a separate example. Each dependent clause may refer within itself to a particular combination with one of the other clauses, but the embodiments (singular or plural) of that dependent clause are not limited to that particular combination. It will be understood that other exemplary clauses may also contain combinations of embodiments (singular or plural) of dependent clauses with the subject matter of any other dependent or independent clause, or any combination of features with other dependent and independent clauses. Unless it is explicitly stated or easily inferred that a particular combination is not intended (e.g., contradictory embodiments such as defining an element as both an insulator and a conductor), the various embodiments disclosed herein explicitly include these combinations. Furthermore, even if a clause is not directly subordinate to an independent clause, it is intended that the form of the clause may be included in any other independent clause.

[0079]

[0082] Implementation examples are described in the following numbered clauses.

[0080]

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

[0081]

[0084] Clause 2. Relevance is defined as described in Clause 1, including distance relevance of data.

[0082]

[0085] Clause 3. Relevance is as described in Clause 2, further including time span relevance of the data.

[0083]

[0086] Clause 4. Distance relationship is determined in the manner described in Clause 2 or 3, based on another object affected by the data and the distance from that object to the sensor.

[0084]

[0087] Clause 5. Time span relevance is determined as described in Clause 3 or 4, 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 according to Clause 6, where the selected interface is the PC5 interface when the distance relationship is proximity and the time span relationship is near future.

[0087]

[0090] Clause 8. The method according to Clause 6 or 7, where the distance relation is remote and the time span relation is in the distant future, the selected interface is a V2N interface or a V2I interface.

[0088]

[0091] Clause 9. When the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is the PC5 interface and the V2N interface, as described in any of Clauses 6 to 8.

[0089]

[0092] Clause 10. The method described in any of Clauses 6-9, wherein the V2N interface is a Uu interface.

[0090]

[0093] Clause 11. A mobile device comprising memory, a sensor for detecting objects and generating data about the objects, 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 the relevance of the data, and select an interface for transmitting the data based on the relevance.

[0091]

[0094] Clause 12. Relevance includes data distance relevance, as defined in Clause 11 for mobile devices.

[0092]

[0095] Clause 13. Relevance includes the time span relevance of the data, as defined in Clause 12, for mobile devices.

[0093]

[0096] Clause 14. Distance relevance is based on the distance from another object affected by the data and the distance from that object to the sensor, as described in Clause 12 or 13 for the mobile device.

[0094]

[0097] Clause 15. Time span relevance is based on how long the data is useful, as defined in Clause 13 or 14 for mobile devices.

[0095]

[0098] Clause 16. A mobile device as described in any of Clauses 13-15, further configured to transmit data using a selected interface, with at least one processor.

[0096]

[0099] Clause 17. When the distance relation is proximity and the time span relation is near future, the selected interface is the PC5 interface, as described in Clause 16.

[0097]

[0100] Clause 18. When the distance relation is remote and the time span relation is in the distant future, the selected interface is a V2N interface or a V2I interface, as described in Clause 16 or 17 for the mobile device.

[0098]

[0101] Clause 19. When the distance relation is both near and far, and the time span relation is both near and far future, the selected interface is the PC5 interface and the V2N interface, as described in any of Clauses 16-18.

[0099]

[0102] Clause 20. A mobile device as described in any of Clauses 16-19, where 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 relating to the object based on the detection, means for receiving data from the sensor, means for determining the relevance of the data, and means for selecting an interface for transmitting the data based on the relevance.

[0101]

[0104] Clause 22. Relevance includes distance relevance of data, as defined in Clause 21.

[0102]

[0105] Clause 23. Relevance includes the time span relevance of the data, as defined in Clause 22, for mobile devices.

[0103]

[0106] Clause 24. Distance relationship is based on the distance from another object affected by the data and the distance from the other object to the sensor, as described in Clause 22 or 23 for the mobile device.

[0104]

[0107] Clause 25. Time span relevance is based on how long the data is useful, as defined in Clause 23 or 24 for mobile devices.

[0105]

[0108] Clause 26. A mobile device as described in any of Clauses 23 to 25, further including means for transmitting data using the selected interface.

[0106]

[0109] Clause 27. When the distance relation is proximity and the time span relation is near future, the selected interface is the PC5 interface, as described in Clause 26.

[0107]

[0110] Clause 28. When the distance relation is remote and the time span relation is in the distant future, the selected interface is a V2N interface or a V2I interface, as described in Clause 26 or 27 for the mobile device.

[0108]

[0111] Clause 29. When the distance relation is both near and far, and the time span relation is both near and far future, the selected interface is the PC5 interface and the V2N interface, as described in any of Clauses 26-28.

[0109]

[0112] Clause 30. A mobile device as described in any of Clauses 26-29, where the V2N interface is a Uu interface.

[0110]

[0113] Clause 31. A non-temporary computer-readable medium storing computer-executable instructions, wherein, when executed by a processor, the computer-executable instructions cause the processor to receive data relating to objects from a sensor, determine the relevance of the data, and select an interface for transmitting the data based on the relevance.

[0111]

[0114] Clause 32. Relevance includes distance relevance of data, as defined in Clause 31, in non-temporary computer-readable media.

[0112]

[0115] Clause 33. Relevance includes, further, the time-span relevance of the data, in the non-temporary computer-readable media described in Clause 32.

[0113]

[0116] Clause 34. Distance relationship is based on the distance to another object affected by the data and the distance from the other object to the sensor, as described in Clause 32 or 33, in a non-temporary computer-readable medium.

[0114]

[0117] Clause 35. Time-span relevance is based on how long the data is useful, as defined in non-temporary computer-readable media as described in Clause 33 or 34.

[0115]

[0118] Clause 36. A non-temporary computer-readable medium as described in any of Clauses 33 to 35, further including computer-executable instructions that, when executed by the processor, cause the processor to transmit data using a selected interface.

[0116]

[0119] Clause 37. When the distance relation is proximity and the time span relation is near future, the selected interface is the PC5 interface, which is a non-temporary computer-readable medium as described in Clause 36.

[0117]

[0120] Clause 38. When the distance relation is remote and the time span relation is in the distant future, the selected interface is a V2N interface or a V2I interface, a non-temporary computer-readable medium as described in either Clause 36 or 37.

[0118]

[0121] Clause 39. When the distance relation is both near and far, and the time span relation is both near and far future, the selected interface is the PC5 interface and the V2N interface, a non-temporary computer-readable medium as described in any of Clauses 36 to 38.

[0119]

[0122] Clause 40. A non-temporary computer-readable medium as described in any of Clauses 36-39, where the V2N interface is a Uu interface.

[0120]

[0123] Clause 41. An apparatus comprising 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 any method described in Clauses 1 to 40.

[0121]

[0124] Clause 42. Apparatus including means for performing the method described in any of Clauses 1 to 40.

[0122]

[0125] Clause 43. A non-temporary computer-readable medium storing computer-executable instructions, wherein the computer-executable instructions include at least one instruction causing a computer or processor to perform any of the methods described in Clauses 1 to 40.

[0123]

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

[0124]

[0127] Furthermore, those skilled in the art will understand that various exemplary logic blocks, modules, circuits, and algorithmic steps described in relation to the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly demonstrate this hardware-software compatibility, various exemplary components, blocks, modules, circuits, and steps have been outlined above in relation to their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for specific applications, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure.

[0125]

[0128] The various exemplary logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run using general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration.

[0126]

[0129] The methods, sequences, and / or algorithms described in relation to the embodiments disclosed herein may be embodied in hardware directly, in software modules executed by a processor, or in a combination of both. The software modules may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM®), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside in the user terminal as separate components.

[0127]

[0130] In one or more exemplary embodiments, the described functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via computer-readable media as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any media that facilitate the transfer of computer programs from one location to another. Storage media may be any available media accessible by a computer. Such computer-readable media, not limited to but including, are RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media accessible by a computer that may be used to carry or store desired program code in the form of instructions or data structures. Any connection is also appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of a medium. As used herein, disk and disc include compact disc (CD), laserdisc (registered trademark) (disc), optical disc (disc), digital versatile disc (DVD), floppy disk (registered trademark) (disk), and Blu-ray (registered trademark) disc (disc), where a disk typically reproduces data magnetically and a disc (disc) reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0128]

[0131] The above disclosures represent exemplary aspects of the Disclosure, but it should be noted that various changes and modifications can be made herein without departing from the scope of the Disclosure as defined by the appended claims. The functions, steps, and / or operations of the method claims in the aspects of the Disclosure described herein do not need to be performed in any particular order. Furthermore, elements of the Disclosure may be described or claimed in the singular, but the plural is intended unless a limitation to the singular is expressly stated. The invention described in the original claims of this application is listed below. [C1] A method for sharing data about an object, Detecting the object using a sensor, To generate the data relating to the object based on the detection, Receiving the data from the aforementioned sensor, To determine the relationships between the aforementioned data, Selecting an interface for transmitting the aforementioned data based on the aforementioned relevance, Methods that include... [C2] The method according to C1, wherein the relationship includes the distance relationship of the data. [C3] The method of C2, wherein the relationship further includes a time span relationship of the data. [C4] The method of C2, wherein the distance relationship is based on another object affected by the data and the distance from the other object to the sensor. [C5] The time span relationship is the method described in C3, based on how long the data is useful. [C6] Transmitting the data using the selected interface. The method described in C3, further including the above. [C7] The method according to C6, wherein the selected interface is a ProSe communication-5 (PC5) interface when the distance relationship is proximity and the time span relationship is near future. [C8] The method according to C6, wherein when the distance relationship is remote and the time span relationship is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface. [C9] The method according to C6, wherein when the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface. [C10] The method according to C8, wherein the V2N interface is a Uu interface. [C11] Memory and, A sensor that detects an object and generates data related to the object, At least one processor communicatively coupled to the memory, The at least one processor is provided The data is received from the aforementioned sensor, Determine the relationship between the aforementioned data, An interface for transmitting the aforementioned data is selected based on the relevance. A mobile device configured in such a way. [C12] The relationship includes the distance relationship of the data, as described in C11, for the mobile device. [C13] The mobile device according to C12, wherein the association further includes the time span association of the data. [C14] The mobile device according to C12, wherein the distance relationship is based on another object affected by the data and the distance from the other object to the sensor. [C15] The time span relevance is based on how long the data is useful, as described in C13 for the mobile device. [C16] The at least one processor, The data is transmitted using the selected interface. A mobile device as described in C13, further configured as follows. [C17] The mobile device according to C16, where the selected interface is the ProSe communication-5 (PC5) interface when the distance relationship is proximity and the time span relationship is near future. [C18] The mobile device according to C16, wherein when the distance relationship is remote and the time span relationship is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface. [C19] The mobile device according to C16, where the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface. [C20] The mobile device described in C18, wherein the V2N interface is a Uu interface. [C21] Means for detecting objects using sensors, Means for generating data relating to the object based on the detection, Means for receiving the data from the sensor, Means for determining the relationships between the aforementioned data, Means for selecting an interface for transmitting the aforementioned data based on the relevance, Mobile devices, including [C22] The relationship includes the distance relationship of the data, as described in C21, for the mobile device. [C23] The relationship further includes the time span relationship of the data, as described in C22, for the mobile device. [C24] The mobile device according to C22, wherein the distance relationship is based on another object affected by the data and the distance from the other object to the sensor. [C25] The time span relevance is based on how long the data is useful, as described in C23 for the mobile device. [C26] Means for transmitting the data using the selected interface Mobile devices as described in C23, including, furthermore. [C27] The mobile device according to C26, wherein the selected interface is the ProSe communication-5 (PC5) interface when the distance relationship is proximity and the time span relationship is near future. [C28] The mobile device according to C26, wherein when the distance relationship is remote and the time span relationship is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface. [C29] The mobile device according to C26, where the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface. [C30] The mobile device described in C28, wherein the V2N interface is a Uu interface. [C31] A non-temporary computer-readable medium storing computer-executable instructions, wherein, when executed by a processor, the computer-executable instructions cause the processor to receive data relating to an object from a sensor. Determine the relationship between the aforementioned data, A non-temporary computer-readable medium that causes an interface for transmitting the aforementioned data to be selected based on the aforementioned relevance. [C32] The relationship includes the distance relationship of the data, as described in C31, in a non-temporary computer-readable medium. [C33] The relationship described above further includes the time span relationship of the data, as described in C32, for a non-temporary computer-readable medium. [C34] The non-temporary computer-readable medium according to C32, wherein the distance relationship is based on another object affected by the data and the distance from the other object to the sensor. [C35] The time span relevance is based on how long the data is useful, as described in C33 for a non-temporary computer-readable medium. [C36] When executed by the aforementioned processor, the aforementioned processor: The selected interface is used to transmit the data. A non-temporary computer-readable medium as described in C33, further containing computer-executable instructions. [C37] When the distance relationship is proximity and the time span relationship is the near future, the selected interface is the ProSe communication-5 (PC5) interface, as described in C36, a non-temporary computer-readable medium. [C38] When the distance relation is remote and the time span relation is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface, the non-temporary computer-readable medium according to C36. [C39] When the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface, the non-temporary computer-readable medium as described in C36. [C40] The non-temporary computer-readable medium described in C38, wherein the V2N interface is a Uu interface.

Claims

1. A method for sharing data about an object, performed by a mobile device, Detecting the object using a sensor, To generate the data relating to the object based on the detection, Receiving the data from the aforementioned sensor, To determine the relationships between the aforementioned data, Selecting an interface for transmitting the data based on the relevance, wherein the relevance includes the distance relevance of the data and the time span relevance of the data, the distance relevance being based on another object affected by the data and the distance from the other object to the sensor, and the time span relevance being based on how long the data is useful. Methods that include...

2. To transmit the data using the selected interface. The method according to claim 1, further comprising:

3. The method according to claim 2, wherein when the distance relationship is proximity and the time span relationship 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 relationship is remote and the time span relationship is in the distant 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 relationship is both near and far, and the time span relationship is both near and 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. Memory and A sensor that detects an object and generates data related to the object, At least one processor is communicatively coupled to the memory, The at least one processor is Receiving the data from the aforementioned sensor, To determine the relationships between the aforementioned data, Selecting an interface for transmitting the data based on the relevance, wherein the relevance includes the distance relevance of the data and the time span relevance of the data, the distance relevance being based on another object affected by the data and the distance from the other object to the sensor, and the time span relevance being based on how long the data is useful. A mobile device configured to perform the following actions.

8. The aforementioned at least one processor, The data is transmitted using the selected interface. The mobile device according to claim 7, further configured as follows.

9. The mobile device according to claim 8, wherein when the distance relationship is proximity and the time span relationship is the near future, the selected interface is a ProSe communication-5 (PC5) interface.

10. The mobile device according to claim 8, wherein when the distance relationship is remote and the time span relationship is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface.

11. The mobile device according to claim 8, where the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface, when the distance relationship is both near and far and the time span relationship is both near and far future.

12. The mobile device according to claim 10, wherein the V2N interface is a Uu interface.

13. A non-temporary computer-readable medium storing computer-executable instructions, wherein, when the computer-executable instructions are executed by the processor, the processor... Receiving data about objects from sensors, To determine the relationships between the aforementioned data, Selecting an interface for transmitting the data based on the relevance, wherein the relevance includes the distance relevance of the data and the time span relevance of the data, the distance relevance being based on another object affected by the data and the distance from the other object to the sensor, and the time span relevance being based on how long the data is useful. A non-temporary computer-readable medium that enables the operation of [the process].

14. When executed by the aforementioned processor, the processor: The selected interface is used to transmit the data. A non-temporary computer-readable medium according to claim 13, further comprising computer-executable instructions.

15. When the distance relationship is proximity and the time span relationship is near future, the selected interface is the ProSe communication-5 (PC5) interface, or When the distance relationship is remote and the time span relationship is in the distant future, the selected interface is a vehicle-to-network (V2N) interface or a vehicle-to-infrastructure (V2I) interface, and the V2N interface is a Uu interface, or The non-temporary computer-readable medium according to claim 14, wherein when the distance relationship is both near and far, and the time span relationship is both near and far future, the selected interface is a ProSe communication-5 (PC5) interface and a vehicle-to-network (V2N) interface.

Images