Patent Description:
Many vehicles manufactured today are equipped with numerous sensors, including cameras, radar, Light Detection and Ranging (LIDAR) and ultrasound. These sensors are used to detect environment about the car, including other vehicles, obstacles and vulnerable road users (VRUs), such as pedestrians, cyclists, etc. To address instances where vehicle sensors are subject to occlusion, or objects are beyond the range of a vehicle's sensors, standards bodies, including SAE, ETSI-ETS and CSAE, are defining application-layer standards for vehicle-to-everything (V2X) sensor-sharing, or the dissemination of detected vehicles and/or objects. These standards are applicable to any V2X entity, including vehicles, infrastructure Road Side Units (RSUs) and V2X-equipped mobile devices.

Patent application publication <CIT> discloses a method at computing device associated with a parked vehicle, the method including receiving a request for sensor information from an external computing device, the request including an area of interest; activating sensors of the parked vehicle; obtaining sensor data for the area of interest; and providing a response to the external computing device. Patent application publication <CIT>) discloses an information processing apparatus, which obtains, from a right/left-turn vehicle, first obtaining information for providing an instruction to sense a blind-spot area of the right/left-turn vehicle, and determines whether to sense the blind-spot area on the basis of the first obtaining information.

In the following, each of the described methods, apparatuses, systems, examples and aspects which does not correspond to the invention as defined in the claims is present for illustration purposes or to highlight specific aspects or features of the claims. The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

A method of operating a vehicle apparatus includes monitoring, via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus; and transmitting, based on the monitoring, a first message that requests sensor data from one or more neighboring devices and indicates at least one sensor data filtering condition for the requested sensor data.

In some aspects, the at least one sensor data filtering condition specifies at least one region where sensor data is desired, or the at least one sensor data filtering condition specifies at least one region where sensor data is not desired, or a combination thereof.

In some aspects, the method includes detecting a first occluded region within the FOV based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the first occluded region as a region where sensor data is desired.

In some aspects, the first occluded region corresponds to a 2D region or 3D region, or the first occluded region is based on one or more angular ranges relative to one or more reference points, or any combination thereof.

In some aspects, the method includes detecting a second occluded region within the FOV of the vehicle apparatus based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the second occluded region as another region where sensor data is desired.

In some aspects, the method includes receiving, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the at least one neighboring communication device and is filtered based on the at least one sensor data filtering condition.

In some aspects, relative to a vehicle associated with the vehicle apparatus, the at least one neighboring communication device is associated with a neighboring vehicle, a neighboring vulnerable road user (VRU), or a neighboring roadside unit (RSU).

In some aspects, the transmitting transmits the first message via a vehicle-to-vehicle (V2V) protocol or vehicle-to-everything (V2X) protocol.

In some aspects, the first message is an application-layer message.

A method of operating a communication device includes receiving, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a field of view (FOV) of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data; and determining, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data.

In some aspects, the at least one sensor data filtering condition for the requested sensor data includes an indication of a first occluded region as a region where sensor data is desired.

In some aspects, the at least one sensor data filtering condition for the requested sensor data further includes an indication of a second occluded region as another region where sensor data is desired.

In some aspects, the determining determines that sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data, further comprising: filtering, based on the at least one sensor data filtering condition, sensor data obtained at the communication device via a set of sensors communicatively coupled to the communication device; and transmitting, to the vehicle apparatus, a second message including the filtered sensor data.

In some aspects, the transmitting transmits the second message via a vehicle-to-vehicle (V2V) protocol or vehicle-to-everything (V2X) protocol.

In some aspects, relative to a vehicle associated with the vehicle apparatus, the communication device is associated with a neighboring vehicle, a neighboring vulnerable road user (VRU), or a neighboring roadside unit (RSU).

In some aspects, the request for the sensor data and the at least one sensor data filtering condition is included in the first message expressly.

The request for the sensor data and the at least one sensor data filtering condition is included in the first message implicitly.

The first message comprises a location of the vehicle apparatus, further comprising: detecting at least one occluded region in the FOV of the vehicle apparatus based on the location of the vehicle apparatus, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

The first message comprises sensor data that depicts at least part of the FOV of the vehicle apparatus, further comprising: detecting at least one occluded region in the FOV of the vehicle apparatus based on the sensor data in the first message, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

In an aspect, a vehicle apparatus includes a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: monitor, via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus; and cause the communication interface to transmit, based on the monitoring, a first message that requests sensor data from one or more neighboring devices and indicates at least one sensor data filtering condition for the requested sensor data.

In some aspects, the at least one processor is further configured to: detect a first occluded region within the FOV based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the first occluded region as a region where sensor data is desired.

In some aspects, the at least one processor is further configured to: detect a second occluded region within the FOV of the vehicle apparatus based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the second occluded region as another region where sensor data is desired.

In some aspects, the at least one processor is further configured to: receive, via the communication interface, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the at least one neighboring communication device and is filtered based on the at least one sensor data filtering condition.

In an aspect, a communication device includes a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: receive, via the communication interface, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a field of view (FOV) of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data; and determine, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data.

The first message comprises a location of the vehicle apparatus, further comprising: detect at least one occluded region in the FOV of the vehicle apparatus based on the location of the vehicle apparatus, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

The first message comprises sensor data that depicts at least part of the FOV of the vehicle apparatus, further comprising: detect at least one occluded region in the FOV of the vehicle apparatus based on the sensor data in the first message, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

In an aspect, a vehicle apparatus includes means for monitoring, via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus; and means for transmitting, based on the monitoring, a first message that requests sensor data from one or more neighboring devices and indicates at least one sensor data filtering condition for the requested sensor data.

In some aspects, the method includes means for detecting a first occluded region within the FOV based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the first occluded region as a region where sensor data is desired.

In some aspects, the method includes means for detecting a second occluded region within the FOV of the vehicle apparatus based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the second occluded region as another region where sensor data is desired.

In some aspects, the method includes means for receiving, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the at least one neighboring communication device and is filtered based on the at least one sensor data filtering condition.

In an aspect, a communication device includes means for receiving, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a field of view (FOV) of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data; and means for determining, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data.

The first message comprises a location of the vehicle apparatus, further comprising: means for detecting at least one occluded region in the FOV of the vehicle apparatus based on the location of the vehicle apparatus, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

The first message comprises sensor data that depicts at least part of the FOV of the vehicle apparatus, further comprising: means for detecting at least one occluded region in the FOV of the vehicle apparatus based on the sensor data in the first message, wherein the detected at least one occluded region is interpreted by the communication device as an implicit request for sensor data in the at least one occluded region.

In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a vehicle apparatus, cause the vehicle apparatus to: monitor, via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus; and transmit, based on the monitoring, a first message that requests sensor data from one or more neighboring devices and indicates at least one sensor data filtering condition for the requested sensor data.

In some aspects, the one or more instructions further cause the vehicle apparatus to: detect a first occluded region within the FOV based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the first occluded region as a region where sensor data is desired.

In some aspects, the one or more instructions further cause the vehicle apparatus to: detect a second occluded region within the FOV of the vehicle apparatus based on the monitoring, wherein the at least one sensor data filtering condition for the requested sensor data includes an indication of the second occluded region as another region where sensor data is desired.

In some aspects, the one or more instructions further cause the vehicle apparatus to: receive, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the at least one neighboring communication device and is filtered based on the at least one sensor data filtering condition.

In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication device, cause the communication device to: receive, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a field of view (FOV) of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data; and determine, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data.

Aspects of the disclosure relate generally to a method and apparatus related to a vehicle request for sensor data with at least one sensor data filtering condition. A vehicle apparatus monitors, via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus. The vehicle apparatus transmits, based on the monitoring, a first message that requests sensor data from one or more neighboring communication devices and indicates at least one sensor data filtering condition for the requested sensor data. At least one of the neighboring communication devices receives the first message, and determines whether sensor data is available which satisfies the at least one sensor data filtering condition for the requested sensor data. If so, a second message is transmitted back to the vehicle apparatus that includes some or all of the requested sensor data. In a specific example, the at least one sensor data filtering condition may comprise an indication of one or more occluded regions in the FOV of the vehicle apparatus.

Additionally, well-known aspects of the disclosure may not be described in detail or may be omitted so as not to obscure more relevant details.

It will be recognized that various actions described herein can be performed by specific circuits (e.g., Application Specific Integrated Circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. In addition, for each of the aspects described herein, the corresponding form of any such aspect may be implemented as, for example, "logic configured to" perform the described action.

According to various aspects, <FIG> illustrates an exemplary wireless communications system 100A. The wireless communications system 100A (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102A and various UEs 104A. The base stations 102A may include macro cells (high power cellular base stations) and/or small cells (low power cellular base stations), wherein the macro cells may include Evolved NodeBs (eNBs), where the wireless communications system 100A corresponds to an LTE network, or gNodeBs (gNBs), where the wireless communications system 100A corresponds to a <NUM> network or a combination of both, and the small cells may include femtocells, picocells, microcells, etc..

The base stations 102A may collectively form a Radio Access Network (RAN) and interface with an Evolved Packet Core (EPC) or Next Generation Core (NGC) through backhaul links. In addition to other functions, the base stations 102A may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102A may communicate with each other directly or indirectly (e.g., through the EPC / NGC) over backhaul links 134A, which may be wired or wireless.

The base stations 102A may wirelessly communicate with the UEs 104A. Each of the base stations 102A may provide communication coverage for a respective geographic coverage area 110A. In an aspect, although not shown in <FIG>, geographic coverage areas 110A may be subdivided into a plurality of cells (e.g., three), or sectors, each cell corresponding to a single antenna or array of antennas of a base station 102A. As used herein, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station 102A, or to the base station 102A itself, depending on the context.

While neighboring macro cell geographic coverage areas 110A may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110A may be substantially overlapped by a larger geographic coverage area 110A. For example, a small cell base station 102A' may have a geographic coverage area 110A' that substantially overlaps with the geographic coverage area 110A of one or more macro cell base stations 102A. A network that includes both small cell and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120A between the base stations 102A and the UEs 104A may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104A to a base station 102A and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102A to a UE 104A. The communication links 120A may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

The wireless communications system 100A may further include a wireless local area network (WLAN) access point (AP) 150A in communication with WLAN stations (STAs) 152A via communication links 154A in an unlicensed frequency spectrum (e.g., <NUM>). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152A and/or the WLAN AP 150A may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell base station 102A' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102A' may employ LTE or <NUM> technology and use the same <NUM> unlicensed frequency spectrum as used by the WLAN AP 150A. The small cell base station 102A', employing LTE / <NUM> in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. LTE in an unlicensed spectrum may be referred to as LTE-unlicensed (LTE-U), licensed assisted access (LAA), or MulteFire.

The wireless communications system 100A may further include a mmW base station 180A that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182A. Radio waves in this band may be referred to as a millimeter wave (mmW). The mmW base station 180A may utilize beamforming 184A with the UE 182A to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102A may also transmit using mmW or near mmW and beamforming.

The wireless communications system 100A may further include one or more UEs, such as UE 190A, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the embodiment of <FIG>, UE 190A has a D2D P2P link 192A with one of the UEs 104A connected to one of the base stations 102A (e.g., through which UE 190A may indirectly obtain cellular connectivity) and a D2D P2P link 194A with WLAN STA 152A connected to the WLAN AP 150A (through which UE 190A may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192A-194A may be supported with any well-known D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), BLUETOOTH, and so on.

In some systems, there are six levels that have been defined to achieve full automation. At Level <NUM>, the human driver does all the driving. At Level <NUM>, an Advanced Driver Assistance System (ADAS) on the vehicle can sometimes assist the human driver with either steering or braking/accelerating, but not both simultaneously. At Level <NUM>, an ADAS on the vehicle can itself actually control both steering and braking/accelerating simultaneously under some circumstances. The human driver must continue to pay full attention at all times and perform the remainder of the driving tasks. At Level <NUM>, an ADS on the vehicle can itself perform all aspects of the driving task under some circumstances. In those circumstances, the human driver must be ready to take back control at any time when the ADS requests the human driver to do so. In all other circumstances, the human driver performs the driving task. At Level <NUM>, an ADS on the vehicle can itself perform all driving tasks and monitor the driving environment, essentially doing all of the driving, in certain circumstances. The human occupant need not pay attention in those circumstances. At Level <NUM>, an ADS on the vehicle can do all the driving in all circumstances. The human occupants are just passengers and need never be involved in driving.

These and other safety technologies use a combination of hardware (sensors, cameras, and radar) and software to help vehicles identify certain safety risks so they can warn the driver to act (in the case of an ADAS), or act themselves (in the case of an ADS), to avoid a crash. A vehicle outfitted with an ADAS or ADS includes one or more camera sensors mounted on the vehicle that capture images of the scene in front of the vehicle, and also possibly behind and to the sides of the vehicle. Radar systems may also be used to detect objects along the road of travel, and also possibly behind and to the sides of the vehicle. Radar systems utilize radio frequency (RF) waves to determine the range, direction, speed, and/or altitude of the objects along the road. More specifically, a transmitter transmits pulses of RF waves that bounce off any object(s) in their path. The pulses reflected off the object(s) return a small part of the RF waves' energy to a receiver, which is typically located at the same location as the transmitter. The camera and radar are typically oriented to capture their respective versions of the same scene.

A processor, such as a digital signal processor (DSP), within the vehicle analyzes the captured camera images and radar frames and attempts to identify objects within the captured scene. Such objects may be other vehicles, pedestrians, road signs, objects within the road of travel, etc. The radar system provides reasonably accurate measurements of object distance and velocity in various weather conditions. However, radar systems typically have insufficient resolution to identify features of the detected objects. Camera sensors, however, typically do provide sufficient resolution to identify object features. The cues of object shapes and appearances extracted from the captured images may provide sufficient characteristics for classification of different objects. Given the complementary properties of the two sensors, data from the two sensors can be combined (referred to as "fusion") in a single system for improved performance.

To further enhance ADAS and ADS systems, especially at Level <NUM> and beyond, autonomous and semi-autonomous vehicles may utilize high definition (HD) map datasets, which contain significantly more detailed information and true-ground-absolute accuracy than those found in current conventional resources. Such HD maps may provide accuracy in the <NUM>-<NUM> absolute ranges, highly detailed inventories of all stationary physical assets related to roadways, such as road lanes, road edges, shoulders, dividers, traffic signals, signage, paint markings, poles, and other data useful for the safe navigation of roadways and intersections by autonomous / semi-autonomous vehicles. HD maps may also provide electronic horizon predictive awareness, which enables autonomous / semi-autonomous vehicles to know what lies ahead.

Referring now to <FIG>, a vehicle 100B is illustrated that includes a radar-camera sensor module 120B located in an interior compartment of the vehicle 100B behind a windshield 112B. The radar-camera sensor module 120B includes a radar sensor component configured to transmit radar signals through the windshield 112B in a horizontal coverage zone 150B (shown by dashed lines), and receive reflected radar signals that are reflected off of any objects within the coverage zone 150B. The radar-camera sensor module 120B further includes a camera component for capturing images based on light waves that are seen and captured through the windshield <NUM> in a horizontal coverage zone 160B (shown by dashed lines). The respective coverage zones 150B and 160B form part of the field of view (FOV) of the vehicle 100B. In some cases, each sensor that is communicatively coupled (e.g., mounted on) a respective vehicle may be characterized as having its own FOV, each of which constitutes an example of a FOV for the vehicle 100B. In this case, the vehicle 100B may be characterized as having multiple FOVs (e.g., one for each sensor). Alternatively, sensors may be arranged in groups (e.g., one or more sensor groups), with each sensor group characterized as having its own FOV, each of which constitutes an example of a FOV for the vehicle 100B. Alternatively, the FOVs of individual sensors and/or sensor groups may be aggregated (e.g., so that an occluded region in one sensor's FOV can be patched by another sensor's FOV via the aggregation). Accordingly, as used herein, a FOV of the vehicle 100B may reference either a sensor-specific or sensor group-specific FOV, or alternatively an aggregation of FOVs from various sensors and/or sensor groups.

Although <FIG> illustrates an example in which the radar sensor component and the camera component are collocated components in a shared housing, as will be appreciated, they may be separately housed in different locations within the vehicle 100B. For example, the camera part of the radar-camera sensor module 120B may be located as shown in <FIG>, and the radar sensor part of the radar-camera sensor module 120B may be located in the grill or front bumper of the vehicle 100B. Additionally, although <FIG> illustrates the radar-camera sensor module 120B located behind the windshield 112B, it may instead be located in a rooftop sensor array, or elsewhere. Further, although <FIG> illustrates only a single radar-camera sensor module 120B, as will be appreciated, the vehicle 100B may have multiple radar-camera sensor modules 120B pointed in different directions (to the sides, the front, the rear, etc.). The various radar-camera sensor modules 120B may be under the "skin" of the vehicle (e.g., behind the windshield 112B, door panels, bumpers, grills, etc.) or within a rooftop sensor array.

The radar-camera sensor module 120B may detect one or more (or none) objects relative to the vehicle 100B. In the example of <FIG>, there are two objects, vehicles 130B and 140B, within the horizontal coverage zones 150B and 160B that the radar-camera sensor module 120B can detect. The radar-camera sensor module 120B may estimate parameters of the detected object(s), such as the position, range, direction, speed, size, classification (e.g., vehicle, pedestrian, road sign, etc.), and the like. The radar-camera sensor module 120B may be employed onboard the vehicle 100B for automotive safety applications, such as adaptive cruise control (ACC), forward collision warning (FCW), collision mitigation or avoidance via autonomous braking, lane departure warning (LDW), and the like. More specifically, the radar-camera sensor module <NUM> may be part of an onboard unit (OBU) (alternatively referred to as an on-board computer (OBC)), which is described in more detail below with respect to <FIG>.

In one or more aspects, co-locating the camera and radar sensor permits these components to share electronics and signal processing, and in particular, enables early radar-camera data fusion. For example, the radar sensor and camera may be integrated onto a single board. A joint radar-camera alignment technique may be employed to align both the radar sensor and the camera. However, collocation of the radar sensor and camera is not required to practice the techniques described herein.

In the aspect of <FIG>, vehicles 100B, 130B and 140B are traveling in the same direction along a road in proximity to a roadside unit (RSU) 170B, whereby vehicle 140B is in a first lane ("Lane <NUM>") and vehicles 100B and 130B are in a second lane ("Lane <NUM>"). The RSU 170B may correspond to one of a plurality of fixed reference nodes that are deployed along various roadways. RSUs may form part of a Vehicular ad-hoc networks (VANET) and may be configured for direct communication with vehicles via a vehicle-to-vehicle (V2V) communications protocol or vehicle-to-everything (V2X) communications protocol, while further being connected to one or more communication networks (e.g., wireless communications system 100A of <FIG>) via a wired or wireless backhaul connection. In an example, the RSU 170B may correspond to a small cell or an access point as described above with respect to the wireless communications system 100A of <FIG>. In some aspects, the RSU 170B may be implemented as a vehicle management entity that manages (or coordinates actions) between the neighboring vehicles 100B, 130B and 140B. The RSU 170B may be equipped with various functionalities, including but not limited to short-range communications (e.g., <NUM> Direct Short Range Communications (DSRC), non-DSRC technologies as means of facilitating communication for vehicle-to-vehicle (V2V) and/or vehicle-to-infrastructure (V2I) applications, etc.), location-detection (e.g., GPS, etc.), communicative support functions (e.g., a WiFi hotspot, etc.), navigational support functions (e.g., local map data, Signal Phase and Timing (SPaT) information for intersection-based applications and localized roadway warnings, etc.), and so on.

Referring to <FIG>, in one aspect, the vehicles 130B and 140B may be similarly provisioned with respective radar-camera sensor modules 120B, and may be capable of direct vehicle-to-vehicle (V2V) communication via respective communication interfaces. However, it is also possible for only one or even none of vehicles 130B and 140B to be equipped with such 'smart' vehicle technology.

<FIG> illustrates an on-board unit (OBU) <NUM> of the vehicle 100B of <FIG>, according to various aspects. In an aspect, the OBU <NUM> may be referred to herein as a vehicle apparatus, and may be part of an ADAS or ADS. The OBU <NUM> includes a non-transitory computer-readable storage medium, i.e., memory <NUM>, and one or more processors <NUM> in communication with the memory <NUM> via a data bus <NUM>. The memory <NUM> includes one or more storage modules storing computer-readable instructions executable by the processor(s) <NUM> to perform the functions of the OBU <NUM> described herein.

One or more radar-camera sensor modules 120B are coupled to the OBU <NUM> (only one is shown in <FIG> for simplicity). In some aspects, the radar-camera sensor module 120B includes at least one camera <NUM> (e.g., a forward-facing camera as shown via the coverage zone 160B in <FIG>), at least one radar sensor <NUM>, and an optional Light Detection and Ranging (LIDAR) sensor <NUM>. While not shown expressly, the radar-camera sensor module 120B may further optionally include a Sound Navigation and Ranging (SONAR) detector, a Radio Detection and Ranging (RADAR) detector, and/or an infrared detector. The OBU <NUM> also includes one or more communication interfaces <NUM> connecting the processor(s) <NUM>, by way of the data bus <NUM>, to the radar-camera sensor module 120B, other vehicle sub-systems (not shown), and in some cases, wireless communication networks (not shown), such as wireless local area networks (WLANs), global positioning systems (GPS) networks, cellular telecommunication networks, and the like. In an example, the one or more communication interfaces <NUM> may include a network interface (e.g., a wireless LTE, <NUM> NR, a wired backhaul connection to a core network component, etc.) to connect to one or more network access points or base stations (e.g., cellular base stations, RSUs, etc.), and a second interface (e.g., V2X, <NUM> DSRC, etc.) to connect directly to nearby (or neighboring) vehicles. In an example, V2X connections may be implemented via unicast, multicast or broadcast protocols. The various V2X connections described below may be implemented in accordance with any one of these protocols.

In an aspect, the OBU <NUM> may utilize the communication interfaces <NUM> to download one or more maps <NUM> that can then be stored in memory <NUM> and used for vehicle navigation. Map(s) <NUM> may be one or more high definition (HD) maps, which may provide accuracy in the <NUM>-<NUM> absolute ranges, highly detailed inventories of all stationary physical assets related to roadways, such as road lanes, road edges, shoulders, dividers, traffic signals, signage, paint markings, poles, and other data useful for the safe navigation of roadways and intersections by vehicle 100B. Map(s) <NUM> may also provide electronic horizon predictive awareness, which enables the vehicle <NUM> to know what lies ahead.

In an aspect, the camera <NUM> may capture image frames of the scene within the viewing area of the camera <NUM> (as illustrated in <FIG> as horizontal coverage zone 160B) at some periodic rate. Likewise, the radar sensor <NUM> may capture radar frames of the scene within the viewing area of the radar sensor <NUM> (as illustrated in <FIG> as horizontal coverage zone 150B) at some periodic rate. The periodic rates at which the camera <NUM> and the radar sensor <NUM> capture their respective frames may be the same or different. In an aspect, each camera and radar frame may be timestamped. Thus, where the periodic rates are different, the timestamps can be used to select simultaneously, or nearly simultaneously, captured camera and radar frames for further processing (e.g., fusion).

<FIG> illustrates components of the RSU 170B of <FIG> according to various aspects. In an aspect, the RSU 170B is configured with a memory <NUM>, and one or more processors <NUM> in communication with the memory <NUM> via a data bus <NUM>. The RSU 170B further includes one or more network communication interfaces <NUM>, which may be used to communicatively couple the RSU 170B to a communications network (e.g., a macro base station, another RSU, a core network component, etc.) via a wired or wireless backhaul connection. The RSU 170B is further configured with a RSU-to-vehicle communications interface <NUM> (e.g., V2X, <NUM> DSRC, etc.) for direct RSU-to-vehicle communication. The RSU 170B is also optionally configured with a sensor module <NUM>, which may be configured with any combination of camera(s), radar, LIDAR, GPS, etc. As will be described below in more detail, in certain aspects the sensor module <NUM> may be used to scan the locations of a set of neighboring vehicles to obtain sensor data that replaces and/or supplements sensor data measured or derived by one or more of the neighboring vehicles.

<FIG> is a flow diagram illustrating an example method <NUM> of communication in accordance with an aspect of the present disclosure. The method <NUM> may be performed, for example, by a vehicle apparatus <NUM> (or more specifically, by a computer or OBU on-board a vehicle), which may be associated with a vehicle such as the vehicle 100B described above with respect to <FIG>.

Referring to <FIG>, at block <NUM>, the vehicle apparatus <NUM> (e.g., OBU <NUM> of <FIG>) monitors via a set of sensors (e.g., radio-camera sensor module 120B of <FIG>) communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus.

At block <NUM>, the vehicle apparatus <NUM> (e.g., OBU <NUM> of <FIG>) optionally detects a first occluded region within the FOV based on the monitoring. In this case, the at least one sensor data filtering condition for the requested sensor data may include an indication of the first occluded region as a region where sensor data is desired. In a further aspect, one or more additional occluded regions within the FOV of the vehicle apparatus may further be detected based on the monitoring, in which case the at least one sensor data filtering condition for the requested sensor data further includes an indication of these additional occluded regions as other regions where sensor data is desired. In an example, one or more of the occluded regions may be defined as a 2D region (or planar region) or a 3D region, one or more of the occluded regions may be based on one or more angular ranges relative to one or more reference points (e.g., a representative location of the associated vehicle, a sensor-specific location, etc.), or any combination thereof. In an example, the first message may correspond to a unicast, multicast or broadcast message with an application-layer part that includes the indicates at least one sensor data filtering condition.

At block <NUM>, the vehicle apparatus <NUM> (e.g., one or more of communication interfaces <NUM>) transmits, based on the monitoring, a first message that requests sensor data from one or more neighboring communication devices and indicates at least one sensor data filtering condition for the requested sensor data. In an example, the at least one sensor data filtering condition specifies at least one region where sensor data is desired, at least one region where sensor data is not desired, or a combination thereof. In an example, the first message may be transmitted via a vehicle-to-vehicle (V2V) protocol or vehicle-to-everything (V2X) protocol. In an example, the first message may correspond to an application-layer (or L3) message. In some designs, the sensor data request may correspond to a one-time request data. In other designs, the sensor data request may correspond to a request for sensor data for some period of time (e.g., sharing a video camera feed for some amount of time, e.g., until the neighboring communication device(s) are no longer in range, or until some expiration time is reached, etc.).

At block <NUM>, the vehicle apparatus <NUM> (e.g., one or more of communication interfaces <NUM>) receives, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the respective neighboring communication device and is filtered based on the at least one sensor data filtering condition. In some designs, relative to a vehicle associated with the vehicle apparatus <NUM>, the at least one neighboring communication device may be associated with a neighboring vehicle, a neighboring vulnerable road user (VRU), or a neighboring roadside unit (RSU). In an example, the second message may correspond to a unicast message with an application-layer part that includes the filtered sensor data.

<FIG> is a flow diagram illustrating an example method <NUM> of communication in accordance with another aspect of the present disclosure. The method <NUM> may be performed, for example, by a communication device <NUM>, which may be associated with a vehicle such as the vehicle 100B described above with respect to <FIG>, an infrastructure device such as RSU 170B, a VRU (e.g., a UE operated by a bicyclist or a pedestrian), a V2X-equipped mobile device, etc..

At block <NUM>, the communication device <NUM> (e.g., one or more of communication interfaces <NUM>, the RSU-to-vehicle communications interface <NUM>, a communications interface associated with a UE operated by a VRU, etc.) receives, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a FOV of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data. In an example, the first message received at <NUM> may correspond to the first message transmitted at <NUM> of <FIG>. In an example, the first message may correspond to a unicast, multicast or broadcast message with an application-layer part that includes the indicates at least one sensor data filtering condition. In some designs, the sensor data request may correspond to a one-time request data. In other designs, the sensor data request may correspond to a request for sensor data for some period of time (e.g., sharing a video camera feed for some amount of time, e.g., until the neighboring communication device(s) are no longer in range, or until some expiration time is reached, etc.).

At block <NUM>, the communication device <NUM> (e.g., processor(s) <NUM>, processor(s) <NUM>, processor(s) of a UE operated by a VRU, etc.) determines, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data. For example, if the at least one sensor data filtering condition specifies at least one region where sensor data is desired, then the communication device <NUM> can determine whether sensor data inside the at least one region is available at <NUM>. In another example, if the at least one sensor data filtering condition specifies at least one region where sensor data is not desired, then the communication device <NUM> can determine whether sensor data outside of the at least one region is available at <NUM>.

At block <NUM>, the communication device <NUM> (e.g., processor(s) <NUM>, processor(s) <NUM>, processor(s) of a UE operated by a VRU, etc.) optionally filters, based on the at least one sensor data filtering condition, sensor data obtained at the communication device via a set of sensors communicatively coupled to the communication. For example, if the at least one sensor data filtering condition specifies at least one region where sensor data is desired, then the communication device <NUM> can filter out sensor data that is outside of the at least one region at <NUM>. In another example, if the at least one sensor data filtering condition specifies at least one region where sensor data is not desired, then the communication device <NUM> can filter out sensor data that is inside of the at least one region at <NUM>.

At block <NUM>, the communication device <NUM> (e.g., one or more of communication interfaces <NUM>, the RSU-to-vehicle communications interface <NUM>, a communications interface associated with a UE operated by a VRU, etc.) optionally transmits, to the vehicle apparatus, a second message including the filtered sensor data from optional block <NUM>. In an example, the second message may correspond to a unicast message with an application-layer part that includes the filtered sensor data.

Referring to <FIG>, in an aspect, the at least one sensor data filtering condition may include one or more 'occluded' regions. For example, in the presence of other vehicles, buildings or environmental features, the sensors mounted on a vehicle, RSU or other V2X entity may be occluded in a portion of the FOV. In an aspect, obtaining sensor data from another vehicle, VRU and/or an RSU allows the V2X entity subject to occlusion to fill in the gaps (at least partially) in the perception of its surroundings. For example, in some conventional designs, V2X entities from which sensor data is requested may share all sensor data (or identification of all objects) within their respective FOV. However, at least some part of this sensor data may be irrelevant to the requesting entity (e.g., outside of an occluded region, or outside of a relevant FOV region). As such, this information will not aid the vehicle experiencing occlusion, and will instead contribute to over-the-air congestion as well as processing overhead. Similarly, if the FOV is a superset of the obstructed region of the vehicle experiencing occlusion, it may include information already detected by the vehicle experiencing occlusion. Hence, in some designs, specifying at least one sensor data filtering condition (e.g., occluded region identification) may provide various technical advantages, such as reducing OTA congestion, reducing processing overhead and/or memory requirements, etc..

Referring to <FIG>, the at least one sensor data filtering condition is indicated implicitly. The first message at <NUM> may specify a location of the vehicle apparatus. The communication device <NUM> may then infer the at least one sensor data filtering condition from the specified vehicle location. In a specific example, assume that the first message indicates that the vehicle apparatus is positioned directly behind a vehicle to which the communication device <NUM> is coupled. In this case, the relative location of the vehicle apparatus implies that a region in front of this vehicle would be occluded in the FOV of the vehicle apparatus (e.g., because this vehicle itself constitutes a physical obstruction to the FOV of the vehicle apparatus). Instead of waiting for an explicit request for this sensor data, the communication device <NUM> can instead act in a more preemptive manner by interpreting the vehicle location data as an implicit indication of a sensor data filtering condition (e.g., implicitly requesting data in front of the vehicle to which the communication device <NUM> is coupled).

Alternative, the first message comprises at least part of the FOV of the vehicle apparatus itself. For example, the first message may comprise a image (e.g., a video frame or static image) that is captured from a camera of the vehicle apparatus. The communication device <NUM> can then scan the image to detect at least one occluded region. The communication device <NUM> may then infer the at least one sensor data filtering condition from the detected occluded region(s). Instead of waiting for an explicit request for this sensor data, the communication device <NUM> can instead act in a more preemptive manner by interpreting the 'raw' sensor data (e.g., image) as an implicit indication of a sensor data filtering condition (e.g., implicitly requesting data that is occluded from the FOV of the shared camera feed). In some designs, vehicles with communication devices that are capable of sharing sensor data in this manner may further be capable of advertising their sensor data sharing capability. In this case, the first message may be transmitted responsive to receipt of a sensor sharing capability message.

<FIG> illustrates a scenario <NUM> in which the processes of <FIG> may be implemented in accordance with an embodiment of the disclosure. In scenario <NUM>, a vehicle (V1) is approaching an intersection with a traffic light <NUM>. Another vehicle (V2) is stopped at the traffic light <NUM>. Also proximate to the intersection are VRUs <NUM>-<NUM>, whereby VRUs <NUM>-<NUM> are pedestrians and VRU <NUM> is a bicyclist. V1 has a FOV depicted as <NUM>, and V2 has a FOV depicted as <NUM>. Further depicted in scenario <NUM> are obstructions <NUM>-<NUM> (e.g., buildings, signs, etc.) that occlude part of the FOV <NUM> of V1. In an example, V1 and V2 may be configured as 'smart' vehicles, similar to vehicle 100B as described above.

<FIG> illustrates a zoomed-in perspective <NUM> of the scenario <NUM> in accordance with an embodiment of the disclosure. In <FIG>, occluded regions are defined based on respective angular ranges denoted as φ and θ relative to an axis <NUM> that is aligned with a reference point <NUM>. In an example, the reference point <NUM> may correspond to a sensor location of a sensor (or group of sensors) that is scanning the FOV <NUM>. For example, different sensor groups (or individual sensors) may be associated with their own sensor-specific or sensor group-specific FOVs. In another example, the reference point <NUM> may correspond to a default or representative reference point for V1 that is independent of sensor location or is based on multiple sensor locations (e.g., an averaged or weighted-averaged location of the distributed sensors of V1 is used as the reference point <NUM>). As shown in <FIG>, occluded regions φ and θ are defined by the obstructions <NUM>-<NUM>, which block part of the FOV <NUM>. In this case, the result is that VRUs <NUM>-<NUM> are not detected within the FOV <NUM> due to the occluded regions φ and θ.

However, while not visible to V1, VRUs <NUM>-<NUM> are part of the FOV <NUM> of V2. Hence, via execution of the processes of <FIG>, V1 can transmit a request for sensor data (e.g., via V2X, V2V, etc.) that identifies the occluded regions φ and θ, and V2 can receive the sensor data request, determine that V2 has some sensor data that maps to the occluded regions φ and θ, and can respond with the requested sensor data (e.g., via V2X, V2V, etc.). In some designs, the response from V2 can indicate the raw sensor data for the occluded regions φ and θ. In other designs, V2 can indicate object-specific information, such as the locations of VRUs <NUM>-<NUM>.

<FIG> illustrates another scenario <NUM> in which the processes of <FIG> may be implemented in accordance with another embodiment of the disclosure. In scenario <NUM>, a vehicle (V1) is driving behind a truck (T1) that is in turn driving behind a vehicle (V2). A vehicle (V3) is driving in the opposite direction towards V1, T1 and V2. V1 has a FOV depicted as <NUM>. In an example, V1 and V2 may be configured as 'smart' vehicles, similar to vehicle 100B as described above. However, V3 is a legacy vehicle that does not have 'smart' interactive capability (e.g., V2X).

In the scenario <NUM>, T1 is positioned as an obstruction to V2's FOV <NUM>, which results in an occluded region denoted as θ relative to a respective axis (not shown expressly in <FIG>) that is aligned with a reference point <NUM>. In an example, the reference point <NUM> may correspond to a sensor location of a sensor (or group of sensors) that is scanning the FOV <NUM>. For example, different sensor groups (or individual sensors) may be associated with their own sensor-specific or sensor group-specific FOVs. In another example, the reference point <NUM> may correspond to a default or representative reference point for V1 that is independent of sensor location or is based on multiple sensor locations (e.g., an averaged or weighted-averaged location of the distributed sensors of V1 is used as the reference point <NUM>). In this case, the result is that V2 is not detected within V1's FOV <NUM> due to the occluded region θ.

However, while not visible to V1, V2 is not obstructed with respect to V3's FOV (not expressly shown in <FIG>). Hence, via execution of the processes of <FIG>, V1 can transmit a request for sensor data (e.g., via V2X, V2V, etc.) that identifies the occluded region θ, and V3 can receive the sensor data request, determine that V3 has some sensor data that maps to the occluded region θ, and can respond with the requested sensor data (e.g., via V2X, V2V, etc.). In some designs, the response from V3 can indicate the raw sensor data for the occluded region θ. In other designs, V3 can indicate object-specific information, such as the locations of V2.

Referring to <FIG>, as an alternative, V1 indicates its location instead of an explicit occlusion region identification (e.g., θ). In this case, V3 receives V1's location message and then use its own knowledge of the relative locations of T1 and V2 to intuit that V1 most likely has no knowledge of V2's presence. Hence, the location message from V1 is interpreted as an implicit request for sensor data for an implicitly indicated occluded region for V1 (in this case, a region that comprises V2).

<FIG> illustrates another scenario <NUM> in which the processes of <FIG> may be implemented in accordance with another embodiment of the disclosure. In scenario <NUM>, a vehicle (V1) is driving proximate to a physical objection <NUM> that occludes part of V1's FOV <NUM>. In <FIG>, an occluded region which may be denoted as (θ<NUM>, θ<NUM>) is defined based on respective angular start and stop points, denoted as θ<NUM> and θ<NUM> relative to an axis <NUM> that is aligned with a reference point <NUM>. Similar to <FIG>, the reference point <NUM> may be a representative location for V1, or may be sensor-specific or sensor-group specific.

Referring to <FIG>, in some designs, the occluded region (θ<NUM>, θ<NUM>) may be indicated in an OTA application-layer message that may be defined by a C-V2X standard (e.g., SAE, ETSI-ITS, C-SAE/C-ITS, etc.), whereby the parameters θ<NUM> and θ<NUM> are specified via Information Element (IE) data fields or data elements in a new, dedicated OcclusionAssistance message or appended to an existing message, such as an SAE SensorSharing message.

One example of a dedicated application-layer OcclusionAssistance message is shown below in Table <NUM>:.

In Table <NUM>, the OcclusionAssistance message is specific to 2D occlusion regions, although other embodiments may encompass 3D occlusion regions as well. The OcclusionRegion Message Part includes new fields that are added to a standard HostData section. In an example, fields in the HostData Message Part may be used to derive the reference point <NUM>. In this case, each OcclusionAngle Element for each respective 2D occlusion region may specify the parameters θ<NUM> and θ<NUM> for a particular occlusion region. In Table <NUM>, the parameters θ<NUM> and θ<NUM> are defined more specifically, relative to WGS84 North, which in this case corresponds to the axis <NUM>.

<FIG> illustrates an example whereby the IE data fields or data elements are appended to an existing message, such as an SAE SensorSharing message, so as to convey the parameters θ<NUM> and θ<NUM> shown in <FIG>, in accordance with an embodiment of the disclosure. In the example of <FIG>, a new Element objCount indicates a detected object count (DE_DetectedObjectCount) and a new Element detObj indicates a sequence or listing of the detected objects (DF_DetectedObject). For example, these fields may be used by V1 in <FIG> to report its own known or detected objects (e.g., VRUs, other vehicles, obstructions, etc.), so that neighboring devices can identify objects (e.g., VRUs, other vehicles, obstructions, etc.) that have not been identified by V1 due to the occlusion region (θ<NUM>, θ<NUM>).

Referring to <FIG>, the SAE SensorSharing message further includes a new OcclusionRegionExtension data frame that indicates a number of occlusion regions (OcclusCount / DE_OcclusionCount) and an angular definition of each occlusion region (OcclusAngle / DF_OcclusionAngle). Similar to Table <NUM>, the parameters θ<NUM> and θ<NUM> for each occlusion region may be indicated via these respective Element or Content fields.

While Tables <NUM>-<NUM> and <FIG> are described specifically with respect to the scenario <NUM> of <FIG>, it will be appreciated that these aspects can readily be modified to accommodate various modifications, such as the scenario <NUM> where a single angular reference θ is used to denote an occlusion region, the scenario <NUM> where multiple occlusion regions are identified, 3D occlusion regions, etc..

<FIG> illustrates an example implementation <NUM> of the processes of <FIG> in accordance with an embodiment of the disclosure. In particular, <FIG> relates to a scenario where Vehicle A is proximate to VRU B, RSU 170B and Vehicle C. In <FIG>, Vehicle A performs the process <NUM> of <FIG>, and VRU B, RSU 170B and Vehicle C each perform the process <NUM> of <FIG>.

At block <NUM> (e.g., as in <NUM> of <FIG>), Vehicle A monitors its FOV via one or more sensors. At block <NUM> (e.g., as in <NUM> of <FIG>), Vehicle A detects two occluded regions <NUM> and <NUM>. At block <NUM> (e.g., as in <NUM> of <FIG> and <NUM> of <FIG>), Vehicle A transmits a sensor data request, which is received at VRU B, RSU 170B and Vehicle C.

At block <NUM> (e.g., as in <NUM> of <FIG>), VRU B determines that sensor data in occluded regions <NUM> and <NUM> is unavailable. In this example, VRU B does not respond to the sensor data request from <NUM> based on the determination from <NUM>. However, in other designs, VRU B may acknowledge the sensor data request from <NUM> to expressly indicate its lack of relevant sensor data.

At block <NUM> (e.g., as in <NUM> of <FIG>), RSU 170B determines that sensor data in occluded region <NUM> is available while sensor data in occluded region <NUM> is unavailable. At block <NUM> (e.g., as in <NUM> of <FIG>), RSU 170B filters its total available sensor data to occluded region <NUM> (e.g., to avoid delivering irrelevant sensor data to Vehicle A). At block <NUM> (e.g., as in <NUM> of <FIG> and <NUM> of <FIG>), RSU 170B transmits the filtered sensor data to Vehicle A, and Vehicle A receives the filtered sensor data.

At block <NUM> (e.g., as in <NUM> of <FIG>), Vehicle C determines that sensor data in occluded region <NUM> is available while sensor data in occluded region <NUM> is unavailable. At block <NUM> (e.g., as in <NUM> of <FIG>), Vehicle C filters its total available sensor data to occluded region <NUM> (e.g., to avoid delivering irrelevant sensor data to Vehicle A). At block <NUM> (e.g., as in <NUM> of <FIG> and <NUM> of <FIG>), Vehicle C transmits the filtered sensor data to Vehicle A, and Vehicle A receives the filtered sensor data. At block <NUM>, Vehicle A supplements its FOV based on the received, filtered sensor data.

Referring to <FIG>, in a first implementation example, the communication device (e.g., OBU of VEgo) may obtain the sensor data so as to detect a non-V2X vehicle. For example, the communication device may correspond to a V2X-capable vehicle, VEgo, which detects a non-V2X vehicle VNV using its on-board sensors. To this end, VEgo transmits a sensor-sharing message including the detected characteristics of the detected vehicle (VNV). Recipient(s) of the sensor-sharing message (e.g., RSU, another V2X-capable vehicle denoted as Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

Referring to <FIG>, in a second implementation example, the communication device (e.g., OBU of VEgo) may detect an obstacle in the road using its on-board sensors. VEgo transmits a sensor-sharing message including the detected characteristics of the object. Recipient(s) of the sensor-sharing message (e.g., RSU, Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

Referring to <FIG>, in a third implementation example, the communication device (e.g., OBU of VEgo) detects a VRU proximate to the road using its on-board sensors. VEgo transmits a sensor-sharing message including the detected characteristics of the VRU. Recipient(s) of the sensor-sharing message (e.g.,. RSU, Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

Referring to <FIG>, in a fourth implementation example, the communication device (e.g., V2X-capable RSU) detects a non-V2X vehicle (VNV) using its sensors. RSU transmits a sensor-sharing message including the detected characteristics of the detected vehicle (VNV). Recipient(s) of the sensor-sharing message (Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

Referring to <FIG>, in a fifth implementation example, the communication device (e.g., V2X-capable RSU) detects an obstacle in the road using its on-board sensors. RSU transmits a sensor-sharing message including the detected characteristics of the object. Recipient(s) of the sensor-sharing message (Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

Referring to <FIG>, in a sixth implementation example, the communication device (e.g., V2X-capable RSU) detects a VRU proximate to the road using its on-board sensors. RSU transmits a sensor-sharing message including the detected characteristics of the VRU. Recipient(s) of the sensor-sharing message (Vremote) may use information to determine maneuvers and/or coordination with other vehicle(s).

<FIG> illustrates an example vehicle apparatus <NUM> for implementing the process <NUM> of <FIG> represented as a series of interrelated functional modules in accordance with an aspect of the disclosure. In the illustrated example, the apparatus <NUM> includes a module for monitoring <NUM>, an optional module for detecting <NUM>, a module for transmitting <NUM>, and an optional module for receiving <NUM>.

The module for monitoring <NUM> may be configured to monitor via a set of sensors communicatively coupled to the vehicle apparatus, a field of view (FOV) of the vehicle apparatus (e.g., <NUM> of <FIG>). The optional module for detecting <NUM> may be configured to detect at least one occluded region within the FOV based on the monitoring (e.g., <NUM> of <FIG>). The module for transmitting <NUM> may be configured to transmit, based on the monitoring, a first message that requests sensor data from one or more neighboring communication devices and indicates at least one sensor data filtering condition for the requested sensor data (e.g., <NUM> of <FIG>). The module for receiving <NUM> may be configured to receive, from at least one of the one or more neighboring communication devices in response to the first message, a second message that includes information that is based on sensor data collected at the respective neighboring communication device and is filtered based on the at least one sensor data filtering condition (e.g., <NUM> of <FIG>).

<FIG> illustrates an example communication device <NUM> for implementing the process <NUM> of <FIG> represented as a series of interrelated functional modules in accordance with an aspect of the disclosure. In the illustrated example, the communication device <NUM> includes a module for receiving <NUM>, a module for determining <NUM>, an optional module for filtering <NUM>, and an optional module for transmitting <NUM>.

The module for monitoring <NUM> may be configured to receive, from a vehicle apparatus that neighbors the communication device, a first message that requests sensor data associated with a FOV of the vehicle apparatus and that indicates at least one sensor data filtering condition for the requested sensor data (e.g., <NUM> of <FIG>). The module for determining <NUM> may be configured to determine, in response to the first message, whether sensor data is available at the communication device which satisfies the at least one sensor data filtering condition for the requested sensor data (e.g., <NUM> of <FIG>). The optional module for filtering <NUM> may be configured to filter, based on the at least one sensor data filtering condition, sensor data obtained at the communication device via a set of sensors communicatively coupled to the communication (e.g., <NUM> of <FIG>). The optional module for transmitting <NUM> may be configured to transmit, to the vehicle apparatus, the filtered sensor data from optional block <NUM>.

The functionality of the modules of <FIG> may be implemented in various ways consistent with the teachings herein. In some designs, the functionality of these modules may be implemented as one or more electrical components. In some designs, the functionality of these blocks may be implemented as a processing system including one or more processor components. In some designs, the functionality of these modules may be implemented using, for example, at least a portion of one or more integrated circuits (e.g., an ASIC). As discussed herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. Thus, the functionality of different modules may be implemented, for example, as different subsets of an integrated circuit, as different subsets of a set of software modules, or a combination thereof. Also, it will be appreciated that a given subset (e.g., of an integrated circuit and/or of a set of software modules) may provide at least a portion of the functionality for more than one module.

In addition, the components and functions represented by <FIG>, as well as other components and functions described herein, may be implemented using any suitable means. Such means also may be implemented, at least in part, using corresponding structure as taught herein. For example, the components described above in conjunction with the "module for" components of <FIG> also may correspond to similarly designated "means for" functionality. Thus, in some aspects one or more of such means may be implemented using one or more of processor components, integrated circuits, or other suitable structure as taught herein, including as an algorithm. One skilled in the art will recognize in this disclosure an algorithm represented in the prose described above, as well as in sequences of actions that may be represented by pseudocode. For example, the components and functions represented by <FIG> may include code for performing a LOAD operation, a COMPARE operation, a RETURN operation, an IF-THEN-ELSE loop, and so on.

In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

Implementation examples are described in the following numbered clauses:.

It should be understood that any reference to an element herein using a designation such as "first," "second," and so forth does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise a set of elements may comprise one or more elements. In addition, terminology of the form "at least one of A, B, or C" or "one or more of A, B, or C" or "at least one of the group consisting of A, B, and C" used in the description or the claims means "A or B or C or any combination of these elements. " For example, this terminology may include A, or B, or C, or A and B, or A and C, or A and B and C, or 2A, or 2B, or 2C, and so on.

In view of the descriptions and explanations above, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.

Accordingly, it will be appreciated, for example, that an apparatus or any component of an apparatus may be configured to (or made operable to or adapted to) provide functionality as taught herein. This may be achieved, for example: by manufacturing (e.g., fabricating) the apparatus or component so that it will provide the functionality; by programming the apparatus or component so that it will provide the functionality; or through the use of some other suitable implementation technique. As one example, an integrated circuit may be fabricated to provide the requisite functionality. As another example, an integrated circuit may be fabricated to support the requisite functionality and then configured (e.g., via programming) to provide the requisite functionality. As yet another example, a processor circuit may execute code to provide the requisite functionality.

Moreover, 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. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In the alternative, the storage medium may be integral to the processor (e.g., cache memory).

Accordingly, it will also be appreciated, for example, that certain aspects of the disclosure can include a computer-readable medium embodying the methods described herein.

Claim 1:
A method of operating a vehicle apparatus, comprising:
monitoring (<NUM>), via a set of sensors communicatively coupled to the vehicle apparatus, a field of view, FOV, of the vehicle apparatus; and
transmitting (<NUM>), based on the monitoring, a first message that requests sensor data from one or more neighboring devices and indicates at least one sensor data filtering condition for the requested sensor data, wherein the request for the sensor data and the at least one sensor data filtering condition is included in the first message implicitly by specifying in the first message a location of the vehicle apparatus or sensor data that depicts at least part of the FOV of the vehicle apparatus, to allow the one or more neighboring devices to detect at least one occluded region in the FOV based, respectively, on a relative location of the vehicle apparatus with regard to the neighboring devices based on the location of the vehicle apparatus or to detect at least one occluded region in the FOV based on the at least part of the FOV of the vehicle apparatus.