Patent Grant
10051060
The present invention relates to sensor data, and more specifically, to managing communication of sensor data.
The Internet of Things (IoT) is the network of physical objects or “things” embedded with electronics, software, sensors, and network connectivity, which enables these objects to collect and exchange data. The Internet of Things allows objects to be sensed and controlled remotely across existing network infrastructure, creating opportunities for more direct integration between the physical world and computer-based systems. This results in improved efficiency and accuracy in data management, and provides corresponding economic benefits. Each thing is uniquely identifiable through its embedded computing system and is able to interoperate within the existing Internet infrastructure. Experts estimate that the IoT will consist of almost 50 billion objects by the year 2020.
A method includes monitoring a utilization of sensor data, provided by at least one sensor, by at least one virtual sensor. The method also can include monitoring a utilization by at least one application of virtual sensor data, wherein the virtual sensor data is generated by the at least one virtual sensor based on the sensor data. The method also can include generating, using a processor, at least a first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application.
A system includes a processor programmed to initiate executable operations. The executable operations include monitoring a utilization of sensor data, provided by at least one sensor, by at least one virtual sensor. The executable operations also can include monitoring a utilization by at least one application of virtual sensor data, wherein the virtual sensor data is generated by the at least one virtual sensor based on the sensor data. The executable operations also can include generating, using a processor, at least a first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application.
A computer program includes a computer readable storage medium having program code stored thereon. The program code is executable by a processor to perform a method. The method includes monitoring, by the processor, a utilization of sensor data, provided by at least one sensor, by at least one virtual sensor. The method also can include monitoring, by the processor, a utilization by at least one application of virtual sensor data, wherein the virtual sensor data is generated by the at least one virtual sensor based on the sensor data. The method also can include generating, by the processor, at least a first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application.
The present invention relates to sensor data, and more specifically, to providing sensor data as a service using a virtual sensor infrastructure that publishes various types of sensor data to applications which subscribe to the sensor data. The infrastructure can include a plurality of virtual sensors that subscribe to sensor data generated by sensors, and publish the sensor data for consumption by one or more applications. In illustration, each virtual sensor can subscribe to a sensor data broker, which can broker sensor data received from one or more sensors. Thus, each virtual sensor can represent sensor data generated by one or more sensors. Each virtual sensor can publish the sensor data to a virtual sensor data broker. Applications can, via the virtual sensor data broker, subscribe to virtual sensors, and thus the sensor data they publish.
Publishing and subscribing is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers, but instead characterize published messages into classes without regard to which subscribers will receive the messages. Similarly, subscribers express interest in one or more classes and only received messages that are if interest. Subscribers need not send requests each time messages are desired. Instead, messages are sent by publishers to subscribers in accordance with a subscription scheme, for example as defined in a sensor data service agreement. In the arrangements described herein, the messages contain sensor data. Thus, various components can publish sensor data and various components can subscribe to the sensor data.
The arrangements described herein provide a high level of flexibility in sharing and consuming sensor data. For example, if an application requires sensor data generated by a plurality of different sensors, the application can subscribe to a virtual sensor that provides all such sensor data as though the sensor data is generated by a single sensor. Moreover, failover protection can be provided. For example, if a first sensor becomes faulty or inoperative, a virtual sensor data broker can publish sensor data from a second sensor in place of the sensor data which otherwise would be obtained from the first sensor. In another aspect, sensor data for the faulty or inoperative sensor can be approximated and the approximated sensor data can be published as sensor data for that sensor. Still, there are numerous other aspects of the present arrangements, which will described.
Several definitions that apply throughout this document now will be presented.
As defined herein, the term “sensor” means a device and/or software that senses absolute value or a change in a quantity and generates a corresponding signal or data. A sensor can be, for example, a physical sensor, a software sensor, or a combination of a physical sensor and a software sensor.
As defined herein, the term “physical sensor” means a physical device that senses the absolute value or a change in a physical quantity and generates a corresponding signal or data. Examples of a physical quantity include, but are not limited to, temperature, pressure, humidity, level precipitation, flow rate, pH, coefficient of friction, intensity of light, intensity of sound, intensity of radio waves, and the like.
As defined herein, the term “software sensor” means software that senses the absolute value or a change in software based system and generates a corresponding signal or data. A software sensor can, for example, detect processor utilization, memory utilization or the like. As the term “software sensor” is defined herein, a “software sensor” is not a virtual sensor.
As defined herein, the term “virtual sensor” means a data structure that receives sensor data generated by one or more sensors (e.g., physical sensors and/or software sensors), converts or combines the sensor data, and provides a corresponding output.
As defined herein, the term “sensor data broker” means a data structure that receives sensor data from one or more sensors and publishes the sensor data for subscription by one or more virtual sensors.
As defined herein, the term “virtual sensor data broker” means a data structure that receives sensor data from one or more virtual sensors and publishes the sensor data for subscription by one or more applications.
As defined herein, the term “publish” means to make available for subscription. For example, sensor data that is published can be made communicated to applications subscribing to that sensor data.
As defined herein, the term “close approximation” means to be within a particular tolerance. For example, first sensor data that is a close approximation to second sensor data can be data that is within one percent, five percent, ten percent, twenty percent, or the like, of the second sensor data, or meet some pre-defined data correlation.
As defined herein, the term “frequency” means a number of times something occurs within a given time interval. For example, a frequency of communicating sensor data can be two times per second (e.g., at 500 millisecond intervals).
As defined herein, the term “normalize” means to adjust a value measured on one scale to another scale, or to adjust a value measured on one system to be configured to be properly interpreted by another system.
As defined herein, the term “interpolate” means to construct new data points within a range of a discrete set of known data points.
As defined herein, the term “responsive to” means responding or reacting readily to an action or event. Thus, if a second action is performed “responsive to” a first action, there is a causal relationship between an occurrence of the first action and an occurrence of the second action, and the term “responsive to” indicates such causal relationship.
As defined herein, the term “computer readable storage medium” means a storage medium that contains or stores program code for use by or in connection with an instruction execution system, apparatus, or device. As defined herein, a “computer readable storage medium” is not a transitory, propagating signal per se.
As defined herein, the term “processor” means at least one hardware circuit (e.g., an integrated circuit) configured to carry out instructions contained in program code. Examples of a processor include, but are not limited to, a central processing unit (CPU), an array processor, a vector processor, a digital signal processor (DSP), a field-programmable gate array (FPGA), a programmable logic array (PLA), an application specific integrated circuit (ASIC), programmable logic circuitry, and a controller.
As defined herein, the term “real time” means a level of processing responsiveness that a user or system senses as sufficiently immediate for a particular process or determination to be made, or that enables the processor to keep up with some external process.
As defined herein, the term “output” means storing in memory elements, writing to display or other peripheral output device, sending or transmitting to another system, exporting, or the like.
As defined herein, the term “automatically” means without user intervention.
As defined herein, the term “user” means a person (i.e., a human being).
The sensor data broker 120 can be configured to subscribe to sensor data 160, 162, 164 generated by the plurality of sensors 110-114. For example, the sensor data broker 120 can subscribe to the sensor data 160-164 by subscribing to a sensor data service hosted by one or more processing systems that receive the sensor data 160-164 and publish the sensor data 160-162. In this regard, one or more sensor data service agreements can be established between a first entity who controls/manages the sensor data broker 120 and one or more entities who control/manage the sensors 110-114. The sensor data 160-134 can include sensor data generated by one or more physical sensors and/or sensor data generated by one or more software sensors.
The subscription(s) can be defined by a sensor data service agreement indicating subscription parameters, such as sensor data 160-164 generated by one or more sensors 110-114 to which the sensor data broker 120 subscribes, the frequency at which the sensor data 160-164 is communicated to the sensor data broker 120, the applicable fees for subscribing to the sensor data 160-164, etc. Further, the subscription parameters can indicate the manner in which the first entity is charged for access to the sensor data 160-164, for example on a per use basis, or based on an amount of time the sensor data broker 120 subscribes to the sensor data 160-164 (e.g., seconds, minutes, hours, days, weeks, months, years, etc.), and the frequency at which the sensor data 160-164 is communicated to the sensor data broker 120. The charges also can be based on the quality or type of the sensor data used. Still, a sensor data service agreement can be structured in any suitable manner, and the present arrangements are not limited in this regard. In one arrangement, one or more processing systems communicatively linked to the sensors 110-114 can monitor communication of the sensor data 160-164 to the sensor data broker 120 based on the subscription and generate corresponding data to be used for billing purposes. It should be noted that other sensor data brokers also can subscribe to the sensor data 160-162 generated by the sensors 110-114 in a similar manner.
The sensor data broker 120 can receive the sensor data 160 and re-publish at least a portion of that sensor data as published sensor data 170. The sensor data broker 120 also can receive the sensor data 162 and re-publish at least a portion of that sensor data as published sensor data 172. Further, the sensor data broker 120 can receive the sensor data 164 and re-publish at least a portion of that sensor data as published sensor data (not shown in
In one arrangement, the published sensor data 170 can include each type of data (e.g., data X, data Y and data Z) as the sensor data 160. In another arrangement, the published sensor data 170 can include a subset of the sensor data, for example data X and data Y, but not data Z. Similarly, the published sensor data 172 can include all or a portion of the sensor data 162, and the published sensor data 274 can include all or a portion of the sensor data 164. In one non-limiting arrangement, the published sensor data 170, 172, 274 can include samples of the sensor data 160-164, respectively. For example, the sensor data 160 can include data measured at a particular frequency (e.g., at every 500 millisecond interval), but the sensor data broker can publish a portion of these measurements, for example every fifth measurement, every tenth measurement, etc.
The virtual sensors 130-134 can subscribe to the published sensor data 170-172, and the sensor data broker 120 can communicate the published sensor data 170-172 to the virtual sensors 130-134 in accordance with the subscriptions. One or more of the virtual sensors 130-134 also can subscribe to the published sensor data 274 (as shown in
Each virtual sensor 130-134 can re-publish the received sensor data 170-172 received by that virtual sensor 130-134 as published sensor data (e.g., virtual sensor data) 180, 182, 184, respectively. In this example, the virtual sensor 130 can re-publish the published sensor data 170, and the virtual sensors 132, 134 each can re-publish the published sensor data 172. In one arrangement, when re-publishing the sensor data, the virtual sensors 130-134 can process and/or manipulate the sensor data, for example to convert the sensor data from one format to another, combine sensor data, normalize sensor data, interpolate sensor data, etc. In illustration, a virtual sensor 130 can received sensor data published by a plurality of sensor data brokers, and process and/or manipulate such sensor data together and publish that sensor data as the published sensor data 180-184.
Each virtual sensor data broker 140, 144 can subscribe to one or more groups of published sensor data 180-184 published by one or more virtual sensors 130-134, and the virtual sensors 130-134 can communicate the published sensor data 180-184 to the virtual sensor data brokers 140, 144 in accordance with the respective subscriptions. The subscriptions can be defined by one or more sensor data service agreements established between the entities controlling and/or managing the virtual sensor data brokers 140, 144 and the entities managing the virtual sensors 130-134, similar to those sensor data service agreements previously described. Accordingly, the entities controlling and/or managing the virtual sensor data brokers 140, 144 can be charged each time the virtual sensor data brokers 140, 144 receive published sensor data 180-184 from the virtual sensors 130-134, or charged based on an amount of time the virtual sensor data brokers 140, 144 subscribe to the published sensor data 180-184 and the frequency at which the published sensor data 180-184 is communicated to the virtual sensor data brokers 140, 144. The charges also can be based on the quality or type of the sensor data used.
The virtual sensor data brokers 140, 144 can re-publish the sensor data 180-184 as published sensor data 190, 192, 194 for consumption by the applications 150-154. In this regard, the applications 150-154 can subscribe to the published sensor data 190-194, and the virtual sensor data brokers 140, 144 can communicate the published sensor data 190-194 in accordance with corresponding subscriptions. For example, sensor data service agreements can be established between entities who control/manage the applications 150-154 and entities who control/manage the virtual sensor data brokers 140, 144. The frequency at which the applications 150-154 receive the published sensor data 190-194 and the fees for receiving the published sensor data 190-194 can be defined by the sensor data service agreements, for example in a manner similar to that previously described.
In one arrangement, the system can include an error detector 138 communicatively linked to each of the virtual sensors 130-134. In aspect, the error detector 138 can be another virtual sensor (not shown), though this need not be the case. The error detector 138 can implement error detection, for example prescriptive analytic modelling, on the published sensor data 170, 172. Responsive to identifying one or more anomalies in the published sensor data 170, 172, the error detector 138 can communicate an alert the virtual sensors 130-134 subscribing to the published sensor data 170, 172 in which the anomalies are present. The alert can indicate the anomalies in the published sensor data 170, 172.
To identify anomalies, the error detector 138 can compare and contrast sensor data deriving from different sensors that detect similar data and/or identify sensor data having values outside of a predetermined range. For example, assume that the sensors 110 and 112 each provide sensor data relating to ambient temperature and the sensors 110, 112 are located within one mile of each other. Also assume that the lowest ambient temperature recorded on a particular day of the year in the last fifty years is 66° F. and the highest ambient temperature recorded is 92° F. If the sensor 110 provides sensor data indicating an ambient temperature of 78° F. and the sensor 112 provides sensor data indicating an ambient temperature of −34° F., the error detector 138 can indicate to the virtual sensors 130-134 subscribing to the published sensor data 172 that there is an anomaly in the published sensor data 172.
Responsive to receiving the indication from the error detector 138 of the sensor data 172 anomaly, the affected virtual sensors 130-134 can process published sensor data derived from one or more other sensors, for example the sensor 110, to derive sensor data to be published. In illustration, the virtual sensors 130-134 can perform data interpolation and/or normalization to derive the sensor data to be published. If the other sensors already subscribe to such other sensor data, they can process that sensor data. Further, the virtual sensors 130-134 can be configured to dynamically subscribe to published sensor data derived from other sensors. Further, based on projected errors in the sensor data, the virtual sensors 130-134 can correct the sensor data. Accordingly, the applications 150-154 need not be tasked with performing first failure data capture (FFDC) or source data error detection.
The structure described herein can provide isolation of sensor data between the applications 150-154 and the virtual sensors 130-134, the sensor data broker(s) 120 and the sensors 110-114. In illustration, the sensor data broker 120 can receive sensor data 160-164 generated by each of the sensors 110-114, but the virtual sensors 130-134 need not receive all of such sensor data 160-164. For example, in one arrangement, the sensor data broker 120 can publish sensor data every certain number of sensor data readings, every certain number of seconds, minutes, hours, etc. in accordance with corresponding subscriptions. By subscribing to sensor data in this manner, the entities managing/controlling the virtual sensors 130-134 and the virtual sensor data brokers 140, 144 can reduce the fees charged for accessing the published sensor data 182-194 in circumstances in which fees are charged on a per use basis or based on a frequency of sensor data use.
Further, the isolation provided by the present arrangements can enhance security and privacy. In illustration, the entities that manage/control the sensors 110-114 need not be aware of the applications 150-154 using the sensor data. Moreover, the entities that manage/control the sensor data broker 120 and the virtual sensors 130-134 also need not be aware of the applications 150-154 using the sensor data. Thus, if unscrupulous people or systems are able to somehow access the processing systems hosting the sensor data broker 120 and the virtual sensors 130-134, information about the applications 150-154 using the sensor data will not be available, thus enhancing the level of security and privacy provided for the applications 150-154. Moreover, the applications 150-154 need not be provided direct access to the sensor data broker 120 or the virtual sensors 130-134, thus mitigating risk of entities who control/manage the applications 150-154 circumventing sensor data agreements established with the virtual sensor data brokers 140, 144.
In one aspect of the present arrangements, the various components 110-154 can send, receive, publish and subscribe to respective sensor data 160-194 using the MQTT protocol (formerly MQ Telemetry Transport protocol). MQTT is a machine-to-machine/Internet of Things connectivity protocol. MQTT provides extremely lightweight messaging transport using publish/subscribe implementations. MQTT is useful for connections with remote locations where a small code footprint is desired and/or it is desired to optimize use of network bandwidth. In one arrangement, the structure described herein can be implemented using IBM® Bluemix™ which is a cloud platform as a service (PaaS) supporting several programming languages and services.
The virtual sensor 130 can subscribe to the sensor data 172, 274 derived from sensor data 162, 164 generated by the sensors 112, 114, as previously described. In this example, the virtual sensor 130 can be configured to parse different groups or types of sensor data contained in the sensor data 162, for example into sensor data group N and sensor data group M. The virtual sensor 130 also can be configured to parse different groups or types of sensor data contained in the sensor data 164, for example into sensor data group O and sensor data group P. Further, the virtual sensor 130 can be configured to merge sensor data from the different published sensor data 172, 274. For example, the virtual sensor 130 can merge sensor data group N with the sensor data group O, and publish the merged sensor data as published sensor data (e.g., virtual sensor data) 280. Thus. the published sensor data 280 can appear to the virtual sensor data broker 140 to be sensor data generated by, or derived from, a single sensor, even though it can be derived from sensor data 162, 164 generated by a plurality of sensors 112, 114.
In one arrangement, the virtual sensor 130 can normalize and/or interpolate groups of sensor data to publish the sensor data 280. For example, the virtual sensor 130 can normalize and/or interpolate sensor data group N with the sensor data group O. By way of illustration, the sensor data group N can include sensor data pertaining to a coefficient of friction on a first portion of a road (e.g., due to rain, sleet, snow, etc.), and the sensor data group O can include sensor data pertaining to a coefficient of friction on a second particular portion of the road. The virtual sensor 130 can normalize and/or interpolate the sensor data groups N, 0 to estimate a coefficient of friction on a third portion of a road located between the first and second portions.
The virtual sensor data broker 140 can subscribe to the published sensor data 280, and re-publish that sensor data 280 as published sensor data 290. The applications 150, 152 can subscribe to the published sensor data 290. Notably, the published sensor data 290 can appear to the applications 150, 152 to be sensor data generated by, or derived from, a single sensor, even though that not might be the case.
The entity managing/controlling the virtual sensor 130 can charge the entity managing/controlling the virtual sensor data broker 140 for the merged sensor data 280. Continuing with the previous example pertaining to road conditions, the applications 150, 152 can be mobile applications installed on a user's mobile device (e.g., a smart phone or tablet computer) or applications installed on a processing system in a user's vehicle. The applications 150, 152 can process the published sensor data 290 to alert users of potentially hazardous road conditions. In this example, the sensors 112, 114 can be sensors installed on other vehicles that communicate the sensor data 162, 164 to the sensor data broker 120. Owners of such vehicles can be provided compensation for sharing their sensor data. For instance, such owners can share their sensor data 162, 164 in exchange for receiving published sensor data 290 generated based, at least in part, on sensor data shared by other vehicles.
The system 200 also can support the use of ad hoc sensor data. For example, one or more of the sensors 112, 114 can be mobile devices (e.g., smart phones, tablet computers, automotive systems, or the like), and users of the mobile devices can elect to publish their sensor data 162, 164. The sensor data broker 120 can include that sensor data 162, 164 in the published sensor data 172, 274. The virtual sensors can filter the published sensor data 172, 274 to select from among the published sensor data 172, 174 the sensor data to be included in the published sensor data 280.
In illustration, each of the sensor data 162, 164 can include location data generated by a respective mobile device, for example a global positional system (GPS) receiver. Each of the sensor data 162, 164 also can include ambient environment information, such as temperature, humidity, or the like. Assume a particular business entity desires to monitor the temperature and humidity in different areas of their establishment. The virtual sensor 130 can be configured to do so. For example, the virtual sensor 130 can process the location data contained in the published sensor data 172, 174 to filter the published sensor data 172, 174 and include in the published sensor data 280 only published sensor data 172, 174 derived from mobile devices presently located within the establishment. In such case, the published sensor data 280 can include, for each mobile device located in the establishment, the location of the mobile device, and the temperature and humidity detected by the mobile device at that location.
In operation, sensor data generated by the sensors 110-114 can be communicated, via the router(s) 350, to both the sensor data broker 120 and the sensor data broker 322. Further, each of the sensor data brokers 120, 322 each can store shared runtime information 360 to be shared among the sensor data brokers 120, 322 to a computer-readable storage medium that is communicatively linked to each of the sensor data brokers 120, 322, for example via a suitable communication network. The shared runtime information 360 can indicate various infrastructure 380 components (e.g., virtual sensors) receiving published sensor data from the sensor data broker 120 and/or the sensor data broker 322, various information related sensor data utilization by the infrastructure 380 components, subscription topics, authentication information, etc.
The sensor data broker 120 can periodically communicate a signal (e.g., a heartbeat message 370) to the sensor data broker 322, for example every second, five seconds, ten seconds, thirty seconds, or the like. The heartbeat message 370 can indicate that the sensor data broker 120 is operating normally, for example as previously described. Responsive to the sensor data broker 322 not detecting the heartbeat message 370, or the heartbeat message 370 indicating that a fault or error has occurred in the sensor data broker 120, the sensor data broker 322 can, in real time, assume the role of brokering sensor data previously performed by the sensor data broker 120. When assuming such role, the sensor data broker 322 can access the shared runtime information 360 and begin publishing sensor data received from the sensors 110-114 on behalf of the sensor data broker 120. Further, the sensor data broker 322 can communicate with the router(s) 352 to update their DNS records to re-direct communications to/from the virtual sensors to/from the sensor data broker 322. The sensor data broker 322 also can monitor access to the published sensor data by the infrastructure 380 components and store corresponding information to the shared runtime information 360. Accordingly, the sensor data broker 322 can seamlessly take over publishing sensor data on behalf of the sensor data broker 322, thus providing a high level of availability of the sensor information. From the perspective of the virtual sensors, the virtual sensors can have continued access to the published sensor data, and the virtual sensors need not even be made aware that an issue with the sensor data broker 120 has occurred.
Responsive to the sensor data broker 120 recovering from the error, the sensor data broker 120 can, in real time, begin communicating to the sensor data broker 322 heartbeat messages 370 indicating that the sensor data broker 120 is ready to assume its role in publishing sensor data. The sensor data broker 120 also can communicate with the router(s) 352 to update their DNS records to re-direct communications to/from the virtual sensors to/from the sensor data broker 120 and access the shared runtime information 360 to resume its sensor data publishing role. Responsive to the heartbeat message 370 indicating that the sensor data broker 120 has resumed that role, the sensor data broker 322 can enter a standby state and continue monitoring the heartbeat messages 370 for one or more further fault conditions.
Failover of virtual sensor data brokers can be implemented in a manner similar to that described above. In such an arrangement, the DNS record changes to the router(s) 352 can be implemented to identify a failover virtual sensor data broker to both virtual sensors and the applications 150, 152 in place of a primary virtual sensor data broker. Thus, the failover virtual sensor data broker can access published sensor data from the virtual sensors in place of the primary virtual sensor data broker, and the applications 150, 152 can access published sensor data from the failover virtual sensor data broker in place of the primary virtual sensor data broker. Nonetheless, from the perspective of the virtual sensors and the applications 150, 152, the virtual sensors continue publishing the sensor data and the applications 150, 152 can continue accessing the published sensor data, without need to be made aware that an issue with the primary virtual sensor data broker has occurred. When the primary virtual sensor data has recovered from the error, it can again assume the role of receiving sensor data from the virtual sensors and publishing the sensor data to the applications 150, 152.
The sensor 410 can be configured to detect values or changes in physical quantities that are the same as, or similar to, values or changes in physical quantities detected by the sensor 110, and generate corresponding sensor data 460. The sensor data broker 120 can be configured to receive the sensor data 160 and the sensor data 460. For example, by virtue of subscribing to the sensor data 160, a processing system managing and/or controlling the sensors 110, 410 can automatically subscribe the sensor data broker 120 to the sensor data 460.
In operation, the sensor 110 can communicate to the sensor data broker 120 the sensor data 160, which can publish the sensor data 160 as published sensor data 170. Further, the sensor 110 can periodically communicate a signal (e.g., a heartbeat message 470) to the sensor 410, for example every second, five seconds, ten seconds, thirty seconds, or the like. The heartbeat message 470 can indicate that the sensor 110 is operating normally, for example as previously described. Responsive to the sensor 410 not detecting the heartbeat message 470, or the heartbeat message 470 indicating that an error has occurred in the sensor 110, the sensor 410 can determine a fault condition for the sensor 110. Responsive to detecting the fault condition, the sensor 410 can, in real time, begin communicating to the sensor data broker 120 sensor data 460.
The sensor data 460 can be formatted in the same manner as the sensor data 160. Thus, the sensor data broker 120 need not be aware that the sensor data 460 is generated by a different sensor than the sensor data 160. Indeed, the sensor data 460 can represent values or changes in physical quantities that are the same as, or similar to, those represented by the sensor data 160. The sensor data broker 120 can receive the sensor data 460 and publish the sensor data 460 as the published sensor data 170. Nonetheless, the sensor data broker 120 can continue publishing the published sensor data 170 without interruption.
Responsive to the sensor 110 recovering from the error, the sensor 110 can, in real time, begin communicating to the sensor 410 heartbeat messages 470 indicating that the sensor 110 has recovered from the error, and the sensor 410 can again communicate to the sensor data broker 120 the sensor data 160. Responsive to receiving a heartbeat message 470 indicating the sensor has recovered from the error, the sensor 410 can stop communicating the sensor data 460.
In another arrangement, both the sensors 110, 410 can be configured to communicate the sensor data 160, 460, respectively, to the sensor data broker 120 during normal operation, and the sensor data broker 120 can subscribe to each of the sensor data 160, 460. The sensor data broker 120 can normally publish the sensor data 160 as the published sensor data 170. Responsive to the sensor data broker 120 failing to receive the sensor data 160 in a normal manner, for example due to the sensor 110 stopping communication of the sensor data 160 or a communication link between the sensor 110 and the sensor data broker 120 being lost, the sensor data broker 120 can automatically, in real time, begin publishing the sensor data 460 as the published sensor data 170. In such an arrangement, the heartbeat message 470 between the sensors 110, 410 would not be needed.
The sensor data broker 120 can be configured to receive the sensor data 160 from the sensor 110 and publish that sensor data as the published sensor data 170. In one arrangement, the sensor data broker 120 also can be configured to receive the sensor data 560 from the sensor 510 and publish that sensor data as the published sensor data 570. In another arrangement, a different sensor data broker can be configured to receive the sensor data 560 from the sensor 510 and publish that sensor data as the published sensor data 570.
The virtual sensor 130 can subscribe to the published sensor data 170 and the published sensor data 570. The virtual sensor 130 can receive the published sensor data 170 and re-publish the sensor data 170 as published sensor data 180. As noted, when re-publishing the sensor data 170, the virtual sensor 130 can process and/or manipulate the sensor data, for example to convert the sensor data from one format to another, combine sensor data, normalize sensor data, interpolate sensor data, etc.
Responsive to the virtual sensor 130 failing to receive the published sensor data 170 in a normal manner, the virtual sensor 130 can automatically begin publishing the sensor data 570 as the published sensor data 180. The virtual sensor 130 can fail to receive the published sensor data 170, for example, due to communication of the sensor data 160 to the sensor data broker 120 being lost or, in the case the virtual sensor 130 receives the published sensor data 570 from another sensor data broker, responsive to a communication link between the virtual sensor 130 and the sensor data broker 120 being lost.
Again, when re-publishing the sensor data 570, the virtual sensor 130 can process and/or manipulate the published sensor data 570, for example to convert the sensor data from one format to another, combine sensor data, normalize sensor data, interpolate sensor data, etc. In an arrangement in which the sensor 510 generates sensor data 560 that, although being similar to the sensor data 160, is not precisely the same as the sensor data 160, such processing and/or manipulation of the published sensor data 570 can include approximating the published sensor data 170 by normalizing and/or interpolating the published sensor data 570 so that the published sensor data 180 generated based on the published sensor data 570 is a close approximation to the published sensor data 180 generated based on the published sensor data 170. For example, if the sensor 110 measures a particular physical quantity, and the sensor 510 measures the same physical quantity, but is performing its measurement from a different location, and the sensor 510 generally produces sensor data 560 that is ten percent lower in value than the sensor data 160, the virtual sensor can scale the sensor data 560 up by a compensating factor. In illustration, if a particular data parameter indicates a value of nine, that value can be scaled up to have a value of ten. In another arrangement, if the sensor 110 is located between the sensor 510 and another sensor, the published sensor data 570 and sensor data generated by the other sensor can be interpolated so that the published sensor data 180 is a close approximation to the published sensor data 180 generated based on the sensor data 170.
In this example, the sensor data broker 120 can receive sensor data 160, 162 generated by the sensors 110, 112 and publish the sensor data as published sensor data 670, 672. Optionally, the sensor data broker 120 can parse one or more data groups from the sensor data 160, 162 to include in the published sensor data 670, 672, though the present arrangements are not limited in this regard. The virtual sensor 130 can subscribe to the published sensor data 670, 672 and, responsive to receiving the published sensor data 670, 672, publish sensor data (e.g., virtual sensor data) 680 derived from the published sensor data 670, 672. The published sensor data 680 can include one or more sensor data groups contained in the published sensor data 670, 672, for example data group X and data group N. A virtual sensor data broker 620 can subscribe to the published sensor data 680, for example as previously described, and re-publish that sensor data as published sensor data (e.g., virtual sensor data) 690. In addition to, or in lieu of, one or more applications subscribing to the published sensor data 690, the virtual sensor 630 can subscribe to the published sensor data 690 and re-publish that sensor data as published sensor data (e.g., virtual sensor data) 695. One or more applications (not shown), can subscribe to the published sensor data 695.
In illustration, assume that a first entity has developed the virtual sensor 130. Also assume that a second entity that provides published sensor data from their own virtual sensors needs to publish the same sensor data 680 published by the virtual sensor 130. Rather than having to develop the same virtual sensor that the first entity has already developed, the second entity can configure their virtual sensor 630 to subscribe to the published sensor data 690, which corresponds to the published sensor data 680 published by the virtual sensor 130. This can benefit both entities; the first entity can receive a subscription fee from the second entity, and the second entity need not invest in certain development costs.
By way of a specific example, the virtual sensor 130 can be owned by company X and the virtual sensor 630 can be owned by company Y. The sensor data 680 can represent road traction conditions, and can include sensor data generated by sensors from a set of vehicles O traveling on a particular road. The virtual sensor 630 can provide the sensor data 695 to other vehicles P travelling behind the vehicles O on that same road. In this scenario, the virtual sensor 630 can select the sensor data 690 based on the present locations of the vehicles P, for instance as indicated by corresponding GPS data, and the locations of vehicles O that generated the sensor data 160, 162. In this regard, the sensor data 680 can include corresponding location data. Further, the virtual sensor 630 can be configured to subscribe to sensor data 690 pertaining to a particular make and model of a vehicle O. The virtual sensor 630 can normalize the sensor data 690 for vehicles P that are particular make and model.
In this example, the virtual sensor 130 can aggregate sensor data across multiple virtual sensors that publish sensor data pertaining to different vehicle makes and models, but the virtual sensor 630 can subscribe to sensor data 690 generated by vehicles that are of a certain make and model. Another virtual sensor (not shown), for example a virtual sensor within a particular vehicle P), can process the sensor data received from the virtual sensor 630 to determine traction conditions of the road. Further, the virtual sensor can normalize the sensor data 695, along with sensor data generated by that vehicle pertaining to tire wear, traction data, speed, and the like, to determine an impact the road conditions will have on that particular vehicle P. Based on such determination, the vehicle P can present an alert to a driver of the vehicle indicating the road conditions and the impact of the conditions on the vehicle, and may suggest to the driver to slow down.
In another arrangement, the virtual the virtual sensor 630 or another virtual sensor (not shown) can aggregate sensor data received from multiple virtual sensors that publish sensor data pertaining to different vehicle makes and models, and transform the virtual sensors data so that it can be used by a different vehicle make and model. For example, the transformation can be performed by a virtual sensor that understands received sensor data pertaining to the specific make and model.
At step 815, at least a first sensor data use parameter can be generated by a processor. The first sensor data use parameter can indicate the utilization of the virtual sensor data by the at least one application. At step 820, at least a second sensor data use parameter can be generated. The second sensor data use parameter can indicate the utilization of the sensor data by the at least one virtual sensor.
At step 825, a fee to be charged for use of the virtual sensor data by the at least one application can be determined. The fee can be determined based on the first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application. At step 830, a fee to be charged for use of the sensor data by the at least one virtual sensor can be determined. The fee can be determined based on the second sensor data use parameter indicating the utilization of the sensor data by the at least one virtual sensor.
At step 835, a compensation to be provided to an entity managing or controlling the at least one virtual sensor can be determined. The compensation can be determined based on the first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application. At step 840, a compensation to be provided to an entity managing or controlling the at least one sensor can be determined. The compensation can be based on the first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application and/or the second sensor data use parameter indicating the utilization of the sensor data by the at least one virtual sensor. At step 845, a compensation to be provided to an entity managing or controlling a sensor data communication system can be determined. The compensation can be determined based on the first sensor data use parameter indicating the utilization of the virtual sensor data by the at least one application and/or the second sensor data use parameter indicating the utilization of the sensor data by the at least one virtual sensor. The data communication system can provide a sensor data management infrastructure for managing the sharing of sensor data and virtual sensor data.
The data processing system 900 can include at least one processor 905 (e.g., a central processing unit) coupled to memory elements 910 through a system bus 915 or other suitable circuitry. As such, the data processing system 900 can store program code within the memory elements 910. The processor 905 can execute the program code accessed from the memory elements 910 via the system bus 915. It should be appreciated that the data processing system 900 can be implemented in the form of any system including a processor and memory that is capable of performing the functions and/or operations described within this specification. For example, the processing system 700 can be implemented as a server, a plurality of communicatively linked servers, or the like.
The memory elements 910 can include one or more physical memory devices such as, for example, local memory 920 and one or more bulk storage devices 925. Local memory 920 refers to random access memory (RAM) or other non-persistent memory device(s) generally used during actual execution of the program code. The bulk storage device(s) 925 can be implemented as a hard disk drive (HDD), solid state drive (SSD), or other persistent data storage device. The data processing system 900 also can include one or more cache memories (not shown) that provide temporary storage of at least some program code in order to reduce the number of times program code must be retrieved from the bulk storage device 925 during execution.
One or more network adapters 930 can be coupled to data processing system 900, for example via the system bus 915, to enable the data processing system 900 to become coupled to other systems, computer systems, and/or remote storage devices through intervening private or public networks. Modems, cable modems, transceivers, and Ethernet cards are examples of different types of network adapters 930 that can be used with the data processing system 900.
As pictured in
While the disclosure concludes with claims defining novel features, it is believed that the various features described herein will be better understood from a consideration of the description in conjunction with the drawings. The process(es), machine(s), manufacture(s) and any variations thereof described within this disclosure are provided for purposes of illustration. Any specific structural and functional details described are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the features described in virtually any appropriately detailed structure. Further, the terms and phrases used within this disclosure are not intended to be limiting, but rather to provide an understandable description of the features described.
For purposes of simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numbers are repeated among the figures to indicate corresponding, analogous, or like features.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this disclosure, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Reference throughout this disclosure to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment described within this disclosure. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this disclosure may, but do not necessarily, all refer to the same embodiment.
The term “plurality,” as used herein, is defined as two or more than two. The term “another,” as used herein, is defined as at least a second or more. The term “coupled,” as used herein, is defined as connected, whether directly without any intervening elements or indirectly with one or more intervening elements, unless otherwise indicated. Two elements also can be coupled mechanically, electrically, or communicatively linked through a communication channel, pathway, network, or system. The term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms, as these terms are only used to distinguish one element from another unless stated otherwise or the context indicates otherwise.
The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6772099 | Merkin | Aug 2004 | B2 |
| 6904391 | Merkin et al. | Jun 2005 | B2 |
| 7787969 | Grichnik et al. | Aug 2010 | B2 |
| 7830805 | Cohen et al. | Nov 2010 | B2 |
| 9080438 | McCoy | Jul 2015 | B1 |
| 20030088524 | Bibelhausen | May 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20050154598 | Kanayama | Jul 2005 | A1 |
| 20050228627 | Bellantoni et al. | Oct 2005 | A1 |
| 20070002576 | Lee | Jan 2007 | A1 |
| 20070087756 | Hoffberg | Apr 2007 | A1 |
| 20080175356 | Seidberg | Jul 2008 | A1 |
| 20080253284 | Montalvo | Oct 2008 | A1 |
| 20080298248 | Roeck | Dec 2008 | A1 |
| 20080316938 | Shi | Dec 2008 | A1 |
| 20090019486 | Kalaboukis | Jan 2009 | A1 |
| 20090076887 | Spivack | Mar 2009 | A1 |
| 20100015926 | Luff | Jan 2010 | A1 |
| 20100332304 | Higgins | Dec 2010 | A1 |
| 20110276951 | Jain | Nov 2011 | A1 |
| 20110295999 | Ferris | Dec 2011 | A1 |
| 20120011036 | Burton | Jan 2012 | A1 |
| 20120020218 | Li | Jan 2012 | A1 |
| 20120022700 | Drees et al. | Jan 2012 | A1 |
| 20120106391 | van Loon | May 2012 | A1 |
| 20120137003 | Ferris | May 2012 | A1 |
| 20120226808 | Morgan | Sep 2012 | A1 |
| 20120284713 | Ostermeyer et al. | Nov 2012 | A1 |
| 20130054688 | Rourke | Feb 2013 | A1 |
| 20130073261 | Kim et al. | Mar 2013 | A1 |
| 20130110675 | Bouw | May 2013 | A1 |
| 20130223222 | Kotecha | Aug 2013 | A1 |
| 20130227569 | Kohli | Aug 2013 | A1 |
| 20130275059 | Bernhard et al. | Oct 2013 | A1 |
| 20140024336 | Tavares | Jan 2014 | A1 |
| 20140025337 | Blount | Jan 2014 | A1 |
| 20140025338 | Blount | Jan 2014 | A1 |
| 20140075043 | Gerecke | Mar 2014 | A1 |
| 20140101332 | Lipman | Apr 2014 | A1 |
| 20140156467 | Typaldos | Jun 2014 | A1 |
| 20140214726 | Minato | Jul 2014 | A1 |
| 20140218355 | Wilkins | Aug 2014 | A1 |
| 20150006258 | Salama | Jan 2015 | A1 |
| 20150109128 | Fadell | Apr 2015 | A1 |
| 20150127565 | Chevalier | May 2015 | A1 |
| 20150156031 | Fadell | Jun 2015 | A1 |
| 20150207809 | Macaulay | Jul 2015 | A1 |
| 20150227890 | Bednarek | Aug 2015 | A1 |
| 20150294431 | Fiorucci | Oct 2015 | A1 |
| 20150373482 | Barnard | Dec 2015 | A1 |
| 20150373493 | Chowdhury | Dec 2015 | A1 |
| 20160037438 | Manroa | Feb 2016 | A1 |
| 20160072877 | Hirschfeld et al. | Mar 2016 | A1 |
| 20160072891 | Joshi | Mar 2016 | A1 |
| 20160105644 | Smith | Apr 2016 | A1 |
| 20160119262 | Siegel | Apr 2016 | A1 |
| 20160217662 | Kashar | Jul 2016 | A1 |
| 20170078922 | Raleigh et al. | Mar 2017 | A1 |
| 20170160110 | Basu et al. | Jun 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2523112 | Nov 2012 | EP |
| Entry |
|---|
| “MQTT v3.1.1 now an OASIS Standard,” [online] MQTT.org, News, Nov. 7, 2014 [retrieved Nov. 2, 2015] retrieved rom the Internet: <http://mqtt.org/> 2 pg. |
| “Virtual Sensors,” [online] IntelliDynamics © 2015 [retrieved Sep. 22, 2015], retrieved from the Internet: <http://www.intellidynamics.net/content/technologies/virtual-sensors.html>, 4 pg. |
| Steele, J., “Understanding Virtual Sensors: From Sensor Fusion to Context-Aware Applications,” [online] Electronic Design.com, Jul. 10, 2012 [retrieved Dec. 4, 2015], retrieved from the Internet: <http://electronicdesign.com/ios/understanding-virtual-sensors-sensor-fusion-context-aware-applications>, 4 pg. |
| IBM Appendix, List of IBM Patents or Patent Applications Treated as Related, 2 pg. |
| Number | Date | Country | |
|---|---|---|---|
| 20170163734 A1 | Jun 2017 | US |
