Patent Description:
A wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).

Some wireless communications systems may support vehicle-to-everything (V2X) services and may include devices that support perceptive networks where one or more components are used to determine aspects of an environment. In some cases, one or more components may experience a fault such that data produced by the components is inaccurate. <CIT> discloses a method for validating data contained in a request sent by a requestor to a server application, the method comprising the steps of: receiving, by one or more processors, the request from the requestor before processing of the request by the server application; identifying, by one or more processors, a set of data validation rules to apply to the data in the request based on a data format specification contained in the request sent by the requestor; determining, by one or more processors, that the data is valid based on the identified set of data validation rules, and in response, forwarding the request to the server application for processing.

<CIT> discloses a system for determining an accuracy of crowd-sourced information, comprising: a server configured to receive inputs from one or more sources concerning an event, wherein each of the one or more inputs comprises source information and event information, wherein the source information comprises an identifier and a location; wherein the server is configured to analyze the source information of each input of the one or more sources, and assign a credibility rating to each of the sources; wherein the server is further configured to compare the location of the source with an event location and assign an accuracy rating to each input based on the distance of the source from the event location; wherein the server is further configured to query a set of sensors within a predefined range of the event location, and compare the received data from the set of sensors with the received event information; based on this comparison and the credibility and accuracy ratings of each input, the server is configured to assign an accuracy probability rating (APR) to the event.

<CIT> discloses a method comprising: capturing first sensor data from one or more sensors installed in an autonomous vehicle; receiving data associated with a remote autonomous vehicle, the data including one or more of first data associated with a state of the remote autonomous vehicle or second data associated with second sensor data captured by the remote autonomous vehicle; determining a validity of the data; generating a trajectory of the autonomous vehicle based at least in part on the first sensor data, the data, and the validity of the data; and navigating the autonomous vehicle based at least in part on the trajectory.

<CIT> discloses a system comprising a node, wherein the node includes two separate controllers, each of which is configured to output data to a bus, or receive data from a bus, or output data to and receive data from a bus, and wherein at least one controller is configured to monitor the output of the other controller and wherein the at least one controller is configured such that if the at least one controller determines that the other controller is providing improper data or signals, at least part of the output data of the other controller is nullified, overridden or superseded by an output from the at least one controller.

<CIT> discloses a vehicle communication system for cloud-hosting sensor-data from a plurality of vehicles, wherein each of the vehicles is equipped with one or more sensors used to detect objects proximate to each of the vehicles, said system comprising: a transceiver used to communicate sensor-data from a first-sensor on a first-vehicle and from a second-sensor on a second-vehicle; and a controller configured to receive, via the transceiver, first-data from the first-sensor and second-data from the second-sensor, determine when the first-data and the second-data are both indicative of an object proximate to the first-vehicle and the second-vehicle, wherein the first-data is characterized by a first-confidence and the second-data is characterized by a second-confidence, and the controller is configured to prevent communication of the second-data to the first-vehicle when the first-confidence is greater than the second-confidence.

The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for fault detection in wireless communications systems. The described techniques provide for a first device to perform data validation with one or more other devices. For example, a device may generate data at components associated with the device. To validate at least a portion of the data, the device may establish a connection with other devices. In some examples, the device may determine a portion of the data to validate based on a capability of the other devices to generate data that corresponds to the portion of data. The device may exchange data with the other devices and determine a validity of data generated at the device in response.

The invention is defined in the independent claims, to which reference should now be made.

A method of wireless communications at a first device is described. The method includes: generating a first set of data associated with a set of components of the first device; establishing, with one or more other devices, a connection for validation of data generated at the set of components; determining at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data; transmitting the subset of the first set of data to the one or more other devices; receiving, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data; determining at least one component of the plurality of components is experiencing a failure, wherein the first set of data is associated with the at least one component; determining a second set of data associated with one or more other components of the plurality of components; and determining a validity of the subset of the first set of data in response to receiving the at least one other set of data and the second set of data.

An apparatus for wireless communications at a first device is described. The apparatus includes: means for generating a first set of data associated with a set of components of the first device; establishing, with one or more other devices, a connection for validation of data generated at the set of components; determining at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data; transmitting the subset of the first set of data to the one or more other devices; receiving, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data; determining at least one component of the plurality of components is experiencing a failure, wherein the first set of data is associated with the at least one component; determining a second set of data associated with one or more other components of the plurality of components; and determining a validity of the subset of the first set of data in response to receiving the at least one other set of data and the second set of data.

A non-transitory computer-readable medium storing code for wireless communications at a first device is described. The code includes instructions executable by a processor to: generate a first set of data associated with a set of components of the first device; establish, with one or more other devices, a connection for validation of data generated at the set of components; determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data; transmit the subset of the first set of data to the one or more other devices; receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data; determine at least one component of the plurality of components is experiencing a failure, wherein the first set of data is associated with the at least one component; determine a second set of data associated with one or more other components of the plurality of components; and determine a validity of the subset of the first set of data in response to receiving the at least one other set of data and the second set of data.

Some examples of the method, apparatus, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the first set of data may be invalid, transmitting, to the one or more other devices, an indication that the first set of data may be invalid, and transmitting, to the one or more devices, a request to initiate data sharing.

Some examples of the method, apparatus, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the first set of data may be valid, and transmitting, to the one or more other devices, an indication that the first set of data may be valid.

Some examples of the method, apparatus, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for dividing the set of components at the first device into one or more sets of components, where the first set of data may be generated at a first set of components.

In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, determining the validity of the first set of data may include operations, features, means, or instructions for determining whether one or more parameters associated with the first set of data satisfy a threshold.

In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the one or more parameters include one or more of a latency parameter or a quality of service parameter.

In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, establishing the connection may include operations, features, means, or instructions for establishing a vehicle-to-everything connection with the one or more other devices.

Some wireless communications may support vehicle-to-everything (V2X) services where devices (e.g., user equipments (UEs), vehicles, roadside units, base stations, etc.) share information to establish a perceptive network. A perceptive network may be a network in which devices share information generated by sensors at each device to enable the devices to observe or perceive an environment. For example, a device may include components (e.g., sensors) which generate data corresponding to aspects of an environment. Devices may use such data to observe or perceive the environment via the perceptive network. In some cases, perceptive networks may allow for increased safety, efficient communications, driver assistance, or infotainment services, among other benefits. However, perceptive networks, or the devices operating therein, may be susceptible to data faults or component failures resulting in inaccurate data, which may lead to decreased safety conditions, a loss of service, etc..

A technique for detecting faults and validating data generated by components associated with devices in a perceptive network is described herein. The present technique may include a first UE establishing a data validation connection (e.g., a V2X data validation session) with other UEs to validate data generated by sensors associated with the first UE. For example, the UE may include sensors used to generate data corresponding to different aspects of an environment and may establish data validation sessions with other UEs to validate the data. In some examples, the first UE may determine which other UEs to connect to and which data to validate based on a capability of the other UEs to generate data that corresponds to a same aspect of an environment as data generated by sensors at the first UE. For example, data generated by sensors at the first UE may correspond to a particular location, direction, etc. If that data needs to be validated, the first UE may select other UEs that are able to generate data corresponding to the same location, direction, etc. The first UE may transmit data to at least one of the other UEs and, in response, receive other data that corresponds to a same aspect of the environment. The first UE may determine whether the data generated at the first UE is valid based on data received from the other UEs. For example, based on a received set of data (e.g., by comparing the data), the first UE may determine that the portion of data generated by sensors associated with the first UE does or does not satisfy thresholds associated with quality of service, latency, accuracy, error rate, or other parameters. If the first UE determines that the portion of data has a fault (e.g., is inaccurate because it does not satisfy the thresholds), the first device may transmit an indication of the invalid data to the other UEs. Additionally or alternatively, the first UE may request to perform data sharing with the other UEs to mitigate the effects of the data fault.

In some implementations, the first UE may detect a fault or failure (e.g., a power failure, a communications failure, etc.) in sensors associated with the first UE. In response, the first UE may determine other sensors which may generate data corresponding to data generated at the failed sensors. For example, the first UE may divide sensors associated with the first UE into different sections that each correspond to a different aspect (e.g., location, direction, etc.) of an environment. If a sensor in a section experiences a failure, the first UE may use data generated by other sensors in the section to validate data from the failed sensor.

Particular aspects of the present disclosure may be implemented to realize one or more potential advantages. For example, the described techniques include features which provide for fault detection and data validation in V2X perceptive networks. Based on the techniques for data validation, a wireless communications system may experience increased efficiency, an increased reliability for communications and infotainment services, or increased safety conditions, among other benefits.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further described in the context of a device diagram and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for fault detection in wireless communications systems.

<FIG> illustrates an example of a wireless communications system <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The wireless communications system <NUM> may include one or more base stations <NUM>, one or more UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may 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 system <NUM> may 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 stations <NUM> may communicate with the core network <NUM>, or with one another, or both. For example, the base stations <NUM> may interface with the core network <NUM> through one or more backhaul links <NUM> (e.g., via an S1, N2, N3, or other interface). The base stations <NUM> may communicate with one another over the backhaul links <NUM> (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations <NUM>), or indirectly (e.g., via core network <NUM>), or both. In some examples, the backhaul links <NUM> may be or include one or more wireless links.

The time intervals for the base stations <NUM> or the UEs <NUM> may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts = <NUM>/(Δfmax · Nf) seconds, where Δfmax may represent the maximum supported subcarrier spacing, and Nf may 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., <NUM> milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from <NUM> to <NUM>).

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 system <NUM> and 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 system <NUM> may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Some UEs <NUM>, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs <NUM> may be designed to collect information or enable automated behavior of machines or other devices.

In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs <NUM> include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs <NUM> may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

In some systems, the D2D communication link <NUM> may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs <NUM>). In some examples, vehicles may communicate using V2X communications, vehicle-to-vehicle (V2V) communications, or some combination of these. 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 stations <NUM>) using vehicle-to-network (V2N) communications, or with both.

The core network <NUM> may be an evolved packet core (EPC) or <NUM> 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 UEs <NUM> served by the base stations <NUM> associated with the core network <NUM>. 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 IP services <NUM> for one or more network operators. The IP services <NUM> may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The wireless communications system <NUM> may operate using one or more frequency bands, typically in the range of <NUM> megahertz (MHz) to <NUM> gigahertz (GHz). Generally, the region from <NUM> to <NUM> 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 UEs <NUM> located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than <NUM> 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 <NUM>.

A base station <NUM> or a UE <NUM> may 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 station <NUM> or a UE <NUM> may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. In some examples, antennas or antenna arrays associated with a base station <NUM> may be located in diverse geographic locations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.

In some examples, in which a wireless communications system <NUM> supports V2X communications, multiple devices (e.g., UEs <NUM>, base stations <NUM>, roadside units, etc.) may support perceptive networks in which devices share information corresponding to aspects of an environment. For example, UEs <NUM> (e.g., vehicles), base stations <NUM>, or roadside units may include components configured to generate data corresponding to the environment and may share data to assist other devices to observe or perceive the environment. In some examples, devices in a perceptive network may experience data faults or component failures which may lead to inaccurate data being shared via the network. To mitigate the effects of data faults or component failures, devices in the network (e.g., UEs <NUM>, base stations <NUM>, roadside units, etc.) may perform data validation procedures with other devices in the network.

<FIG> illustrates an example of a wireless communications system <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. In some examples, the wireless communications system <NUM> may implement aspects of a wireless communication system <NUM> as described with reference to <FIG>. The wireless communications system <NUM> may include a first device <NUM>-a, a first device <NUM>-b, and a first device <NUM>-b, which may be examples of a UE <NUM> (e.g., a vehicle) as described with reference to <FIG>. The wireless communications system <NUM> may also include a second device <NUM> which, in some implementations, may be an example of a base station <NUM> (e.g., a roadside unit) as described with reference to <FIG>. The first devices <NUM>-a, <NUM>-b, <NUM>-c, and <NUM> may share information via one or more links <NUM>.

In some implementations, the wireless communications system <NUM> may support perceptive networks via V2X services. As such, the first devices <NUM>-a, <NUM>-b, <NUM>-c and <NUM> may support sharing information to observe or perceive an environment <NUM>. For example, each of first devices <NUM>-a, <NUM>-b, <NUM>-c, and <NUM> may include components (e.g., sensors) configured to generate data corresponding to aspects of the environment <NUM>. However, such components may be susceptible to failure, leading to inaccurate data being shared between the first devices <NUM>-a, <NUM>-b, <NUM>-c, and <NUM>. To mitigate the effects of data faults, devices in the wireless communications system <NUM> may perform data validation and sharing procedures.

For example, the first device <NUM>-a may generate data at components associated with the first device <NUM>-a. If the first device <NUM>-a detects a component failure or potential data fault (e.g., through an electronic control unit), the first device <NUM>-a may establish a data validation session with the first device <NUM>-b via the link <NUM>-a. The first device <NUM>-a may determine a portion of the generated data to validate via the data validation session established with the first device <NUM>-b. In some examples, the first device <NUM>-a may determine the portion of data for validation based on a capability of the first device <NUM>-b to generate data that corresponds to at least a same aspect of the environment <NUM> as the portion of data. The first device <NUM>-a may transmit the portion of data to the first device <NUM>-b and the first device <NUM>-b may generate and transmit a corresponding other set of data. In response to receiving the other data from the first device <NUM>-b, the first device <NUM>-a may determine a validity of data generated at components associated with the first device <NUM>-a. For example, the first device <NUM>-a may determine whether the portion of data satisfies one or more thresholds associated with latency, accuracy, error rate, etc. based on the data received from the first device <NUM>-b. Additionally or alternatively, in some examples, the first device <NUM>-a may validate data generated at components associated with the first device <NUM>-a using data generated by other components associated with the first device <NUM>-a. For example, if the first device <NUM>-a detects that a component is experiencing a failure, the first device <NUM>-a may valid data generated by the component using data generated by other components associated with the first device <NUM>-a.

If the first device <NUM>-a determines that the portion of data is valid, the first device <NUM>-a may transmit an indication of validity to the first device <NUM>-b. If the first device <NUM>-a determines that the portion of data is invalid (e.g., has a fault), the first device <NUM>-a may transmit an indication of invalidity to the first device <NUM>-b. Additionally or alternatively, the first device <NUM>-a may transmit a request for data sharing to the first device <NUM>-b. In response, the first device <NUM>-a and the first device <NUM>-b may perform data sharing techniques to mitigate effects of the invalid data at the first device <NUM>-a. In some examples, the first device <NUM>-b may ignore data received from the first device <NUM>-a in response to receiving an indication that data generated at the first device <NUM>-b has a fault. In some examples, the first device <NUM>-a may provide an indication to a user of the first device <NUM>-a that data generated at the first device <NUM>-a has fault. In some examples, the first device <NUM>-a may detect a potential fault in data received form the first device <NUM>-a and may establish a data validation session in response. Although described with reference to the first devices <NUM>-a and <NUM>-b, it is noted that the first device <NUM>-a may perform data validation with the first device <NUM>-c, the second device <NUM>, or any combination of devices associated with the wireless communications system <NUM>.

In some examples, the first device <NUM>-a may transmit an indication of a data fault to the second device <NUM>. In response, the second device <NUM> may determine other devices available for data sharing with the first device <NUM>-a. For example, the second device <NUM> may determine the first device <NUM>-c is available to share data with the first device <NUM>-a to mitigate effects of the data fault detected at the first device <NUM>-a. The second device <NUM> may transmit to the first device <NUM>-a, via a link <NUM>-c, a request for the first device <NUM>-c to perform data sharing with the first device <NUM>-a. Similarly, the second device <NUM> may transmit an indication to the first device <NUM>-a that the first device <NUM>-c is available for data sharing. In response, the first device <NUM>-a and the first device <NUM>-c may perform data sharing to mitigate effects of the data fault detected at the first device <NUM>-a. Implementing aspects of the present disclosure may allow devices in the wireless communications system <NUM> to detect faults and validate data associated with V2X perceptive networks, leading to an increased reliability of communications services.

<FIG> shows a diagram <NUM> of an example device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. In some examples, the device <NUM> may implement aspects of a wireless communication system <NUM> or <NUM> as described with reference to <FIG> and <FIG>. The device <NUM> may be an example of a device (e.g., a UE <NUM> as shown in <FIG>) that supports V2X perceptive networks and includes one or more components <NUM>. In some examples, the components <NUM> may be examples of sensors (e.g., cameras, radars, etc.) configured to generate data corresponding to aspects of an environment associated with the device <NUM>. In some implementations, the components <NUM> may be associated with or controlled via an electronic control unit. In some example, the device may perform fault detection and data validation techniques described with reference to <FIG>.

In some examples, the device <NUM> may divide components <NUM> into different sections <NUM>. For example, a section <NUM>-a may include components <NUM>-a, <NUM>-b and <NUM>-c, a section <NUM>-b may include components <NUM>-d, <NUM>-f, and <NUM>-e, a section <NUM>-c may include components <NUM>-g, <NUM>-h, and <NUM>-i, and a section <NUM>-d may include components <NUM>-j, <NUM>-k, and <NUM>-j. Different sections <NUM> may correspond to different aspects of a surrounding environment. In some examples, in which the device <NUM> is an example of a vehicle, the section <NUM>-a may correspond to a front of the vehicle, the section <NUM>-b may correspond to a back of the vehicle, and the sections <NUM>-c and <NUM>-d may correspond to the driver and passenger sides of the vehicle, respectively. In some examples, the device <NUM> may divide the components <NUM> into the sections <NUM> to increase an efficiency of data validation procedures by validating data associated with multiple components <NUM> rather than data associated with each component <NUM> individually. Similarly, the device <NUM> may share data associated with a second <NUM> with other devices rather than data associated with each component <NUM>.

In some examples, if the device <NUM> detects a failure associated with one or components <NUM> in a section <NUM>, the device <NUM> may use data generated by other components <NUM> in the same section <NUM> to validate the data. For example, if the device <NUM> detects that the component <NUM>-a has a failure, the device <NUM> may validate data generated by the component <NUM>-a based on data generated by the components <NUM>-c and <NUM>-d which may correspond to a same aspect of an environment. Implementing aspects of the present disclosure may enable the device <NUM> to perform fault detection and data validation, leading to an increased reliability of services at the device <NUM>.

<FIG> illustrates an example of a process flow <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. In some examples, the process flow <NUM> may implement aspects of or be implemented by a wireless communications system <NUM> or <NUM>, a device <NUM>, or any combination thereof as described with reference to <FIG>. For example, the process flow <NUM> may be implemented by a device operating in a V2X perceptive network. Alternative examples of the following may be implemented where some processes are performed in a different order than described or not performed at all. In some implementations, processes may include additional features not mentioned below, or further processes may be added.

At <NUM>, a device (e.g., a first device <NUM> or a device <NUM> as described with reference to <FIG> and <FIG>) may determine whether a component at the device is experiencing a failure. For example, an electronic control unit associated with the component may determine that the component is unresponsive, is experiencing a power failure, is experiencing a loss of communications, etc. If the device does not detect a failure, the device may, at <NUM>, determine to validate data associated with the components via data validations sessions with other devices. If the device determines that the data is valid, the device may, at <NUM>, continue operating or communicating based on determining the data is valid.

If, however, the device determines that the data is invalid, or if the device detects a component failure, the device may, at <NUM>, provide an indication to a user of the device that data generated at the device is invalid. Similarly, the device may, at <NUM> indicate the invalid data to other devices and, at <NUM>, may request data sharing from the other devices to mitigate effects of the invalid data. Implementing aspects of the process flow <NUM> may allow a device to perform fault detection and data validation, leading to an increased reliability of services.

<FIG> illustrates an example of a process flow <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. In some examples, the process flow <NUM> may implement aspects of or be implemented by a wireless communications system <NUM> or <NUM>, a device <NUM>, a process flow <NUM>, or any combination thereof as described with reference to <FIG>. For examples, the process flow <NUM> may be implemented by a device operating in a V2X perceptive network. Alternative examples of the following may be implemented where some processes are performed in a different order than described or not performed at all. In some implementations, processes may include additional features not mentioned below, or further processes may be added.

At <NUM>, a first device (e.g., a first device <NUM> or a device <NUM> as described with reference to <FIG> and <FIG>), may establish a connection with other devices in a V2X network to validate data generated at the first device. At <NUM>, the first device may determine at least of portion of data to validate with the other devices based on a capability of the other devices to generate data corresponding to a same aspect of an environment as the portion of data.

At <NUM>, the first device may initiate a data exchange with the other devices. For example, the first device may transmit the determined portion of data and receive corresponding data from the other devices in response. At <NUM>, the first device may determine a validity of the portion of data based on the data received from the other devices. For example, the first device may compare the portion of data to the received data and determine whether the portion of data satisfies a threshold accuracy, latency, error rate, etc..

If the first device determines that the first portion of data is valid, the device may, at <NUM>, provide an indication of validity to the other devices and may continue operating based on determining the data is valid.

If, however, the first device determines that the portion of data has a fault, or is invalid, the device may at <NUM>, indicate the invalid data to a user of the first device. At <NUM>, the first device may also indicate the invalidity to the other devices and, at <NUM>, the first device may request to perform data sharing with the other devices to mitigate the effects of the data fault. Implementing aspects of the process flow <NUM> may allow a device to perform fault detection and data validation, leading to an increased reliability of services.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a UE communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may 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 techniques for fault detection in wireless communications systems, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The UE communications manager <NUM> may generate a first set of data associated with a set of components of the first device, establish, with one or more other devices, a connection for validation of data generated at the set of components, determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data, transmit the subset of the first set of data to the one or more other devices, receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data, and determine a validity of the subset of the first set of data in response to receiving at least the one other set of data. The UE communications manager <NUM> may also receive, from a second device, a first set of data generated at the second device, receive, from the second device, an indication that the first set of data is invalid, ignore the first set of data based on the indication that the first set of data is invalid, and transmit, to the second device, an indication of an availability of the first device to perform data sharing with the second device. The UE communications manager <NUM> may be an example of aspects of the UE communications manager <NUM> described herein.

The UE communications manager <NUM>, 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 UE communications manager <NUM>, 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 UE communications manager <NUM>, 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 UE communications manager <NUM>, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the UE communications manager <NUM>, 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.

In some examples, the transmitter <NUM> may be collocated with a receiver <NUM> in a transceiver component.

In some examples, the UE communications manager <NUM> may be implemented as an integrated circuit or chipset for a mobile device modem, and the receiver <NUM> and transmitter <NUM> may be implemented as analog components (e.g., amplifier, filters, antennas) coupled with the mobile device modem to enable wireless transmission and reception over one or more bands.

The UE communications manager <NUM> as described may be implemented to realize one or more potential advantages. One implementation may allow the device <NUM> to detect faults and perform data validation as part of V2X perceptive networks. Based on the techniques for performing data validation, the device <NUM> may exhibit improved reliability, reduced latency, or improved data reliability, among other benefits.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a UE communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The UE communications manager <NUM> may be an example of aspects of the UE communications manager <NUM> as described herein. The UE communications manager <NUM> may include a data generator <NUM>, a connection manager <NUM>, a data manager <NUM>, a data transmitter <NUM>, a data receiver <NUM>, a validation component <NUM>, and a validity receiver <NUM>. The UE communications manager <NUM> may be an example of aspects of the UE communications manager <NUM> described herein.

The data generator <NUM> may generate a first set of data associated with a set of components of the first device.

The connection manager <NUM> may establish, with one or more other devices, a connection for validation of data generated at the set of components.

The data manager <NUM> may determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data.

The data transmitter <NUM> may transmit the subset of the first set of data to the one or more other devices.

The data receiver <NUM> may receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data.

The validation component <NUM> may determine a validity of the subset of the first set of data in response to receiving at least the one other set of data.

The data receiver <NUM> may receive, from a second device, a first set of data generated at the second device.

The validity receiver <NUM> may receive, from the second device, an indication that the first set of data is invalid.

The data manager <NUM> may ignore the first set of data based on the indication that the first set of data is invalid.

The data transmitter <NUM> may transmit, to the second device, an indication of an availability of the first device to perform data sharing with the second device.

<FIG> shows a block diagram <NUM> of a UE communications manager <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The UE communications manager <NUM> may be an example of aspects of a UE communications manager <NUM>, a UE communications manager <NUM>, or a UE communications manager <NUM> described herein. The UE communications manager <NUM> may include a data generator <NUM>, a connection manager <NUM>, a data manager <NUM>, a data transmitter <NUM>, a data receiver <NUM>, a validation component <NUM>, an invalidity transmitter <NUM>, a request transmitter <NUM>, a validity transmitter <NUM>, a failure manager <NUM>, a component divider <NUM>, a threshold component <NUM>, a validity receiver <NUM>, a data transmitter <NUM>, a request receiver <NUM>, and a data sharing manager <NUM>. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The connection manager <NUM> may establish, with one or more other devices, a connection for validation of data generated at the set of components. In some examples, the connection manager <NUM> may establish a vehicle-to-everything connection with the one or more other devices.

The data manager <NUM> may determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data. In some examples, the data manager <NUM> may ignore the first set of data based on the indication that the first set of data is invalid. In some examples, the data manager <NUM> may determine a second set of data associated with one or more other components of the set of components, where determining the validity of the first set of data is based on the second set of data. In some examples, the data manager <NUM> may determine a second set of data for validating the first set of data based on a capability of the first device to validate the first set of data.

The data transmitter <NUM> may transmit the subset of the first set of data to the one or more other devices. In some examples, the data transmitter <NUM> may transmit, to the second device, an indication of an availability of the first device to perform data sharing with the second device.

The data receiver <NUM> may receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data. In some examples, the data receiver <NUM> may receive, from a second device, a first set of data generated at the second device.

The validation component <NUM> may determine a validity of the subset of the first set of data in response to receiving at least the one other set of data. In some examples, the validation component <NUM> may determine the first set of data is invalid. In some examples, the validation component <NUM> may determine the first set of data is valid.

The invalidity transmitter <NUM> may transmit, to the one or more other devices, an indication that the first set of data is invalid.

The request transmitter <NUM> may transmit, to the one or more devices, a request to initiate data sharing.

The validity transmitter <NUM> may transmit, to the one or more other devices, an indication that the first set of data is valid.

The failure manager <NUM> may determine at least one component of the set of components is experiencing a failure, where the first set of data is associated with at least the one component.

The component divider <NUM> may divide the set of components at the first device into one or more sets of components, where the first set of data is generated at a first set of components.

The threshold component <NUM> may determine whether one or more parameters associated with the first set of data satisfy a threshold. In some cases, the one or more parameters include one or more of a latency parameter or a quality of service parameter.

The data transmitter <NUM> may transmit the second set of data to the second device.

The request receiver <NUM> may receive, from the second device, a request to perform data sharing.

The data sharing manager <NUM> may perform data sharing with the second device in response to receiving the request.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a UE communications manager <NUM>, an I/O controller <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The UE communications manager <NUM> may generate a first set of data associated with a set of components of the first device, establish, with one or more other devices, a connection for validation of data generated at the set of components, determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data, transmit the subset of the first set of data to the one or more other devices, receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data, and determine a validity of the subset of the first set of data in response to receiving at least the one other set of data. The UE communications manager <NUM> may also receive, from a second device, a first set of data generated at the second device, receive, from the second device, an indication that the first set of data is invalid, ignore the first set of data based on the indication that the first set of data is invalid, and transmit, to the second device, an indication of an availability of the first device to perform data sharing with the second device.

The processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (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 processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting techniques for fault detection in wireless communications systems).

<FIG> shows a block diagram <NUM> of a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a base station communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The base station communications manager <NUM> may receive, from a second device, an indication that a first set of data generated at the second device is invalid, determine one or more other devices available for data sharing with the second device in response to receiving the indication, transmit, to the second device, an indication of an availability of the one or more other devices to perform data sharing with the second device, and transmit, to the one or more other devices, the indication that the first set of data generated at the second device is invalid and a request for the one or more other devices to perform data sharing with the second device. The base station communications manager <NUM> may be an example of aspects of the base station communications manager <NUM> described herein.

The base station communications manager <NUM>, 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 base station communications manager <NUM>, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), a 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 base station communications manager <NUM>, 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 base station communications manager <NUM>, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the base station communications manager <NUM>, 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.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a base station communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The base station communications manager <NUM> may be an example of aspects of the base station communications manager <NUM> as described herein. The base station communications manager <NUM> may include an invalidity receiver <NUM>, a data sharing manager <NUM>, an availability transmitter <NUM>, and an invalidity transmitter <NUM>. The base station communications manager <NUM> may be an example of aspects of the base station communications manager <NUM> described herein.

The invalidity receiver <NUM> may receive, from a second device, an indication that a first set of data generated at the second device is invalid.

The data sharing manager <NUM> may determine one or more other devices available for data sharing with the second device in response to receiving the indication.

The availability transmitter <NUM> may transmit, to the second device, an indication of an availability of the one or more other devices to perform data sharing with the second device.

The invalidity transmitter <NUM> may transmit, to the one or more other devices, the indication that the first set of data generated at the second device is invalid and a request for the one or more other devices to perform data sharing with the second device.

<FIG> shows a block diagram <NUM> of a base station communications manager <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The base station communications manager <NUM> may be an example of aspects of a base station communications manager <NUM>, a base station communications manager <NUM>, or a base station communications manager <NUM> described herein. The base station communications manager <NUM> may include an invalidity receiver <NUM>, a data sharing manager <NUM>, an availability transmitter <NUM>, an invalidity transmitter <NUM>, a data receiver <NUM>, a data manager <NUM>, a data transmitter <NUM>, and a request receiver <NUM>. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The data sharing manager <NUM> may determine one or more other devices available for data sharing with the second device in response to receiving the indication. In some examples, the data sharing manager <NUM> may perform data sharing with the second device in response to receiving the request.

The data receiver <NUM> may receive the first set of data from the second device.

The data manager <NUM> may determine a second set of data for validating the first set of data based on a capability of the first device to validate the first set of data.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a base station communications manager <NUM>, a network communications manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The base station communications manager <NUM> may receive, from a second device, an indication that a first set of data generated at the second device is invalid, determine one or more other devices available for data sharing with the second device in response to receiving the indication, transmit, to the second device, an indication of an availability of the one or more other devices to perform data sharing with the second device, and transmit, to the one or more other devices, the indication that the first set of data generated at the second device is invalid and a request for the one or more other devices to perform data sharing with the second device.

The processor <NUM> may 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 processor <NUM> may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting techniques for fault detection in wireless communications systems).

The inter-station communications manager <NUM> may manage communications with other base station <NUM> and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. 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.

At <NUM>, the UE may generate a first set of data associated with a set of components of the first device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Generator as described with reference to <FIG>.

At <NUM>, the UE may establish, with one or more other devices, a connection for validation of data generated at the set of components. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Connection Manager as described with reference to <FIG>.

At <NUM>, the UE may determine at least a subset of the first set of data for validation based on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Manager as described with reference to <FIG>.

At <NUM>, the UE may transmit the subset of the first set of data to the one or more other devices. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Transmitter as described with reference to <FIG>.

At <NUM>, the UE may receive, from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Receiver as described with reference to <FIG>.

At <NUM>, the UE may determine a validity of the subset of the first set of data in response to receiving at least the one other set of data. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Validation Component as described with reference to <FIG>.

At <NUM>, the UE may determine the first set of data is invalid in response to receiving at the one other set of data. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Validation Component as described with reference to <FIG>.

At <NUM>, the UE may transmit, to the one or more other devices, an indication that the first set of data is invalid. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an Invalidity Transmitter as described with reference to <FIG>.

At <NUM>, the UE may transmit, to the one or more devices, a request to initiate data sharing. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Request Transmitter as described with reference to <FIG>.

At <NUM>, the UE may determine at least one component of the set of components is experiencing a failure, where the first set of data is associated with at least the one component. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Failure Manager as described with reference to <FIG>.

At <NUM>, the UE may determine a second set of data associated with one or more other components of the set of components. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Manager as described with reference to <FIG>.

At <NUM>, the UE may determine a validity of the subset of the first set of data based on the second set of data. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Validation Component as described with reference to <FIG>.

At <NUM>, the UE may receive, from a second device, a first set of data generated at the second device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Receiver as described with reference to <FIG>.

At <NUM>, the UE may receive, from the second device, an indication that the first set of data is invalid. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Validity Receiver as described with reference to <FIG>.

At <NUM>, the UE may ignore the first set of data based on the indication that the first set of data is invalid. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Manager as described with reference to <FIG>.

At <NUM>, the UE may transmit, to the second device, an indication of an availability of the first device to perform data sharing with the second device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Transmitter as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports techniques for fault detection in wireless communications systems in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the base station may receive, from a second device, an indication that a first set of data generated at the second device is invalid. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an Invalidity Receiver as described with reference to <FIG>.

At <NUM>, the base station may determine one or more other devices available for data sharing with the second device in response to receiving the indication. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a Data Sharing Manager as described with reference to <FIG>.

At <NUM>, the base station may transmit, to the second device, an indication of an availability of the one or more other devices to perform data sharing with the second device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an Availability Transmitter as described with reference to <FIG>.

At <NUM>, the base station may transmit, to the one or more other devices, the indication that the first set of data generated at the second device is invalid and a request for the one or more other devices to perform data sharing with the second device. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an Invalidity Transmitter as described with reference to <FIG>.

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.

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. 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.

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.

The term "example" used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

Claim 1:
A method for wireless communications at a first device, the method comprising:
generating (<NUM>) a first set of data associated with a plurality of components of the first device;
establishing (<NUM>), with one or more other devices, a connection for validation of data generated at the plurality of components;
determining (<NUM>) at least a subset of the first set of data for validation based at least in part on a capability of the one or more other devices to generate one or more other sets of data corresponding to the first set of data;
transmitting (<NUM>) the subset of the first set of data to the one or more other devices;
receiving (<NUM>), from the one or more other devices, at least one other set of data corresponding to the subset of the first set of data;
characterized in that the method further comprises:
determining at least one component of the plurality of components is experiencing a failure, wherein the first set of data is associated with the at least one component;
determining a second set of data associated with one or more other components of the plurality of components; and
determining (<NUM>) a validity of the subset of the first set of data in response to receiving the at least one other set of data and the second set of data.