Patent ID: 12200057

DETAILED DESCRIPTION

A UE may use its local sensors to sense various conditions of the UE's environment so that the UE can make environmentally-aware decisions. In some cases, a UE may supplement its own sensor data with sensor data from other UEs to increase the UE's knowledge of the environment. For example, the UE may directly communicate with another UE to receive data captured by the sensors of the other UE. The data may be conveyed to the UE in a message that includes a signature of the originating UE. But the message may not include any indication of the data's reliability, which may vary based on the limitations of the sensor that capture the data. For example, data may be unreliable if it indicates a condition that the capturing sensor is not able to accurately detect.

According to the techniques described herein, a UE that transmits sensor data to another UE may also send information about the associated sensor and its performance so that a receiving UE can evaluate the reliability of the sensor data and factor it into decision-making. For example, the transmitting UE may send the sensor's identifier (ID) as well as its type (e.g., camera, lidar, radar, etc.). The UE may also send an indication of the sensor's performance level for various metrics. For example, the UE may indicate the sensor's expected or actual range, resolution, sensitivity, accuracy, etc. Additional information sent by the UE may include the certifying authority (e.g., a standards or regulating body) that sets performance rules for the UE. Once the performance information is determined, the UE may transmit the performance information in the same message as the sensor data (e.g., the performance indication may be transmitted in a sensor sharing message) or a separate message.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to sensor performance indication.

FIG.1illustrates an example of a wireless communications system100that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The wireless communications system100may include one or more base stations105(e.g., gNodeBs (gNBs), and/or radio heads (RHs)), one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system100may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

The base stations105may be dispersed throughout a geographic area to form the wireless communications system100and may be devices in different forms or having different capabilities. The base stations105and the UEs115may wirelessly communicate via one or more communication links125. Each base station105may provide a coverage area110over which the UEs115and the base station105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a base station105and a UE115may support the communication of signals according to one or more radio access technologies.

The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115, the base stations105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown inFIG.1.

The base stations105may communicate with the core network130, or with one another, or both. For example, the base stations105may interface with the core network130through one or more backhaul links120(e.g., via an S1, N2, N3, or other interface). The base stations105may communicate with one another over the backhaul links120(e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105), or indirectly (e.g., via core network130), or both. In some examples, the backhaul links120may be or include one or more wireless links.

One or more of the base stations105described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.

A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples. A UE115may communicate with the core network130through communication link135.

The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the base stations105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1.

The UEs115and the base stations105may wirelessly communicate with one another via one or more communication links125over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.

Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements that a UE115receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE115.

The time intervals for the base stations105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115.

In some examples, a base station105may be movable and therefore provide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas110associated with different technologies may overlap, but the different geographic coverage areas110may be supported by the same base station105. In other examples, the overlapping geographic coverage areas110associated with different technologies may be supported by different base stations105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the base stations105provide coverage for various geographic coverage areas110using the same or different radio access technologies.

The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. The UEs115may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions). Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE115may also be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs115utilizing D2D communications may be within the geographic coverage area110of a base station105. Other UEs115in such a group may be outside the geographic coverage area110of a base station105or be otherwise unable to receive transmissions from a base station105. In some examples, groups of the UEs115communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE115transmits to every other UE115in the group. In some examples, a base station105facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs115without the involvement of a base station105.

In some systems, the D2D communication link135may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs115). In some examples, vehicles may communicate using V2X communications. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., base stations105) using vehicle-to-network (V2N) communications, or with both.

The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the base stations105associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to the network operators IP services150. The operators IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station105, may include subcomponents such as an access network entity140, which may be an example of an access node controller (ANC). Each access network entity140may communicate with the UEs115through one or more other access network transmission entities145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs). Each access network transmission entity145may include one or more antenna panels. In some configurations, various functions of each access network entity140or base station105may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station105).

The wireless communications system100may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system100may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as the base stations105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A base station105or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a base station105may be located in diverse geographic locations. A base station105may have an antenna array with a number of rows and columns of antenna ports that the base station105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

In some cases, a UE115may include or be coupled with sensors that allow the UE115to sense various aspects of the conditions around the UE115. For example, a UE115in a transportation environment (e.g., an environment in which one or more persons or vehicles is travelling) may include or be coupled with one or more cameras, lidar systems, radar systems, infrared systems, thermal sensors, etc., that provide information about the surroundings of the UE115. The UE115may use the information gathered by its sensors to make various decisions, such as driving strategy decisions. To augment its understanding of the environment, the UE115may source sensor data from other devices. For example, the UE115may receive object detection information captured by sensors on other UEs115or base stations105. Thus, the UE may increase its situational awareness by receiving sensor data that conveys information about a transportation environment, including information on road users, received objects, road impairments, and traffic events.

But in some cases, the sensor data received from another device may be unreliable due to performance limitations of the sensor that capture the data. For example, a device with a sensor that is configured to reliably detect objects up to ten meters away may report a detected object that is fifty meters away. If the receiving UE115does not know the performance limitations of the sensor that detected the object, the UE115may treat the sensor data as reliable data upon which decisions can be based, leading to suboptimal results.

According to the techniques described herein, a device that sends sensor data to another device (e.g., a UE115) may also send information about the performance level of the sensor for various metrics. For example, the device may send a certification that indicates the accuracy, resolution, range, refresh rate, sensitivity, depth perception, and/or field-of-view of the sensor, among other metrics. The device may indicate the performance level(s) of a sensor in the same message that conveys data captured by the sensor or in a separate message. A device that receives the indication of the sensor's performance level(s) may use the performance level(s) to determine the reliability of the data captured by sensor so that the device can make informed decisions. One or more of these operations may be performed by a communications manager101, which may be an example of a communications manager1115,1215,1305, or1410as described with reference toFIGS.11through14.

FIG.2illustrates an example of a wireless communications system200that supports sensor performance indication in accordance with one or more aspects of the present disclosure. In some examples, wireless communications system200may implement aspects of wireless communication system100. For example, wireless communications system200may include a base station105-aand UEs115-athrough115-d, which may be examples of a base station105and UEs115, respectively, as described with reference toFIG.1. The UEs115may be examples of roadside units (RSUs) or on-board-units (OBU).

The UEs115in wireless communications system200may directly communicate with each other (e.g., using vehicle-to-everything (V2X) communications, device-to-device (D2D) communications, etc.) to exchange information. For example, in a V2X system a UE115may use vehicle-to-vehicle (V2V) communications to communicate with a vehicle, vehicle-to-person (V2P) communications to communicate with a personal electronic device, or vehicle-to-infrastructure (V21) communications to communicate with roadside infrastructure. In some cases, the V2X communications are facilitated by base station105-a, which may communicate wireless devices that are within coverage area230. Although described with reference to V2X, the techniques described herein may be implemented using any type of communication that allows one UE115to communicate directly with another UE115.

The UEs115in wireless communications system200may exchange sensor sharing messages that convey sensor data about the conditions of a transportation environment. For example, UE115-bmay send to UE115-aa sensor sharing message205that includes sensor data for a detected object. But the sensor data may not be reliable due to limitations of the sensors that collected the data. Although the sensor sharing message205may include a signature or certification of UE115-b(e.g., the originator of the sensor sharing message205), the sensor sharing message205may not include any information about the reliability of the sensor data. According to the techniques described herein, UE115-amay send data structure210to UE115-bso that UE115-bcan determine the reliability of the sensor data. The data structure210may carry performance information for the sensor and may be included in the sensor sharing message205or a separate message (e.g., a message that has a different transmission period than sensor sharing messages). In some cases, the message that includes data structure210may be an application-layer message.

The performance information conveyed by data structure210may include a certification of the sensor's performance. In some cases, the certification may include an indication of the performance level (e.g., the actual or expected capability) of the sensor for various metrics. But sending the exact performance level of a metric for a sensor may use many resources, so UE115-bmay conserve resources by sending an indication of a performance value (e.g., an integer number) that represents the performance level of one or more metrics for one or more sensors. UE115-bmay determine the performance value based on a set of rules that defines a mapping (or an “association”) between performance levels of a sensor and performance values. In some cases, the set of rules is defined by a standards body so that all devices regulated by the standards body use the same set of rules. Thus, a device (e.g., UE115-a) that receives a performance value for a sensor can convert the performance value into an actual or expected performance level of the sensor (e.g., a sensor that receives a performance value ‘1’ may determine that the sensor has a range of x meters).

In some examples of wireless communications system200, there may be multiple standards bodies (e.g., SAE, C-SAE, ESTI-ITS) that certify sensors and predefine the sets of rules described herein. So, a device (e.g., UE115-b) that sends a sensor performance certification may also indicate the standards body (or “certifying authority”) that applies to the device/sensor so that the receiving device knows to use the set of rules predefined by that standards body. Thus a common set of rules may be used by both devices, which allows for a consistent mapping between performance values and performance levels.

In some cases, the set of rules predefined by a standards body may include subsets of rules, each of which defines a unique mapping between performance values and performance levels. For example, the standards body may predefine four subsets of rules. The first subset of rules (which may be referred to as “metric-specific” rules) may map each performance value to a unique performance level for a given metric of a sensor. Thus, a sensor's performance level for each metric may be indicated by a separate performance value (e.g., a performance value w may indicate the sensor's range). The second subset of rules (which may be referred to as “sensor-specific” rules) may associate each performance value with a set of performance levels for a sensor, where each performance level corresponds to a different metric. Thus, a single performance value may indicate the performance levels of multiple metrics of a sensor (e.g., a performance value x may indicate the sensor's range and sensitivity).

The third subset of rules (which may be referred to as “fusion” rules) may map a performance value to an average performance level of multiple sensors for a given metric. Thus, a single performance value may indicate an average performance level for multiple sensors for a given metric (e.g., a performance value y may indicate the average range of multiple sensors). The fourth subset of rules (which may be referred to as “fusion aggregation” rules) may associate each performance value with a set of average performance levels for multiple sensors, where each average performance level corresponds to a different metric. Thus, a single performance value may indicate the average performance level for multiple metrics of multiple sensors (e.g., a performance value z may indicate the average range and average sensitivity of two or more sensors).

Because multiple subsets of rules may be predefined by a single standards body, a device (e.g., UE115-a) that receives a performance value may need to know the subset of rules used to derive the performance value so that the device can use the same subset of rules to determine the associated performance level(s). Thus, UE115-bmay include an indication of the relevant subset of rules in data structure210. In some cases, UE115-bmay also include the type of the sensor and the ID of the sensor in data structure210. Although described with reference to four subsets of rules, the techniques described herein can be implemented with any number of rule subsets.

In some examples, the sensor data and sensor performance information transmitted by a device is associated with one or more local sensors of the device. However, it should be appreciated that the originator of a sensor sharing message and/or sensor information may not necessarily be the device that includes the relevant sensor. For example, the sensor sharing message205transmitted by UE115-bmay include sensor data captured by a sensor on a different device, such as UE115-d. Similarly, the data structure210transmitted by UE115-dmay be for a sensor on a different device. Thus, in some cases, a device may act as a relay for sensor data and performance information associated with sensors on another device.

In some cases, the sensor sharing message205may include multiple parts. For example, the sensor sharing message may include a first part215, a second part220, and a third part225. The first part215may convey host data (e.g., information about the originating device, such as the ID and various characteristics of the device). The second part220may convey sensor data about detected objects, such as type, position, speed, distance, direction, etc. of the object. In some cases, the second part220may include the ID of the sensor(s) that captured the sensor data. For example, the frame in part220that conveys sensor data for Object A may also convey the ID of the sensor that detected Object A, and the frame in part220that conveys sensor data for Object B may also convey the ID of the sensor that detected Object B. The ID of the sensors may match the IDs indicated in data structure210. Thus, a device that receives data structure210may associate a particular set of sensor data with the sensor that captured that set of sensor data.

As noted, the data structure210may be included in a sensor sharing message205or a different message. When the data structure210is included in the sensor sharing message205, the sensor sharing message205may include third part225. The third part225may include a data structure210for different sensors or combinations of sensors. Each data structure210may include an indication of the ID(s) of the sensors associated with the data structure, and those IDs may match the ID(s) conveyed in part220.

FIG.3illustrates an example of a data format300that supports sensor performance indication in accordance with one or more aspects of the present disclosure. Data format300may be used by a device such as a UE115to separately indicate performance levels corresponding to different metrics of a sensor. Thus, data format300may be part of a sensor sharing process between two devices. In some cases, the device that transmits data format300may determine the performance values based on the first subset of rules (e.g., the metric-specific rules) as described with reference toFIG.2. Accordingly, the device that receives data format300may determine the performance levels associated with the performance values based on the first subset of rules.

Data format300may include multiple data frames (DFs) and data elements (DEs). Each data frame may be made up of one or more data frames and/or data elements. Data format300may include a data frame305that conveys SensorCertificateList. SensorCertificateList may include a sequence of SensorCertificates that are conveyed in data structures310. A data structure310may be an example of a data structure210as described with reference toFIG.2. In the example illustrated inFIG.3, each SensorCertificate may include information about a particular sensor. Thus, data structure310may include a number of data elements and data frames that convey sensor information for that sensor. Although shown with a single SensorCertificate, the SensorCertificateList may include multiple SensorCertificates, each associated with a different sensor.

Data structure310may include data elements315through330and data frame335. Data element315may convey an indication of the ID of the sensor (e.g., SensorID) and data element320convey an indication of the type of the sensor (e.g., SensorType). Data element325may convey an indication of the certifying authority (e.g., standards body) that applies to the se430445nsor. Thus, data element325may convey an indication of the set of rules that applies to the sensor (e.g., the set of rules predefined by the certifying authority). Data element330may convey an indication of the subset of rules used by the device with the sensor. In the example depicted inFIG.3, the indicated subset of rules may be the first subset of rules (e.g., the metric-specific rules) described with reference toFIG.2. So, each performance value conveyed by data frame335may be associated with a unique performance level for a given metric of the sensor.

Data frame335may convey PerformanceValueList, which may be a list of performance values for the sensor. Thus, data frame335may include multiple data elements (e.g., data elements340through355) each of which conveys a performance value (e.g., PerformanceValue_x) that is associated with a performance level of a unique metric. The association between the performance values and performance levels may be defined by the first subset of rules indicated by data element325. Because the first subset of rules applies, the performance value PerformanceValue_1 may be associated with a first performance level (e.g., PerformanceLevel_1) corresponding to a first metric (e.g., Metric 1). Similarly, the performance value PerformanceValue_2 may be associated with a second performance level (e.g., PerformanceLevel_2) corresponding to a second metric (e.g., Metric 2). And so on and so forth. Thus, the performance level corresponding to a metric of a sensor may be indicated by a performance value that is carried in its own data element.

A device that receives data structure310may reference the various data frames and data elements to determine information about the sensor associated with data structure. For example, the device may determine the sensor's ID from the value conveyed in data element315(e.g., based on SensorID) and the device may determine the sensor's type (e.g., camera, radar, lidar, etc.) from the value conveyed in data element320(e.g., based on SensorType). The device may also determine the certifying authority (and thus the predefined set of rules) that applies to the indicated sensor based on the value conveyed in data element330(e.g., based on CertAuthority), as well as the subset of rules the device is to use based on the value conveyed in data element325(e.g., based on CertType).

As noted, the first subset of rules may define a one-to-one association between performance values and performance levels corresponding to different metrics of a particular sensor. Accordingly, the device may use the first subset of rules predefined by the indicated certifying authority to associate the performance value PerformanceValue_N with PerformanceLevel_N. The device may determine the metric corresponding to PerformanceLevel_N based on the position of the data element360in data frame335. Thus, the device may determine that the performance level for metric N of Sensor 1 (e.g., the sensor indicated by SensorID) is PerformanceLevel_N.

FIG.4illustrates an example of a process flow400that supports sensor performance indication in accordance with one or more aspects of the present disclosure. In some examples, process flow400may implement aspects of wireless communications systems100and200. For example, process flow400may include UE115-eand UE115-f, and these devices may implement aspects of the sensor information sharing process described with reference toFIG.3. Each UE115may include or be coupled with one or more sensors but for ease of illustration only sensor402is depicted.

In the following description of the process flow400, the operations between UE115-eand UE115-fmay occur in a different order than the exemplary order shown, or the operations performed by the devices may be performed in different orders or at different times. Certain operations may also be left out of the process flow400, or other operations may be added to the process flow400.

At405, UE115-emay determine a set of rules that apply to UE115-e(or sensor402) and the certifying authority that predefined the set of rules. UE115-emay also determine a subset of rules that apply to UE115-e(or its sensor402). The subset of rules may be one of multiple subsets included in the set of rules. In the example illustrated inFIG.4, the subset of rules may be the first subset of rules (e.g., the metric-specific rules) described with reference toFIGS.2and3.

At410, UE115-emay determine a first performance level corresponding to a first metric of sensor402. For example, UE115-emay determine the sensitivity of sensor402which may be a camera, lidar sensor, radar sensor, etc. UE115-emay also determine a second performance level corresponding to a second metric of the sensor402. For example, UE115-emay determine the range of sensor402.

At415, UE115-emay identify a first performance value that is associated with the first performance level corresponding to the first metric. UE115-emay identify the first performance value based on the first performance level and the subset of rules determined at405. At420, UE115-emay identify a second performance value that is associated with the second performance level corresponding to the second metric. UE115-emay identify the second performance value based on the second performance level and the subset of rules determined at405.

At425, UE115-emay transmit a message that includes a SensorCertificate that indicates information about sensor402. The SensorCertificate may be conveyed in a data structure such as the data structure310described with reference toFIG.3. Thus, UE115-emay transmit an indication of the first performance value in a first data element (e.g., data element340) of the message and UE115-emay transmit an indication of the second performance value in a second data element (data element345) of the message. UE115-emay also transmit an indication of the certifying authority's set of rules in a third data element (e.g., data element325) of the message. UE115-emay also transmit an indication of the subset of rules in a fourth data element (e.g., data element330) of the message. UE115-emay also transmit an indication of the ID of sensor402in a fifth data element (e.g., data element315) of the message. UE115-emay also transmit an indication of the type of sensor402in a sixth data element (e.g., data element320) of the message.

At430, UE115-emay transmit sensor data captured by sensor402. The sensor data may be included in a sensor sharing message that also includes the SensorCertificate for sensor402. Alternatively, the SensorCertificate may be included in a different message than the sensor sharing message. In some examples, the sensor data may include an indication of the ID of the sensor that captured the sensor data. The ID may match the ID indicated in data element315.

At435, UE115-fmay determine the certifying authority and the set of rules based on the SensorCertificate (e.g., based on the value of CertAuthority carried in data element325). UE115-fmay also determine the subset of rules based on the SensorCertificate (e.g., based on the value of CertType carried in data element330).

At440, UE115-fmay determine the first performance level corresponding to the first metric of sensor402. UE115-fmay determine the first performance level based on the first performance value and the subset of rules. At445, UE115-fmay determine the second performance level corresponding to the second metric of sensor402. UE115-fmay determine the second performance level based on the second performance value and the subset of rules. At450, UE115-fmay determine the reliability of the sensor data captured by sensor402based on the first and second performance levels.

Although described with reference to sensor402, process flow400may be implemented for a sensor that is on a device other than UE115-e. In such cases, the sensor information determined and transmitted by UE115-emay be based on sensor information received from the device that includes the sensor.

FIG.5illustrates an example of a data format500that supports sensor performance indication in accordance with one or more aspects of the present disclosure. Data format500may be used by a device such as a UE115to indicate multiple performance levels corresponding to multiple metrics of a sensor using a single performance value. Thus, data format500may be part of a sensor sharing process between two devices. In some cases, the device that transmits data format500may determine the performance values based on the second subset of rules (e.g., the sensor-specific rules) as described with reference toFIG.2. Accordingly, the device that receives data format500may determine the performance levels associated with the performance values based on the second subset of rules.

Data format500may include a data frame505that conveys SensorCertificateList. SensorCertificateList may include a sequence of SensorCertificates that are conveyed in data structures510. A data structure510may be an example of a data structure210as described with reference toFIG.2. In the example illustrated inFIG.5, each SensorCertificate may include information about a particular sensor. Thus, data structure510may include a number of data elements and data frames that convey sensor information for that particular sensor. Although shown with a single SensorCertificate, the SensorCertificateList may include multiple SensorCertificates, each associated with a different sensor.

Data structure510may include data elements515through530, which may be examples of corresponding data elements315through330described with reference toFIG.3. Data structure510may also include data element535, which may convey a performance value (e.g., PerformanceValue) for the sensor. The performance value may be associated with multiple performance levels corresponding to various metrics of the sensor. The association between the performance value and performance levels may be defined by the second subset of rules (e.g., the sensor-specific rules) indicated in data element530. Because the second subset of rules applies, the performance value conveyed by data element535may be associated with a first performance level (e.g., Performance Level_1) corresponding to a first metric (e.g., Metric 1), a second performance level (e.g. PerformanceValue_2) corresponding to a second metric (e.g., Metric 2), and so on and so forth. Thus, the performance levels corresponding to multiple metrics may be indicated by a single performance value that is carried in its own data element (e.g., data element535).

A device that receives data structure510may reference the various data frames and data elements to determine information about the sensor associated with the data structure510. For example, the device may determine the sensor's ID from the value (e.g., based on SensorID) conveyed in data element515and the device may determine the sensor's type from the value (e.g., based on SensorType) conveyed in data element520. The device may also determine the certifying authority (and thus a predefined set of rules) that applies to the indicated sensor based on the value (e.g., based on CertAuthority) conveyed in data element525, as well as the subset of rules the device is to use based on the value (e.g., based on CertType) conveyed in data element535.

As noted, the second subset of rules (e.g., the sensor-specific rules) may define the association between a performance value and multiple performance levels corresponding to different metrics of a particular sensor. Accordingly, the device may use the second subset of rules predefined by the indicated certifying authority to associate the performance value conveyed by data element535with performance levels Performance Level_1 through Performance Level_N. The device may also determine the metric corresponding to each performance level based on the subset of rules. Thus, the device may determine that Sensor 1 (e.g., the sensor indicated by SensorID) has Performance Level_1 corresponding to metric 1 (e.g., range), Performance Level 2 corresponding to metric 2 (e.g., sensitivity), Performance Level_3 corresponding to metric 3 (e.g., resolution), Performance Level_4 corresponding metric 4 (accuracy), and a Performance Level_N corresponding to metric N (e.g., refresh rate).

FIG.6illustrates an example of a process flow600that supports sensor performance indication in accordance with one or more aspects of the present disclosure. In some examples, process flow600may implement aspects of wireless communications systems100and200. For example, process flow600may include UE115-gand UE115-h, and these devices may implement aspects of the sensor information sharing process described with reference toFIG.5. Each UE115may include or be coupled with one or more sensors, but for ease of illustration only sensor602is depicted.

In the following description of the process flow600, the operations between UE115-gand UE115-hmay occur in a different order than the exemplary order shown, or the operations performed by the devices may be performed in different orders or at different times. Certain operations may also be left out of the process flow600, or other operations may be added to the process flow600.

At605, UE115-gmay determine a set of rules that apply to UE115-g(or sensor602) and the certifying authority that predefined the set of rules. UE115-gmay also determine a subset of rules that apply to UE115-g(or its sensor602). The subset of rules may be one of multiple subsets included in the set of rules. In the example illustrated inFIG.6, the subset of rules may be the second subset of rules (e.g., the sensor-specific rules) described with reference toFIGS.2and5.

At610, UE115-gmay determine a first performance level corresponding to a first metric of sensor602. For example, UE115-gmay determine the resolution of sensor602. UE115-gmay also determine a second performance level corresponding to a second metric of the sensor602. For example, UE115-gmay determine the accuracy of sensor602.

At615, UE115-gmay identify a performance value that is associated with the first performance level corresponding to the first metric and the second performance level corresponding to the second metric. Thus, UE115-gmay identify the performance value based on the first and second performance levels and the subset of rules determined at605.

At620, UE115-gmay transmit a message that includes a SensorCertificate indicating information about sensor602. The SensorCertificate may be conveyed by a data structure such as the data structure510described with reference toFIG.5. Thus, UE115-gmay transmit an indication of the performance value in a first data element (e.g., data element535) of the message. UE115-gmay also transmit an indication of the certifying authority's set of rules (e.g., in data element525), an indication of the subset of rules (e.g., in data element530), an indication of the ID of sensor602(e.g., in data element515), and/or an indication of the type of sensor602(e.g., in data element520).

At625, UE115-gmay transmit sensor data captured by sensor602. The sensor data may be included in a sensor sharing message that also includes the SensorCertificate for sensor602. Alternatively, the SensorCertificate may be included in a different message than the sensor sharing message. In some examples, the sensor data may include an indication of the ID of the sensor that captured the sensor data. The ID may match the ID indicated in data element515.

At630, UE115-hmay determine the certifying authority and the set of rules based on the SensorCertificate (e.g., based on the value of CertAuthority carried in data element525). UE115-hmay also determine the subset of rules based on the SensorCertificate (e.g., based on the value of CertType carried in data element530).

At635, UE115-hmay determine the first performance level corresponding to the first metric of sensor602. UE115-hmay determine the first performance level based on the performance value and the subset of rules. UE115-hmay also determine the second performance level corresponding to the second metric of sensor602. UE115-hmay determine the second performance level based on the performance value and the subset of rules. At640, UE115-hmay determine the reliability of the sensor data captured by sensor602based on the first and second performance levels.

Although described with reference to sensor602, process flow600may be implemented for a sensor that is on a device other than UE115-g. In such cases, the sensor information determined and transmitted by UE115-gmay be based on sensor information received from the device that includes the sensor.

FIG.7illustrates an example of a data format700that supports sensor performance indication in accordance with one or more aspects of the present disclosure. Data format700may be used by a device such as a UE115to indicate an average performance level corresponding to a metric of multiple sensors using a single performance value. Thus, data format700may be part of a sensor sharing process between two devices. In some cases, the device that transmits data format700may determine the indicated performance value based on the third subset of rules (e.g., the fusion rules) as described with reference toFIG.2. Accordingly, the device that receives data format700may determine the average performance level associated with the performance value based on the third subset of rules.

Data format700may include a data frame705that conveys SensorCertificateList. SensorCertificateList may include a sequence of SensorCertificates that are conveyed in data structures710. A data structure710may be an example of a data structure210as described with reference toFIG.2. In the example illustrated inFIG.7, each SensorCertificate may include information about multiple sensors. Thus, data structure710may include a number of data elements and data frames that convey sensor information for those sensors. Although shown with a single SensorCertificate, SensorCertificateList may include multiple SensorCertificates each of which is associated with multiple sensors.

Data structure710may include data elements715through730, which may be examples of corresponding data elements315through330described with reference toFIG.3. In some cases, the SensorCertificate may include multiple data elements715so that multiple sensor IDs can be indicated. For example, when the SensorCertificate is associated with two sensors the SensorCertificate may include a first data element that carries an indication of the ID of the first sensor (e.g., Sensor 1) and a second data element that carries an indication of the ID of the second sensor (e.g., Sensor 2). The SensorCertificate may also include multiple data elements720so that multiple sensor types can be indicated. For example, when the SensorCertificate is associated with two sensors the SensorCertificate may include a first data element that carries an indication of the type of the first sensor (e.g., Sensor 1) and a second data element that carries an indication of the ID of the second sensor (e.g., Sensor 2). Although described with reference to two sensors, the techniques described with reference toFIG.7may be implemented for any number of sensors.

The SensorCertificate may also include one or more data frames735. Each data frame735may convey PerformanceValueList, which may be a list of performance values for multiple sensors. Thus, data frame735may include multiple data elements (e.g., data elements740through755805) each of which conveys a performance value (e.g., PerformanceValue_x) that is associated with an average performance level of a metric of multiple sensors. The association between the performance values and average performance levels may be defined by the third subset of rules (e.g., the fusion rules) indicated by data element725. Because the third subset of rules applies, the performance value PerformanceValue_1 may be associated with a first average performance level PerformanceLevel_1 corresponding to a first metric (e.g., Metric 1) of multiple sensors (e.g., Sensor 1 and Sensor 2). And the second performance value PerformanceValue_2 may be associated with a second average performance level corresponding to a second metric (e.g., Metric 2) of multiple sensors (e.g., Sensor 1 and Sensor 2). And so on and so forth. Thus, the average performance level corresponding to a metric for multiple sensors may be indicated by a performance value that is carried in its own data element.

A device that receives data structure710may reference the various data frames and data elements to determine information about the sensor associated with the data structure710. For example, the device may determine the sensors' IDs based on the values conveyed in data elements715(e.g., based on SensorIDs) and the device may determine the sensors' types based on the value conveyed in data elements720(e.g., based on SensorTypes). The device may also determine the certifying authority (and thus a predefined set of rules) that applies to the indicated sensor based on the value conveyed in data element725(e.g., based on CertAuthority), as well as the subset of rules the device is to use based on the value conveyed in data element725(e.g., based on CertType).

As noted, the third subset of rules may define the association between performance values and average performance levels corresponding to different metrics of multiple sensors. Accordingly, the device may use the third subset of rules predefined by the indicated certifying authority to associate the performance value PerformanceValue_N conveyed in data element760with AvgPerformanceLevel_N. The device may also determine the metric corresponding to the performance level based on the position of element760in data frame735. Thus, the device may determine that Sensor 1 and Sensor 2 (e.g., the sensors indicated by the SensorIDs) have an average performance level of AvgPerformanceLevel_N for metric N.

FIG.8illustrates an example of a process flow800that supports sensor performance indication in accordance with one or more aspects of the present disclosure. In some examples, process flow800may implement aspects of wireless communications systems100and200. For example, process flow800may include UE115-iand UE115-j, and these devices may implement aspects of the sensor information sharing process described with reference toFIG.7. Each UE115may include or be coupled with one or more sensors, but for ease of illustration only sensor802and sensor804are depicted.

In the following description of the process flow800, the operations between UE115-iand UE115-jmay occur in a different order than the exemplary order shown, or the operations performed by the devices may be performed in different orders or at different times. Certain operations may also be left out of the process flow800, or other operations may be added to the process flow800.

At805, UE115-imay determine a set of rules that apply to UE115-i(or sensors802,804) and the certifying authority that predefined the set of rules. UE115-imay also determine a subset of rules that apply to UE115-g(or sensors802,804). The subset of rules may be one of multiple subsets included in the set of rules. In the example illustrated inFIG.8, the subset of rules may be the third subset of rules (e.g., the fusion rules) described with reference toFIGS.2and7.

At810, UE115-imay determine a first performance level corresponding to a first metric of a first sensor. For example, UE115-imay determine the field-of-view of sensor802. At815UE115-imay determine a second performance level corresponding to the first metric of a second sensor. For example, UE115-imay determine the field-of-view of sensor804.

At820, UE115-imay identify a performance value based on a combination of the first performance level corresponding to the first metric of sensor802and the second performance level corresponding to the first metric of sensor804. For example, UE115-imay determine the average performance level for the first metric based on the first performance level and the second performance level. Upon determining the average performance level for sensor802and sensor804, UE115-imay identify the performance value corresponding to the average performance level. Thus, UE115-gmay identify the performance value based on a combination of the first and second performance levels and the subset of rules determined at805.

At825, UE115-imay transmit a message that includes a SensorCertificate indicating information about sensors802and804. The SensorCertificate may be conveyed by a data structure such as the data structure710described with reference toFIG.7. Thus, UE115-imay transmit an indication of the performance value in a first data element (e.g., data element740) of the message. UE115-imay also transmit an indication of the certifying authority's set of rules (e.g., in data element725), an indication of the subset of rules (e.g., in data element730), an indication of the IDs of sensors802and804(e.g., in data elements715), and/or an indication of the types of sensors802and804(e.g., in data elements720).

At830, UE115-imay transmit sensor data captured by sensor802. The sensor data may be included in a sensor sharing message that also includes the SensorCertificate for sensor602. Alternatively, the SensorCertificate may be included in a different message than the sensor sharing message. In some examples, the sensor data may include an indication of the ID of the sensor that captured the sensor data. The ID may match the ID indicated in data element715.

At835, UE115-jmay determine the certifying authority and the set of rules based on the SensorCertificate (e.g., based on the value of CertAuthority carried in data element725). UE115-jmay also determine the subset of rules based on the SensorCertificate (e.g., based on the value of CertType carried in data element730).

At840, UE115-hmay determine the average performance level corresponding to the first metric of sensor802and sensor804. UE115-hmay determine the average performance level based on the performance value and the subset of rules. At845, UE115-hmay determine the reliability of the sensor data captured by sensor802and sensor804based on the average performance level.

Although described with reference to sensor802and sensor804, process flow800may be implemented for a sensor that is on a device other than UE115-i. In such cases, the sensor information determined and transmitted by UE115-imay be based on sensor information received from the device that includes the sensor.

FIG.9illustrates an example of a data format900that supports sensor performance indication in accordance with one or more aspects of the present disclosure. Data format900may be used by a device such as a UE115to indicate multiple average performance levels corresponding to multiple metrics of multiple sensors using a single performance value. Thus, data format900may be part of a sensor sharing process between two devices. In some cases, the device that transmits data format900may determine the performance values based on the fourth subset of rules (e.g., the fusion-aggregation rules) as described with reference toFIG.2. Accordingly, the device that receives data format900may determine the average performance levels associated with the performance values based on the fourth subset of rules.

Data format900may include a data frame905that conveys SensorCertificateList. SensorCertificateList may include a sequence of SensorCertificates that are conveyed in data structures910. A data structure910may be an example of a data structure210as described with reference toFIG.2. In the example, illustrated inFIG.9, each SensorCertificate may include information about multiple sensors. Thus, data structure910may include a number of data elements and data frames that convey sensor information for those sensors. Although shown with a single SensorCertificate, SensorCertificateList may include multiple SensorCertificates, each of which is associated with multiple sensors.

Data structure910may include data elements915through930, which may be examples of corresponding data elements315through330described with reference toFIG.3. In some cases, the SensorCertificate may include multiple data elements915so that multiple sensor IDs can be indicated. For example, when the SensorCertificate is associated with two sensors the SensorCertificate may include a first data element that carries an indication of the ID of the first sensor (e.g., Sensor 1) and a second data element that carries an indication of the ID of the second sensor (e.g., Sensor 2). The SensorCertificate may also include multiple data elements920so that multiple sensor types can be indicated. For example, when the SensorCertificate is associated with two sensors the SensorCertificate may include a first data element that carries an indication of the type of the first sensor (e.g., Sensor 1) and a second data element that carries an indication of the ID of the second sensor (e.g., Sensor 2). Although described with reference to two sensors, the techniques described with reference toFIG.9may be implemented for any number of sensors.

The SensorCertificate may also include data element935, which carry an indication of a performance value (e.g., PerformanceValue) that is associated with multiple average performance levels corresponding to different metrics. The association between the performance value and average performance levels may be defined by the fourth subset of rules indicated in data element925. Because the fourth subset of rules applies (e.g., the fusion-aggregation rules), the performance value may be associated with a first average performance level (e.g., AvgPerformanceLevel_1) corresponding to a first metric (e.g., Metric 1) of multiple sensors (e.g., Sensor 1 and Sensor 2). The performance value may also be associated with a second average performance level (e.g. AvgPerformanceValue_2) corresponding to a second metric (e.g., Metric 2) of multiple sensors (e.g., Sensor 1 and Sensor 2). And so on and so forth. Thus, the average performance levels corresponding to multiple metrics of multiple devices may be indicated by a single performance value that is carried in its own data element (e.g., data element935).

A device that receives the data structure910may reference the various data frames and data elements to determine information about the sensors associated with the data structure. For example, the device may determine the sensors' IDs based on the value(s) conveyed in data element(s)915(e.g., based on SensorID(s)) and the device may determine the sensors' types based on the value(s) conveyed in data element(s)720(e.g., based on SensorType(s)). The device may also determine the certifying authority (and thus a predefined set of rules) that applies to the indicated sensors based on the value conveyed in data element925(e.g., based on CertAuthority), as well as the subset of rules the device is to use based on the value conveyed in data element935(e.g., based on CertType).

As noted, the fourth subset of rules may define the association between a performance value and multiple average performance levels corresponding to different metrics of multiple sensors. Accordingly, the device may use the fourth subset of rules predefined by the indicated certifying authority to associate the performance value conveyed by data element935with average performance levels AvgPerformanceLevel_1 through AvgPerformanceLevel_N. The device may determine the metric corresponding to each average performance level based on the subset of rules indicated by data element930. Thus, the device may determine that the average performance level corresponding to Metric 1 of Sensor 1 and Sensor 2 is AvgPerformanceLevel_1, the average performance level corresponding to Metric 2 of Sensor 1 and Sensor 2 is AvgPerformanceLevel_2 the average performance level corresponding to Metric 3 of Sensor 1 and Sensor 2 is AvgPerformanceLevel_3, the average performance level corresponding to Metric 4 of Sensor 1 and Sensor 2 is AvgPerformanceLevel_4, and the average performance level corresponding to Metric N of Sensor 1 and Sensor 2 is AvgPerformanceLevel_N.

FIG.10illustrates an example of a process flow1000that supports sensor performance indication in accordance with one or more aspects of the present disclosure. In some examples, process flow1000may implement aspects of wireless communications systems100and200. For example, process flow1000may include UE115-kand UE115-l, and these devices may implement aspects of the sensor information sharing process described with reference toFIG.9. Each UE115may include or be coupled with one or more sensors, but for ease of illustration only sensor1002and sensor1004are depicted.

In the following description of the process flow1000, the operations between UE115-kand UE115-lmay occur in a different order than the exemplary order shown, or the operations performed by the devices may be performed in different orders or at different times. Certain operations may also be left out of the process flow1000, or other operations may be added to the process flow1000.

Prior to1005, UE115-kmay determine a set of rules that apply to UE115-k(or sensors1002,1004) and the certifying authority that predefined the set of rules. UE115-kmay also determine a subset of rules that apply to UE115-k(or sensors1002,1004). The subset of rules may be one of multiple subsets included in the set of rules. In the example illustrated inFIG.10, the subset of rules may be the fourth subset of rules (e.g., the fusion-aggregation rules) described with reference toFIGS.2and9.

At1005, UE115-kmay determine a first performance level corresponding to a first metric of a first sensor. For example, UE115-kmay determine the depth perception of sensor1002. At1010, UE115-kmay determine a second performance level corresponding to the first metric of a second sensor. For example, UE115-kmay determine the depth perception of sensor1004.

At1015, UE115-kmay determine a third performance level corresponding to a second metric of the first sensor. For example, UE115-kmay determine the range of sensor1002. At1020, UE115-kmay determine a fourth performance level corresponding to the second metric of the second sensor. For example, UE115-kmay determine the range of sensor1004.

At1025, UE115-kmay identify a performance value based on a combination of the first, second, third, and fourth performance levels. For example, UE115-kmay determine the average performance level for the first metric based on the first performance level and the second performance level. And UE115-kmay determine the average performance level for the second metric based on the third performance level and the fourth performance level. Upon determining the average performance levels for first and second metrics, UE115-k, may identify the performance value that is associated with the average performance levels. Thus, UE115-kmay identify the performance value based on a combination of the first, second, third, and fourth performance levels and the subset of rules.

At1030, UE115-kmay transmit a message that includes a SensorCertificate indicating information about sensors1002and1004. The SensorCertificate may be conveyed by a data structure910as described with reference toFIG.9. Thus, UE115-kmay transmit an indication of the performance value in a first data element (e.g., data element935) of the data structure. UE115-kmay also transmit an indication of the certifying authority's set of rules (e.g., in data element925), an indication of the subset of rules (e.g., in data element930), an indication of the IDs of sensors1002and1004(e.g., in data elements915), and/or an indication of the types of sensors1002and1004(e.g., in data elements920).

At1035, UE115-kmay transmit sensor data captured by sensor1002and sensor1004. The sensor data may be included in a sensor sharing message that also includes the SensorCertificate for sensor1002and sensor1004. Alternatively, the SensorCertificate may be included in a different message than the sensor sharing message. In some examples, the sensor data may include an indication of the ID of the sensor that captured the sensor data. The ID may match the ID indicated in data element915.

At1040, UE115-lmay determine the certifying authority and the set of rules based on the SensorCertificate (e.g., based on the value of CertAuthority carried in data element925). UE115-lmay also determine the subset of rules based on the SensorCertificate (e.g., based on value of CertType carried in data element930).

At1045, UE115-lmay determine the first average performance level corresponding to the first metric of sensor1002and sensor1004. UE115-lmay determine the first average performance level based on the performance value and the subset of rules. UE115-lmay also determine the second average performance level corresponding to the second metric of sensor1002and sensor1004. UE115-lmay determine the second average performance level based on the performance value and the subset of rules. At1050, UE115-lmay determine the reliability of the sensor data captured by sensor1002and sensor1004based on the first and second average performance levels.

Although described with reference to sensor1002and sensor1004, process flow1000may be implemented for sensors that are on a device other than UE115-k. In such cases, the sensor information determined and transmitted by UE115-kmay be based on sensor information received from the device that includes the sensor.

FIG.11shows a block diagram1100of a device1105that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The device1105may be an example of aspects of a UE115as described herein. The device1105may include a receiver1110, a communications manager1115, and a transmitter1120. The device1105may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1110may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to sensor performance indication, etc.). Information may be passed on to other components of the device1105. The receiver1110may be an example of aspects of the transceiver1420described with reference toFIG.14. The receiver1110may utilize a single antenna or a set of antennas.

In some cases, the device1105may be a device that transmits sensor information to another device as described herein. In such cases, the communications manager1115may identify a configured set of one or more rules that apply to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor; identify a performance value from the set of performance values for the sensor based on a performance level of the sensor and the configured set of one or more rules; and transmit, to a second wireless device, an indication of the configured set of one or more rules for the sensor in a message and an indication of the performance value for the sensor in the message. The communications manager1115may be an example of aspects of the communications manager1410described herein.

In some cases, the device1105may be a device that receives sensor information from another device as described herein. In such cases, the communications manager1115may receive, in a message, an indication of a configured set of one or more rules that applies to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor; receive an indication of a performance value for the sensor in the message; and identify a performance level of the sensor based on the performance value and the configured set of one or more rules.

The actions performed by the communications manager1115as described herein may be implemented to realize one or more potential advantages. For example, the operations of communications manager1115may allow a device to signal the capabilities of its sensor(s) to other devices. This information in turn may allow a device that receives sensor data captured by the sensor(s) to determine the reliability of the sensor data. Additionally, the manner of indicating the sensor information may conserve resources (e.g., be more efficient) compared to other techniques. For example, indicating performance values rather than performance levels may use fewer communications resources (e.g., time and frequency resources) because fewer bits of data are transmitted. Transmitting fewer bits of data may also reduce power consumption of the devices participating in the exchange because the transceivers on the devices turned off sooner (compared to transmitting more bits).

The communications manager1115, or its sub-components, may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager1115, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The communications manager1115, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communications manager1115, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communications manager1115, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

The transmitter1120may transmit signals generated by other components of the device1105. In some examples, the transmitter1120may be collocated with a receiver1110in a transceiver module. For example, the transmitter1120may be an example of aspects of the transceiver1420described with reference toFIG.14. The transmitter1120may utilize a single antenna or a set of antennas.

FIG.12shows a block diagram1200of a device1205that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The device1205may be an example of aspects of a device1105, or a UE115as described herein. The device1205may include a receiver1210, a communications manager1215, and a transmitter1235. The device1205may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1210may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to sensor performance indication, etc.). Information may be passed on to other components of the device1205. The receiver1210may be an example of aspects of the transceiver1420described with reference toFIG.14. The receiver1210may utilize a single antenna or a set of antennas.

The communications manager1215may be an example of aspects of the communications manager1115as described herein. The communications manager1215may include a certification component1220, an association component1225, and a direct communication component1230. The communications manager1215may be an example of aspects of the communications manager1410described herein.

In some cases, the device1205may be a device that transmits sensor information to another device as described herein. In such cases, the certification component1220may identify a configured set of one or more rules that apply to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. In some cases, the configured set of one or more rules may be preconfigured at the device1205. The association component1225may identify a performance value from the set of performance values for the sensor based on a performance level of the sensor and the configured set of one or more rules. The direct communication component1230may transmit, to a second wireless device, an indication of the configured set of one or more rules for the sensor in a message and an indication of the performance value for the sensor in the message.

In some cases, the device1205may be a device that receives sensor information from another device as described herein. In such cases, the certification component1220may receive, in a message, an indication of a configured set of one or more rules that applies to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. The direct communication component1230may receive an indication of a performance value for the sensor in the message. The association component1225may identify a performance level of the sensor based on the performance value and the configured set of one or more rules.

The transmitter1235may transmit signals generated by other components of the device1205. In some examples, the transmitter1235may be collocated with a receiver1210in a transceiver module. For example, the transmitter1235may be an example of aspects of the transceiver1420described with reference toFIG.14. The transmitter1235may utilize a single antenna or a set of antennas.

FIG.13shows a block diagram1300of a communications manager1305that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The communications manager1305may be an example of aspects of a communications manager1115, a communications manager1215, or a communications manager1410described herein. The communications manager1305may include a certification component1310, an association component1315, a direct communication component1320, a performance component1325, and a sensor component1330. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

In some cases, the communications manager1305may be part of a device that transmits sensor information to another device as described herein. In such cases, the certification component1310may identify a configured set of one or more rules that apply to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. In some cases, the one or more metrics of the sensor include a range of the sensor, a resolution of the sensor, a sensitivity of the sensor, an accuracy of the sensor, a refresh rate of the sensor, a depth perception of the sensor, and/or a field-of-view of the sensor. The association component1315may identify a performance value from the set of performance values for the sensor based on a performance level of the sensor and the configured set of one or more rules. The direct communication component1320may transmit, to a second wireless device, an indication of the configured set of one or more rules for the sensor in a message and an indication of the performance value for the sensor in the message.

In some examples, the indication of the configured set of one or more rules may be transmitted in a first data frame of the message. In some examples (e.g., when metric-specific rules are used), the direct communication component1320may transmit the performance value in a first data element of a second data frame of the message and the performance value may correspond to a first metric of the sensor. In some examples, the association component1315may identify a second performance value for the sensor based on a second performance level of the sensor and the configured set of one or more rules, the second performance value corresponding to a second metric different than the first metric. In some examples, the direct communication component1320may transmit the second performance value for the sensor in a second data element of the second data frame.

The performance component1325may determine the performance level of the sensor, the performance level corresponding to a first metric of the sensor. In some cases, the performance level includes an actual performance level of the sensor or an expected capability of the sensor. In some examples (e.g., when sensor-specific rules are used), the performance component1325may determine a second performance level of the sensor and the second performance level may correspond to a second metric different than the first metric. In such cases, the association component1315may identify the performance value identified based on the performance level and the second performance level.

In some examples, the performance component1325may determine the performance level of the sensor, the performance level corresponding to a first metric of the sensor. In some examples, the performance component1325may determine a second performance level of a second sensor and the second performance level may correspond to the first metric. In such cases (e.g., when fusion rules are used), the association component1315may identify the performance value based on a combination of the performance level and the second performance level. In some examples, the indication of the configured set of one or more rules is transmitted in a first data frame of the message and the indication of the performance value is transmitted in a second data frame of the message. In some examples, the performance component1325may determine a third performance level of the sensor, the third performance level corresponding to a second metric of the sensor. In some examples, the performance component1325may determine a fourth performance level of the second sensor, the fourth performance level corresponding to the second metric. In some examples (e.g., when fusion rules are used), the association component1315may identify a second performance value for the sensor based on a combination of the third performance level and the fourth performance level. In some examples, the direct communication component1320may transmit the second performance value for the sensor in a second data element of the second data frame.

In some examples, the performance component1325may determine the performance level of the sensor and the performance level may correspond to a first metric of the sensor. In some examples, the performance component1325may determine a second performance level of a second sensor and the second performance level may correspond to the first metric. In such examples (e.g., when fusion rules are used), the association component1315may identify the performance value based on a combination of the performance level and the second performance level. In some examples, the performance component1325may determine a third performance level of the sensor, the third performance level corresponding to a second metric of the sensor. In some examples, the performance component1325may determine a fourth performance level of the second sensor, the fourth performance level corresponding to the second metric. In such examples (e.g., when fusion-aggregation rules are used), the association component1315may identify the performance value based on a combination of the third and fourth performance levels.

In some examples, the certification component1310may transmit, in the message, a value that indicates a subset of rules of the configured set of one or more rules. In such cases, the association component1315may identify the performance value based on the subset of rules.

The sensor component1330may determine an identifier of the sensor. In some examples, the direct communication component1320may transmit an indication of the identifier in the message.

In some examples, the direct communication component1320may transmit information about an object detected by the sensor in the message, where the information is associated with the ID of the sensor.

In some examples, the sensor component1330may determine a type of the sensor. In some examples, the direct communication component1320may transmit an indication of the type in the message.

In some examples, the direct communication component1320may receive an indication of the performance level from a third wireless device, where the sensor is at the third wireless device and the performance level is identified based on the indication of the performance level.

In some cases, the communications manager1305may be part of a device that receives sensor information from another device as described herein. In such cases, certification component1310may receive, in a message, an indication of a configured set of one or more rules that applies to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. The direct communication component1320may receive an indication of a performance value for the sensor in the message. The association component1315may identify a performance level of the sensor based on the performance value and the configured set of one or more rules.

In some examples, the reliability component1335may receive information about an object detected by the sensor and determine a reliability value of the information based on the performance level. In some cases, the information about the object is received in the same message as the indication of the configured set of one or more rules and the indication of the performance value. In some examples, the reliability component1335may receive an indication of an ID of the sensor in the message. In such cases, the information about the object may be associated with the ID of the sensor.

In some examples, the indication of the configured set of one or more rules is received in a first data frame of the message and the indication of the performance value is received in a first data element of a second data frame of the message. In some examples (e.g., when metric-specific rules are used), the direct communication component1320may receive a second performance value for the sensor in a second data element of the second data frame, the second performance value corresponding to a different metric of the sensor than the performance value. In some examples, the association component1315may identify a second performance level of the sensor based on the second performance value and the configured set of one or more rules.

In some examples (e.g., when sensor-specific rules are used), the association component1315may identify a second performance level of the sensor based on the performance value and the configured set of one or more rules. In such cases, the performance level may correspond to a first metric of the sensor and the second performance level may correspond to a second metric different than the first metric. In some examples, the first metric or the second metric is a range of the sensor, a resolution of the sensor, a sensitivity of the sensor, an accuracy of the sensor, a refresh rate of the sensor, a depth perception of the sensor, or a field-of-view of the sensor.

In some examples (e.g., when fusion rules are used), the configured set of one or more rules associates the performance value with an average performance level of a plurality of sensors and the average performance level corresponds to a metric of the sensor. In some examples (e.g., when fusion-aggregation rules are used), the configured set of one or more rules associates the performance value with a second average performance level of the plurality of sensors and the second average performance level corresponds to a second metric of the sensor.

In some examples, the sensor component1330may receive an indication of a type of the sensor in the message and determine the type of the sensor based on the indication of the type.

In some examples, the certification component1310may receive, in the message, a value that indicates a subset of rules of the configured set of one or more rules. In such cases, the association component1315may identify the performance value based on the subset of rules.

FIG.14shows a diagram of a system1400including a device1405that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The device1405may be an example of or include the components of device1105, device1205, or a UE115as described herein. The device1405may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager1410, an I/O controller1415, a transceiver1420, an antenna1425, memory1430, and a processor1440. These components may be in electronic communication via one or more buses (e.g., bus1445).

In some examples, the device1405may transmit sensor information to another device as described herein. In such examples, the communications manager1410may identify a configured set of one or more rules that apply to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor; identify a performance value from the set of performance values for the sensor based on a performance level of the sensor and the configured set of one or more rules; and transmit, to a second wireless device, an indication of the configured set of one or more rules for the sensor in a message and an indication of the performance value for the sensor in the message.

In some examples, the device1405may receive sensor information from another device as described herein. In such examples, the communications manager1410may receive, in a message, an indication of a configured set of one or more rules that applies to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor; receive an indication of a performance value for the sensor in the message; and identify a performance level of the sensor based on the performance value and the configured set of one or more rules.

The I/O controller1415may manage input and output signals for the device1405. The I/O controller1415may also manage peripherals not integrated into the device1405. In some cases, the I/O controller1415may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1415may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, the I/O controller1415may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1415may be implemented as part of a processor. In some cases, a user may interact with the device1405via the I/O controller1415or via hardware components controlled by the I/O controller1415.

The transceiver1420may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver1420may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1420may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna1425. However, in some cases the device may have more than one antenna1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

The memory1430may include random-access memory (RAM) and read-only memory (ROM). The memory1430may store computer-readable, computer-executable code1435including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory1430may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1440may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1440may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor1440. The processor1440may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1430) to cause the device1405to perform various functions (e.g., functions or tasks supporting sensor performance indication).

The code1435may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code1435may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code1435may not be directly executable by the processor1440but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

FIG.15shows a flowchart illustrating a method1500that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The operations of method1500may be implemented by a UE115or its components as described herein. For example, the operations of method1500may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At1505, the UE may identify a configured set of one or more rules that apply to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. The operations of1505may be performed according to the methods described herein. In some examples, aspects of the operations of1505may be performed by a certification component as described with reference toFIGS.11through14.

At1510, the UE may identify a performance value from the set of performance values for the sensor based on a performance level of the sensor and the configured set of one or more rules. The operations of1510may be performed according to the methods described herein. In some examples, aspects of the operations of1510may be performed by an association component as described with reference toFIGS.11through14.

At1515, the UE may transmit, to a second wireless device, an indication of the configured set of one or more rules for the sensor in a message and an indication of the performance value for the sensor in the message. The operations of1515may be performed according to the methods described herein. In some examples, aspects of the operations of1515may be performed by a direct communication component as described with reference toFIGS.12and13.

FIG.16shows a flowchart illustrating a method1600that supports sensor performance indication in accordance with one or more aspects of the present disclosure. The operations of method1600may be implemented by a UE115or its components as described herein. For example, the operations of method1600may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At1605, the UE may receive, in a message, an indication of a configured set of one or more rules that applies to a sensor configured to monitor one or more conditions, the configured set of one or more rules defining an association between a set of performance values and a set of performance levels corresponding to one or more metrics of the sensor. The operations of1605may be performed according to the methods described herein. In some examples, aspects of the operations of1605may be performed by a certification component as described with reference toFIGS.12and13.

At1610, the UE may receive an indication of a performance value for the sensor in the message. The operations of1610may be performed according to the methods described herein. In some examples, aspects of the operations of1610may be performed by a direct communication component as described with reference toFIGS.12and13.

At1615, the UE may identify a performance level of the sensor based on the performance value and the configured set of one or more rules. The operations of1615may be performed according to the methods described herein. In some examples, aspects of the operations of1615may be performed by an association component as described with reference toFIGS.12and13.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.