Sensor data search platform

Patent metadata

Field	Value
Publication number	US-11665239-B2
Application number	US-202017113849-A
Country	US
Kind code	B2
Filing date	Dec 7, 2020
Priority date	Apr 1, 2016
Publication date	May 30, 2023
Grant date	May 30, 2023

Abstract

Disclosed in some examples are methods, systems, and machine readable mediums which automatically generate standardized interfaces to sensor data consumers, provide sensor data search functionality, automatically determine data quality, and cache previously used sensor data to minimize the burden on application developers and minimize API call costs.

First claim

What is claimed is:

1. An Internet of things (IoT) service platform communicatively coupling sensors with client devices over a network, the IoT service platform comprising:
a processor; and
a memory communicatively coupled to the processor and comprising instructions, which when performed by the processor, cause the processor to perform operations comprising:
receiving, over the network, from a client device, a set of sensor data sources associated with sensors;
assigning a numerical quality score to each sensor data source based upon a comparison of values from a particular sensor data source with values from a subset of a plurality of available sensor data sources that are within a predetermined geographic distance to the particular data source, the numerical quality score representing a quality measurement of sensor data produced by the sensor data source;
responsive to receiving a request from the client device for sensor data produced by the set of sensor data sources, requesting current sensor readings from the corresponding sensors; and
transmitting to the client device the current sensor readings associated with the set of sensor data sources.

2. The IoT service platform of claim 1 , wherein the sensors include a first sensor of a first type and a second sensor of a second type.

3. The IoT service platform of claim 2 , wherein the first and second sensor produce similar data types.

4. The IoT service platform of claim 1 , wherein the numerical quality score is calculated using a weighted function.

5. The IoT service platform of claim 4 , wherein the weighted function includes a down time metric and a response time metric, the down time metric related to how much down time a corresponding sensor experiences, and the response time metric related to a response time that the corresponding sensor provides.

6. The IoT service platform of claim 4 , wherein the numerical quality score is updated periodically.

7. The IoT service platform of claim 4 , wherein the numerical quality score is updated after new sensor data is received.

8. The IoT service platform of claim 1 , comprising operations including:
determining that a particular numerical quality score of a corresponding sensor data source is below a threshold; and
generating a notification of the particular numerical quality score.

9. The IoT service platform of claim 8 , wherein the corresponding sensor data source is deregistered from the IoT service platform based on the particular numerical quality being below the threshold.

10. The IoT service platform of claim 1 , comprising operations including:
storing the numerical quality scores over time.

11. The IoT service platform of claim 10 , comprising operations including:
analyzing changes to the stored numerical quality scores over time.

12. The IoT service platform of claim 1 , wherein the operations comprise:
searching a cache to determine if sensor data is available from the cache; and
providing the sensor data from cache instead of requesting the sensor data from the corresponding sensor.

13. The IoT service platform of claim 1 , wherein the operations comprise:
translating the current sensor readings to a common format before transmitting the current sensor readings to the client device.

14. The IoT service platform of claim 1 , wherein the sensors include a first sensor that uses a first application programming interface (API) and a second sensor that uses a second API that is different from the first API.

15. The IoT service platform of claim 1 , wherein the operation of transmitting the current sensor readings comprises ordering the current sensor readings based upon the numerical quality score of each of the corresponding sensor data sources.

16. A method for managing sensor data, the method comprising:
receiving, over a network, from a client device, a set of sensor data sources associated with sensors;
assigning a numerical quality score to each sensor data source based upon a comparison of values from a particular sensor data source with values from a subset of a plurality of available sensor data sources that are within a predetermined geographic distance to the particular data source, the numerical quality score representing a quality measurement of sensor data produced by the sensor data source;
responsive to receiving a request from the client device for sensor data produced by the set of sensor data sources, requesting current sensor readings from the corresponding sensors; and
transmitting to the client device the current sensor readings associated with the set of sensor data sources.

17. The method of claim 16 , wherein the numerical quality score is calculated using a weighted function.

18. The method of claim 17 , wherein the weighted function includes a down time metric and a response time metric, the down time metric related to how much down time a corresponding sensor experiences, and the response time metric related to a response time that the corresponding sensor provides.

19. The method of claim 17 , wherein the numerical quality score is updated periodically.

20. The method of claim 17 , wherein the numerical quality score is updated after new sensor data is received.

21. The method of claim 16 , comprising:
determining that a particular numerical quality score of a corresponding sensor data source is below a threshold; and
generate a notification of the particular numerical quality score.

22. The method of claim 21 , wherein the corresponding sensor data source is deregistered from an IoT service platform based on the particular numerical quality being below the threshold.

23. The method of claim 16 , comprising:
storing the numerical quality scores over time.

24. The method of claim 23 , comprising:
analyzing changes to the stored numerical quality scores over time.

25. The method of claim 16 , comprising:
searching a cache to determine if sensor data is available from the cache; and
providing the sensor data from cache instead of requesting the sensor data from the corresponding sensor.

26. The method of claim 16 , comprising:
translating the current sensor readings to a common format before transmitting the current sensor readings to the client device.

27. The method of claim 16 , wherein requesting current sensor readings from the corresponding sensors comprises requesting sensor readings a first sensor that uses a first application programming interface (API) and requesting sensor readings from a second sensor that uses a second API that is different from the first API.

28. The method of claim 16 , wherein transmitting the current sensor readings comprises ordering the current sensor readings based upon the numerical quality score of each of the corresponding sensor data sources.

29. A non-transitory machine-readable medium for managing sensor data, the non-transitory machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations comprising:
receiving, over a network, from a client device, a set of sensor data sources associated with sensors;
assigning a numerical quality score to each sensor data source based upon a comparison of values from a particular sensor data source with values from a subset of a plurality of available sensor data sources that are within a predetermined geographic distance

Assignees

• Intel Corp

Inventors

• Graefe Ralf
• Kelly Damian

Classifications

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/12 Primary

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title