System and method for enabling extensibility in sensing systems

• US 9,104,430 B2
• Filed: 02/11/2008
• Issued: 08/11/2015
• Est. Priority Date: 02/11/2008
• Status: Active Grant

• Current Assignee: Xerox Corporation (Xerox Holdings Corp.)
• Original Assignee: Palo Alto Research Center, Inc. (Xerox Holdings Corp.)
• Inventors: Chu, Maurice K., Liu, Juan
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Aguilera, Todd
• Application Number:
  US12/029,414
• Publication Number:
  US 20090204370A1
• Time in Patent Office: 2,738 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/5066 Algorithms for mapping a plurality of inter-dependent sub-tasks onto a plurality of physical CPUs mappping at compile time, see G06F8/451
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

One embodiment of the present invention provides a method and apparatus for enabling extensibility in sensing systems. The distributed sensing system comprises a number of sensor nodes, a device database, a sensing module registry, a sensing needs monitor, and an automatic composer. The device database is in communication with at least one sensor node and configured to maintain physical information on at least one sensor node. The sensing module registry is configured to maintain a registry of a number of software modules that are available for extracting information from sensor data. The sensing needs monitor is configured to maintain a list of context pairs that represent a number of sensing needs of a sensing application. The automatic composer is configured to generate a composition of software modules, at runtime, to realize the sensing needs of users and applications.

Claims

1. A method for enabling extensibility in a sensing system, the method comprising:

maintaining physical information, by a device database, on at least one deployed sensor node, wherein the physical information describes sensor-specific calibration information;

maintaining a sensing module registry, wherein the sensing module registry includes a number of software modules that are available for extracting information from sensor data received from the at least one deployed sensor node;

maintaining a set of context pairs, wherein a respective context pair represents a sensing need of a user or a sensing application;

in response to state changes within the sensing module registry, generating a directed graph that represents data flow among deployed sensing devices and software modules, wherein the directed graph comprises a plurality of graph nodes that each represents an instance of a software module deployed on a sensor node, and further comprises one or more edges that each connects a first graph node to a second graph node to represent a configured interface of an output from a first software module instance to a second software module instance;

in response to the set of context pairs changing;

determining a set of graph nodes that satisfy a plurality of sensing needs associated with the set of context pairs, wherein a graph node corresponds to a sensor node that satisfies a respective sensing need represented by a context pair; and

generating, based on the set of graph nodes, a composition of software module instances that are each deployed on a corresponding sensor node to extract information from the distributed sensor data, wherein the composition of software module instances satisfies the plurality of sensing needs of the user or the sensing application.

2. The method of claim 1, further comprising detecting at a sensor node one or more of:

a sound signal, motion signal, vibration signal, altitude signal, luminous intensity signal, proximity signal, pressure signal, temperature signal, radiation signal, timing signal, humidity signal, electromagnetic field intensity signal, weight signal, airborne particulates signal, velocity signal, direction signal, and distance signal.

3. The method of claim 1, further comprising reporting, at the automatic composer, when an existing sensor node configuration does not provide sufficient sensor coverage for realizing the sensing requirements of users and applications.

4. The method of claim 1, wherein a respective context pair represents sensing information as a name-location pair of the form:

<

name, location>

;

wherein the “

name”

field indicates a type of data or information on which the sensing information is based; and

wherein the “

location”

field indicates a point or region on which the sensing information is based.

5. The method of claim 1, wherein a respective context pair represents sensing information as a name-spatiotemporal pair of the form:

<

name, location/time>

;

wherein the “

name”

field indicates a type of data or information on which the sensing information is based; and

wherein the “

location/time”

field indicates a point or region, and a time, on which the sensing information is based.

6. The method of claim 1, further comprising interfacing between the sensing needs monitor and a graphical user interface (GUI);

and

wherein the GUI is configured to allow users to insert and delete context pairs.

7. The method of claim 1, wherein generating the composition of software modules comprises:

determining a set of software modules that achieve the sensing needs;

determining, for a respective type of software module, one or more sensor nodes on which to instantiate the respective type of software module;

determining a configuration for a respective instance of a software module; and

deploying the composition of software modules, which involves configuring a respective sensor node to execute one or more software module instances assigned to the sensor node based on the configuration of the software module instances.

8. The method of claim 1, wherein when a sensor node failure is detected, the method further comprises generating a new composition of software modules, at runtime, using only sensor nodes that are available for the new composition.

9. The method of claim 1, wherein the physical information includes lens distortion coefficients, a camera orientation, or a location of a deployed sensor node.

10. The method of claim 1, further comprising deleting a respective node of the directed graph that does not contribute to satisfying a sensing need from the directed graph.

11. A distributed sensing system, comprising:

one or more processors;

a memory;

a set of deployed sensor nodes;

a device database implemented by at least one of the one or more processors configured to maintain physical information in the memory for at least one deployed sensor node;

a sensing module registry implemented by at least one of the one or more processors configured to maintain a registry in the memory of one or more software modules that are available for extracting information from sensor data received from a deployed sensor node;

a sensing needs monitor implemented by at least one of the one or more processors configured to maintain a set of context pairs in the memory, wherein a respective context pair represents a sensing need of a user or a sensing application; and

an automatic composer implemented by at least one of the one or more processors configured to;

in response to state changes within the sensing module registry, generate a directed graph that represents data flow among deployed sensing devices and software modules, wherein the directed graph comprises a plurality of graph nodes that each represents an instance of a software module deployed on a sensor node, and further comprises one or more edges that each connects a first graph node to a second graph node to represent a configured interface of an output from a first software module instance to a second software module instance;

in response to the set of context pairs changing;

determine a set of graph nodes that satisfy a plurality of sensing needs associated with the set of context pairs, wherein a graph node corresponds to a sensor node that satisfies a respective sensing need represented by a context pair; and

generate, based on the set of graph nodes, a composition of software module instances that are each deployed on a corresponding sensor node to extract information from the distributed sensor data, wherein the composition of software module instances satisfies the plurality of sensing needs of the user or the sensing application.

12. The distributed sensing system of claim 11, wherein a respective sensor node comprises one or more sensing devices to detect one or more of:

a sound signal, motion signal, vibration signal, altitude signal, luminous intensity signal, proximity signal, pressure signal, temperature signal, radiation signal, timing signal, humidity signal, electromagnetic field intensity signal, weight signal, airborne particulates signal, velocity signal, direction signal, and distance signal.

13. The distributed sensing system of claim 11, wherein the automatic composer is further configured to report when an existing sensor node configuration does not provide sufficient sensor coverage for realizing the sensing requirements of users and applications.

14. The distributed sensing system of claim 11, wherein a respective context pair represents sensing information as a name-location pair of the form:

<

name, location>

;

wherein the “

name”

field indicates a type of data or information on which the sensing information is based; and

wherein the “

location”

field indicates a point or region on which the sensing information is based.

15. The distributed sensing system of claim 11, wherein a respective context pair represents sensing information as a name-spatiotemporal pair of the form:

<

name, location/time>

;

wherein the “

name”

field indicates a type of data or information on which the sensing information is based; and

wherein the “

location/time”

field indicates a point or region, and a time, on which the sensing information is based.

16. The distributed sensing system of claim 11, wherein the sensing needs monitor is configured to interface with a graphical user interface (GUI);

and

wherein the GUI is configured to allow users to insert and delete context pairs.

17. The distributed sensing system of claim 11, wherein the physical information maintained by the device database describes sensor-specific calibration information, which includes lens distortion coefficients, a camera orientation, or a location of a deployed sensor node.

18. The distributed sensing system of claim 11, wherein the automatic composer is further configured to generate a composition of software modules, at runtime, to realize the plurality of sensing needs of the user or the sensing application by:

determining a set of software modules that achieve the sensing needs;

determining, for a respective type of software module, one or more sensor nodes on which to instantiate the respective type of software module;

determining a configuration for a respective instance of a software module; and

deploying the composition of software modules, which involves configuring a respective sensor node to execute one or more software module instances assigned to the sensor node based on the configuration of the software module instances.

19. The distributed sensing system of claim 11, wherein when a sensor node failure is detected, the automatic composer is configured to generate a new composition of software modules, at runtime, using only sensor nodes that are available for the new composition.

20. The system of claim 11, wherein the automatic composer is further configured to delete a respective node of the directed graph that does not contribute to satisfying a sensing need from the directed graph.