Patent Application
20090222541
The invention relates generally to sensor networks. More particularly, the invention relates to a dynamic sensor network resolution and management service.
Advancements in computing technology have led to the production of sensors capable of observing and reporting various real-world phenomena in a time-sensitive manner. Additionally, the growth in distributed communication technology (e.g., the Internet) has led to the development of sensor networks. Sensor networks are used in numerous applications, including military, industrial and civilian applications. Generally, sensors are adapted to detect or monitor certain events or conditions. A sensor may be simple, such as a device that monitors temperature, or more complex, such as a video camera. Data generated at the sensor is transmitted in data packets over a sensor network to one or more application nodes. An application node includes one or more application software instantiations that can react to the sensor data, and may include a user interface that presents the sensor data in numerical, textual and graphical forms to users.
Sensors have been used for industrial applications and commercial applications in the past. More recently, sensors have been used for homeland security and public safety applications. Sensors are transitioning from “wired-based” or “circuit-based” implementations to packet-based networks over shared infrastructure and wireless communication networks. Examples of applications for wireless sensor networks include surveillance, inventory tracking, environmental monitoring, acoustic detection and optical detection. Wireless sensor networks are often suitable for harsh environments and wide geographical areas where unattended operation of sensors is desirable.
The ability to manage a sensor network is increasingly difficult as the number of sensors deployed increases. Moreover, sensors can be of a variety of types and can be distributed over a wide geographical area. Mobile sensors make the task more difficult as the location of mobile sensors within the network changes over time. Conventionally, application nodes communicate directly to sensors or sensor gateways. The sensor gateways do not maintain a local list of it sensors. Instead, each application maintains a statically defined list of sensors with which the application can communicate. Generally, the ability of an application to interact with other sensors is limited without knowledge of their physical addresses or the associated network access devices. Moreover, the introduction of new sensors to the network typically requires a manual reconfiguration to permit the application to communicate with such sensors.
What is needed is a means to scale, manage, access and track sensors of various types that are geographically distributed and connected to a network through various network access mechanisms. The present invention satisfies this need and provides additional advantages.
In one aspect, the invention features a method for registering a sensor in a sensor network. A sensor is detected in communication with a network access node. Information is received from the network access node indicating a sensor type for the sensor and a number of sensors of the sensor type that communicate with the network access node. A unique registry name is automatically assigned to the sensor based on a name of the network access node, the sensor type and the number of sensors of the sensor type.
In another aspect, the invention features a method for querying sensors in a sensor network. A query for sensor data is received from an application. The query includes an application label having a context for at least one application having access to the sensor network. A network address is determined for each of a plurality of sensors associated with the application label. Sensor data are provided to the application from each of the sensors associated with the application label.
In still another aspect, the invention features a sensor registry system for management of a sensor network. The sensor registry includes a registry module configured to receive sensor information transmitted from a sensor gateway through the sensor network and to automatically generate a unique sensor name in response to the sensor information. The sensor information includes a sensor type and a network address for the sensor gateway. The sensor registry also includes a database in communication with the registry module. The database is configured to store the sensor type, the network address for the sensor gateway and sensor data most recently transmitted from the sensor gateway.
The above and further advantages of this invention may be better understood by referring to the following description in conjunction with the accompanying drawings, in which like numerals indicate like structural elements and features in the various figures. For clarity, not every element may be labeled in every figure. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.
In brief overview, the invention relates to a scalable network architecture adapted to interface with various sensor types and sensor access mechanisms while providing real-time access to sensor data for distributed applications and organizations. A centralized sensor network service manages the registration, capabilities and near real-time status (i.e., “heartbeat) of the sensors, and current network connections for the sensors. New sensors are discovered automatically through messaging between network access nodes and the sensor registry. The registry service automatically assigns new unique names to the new sensors. It is possible for multiple islands of sensor registries to be shared through an authentication, authorization and accounting (AAA) service. The registry service can be made available to distributed sensor applications and sensor middleware used to support distributed applications. In addition, the registry service facilitates the sharing of sensors across organizations.
Advantageously, the sensor registry is automatically updated by network software. Thus, unlike IP address registration in domain name service (DNS) processes, the sensor registry service does not require manual configuration or reconfiguration each time a sensor is added to or relocated within the network. AAA policies can be implemented to ensure that only authorized applications can query the registry and view authorized portions of the registry. The registry can be implemented for multi-vendor sensor networks and can accommodate multiple addressing schemes.
The illustrated network configuration 10 includes two local sensor networks 30. One local sensor network (Billerica) 30′ includes three stationary sensors S1, S2 and S3, and a dynamic (i.e., mobile) sensor D1 which is not restricted for use with a single network edge device. The second local sensor network (Bedford) 30″ includes two stationary sensors S4 and S5. The sensors S1 to S5 (generally S) can be of a variety of types. Generally, each type corresponds to a physical or environmental measurement parameter, such as temperature, sound, vibration, acceleration and pressure.
The sensor registry of the invention is instantiated at the command module 14 which includes processing and database components as described in more detail below. Although the sensor registry is “centralized” at the command module 14, the registry is implemented and maintained in a distributed manner. More specifically, the network access nodes 18 and aggregation node 16 update and maintain the dynamic components of the sensor registry. In one embodiment, the sensor registry determines that the information for one or more sensors S is no longer useful, or “stale.” The determination may be made upon the expiration of a programmable update time. To retrieve updated information, the command module 14 queries the network access nodes 18 for fresh information.
As new sensors are added to the network 10, messaging between the network access nodes 18 and the sensor registry allows for their discovery. The discovery of a new sensor occurs when the sensor starts sending data back to the aggregation point. Mechanisms defined in standards, such as IEEE 1451, can be used to gather further details about the sensor type and configuration and a new name is generated for the new sensor. Advantageously, the messaging avoids any need to modify legacy sensors and sensor gateways 26, as the network access nodes 18 act as proxies.
In some network configurations, one or more dynamic sensors change their location over time.
Sensors names generated for static sensors are based on the type, or “capability”, of the sensor and its network edge device. In one embodiment, static sensor names are of the form
<network edge device>:capability:index
where “capability” represents the type of device measurement, such as temperature, sound, vibration, acceleration or pressure, and where index indicates a specific one of similar capability sensors at the same network edge device. Index values are maintained at the edge device.
A dynamic sensor has no “permanent” network edge device therefore the generation of dynamic sensor names is different than for static sensors. In one embodiment, dynamic sensor names are of the form
<mobile>: capability:index
where the index values are maintained at the command module and each index value indicates a specific one of similar capability dynamic sensors.
According to the above naming procedure and with reference to
The dynamic sensor D1 which is not constrained to a single network edge device 26 is named
In normal IP network addressing, having a name for a device on a network is not sufficient to send data to that device. Generally, a DNS server is required to resolve an IP address associated with the device name. Although the method of the invention provides a similar service by resolving the sensor name with an IP address, substantially more functionality is provided by the sensor registry service. Sensors are typically not addressed using IP addresses. Instead, a flexible address translation function associates sensor names (or application labels, as described below) and the respective IP addresses. Instead of a single IP address, the sensor registry provides the addressing path for communicating with the sensor which may include, for example, the IP network access node, sensor gateway identification (ID), wireless mesh end-device ID, and the analog or digital channel number for the sensor.
The sensor registry optionally provides “protection” of sensors by implementing authentication, authorization and accounting (AAA) policies for applications accessing the registry. An application that only has the name of a sensor cannot gain access to that sensor without contacting the sensor registry. Thus, without knowing the sensor gateway IP address, the application cannot access data from the sensor or execute a denial of service attack on the sensor gateway. Applications with correct authentication are able to query the sensor registry and to view authorized portions of the registry.
In addition to the automatic sensor naming procedure described above, another feature of the sensor registry is application-specific naming of sensors. The sensor registry can label sensors according to application-based contexts which may have specialized meaning to one or more applications. Labels can be based on zone, location, function or capability, sensor vendor and other distinguishing contextual information.
Each application utilizing the sensor registry can add one or more application labels, or “tags”, to sensors or groups of sensors. A sensor may be associated with multiple application labels. An application label can be a shared label available for use by at least two applications. Shared labels are stored in the registry database. Alternatively, an application label can be a private label used only by a single application. Application labels enable easy access to sensor data from multiple sensors. For instance, an application might issue a single request using a label “temp” to retrieve all temperature sensor data or use a request “zone10” to obtain data from all sensors in a 10 mile radius.
Another sensor registry feature is the ability to monitor a sensor status (or “dynamic heartbeat”). Sensor status information can indicate problems due to changes in network topology, the presence of wireless interference, loss of connectivity and the like. Sensor status is determined from direct messaging or inferred by “sniffing” sensor messages that pass through the aggregation node communicating with the sensor registry. When a sensor is present online, data from the aggregation node and timestamps for the data are used to monitor the average and maximum latencies for communicating with each sensor. Examples of sensor status information are “online, 250 ms average latency, 800 ms maximum latency”, “offline, last data received 2 Jan. 2005, 15:43:55 am”, “sleep” and “unreachable, <cause>” where <cause> is a specific description for the inability to communicate with the sensor.
The registry module 34 also communicates with aggregation nodes to receive sensor status information and to enable communication with sensors such as sending sensor commands. Application nodes 46 communicate with the registry module to perform certain functions such as assigning application labels to sensors, defining other applications allowed to share labels, viewing sensor status data, and initiating the sending of commands to sensors.
While the invention has been shown and described with reference to specific embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
This application claims the benefit of the earlier filing date of U.S. Provisional Patent Application Ser. No. 60/734,480, filed Nov. 8, 2005, titled “Dynamic Sensor Network Resolution and Management Service,” the entirety of which is incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/US2006/060560 | 11/6/2006 | WO | 00 | 4/2/2009 |
| Number | Date | Country | |
|---|---|---|---|
| 60734480 | Nov 2005 | US |
