Method of and system for managing data in a sensor network

• US 20070265866A1
• Filed: 05/12/2006
• Published: 11/15/2007
• Est. Priority Date: 05/12/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Fehling, Ronny, Biswas, Prabuddha
• Granted Patent: US 7,479,875 B2
• Time in Patent Office: Days
• US Class Current: 340/506
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• 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
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

The present invention relates to a method of and system for managing sensor data in a computer database environment. An exemplary method of the invention is described, comprising the steps of: defining a Sensor Network environment in terms of zones, each zone being defined by its entrance or exit condition, and having a distinct and consistent property associated with it; collecting sensor data regarding the state of objects within the Sensor Network environment; analyzing the collected sensor data in the context of said Sensor Network environment and the zones; and storing the analyzed sensor data as records in a database, in an application agnostic form, and in terms of the zones. A corresponding system is also described.

Claims

1. A method of managing sensor data comprising the steps of:

defining a Sensor Network environment in terms of zones, each said zone being defined by its entrance or exit condition, and having a distinct and consistent property associated with it;

collecting sensor data regarding the state of objects within said Sensor Network environment;

analyzing said collected sensor data in the context of said Sensor Network environment and said zones; and

storing said analyzed sensor data as records in a database, in an application agnostic form, and in terms of said zones.

2. The method of claim 1, wherein said step of defining a Sensor Network environment comprises the step of:

defining the state of an object in a given zone to be responsive to a sensor reading reaching a predetermined value.

3. The method of claim 1, wherein said step of defining a Sensor Network environment comprises the step of:

defining the state of an object in a given zone to be responsive to a logical process definition being satisfied.

4. The method of claim 1, wherein said step of defining a Sensor Network environment comprises the step of:

defining the state of an object in a given zone to be responsive to the requirements of a time-based restriction being satisfied.

5. The method of claim 1, wherein said step of collecting sensor data further comprises the step of:

collecting sensor data representing the state of environmental conditions within said Sensor Network environment.

6. The method of claim 1, wherein said step of defining a Sensor Network environment comprises the steps of:

identifying, defining and configuring said zones; and

setting values for parameters of each of said zones.

7. The method of claim 6, wherein said step of defining a Sensor Network environment comprises the steps of:

identifying, defining and configuring said sensors associated with said zones; and

setting values for parameters of each of said sensors.

8. The method of claim 7 wherein at least one of said zones is selected from the group consisting of:

Physical Sensor Zones (PSZs) defined by one or more physical sensors;

spatio-temporal Sensor Coverage Zones (SCZs); and

Logical Zones (LZs) defined at least in part by abstract constraints.

9. The method of claim 8 wherein at least one of said Physical Sensor Zones (PSZ) is defined by a Zone Sensor.

10. The method of claim 8 wherein at least one of said Physical Sensor Zones (PSZ) is defined as a Gate Sensor between two Zones.

11. The method of claim 8 wherein at least one of said Logical Zones (LZ) represents a conglomerate of Sensors and PSZ and SCZ together with abstract constraints.

12. The method of claim 8 wherein at least one of said Logical Zones (LZ) incorporates additional context to determine whether one of said objects is inside or outside said LZ.

13. The method of claim 8 wherein at least one of said Logical Zones (LZ) is defined through access privileges of a user or software application.

14. The method of claim 8, wherein at least one of said SCZs comprises one or more of:

the temporal location of a sensor, its quality of measurement, the area in which its measurements are valid and the quality change coefficient which describes the change of quality with increasing distance or time.

15. The method of claim 7 wherein the step of defining said zone comprises the step of launching a software wizard.

16. The method of claim 7 wherein said step of analyzing said stored sensor data includes the step of determining zone transitions for objects.

17. The method of claim 16, wherein each said zone is defined in terms of a zone transition model defining constraints on said zones, defining allowable movements of objects through said zones.

18. The method of claim 16, wherein said zone transitions are context-based, defining object movements based on the context that they are in, changing path in response to a change in environmental conditions, or a business process outcome could be the trigger for a zone transition.

19. The method of claim 7, further comprising the step of notifying a software application of a state change for a zone.

20. The method of claim 19, wherein said step of notifying comprises the step of notifying a software application of a state change for a zone in response to said software application subscribing to notification of said state change for said zone.

21. The method of claim 7, wherein said zones may be defined under parent, child or sibling relationships, whereby properties and constraints may be held in common.

22. The method of claim 21, wherein each said zone is defined in terms of:

location,

containment,

inheritance,

coverage,

connectivity and

constraints of sensors.

23. The method of claim 1, wherein said step of designing includes the step of assigning properties and metadata for sensors within said Sensor Network environment.

24. The method of claim 1 wherein said step of analyzing comprises the step of determining the direction of motion for an object by considering relative times of sensor states, locations and whether sensors are gate or zone sensor types which have detected said object.

25. The method of claim 1 wherein said step of analyzing includes the step of responding to an exception by issuing an automatic email, voice alert or webpage display to an End User.

26. The method of claim 1 wherein said step of designing a Sensor Network environment configuration comprises the step of defining the operational and business process rules that apply to said Sensor Network environment.

27. The method of claim 26, wherein said operational and business process rules are defined through layers, whereby said system can be easily customized for each operational environment.

28. The method of claim 1, wherein at least one of said zones has a temporal construct that varies over time.

29. The method of claim 28, wherein at least one of said zones is defined to have a validity time, defined through a start and end time of its construct.

30. The method of claim 1, further comprising the step of defining rules or actions based on zone events rather than on sensor observations.

31. A system for managing sensor data comprising:

a plurality of sensors for detecting environment conditions including the presence of objects;

a Sensor management engine; and

a database;

said Sensor management engine being operable to;

define a Sensor Network environment in terms of zones, each said zone being defined by its entrance or exit condition, and having a distinct and consistent property associated with it;

collect data from said sensors regarding the state of objects within said Sensor Network environment;

analyze said collected sensor data in the context of said Sensor Network environment and said zones; and

store said analyzed sensor data as records in a database, in an application agnostic form, and in terms of said zones.