CN101529208B - Methods and systems for providing sensor data using a sensor web - Google Patents

Abstract

A system and method for providing sensor data may comprise receiving a request for sensor data, the request including a triggering parameter. Furthermore, the system and method for providing sensor data may comprise searching for information identifying devices that meet the triggering parameter. Devices are selected from a plurality of item tracking devices, where the plurality of item tracking devices correspond to a plurality of items. Moreover, the system and method for providing sensor data may retrieve the requested sensor data that corresponds to the devices that meet the triggering parameter, and return the requested sensor data.

Description

Method and system for providing sensor data using a sensor network

This application claims priority to US Patent Application 11/453881, filed June 16, 2006, the contents of which are hereby incorporated by reference.

technical field

The present invention generally relates to systems and methods for tracking projects. More specifically, the present invention relates to systems and methods for providing sensor data related to tracked items using context based sensor networks.

Background technique

Asset management has always been an important part of doing business. Tracking assets is important to a variety of organizations, whether it is a company tracking inventory for sale in its stores or a package delivery provider tracking packages being routed through its delivery network. In order to provide quality service, organizations typically build highly organized networks in order to track their assets. Efficient management of such networks allows for reduced costs, reduced delivery times, and improved customer service.

Technological advances have enabled items to be tracked in a variety of ways that far exceed the capabilities of simple checklists. Now, a rich information architecture can be applied to describe the item's interactions with its surroundings, such as transport and custody handovers.

Barcodes are a way for organizations of all kinds to track items. For example, retailers can use barcodes on items in their inventory. For example, items for sale in a retailer's store may each have a different barcode on them. To track inventory, retailers typically scan barcodes on each item. Additionally, when an item is sold to a consumer, the item's barcode is scanned.

Likewise, package delivery providers can take advantage of barcodes by associating them with packages to be delivered to recipients. For example, a package may have a barcode corresponding to a tracking number for the package. Each time a package passes through an inspection point (eg, the courier that originally controlled the package, the package placed in a storage facility, the package delivered to a recipient, etc.), the package's barcode may be scanned. However, barcodes have the disadvantage of having to manually scan the individual barcodes on each item in order to effectively track items.

Radio-frequency identification (RFID) tags are an improvement over typical barcodes. RFID tags do not require the manual scanning required by typical barcodes. For example, in a retail environment, RFID tags on inventory items can communicate with an e-reader that detects the items in a shopping cart and adds the price of each item to the consumer's bill. RFID tags are also used to track items such as livestock, railroad cars, trucks and airline luggage. These tags generally only allow basic tracking and do not provide a way to improve asset management using information about the environment in which the item being tracked is located.

Sensor-based tracking systems are also known that can provide more information than RFID systems. However, such systems are expensive and may provide irrelevant and redundant item information.

Accordingly, it would be desirable to provide a system that reduces the cost of sensor-based tracking and enables sensor data to be shared in order to create a robust information network around the item being tracked.

Contents of the invention

Systems and methods for providing sensor data consistent with embodiments of the invention are disclosed. Systems and methods for providing sensor data may include receiving a request for sensor data, the request including trigger parameters. Additionally, the systems and methods of providing sensor data may include searching for information identifying devices that satisfy the trigger parameters. A device is selected from a plurality of item tracking devices, wherein the plurality of item tracking devices correspond to a plurality of items. Also, systems and methods that provide sensor data may retrieve requested sensor data corresponding to devices meeting trigger parameters and return the requested data.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments and aspects of the invention. In the attached picture:

1 is a block diagram of an example project tracking system, consistent with an embodiment of the present invention;

Figure 2 is a block diagram of an example tracking center consistent with an embodiment of the present invention;

3 is a flowchart of an example method for tracking projects, consistent with an embodiment of the invention;

4 is a flowchart of an example method of accessing sensor data using a context-based sensor network, consistent with an embodiment of the invention;

5 is an example graphical user interface displaying sensor data retrieved in response to a request for sensor data, consistent with an embodiment of the invention;

6 is an example graphical user interface for searching sensor data, consistent with an embodiment of the invention;

FIG. 7 illustrates example search results for the search performed in FIG. 6, consistent with an embodiment of the invention.

Detailed ways

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers will be used in the drawings and the following description to refer to the same or like parts. While several example embodiments and features of the invention are described herein, changes, adaptations and other implementations can be made without departing from the spirit and scope of the invention. For example, substitutions, additions, or changes may be made to components shown in the figures, and the example methods described herein may be varied by substituting, reordering, or adding steps to the disclosed methods. Accordingly, the following detailed description does not limit the invention, but the proper scope of the invention is defined by the appended claims.

overview

Systems and methods consistent with the present invention reduce the cost of item tracking and also enable sensor data to be shared to create a robust information network around tracked items. For example, sensor data is combined with surrounding sensors and/or data sources to drive rule-based logic based on relationships between sensors and associated sensor data. This enables context-based rule sets to replace the need for traditional tracking solutions and build richer information describing the items being tracked.

For each case of data acquisition, leveraging the surrounding environment (eg using sensor data from one sensor to describe the environment of multiple items) removes duplication of capture and drives down costs. This is especially true for sharing sensor data between a large number of projects. The data could be the temperature of a room or the location of a building or a picture of a road with rain.

system architecture

By way of non-limiting example, Figure 1 shows a network environment 100 in which the features and principles of the present invention may be implemented. The number of components in environment 100 is not limited to what is shown in the figures, and other variations in the number of configured components are possible consistent with the present invention. The components of Figure 1 may be implemented in hardware, software and/or firmware. Network environment 100 may include item tracking devices 102a-102n, beacon devices 104a-104n, network 106, tracking center 108, and clients 110a-110n.

Network 106 provides communications between the various entities shown in network 100 . The network 106 can be a shared public or private network and include wide or local areas. The network 106 may be implemented by any suitable combination of wired and/or wireless communication networks (including Wi-Fi network, GSM/GPRS network, TDMA network, CDMA network, Bluetooth network or any other wireless network). By way of example, network 106 may be implemented through a wide area network (WAN), a local area network (LAN), the Internet, and/or the Internet. Additionally, entities of network environment 100 may be connected to multiple networks 106, such as to wireless carrier networks, private data networks, and the public Internet.

Item tracking devices 102a-102n may be devices for tracking various items, which may be attached to or included within the item to be tracked. For example, item tracking device 102a may be attached to or encased in a package that is being sent to a recipient using a delivery service such as Federal Express Inc. ("FedEx"). Alternatively, the item tracking device 102a may be attached to or encased in a container that holds inventory that is delivered to the retailer. The foregoing items are exemplary and may include any deliverable item.

The item tracking device 102a may store information associated with an item tracking number for a corresponding item. The item tracking number can be a FedEx tracking number or similar. Item tracking device 102a may also store information indicative of other tracking devices and/or beaconing devices currently within a given proximity. For example, when an item with a corresponding item tracking device 102 is placed inside a vehicle or storage facility that includes a beacon device 104, the item tracking device 102 and/or the beacon device may sense that the item tracking device 102 is in a position indicating that the corresponding item is present. Within the immediate vicinity of a conveyance or storage facility. Information reflecting the association between the beacon device 104 and the item tracking device 102 may then be stored in memory located at one or more of the item tracking device 102 , the beacon device 104 , or the tracking center 108 .

In one embodiment, item tracking device 102 is capable of measuring or detecting one or more conditions, such as location, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other environmental conditions. Alternatively, item tracking device 102 may be a low-cost device that does not detect such environmental conditions.

Item tracking device 102 may also be capable of sending information directly to and receiving information from tracking center 108 via network 106 (eg, using known wireless communication methods). Alternatively, item tracking device 102 may first send information to nearby beacon devices 104 , which in turn send information to tracking center 108 . For example, item tracking device 102 may be implemented using a sensor device such as a wireless sensor available from Crossbow Technology. Those skilled in the art will appreciate that alternative sensors may be used.

Beacon devices 104a - 104n are devices capable of wireless communication with item tracking device 102 and tracking center 108 . Additionally, beacon devices 104a-104n are also capable of communicating with other beacon devices. Beacon devices 104a-104n may be located at various stations along the item's delivery path. For example, a vehicle driven by a courier may have a beacon device 104 associated therewith. Aircraft used to transport items may also have beacon devices 104 associated therewith. Those skilled in the art will appreciate that these locations of the beacon device 104 are exemplary only.

In one embodiment, beacon device 104 may include a sensor that measures or detects one or more conditions, such as location, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other environmental conditions . Alternatively, the beacon device may not include such sensors. Beacon devices 104 may periodically report detected sensor data to tracking center 108 via network 106 (eg, using known wireless communication methods).

The beacon device 104 is operable to periodically determine whether any item tracking devices 102 are present within a certain proximity of the beacon device 104 . For example, a beacon device 104a located within a delivery truck may periodically check to see if any item tracking devices 102 are within a predetermined distance of the beacon device 104a by listening for signals from the item tracking devices 102 . Such signals may be wireless signals periodically emitted by item tracking device 102 . As such, the item tracker 102 basically announces "here I am" periodically. Those skilled in the art will appreciate that beacon device 104 may use other methods of detecting item tracking device 102 within a predetermined distance.

The predetermined distance in this embodiment is set so that item tracking devices 102 within that distance are assumed to be inside or very close to the truck. Item tracking devices 102 outside this distance are considered to be outside the truck. When the beacon device 104 determines that the item tracking device 102 is within its range, it may store information indicating an association between the two devices. The association information may include, for example, data indicating that the specific identification number of the beacon device (104) corresponds to the specific identification number of the item tracking device (102). The beacon device may also periodically send such association information to tracking center 108 via network 106 (eg, beacon device 104 may periodically send to tracking center 108 an indication of each of its current associations with item tracking device 102 ). When beacon device 104 determines that an item tracking device is no longer within its range, it may update stored information residing at beacon device 104 and tracking center 108 to reflect that the devices are no longer associated with each other. For example, while the beacon device 104a checks for an item tracking device within its range, there may be an item tracking device 102a that was previously within range but is no longer within range. When the beacon device 104a stores its current association locally and then reports it to the tracking center 108, the current association information no longer indicates that the item tracking device 102a is currently associated with the beacon device 104a.

Tracking center 108 provides a platform for tracking items being delivered to recipients. Tracking center 108 may be implemented using a combination of hardware, software, and/or firmware, and is operable to receive and store sensor data from various item tracking devices 102 and/or beacon devices 104 . For example, beacon device 104a may periodically send sensor data to tracking center 108 reflecting conditions measured or detected by beacon device 104a. Such sensor data may include location, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other environmental conditions. Tracking center 108 is also operable to receive and store information indicative of an association between beacon device 104, item tracking device 102, and user tracking device 112 (eg, device 102 in the truck is associated with beacon device 104a). For example, beacon device 104a residing in a delivery truck may send information to tracking center 108 identifying item tracking device 102 in the truck.

Tracking center 108 is also operable to respond to requests for sensor data. For example, a customer may use client 110 to enter a request for sensor data stored at tracking center 108 . The request may include one or more trigger parameters that may be used to look up the requested sensor data. Exemplary trigger parameters may include sensor identification number, item tracking number, location, temperature, light level, humidity, pressure, air level, airflow, vibration, and the like. Thus, by way of example, a customer may request a temperature measurement within a certain range of a particular location. In that case, the distance from a specific location is the trigger parameter.

When tracking center 108 receives a request for sensor data from client 110, tracking center 108 may search the database residing at tracking center 108 and, if found, return the requested sensor data. Access to sensor data is managed or open. For example, if access is manageable, the client 110 and/or customer need to be authenticated before sensor data is made available to the client 110 and/or customer. In addition to or without searching the database for sensor data, tracking center 108 may request sensor data directly from associated item tracking devices 102 and/or beacon devices 104 .

Tracking center 108 may also provide updated and/or new programming to item tracking device 102 , beacon device 104 , and user tracking device 112 . For example, programming may specify the manner in which the device senses environmental conditions. For example, the programming of the aforementioned devices may be changed by storing new or modified instructions in memory (not shown) located in the corresponding devices. Programming changes can be made arbitrarily (eg, at the programmer's discretion) or in response to detected conditions. For example, assume that the beacon device 104a detects a temperature above a certain level. When the beacon device 104a reports this temperature level to the tracking center 108 , an alarm or alert may be triggered to bring the information to the attention of personnel associated with the tracking center 108 . Tracking center 108 may in turn change the programming of beacon device 104a to check the temperature more frequently. It will be apparent to those skilled in the art that other parameters may be used as a basis for changing the programming.

Clients 110a-110n provide an interface to network 106 for users. By way of example, clients 110a-110n can be implemented using any device capable of accessing a data network, such as a general purpose computer or a personal computer equipped with a modem or other network interface. Clients 110a-110n can also be implemented in other devices such as Blackberry ^™ , ErgoAudrey ^™ , mobile phones (with data access capabilities), personal digital assistants (PDAs) Any device that communicates over a network.

Clients 110a - 110n may be used by users to request sensor data from tracking center 108 . For example, a user may subscribe to a service that allows the user to access the latest information related to one or more sensors. Alternatively, a subscription to the service is not necessary to access the information. To request sensor data, a user may enter information on the client 110a indicating the desired sensor data. For example, a user may enter information requesting the current location and temperature of all sensors within a certain range of a specified sensor. After the customer enters this information, the client 110a can send a request to the tracking center 108, which in turn can search its database or request the information directly from the sensor. After tracking center 108 finds the requested information, it may send the information back to client 110a.

In one embodiment, a user may enter information to be searched for on a web page associated with a search engine. For example, a user may use a popular search engine such as Google ^™ . More information on the utilization of search engines in this manner is provided below in the discussion of FIGS. 6 and 7 . Alternatively, the customer or user may enter this information using an application program resident on the client machine 110 .

User tracking device 112 may be a device similar to beacon device 104 that is capable of communicating with beacon device 104 and tracking center 108 . Rather than being located in a location such as a vehicle, the user tracking device 112 is attached to or placed near the particular user himself. For example, a user may be a courier responsible for the delivery of the item being tracked, a recipient to whom the item is being delivered, a sender sending the item to a recipient, or any other person involved in the delivery and/or tracking process. User tracking device 112 may include sensors that measure or detect one or more conditions such as location, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other environmental conditions. Alternatively, the user tracking device may not include such sensors. User tracking device 112 may periodically report detected sensor data to tracking center 108 via network 106 (eg, using known communication methods).

User tracking device 112 is operable to periodically determine whether any item tracking devices 102 are within a certain proximity of user tracking device 112 . When user tracking device 112 determines that item tracking device 102 is within its range, it may store information indicating an association between the two devices. User tracking device 112 may also send this information to tracking center 108 via network 106 . When user tracking device 112 determines that an item tracking device is no longer within its range, it may update the stored information resident at user tracking device 112 and tracking center 108 to reflect that the devices are no longer associated with each other (e.g., Sensor data from the user tracking device 112 may no longer be used to understand the context of the item tracking device).

2 is a diagram of an example tracking center consistent with the present invention. Tracking center 108 may include at least web server 202 , sensor information database 204 , authentication server 206 , and rules engine 208 . The number of components in tracking center 108 is not limited to what is shown in the figures, and variations in the number of configurations of components are possible consistent with the present invention.

The web server 202 provides functionality for receiving traffic over the web. For example, the web server may be a standard web server that a user may access at client machine 110 using a web browser program such as Internet Explorer or Netscape Communicator. Web server 202 is operable to receive requests for sensor data from clients and pass the requests to sensor information database 204, authentication server 206, and/or rules engine 208 for processing.

Sensor information database 204 stores sensor data received from various item tracking devices 102 , beacon devices 104 , and user tracking devices 112 . The sensor information database 204 may also store information indicating associations between beacon devices 104 and item tracking devices 102, information indicating associations between different item tracking devices 102, and information indicating associations between user tracking devices 112 and item tracking devices 102. associated information.

For example, beacon devices such as beacon device 104a may periodically send sensor data to tracking center 108 where the sensor data is stored in sensor information database 204 . Example sensor data may include location, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other environmental conditions. Sensor data transmitted to sensor information database 204 may be accompanied by information identifying the item tracking device 102, beacon device 104, or user tracking device 112 that detected the sensor data.

Correlation data stored by sensor information database 204 may also be periodically transmitted by beacon device 104 , item tracking device 102 , or user tracking device 112 . For example, when an activated item tracking device 102 is placed within a predetermined proximity of a beacon device 104, the item tracking device 102 and/or the beacon device 104 may locally store information reflecting the association. The beacon device 104 may then send information indicative of the association to the tracking center 108 . Additionally or alternatively, item tracking device 102 may send information indicative of the association to tracking center 108 .

When tracking center 108 receives a request for sensor data from client 110, sensor information database 204 may be searched for the requested data. If the data is found, the data may be sent back to the client 110.

Authentication center 206 is operable to control access to data residing in sensor information database 204 . For example, only client 110a or a user of client 110a may be authorized to receive sensor data corresponding to a certain item tracking device 102 and/or a certain beacon device 104 . When the user requests a collection of sensor data that includes data that the client or user is not authorized to access, the authentication center 206 identifies the lack of authorization and allows the tracking center 108 to send the requested sensor data to the client or user only for which the client or user has authorization that part.

Wherein, the rule engine 208 is operable to send a query to the sensor information database 204 according to a request for sensor data from the client 110; after receiving the requested sensor data from the sensor information database 204, send it to the client 110; Process sensor data received from item tracking device 102, beacon device 104, and/or user tracking device 112 (and take appropriate action); request sensor data from item tracking device 102, beacon device 104, and/or user tracking device 112 data; and, changing the programming of each item tracking device 102, beacon device 104, and/or user tracking device 112.

system operation

3 illustrates a flowchart of an example method for tracking projects, consistent with the principles of the invention. Although the steps of this flowchart are described in a particular order, those skilled in the art will appreciate that the steps may be performed in an altered or different order, or that certain steps may be omitted. Furthermore, one or more of the steps of FIG. 3 may be performed simultaneously or in parallel.

One or more item tracking devices 102 are configured according to the shipper's requirements (step 302). For example, an organization may require specific programming of the item tracking device 102 to be associated with items to be sent to recipients. Alternatively, project tracking device 102 may be configured according to default programming. A customer wishing to send an item to a recipient may purchase or otherwise obtain an item tracking device 102 to attach or place in the item to be checked. For example, the shipper can be an item delivery company such as FedEx, a retailer, or a manufacturer that makes its own deliveries. Those skilled in the art will appreciate that it is possible for the customer and the shipper to be the same entity.

An item tracker can be activated and associated with the item being shipped (step 304). For example, a courier or other employee of the shipper may unlock the item tracking device 102a and place or attach it to the packaging associated with the corresponding item. A courier or other employee may also associate the item tracking device 102a with the item tracking number. For example, a courier or other employee may cause information to be stored at tracking center 108 indicating that an item tracking number is currently assigned to an item tracking device's identification number. Alternatively, the item tracking number is not associated with the item tracking device 102a.

Once the item tracking device 102 is activated, the item tracking device 102 may then be associated with the user tracking device 112 if the courier possesses the user tracking device 112 (step 306). For example, user tracking device 112 and/or item tracking device 102 may automatically detect when user tracking device 112 comes within a certain distance of item tracking device 102 . The user tracking device 112 may store information reflecting its association with the item tracking device 102 . Additionally, user tracking device 112 may forward this information to tracking center 108 for storage.

After the item is placed in the delivery vehicle (step 308), the item tracking device 102 for the item is associated with the beacon device 104 corresponding to the delivery vehicle (step 310). For example, the item tracking device 102 and/or the beacon device 104 may detect that the item tracking device 102 is within a predetermined distance of the beacon device 104 indicating that the corresponding item is present at or in close proximity to the vehicle. Information reflecting an association between item tracking device 102 and beacon device 104 may be stored in item tracking device 102 and/or beacon device 104 . For example, the association information may include data indicating that the specific identification number of the beacon device (104) corresponds to the specific identification number of the item tracking device (102). Beacon device 104 and/or item tracking device 102 (if it is capable of doing so) may also send this information to tracking center 108 via network 106 . Those skilled in the art will understand that a vehicle may refer to a truck, van, airplane, boat, or any other moving vehicle used to transport an item to a recipient. It will also be appreciated by those skilled in the art that the item tracking device 102 may also be associated with a beacon device located at a location other than the vehicle, such as a storage facility or an item processing facility (eg, when the corresponding item is placed at such a site).

By allowing item tracking devices to be associated with beacon devices in this manner, tracking system 108 can leverage (e.g., use sensor data from one device to describe the environment of multiple items) sensor data from beacon devices in order to provide More information about the environment of the item being tracked than previously possible. For example, assume that item tracking device 102a does not have the capability to sense temperature, but beacon device 104a does. Assume also that item tracking device 102a is associated with beacon device 104a by virtue of being disposed in a vehicle having beacon device 104a. Even if item tracking device 102a cannot sense temperature, a user later trying to find temperature information corresponding to item tracking device 102a may do so because beacon device 104a can sense temperature and be associated with item tracking device 102a. Those skilled in the art will appreciate that similar exploits can occur between item tracking devices and user tracking devices.

As described above with reference to FIG. 1 , certain item tracking devices 102 , beacon devices 104 , and user tracking devices 112 may include measurements or detections such as position, temperature, light level, motion, pressure, humidity, air level, airflow, vibration, or other One or more condition sensors for environmental conditions. Item tracking devices 102, beacon devices 104, and user tracking devices 112 that include such sensors periodically report sensor data to tracking center 108 (step 312). Item tracking devices 102 that include sensors and do not have the functionality to send information directly to and receive information from tracking center 108 via network 106 may first send sensor data to nearby beacon devices 104 or user tracking devices 112, nearby The beacon device 104 or user tracking device 112 in turn sends the sensor data to the tracking center 108 .

When the sensor data is received by the tracking center 108, if the data indicates a predetermined condition, the tracking center 108 may trigger an appropriate alarm (step 314). For example, assume that the beacon device 104a detects a temperature above a certain level. When the beacon device 104a reports this temperature level to the tracking center 108 , alarms and alerts may be triggered to bring this information to the attention of personnel associated with the tracking center 108 . Staff may then monitor the situation more closely or take other appropriate action. Alternatively or additionally, relevant couriers or other users may be notified of the alert condition via user tracking device 112 . Those skilled in the art will appreciate that instead of the tracking center 108 detecting the alert condition, the item tracking device, beacon device 104 or user tracking device 112 may identify the alert condition. Thereafter, an appropriate notification may be sent to the tracking center 108 and/or the relevant user tracking device 112 .

Tracking center 108 may also change the programming of item tracking device 102, beacon device 104, or user tracking device 112 if needed or desired (step 316). In instances where the beacon device 104a detects a temperature above a certain level, the tracking center 108 may in turn change the programming of the beacon device 104a to check the temperature more frequently. It will be apparent to those skilled in the art that other parameters may be used as a basis for changing programming. Furthermore, those skilled in the art will appreciate that the programming can be changed due to detection of conditions other than predetermined, and that the programming of the aforementioned devices can be changed without interfering with the tracking center 108 .

As the item travels through the delivery network, the item tracking device is disassociated from the beacon device if necessary (step 318). For example, when an item tracking device 102 moves out of range of its associated beacon device 104, any records reflecting an association between the item tracking device 102 and the beacon device 104 are deleted. This includes any records residing on item tracking device 102 , beacon device 104 , and tracking center 108 . For example, such disassociation may occur when items are removed from a vehicle that includes a beacon device, when items are removed from a storage facility that includes a beacon device, and the like. For example, when the beacon device 104a checks for an item tracking device within its range, there may be an item tracking device 102a that was previously within range and is no longer within range. When the beacon device 104a stores its current association locally and then reports it to the tracking center 108, the current association information no longer indicates that the item tracking device 102a is currently associated with the beacon device 104a.

In one embodiment, even when an item tracking device 102 is disassociated from the beacon device 104, it can continue to track the item corresponding to the item tracking device 102. For example, user tracking device 112 may also be associated with item tracking device 102 such that conditions sensed by user tracking device 112 may be leveraged to learn more about the context of the item. By way of example, when a courier removes a particular item from the vehicle, the corresponding item tracking device 102a may be disassociated from the beacon device 104a corresponding to the vehicle. However, item tracking device 102a may also be associated with user tracking device 112a attached to the messenger. If the user tracking device 112a has functionality to determine its location (eg, GPS or similar functionality), that location information may be used as location information for the item tracking device 102a. Additionally, if the location information is determined to be close to the recipient's address, the user tracking device 112a may send information to the tracking center 108 to that effect. Thereafter, tracking center 108 may send a notification to the recipient or another user (eg, via client 110) that the item will be delivered.

If desired, the item tracking device may also be associated with additional beacon devices or item tracking devices (step 320). For example, when an item tracking device is moved within range of a beacon device 104 with which it is not currently associated, information reflecting the association between the item tracking device and the beacon device may be stored in the item tracking device 102 and/or the beacon device 104 in. For example, the association information may include data indicating that the specific identification number of the beacon device 104 corresponds to the specific identification number of the item tracking device 102 . Beacon device 104 or item tracking device 102 (if it is capable of doing so) may also send this information to tracking center 108 via network 106 .

In one embodiment, when a project tracking device 102 and another project tracking device 102 are within a certain range of each other, the two devices may associate. An example of when it is necessary for two item tracking devices to correlate with each other is when the first item tracking device 102a is attached to an item that is within the expected association range of the beacon device 104a, but cannot detect it due to low battery power or some other reason. until it is within range. A second item tracking device 102b, also within the associated range of the beacon device, may be closer to the beacon device 104a than the first item tracking device 102a, yet still be close enough to the first item tracking device 102a for the first item tracking device Tracking device 102a detects. In this case, information reflecting the association of the first item tracking device 102a with the second item tracking device 102b may be stored at the first item tracking device 102a, the second item tracking device 102b, the beacon device 104 (which may be accessed via the second The item tracking device receives the information) and one or more of the tracking center 108. For example, the association information may include data indicating that the specific identification number of the item tracking device 102a corresponds to the specific identification number of the item tracking device 102b.

When the item reaches its final destination (eg, delivered to the recipient), the courier removes and disables the item tracking device (step 322). Thereafter, the tracking center 108 deletes the recorded data corresponding to the item tracking device and resets the item tracking device (step 324). For example, a courier or other personnel may send or provide tracking center 108 with information identifying a recently deactivated item tracking device. Tracking center 108 may then proceed to search database 204 for an entry corresponding to the item tracking device and delete it.

4 illustrates a flowchart of an example method of accessing sensor data using an environment-based sensor network, consistent with aspects of the invention. Although the steps of this flowchart are described in a particular order, those skilled in the art will appreciate that the steps may be performed in an altered or different order, or that certain steps may be omitted. Additionally, one or more steps in FIG. 4 may be performed concurrently or in parallel.

Tracking center 108 may receive a request for sensor data (step 402). A user may use the client 110 to enter a request for sensor data. For example, a user may enter a request for the current location and temperature of all sensors within the radius of a specified sensor. After the user enters the request, client 110 may send it to tracking center 108 . Alternatively, a user may enter a request for sensor data using a computer resident at tracking center 108 .

Once the tracking center 108 has received the request, it may determine whether real-time sensor data is required (step 404). For example, requests received at tracking center 108 from client 110 may be forwarded from web server 202 to rules engine 208 . Rules engine 208 may process the request and determine that it needs real-time data as opposed to stored in sensor information database 204 . Such determinations may be made based on, for example, the type of information requested, user selections, programming of rules engine 208 , or applications running on client 110 .

If real-time data is desired, processing continues to step 422, which is described in detail below. If real-time data is not required, tracking center 108 may proceed to determine a set of sensors that satisfy one or more trigger parameters (step 406). These trigger parameters may be included as part of the request for sensor data. For example, rules engine 208 may examine the request to determine the trigger parameters. Thereafter, rules engine 208 may search sensor information database 204 for information identifying item tracking devices 102 , beacon devices 104 , and/or user tracking devices 112 that meet the criteria set forth by the respective trigger parameters. For example, if the request is for temperature information from a sensor within 2 miles of a specified item tracking device 102a, the rules engine 208 looks for item tracking devices 102, Beaconing device 104 and/or user tracking device 112 .

For example, if the item tracking device 102a does not have location-determining functionality, the location may also be determined by looking up associated data corresponding to the item tracking device 102a in the information database 204 to find the associated beacon device 104 or user tracking device 112. Thus, assuming the associated beacon device 104 or user tracking device 112 can determine the location, a location corresponding to the associated item tracking device can be determined. Thereafter, continuing the example, the rules engine 208 may determine which devices are within 2 miles of the location.

Once an appropriate sensor set has been determined, tracking center 108 may attempt to retrieve the requested sensor data from the entry corresponding to that sensor set (step 408). For example, rules engine 208 may search sensor information database 204 for entries corresponding to the aforementioned set of sensors. An entry for the requested sensor data is left as part of the result set. For example, continuing the example of the request for temperature information from sensors within 2 miles of a specified location, the rules engine 208 may access entries in the sensor information database corresponding to the set of sensors that are within 2 miles of the location. Temperature information from those entries may form part of the result set. Those skilled in the art will appreciate that sensor data from beacon devices 104 or user tracking devices 112 may be leveraged (e.g., using sensor data from one device to describe the environment of multiple items) in order to determine that temperature cannot be detected The temperature information of the sensors in the sensor collection. Those skilled in the art will also appreciate that the foregoing assumptions are exemplary only, and any combination of trigger parameters and requested sensor data may be used.

If the requested sensor data is not found in the sensor information database 204 (step 410—NO), then a decision is made as to whether the tracking center 108 should attempt to retrieve real-time data (step 412). If so, processing may continue to step 424, which is discussed in more detail below. If not, the tracking center 108 may issue a notification that the requested sensor data is not available (step 414). For example, where a client 110 initiates a request for sensor data, rules engine 208 may generate such a notification and send it to the appropriate client 110 via web server 202 and network 106 .

If the requested sensor data is successfully found after step 408 (step 410—Yes), the tracking center 108 determines whether the requester has authorization to access all retrieved data (step 416). For example, authentication server 206 may interact with sensor information database 204, rules engine 208, and/or client 110 originating the request to make this determination. Authentication server 206 may receive the request, which may include authorization information. From this authorization information, the authentication server 206 can determine which portions, if any, of the sensor data contained in the result set are authorized for the requestor to access.

If the requester has access to all sensor data in the result set, then all data is sent to the requester (step 418). For example, where the user of client 110 has such access, all requested sensor data is returned to client 110 where it can be displayed for viewing by the user. If the requester only has access to a portion of the sensor data, or has no access to the data at all, then only the portion of the data for which the requester is authorized is sent to the requester (step 420). For example, if the user of the client machine 110 has access to only half of the requested sensor data, only that half of the data is returned to the client machine 110, where it can be displayed for viewing by the user. Those skilled in the art will appreciate that if the user in this example does not have access to any of the requested sensor data, then no data from the result set is returned to the client 110 .

Returning to step 404, upon determining that real-time data is required (step 404-Yes), the tracking center 108 determines a set of sensors that satisfy one or more trigger parameters (step 422). As previously described, these trigger parameters are included as part of the request for sensor data. For example, rules engine 208 may examine the request to determine the trigger parameters. Thereafter, rules engine 208 may search sensor information database 204 for information identifying item tracking devices 102 , beacon devices 104 , and/or user tracking devices 112 that meet the criteria set forth by the respective trigger parameters. For example, if the request is for information from sensors within 2 miles of a specified item tracking device 102a, the rules engine 208 looks for item tracking devices 102 and/or that are indicated to be within 2 miles of the specified item tracking device 102a or beacon device 104 .

Alternatively, tracking center 108 may attempt to determine the set of relevant sensors by requesting information directly from item tracking device 102 , beacon device 104 , and user tracking device 112 . In the above example of a request for temperature information from a sensor within 2 miles of a given item tracking device 102a, the rules engine 208 (or, more generally, the tracking center 108) may send a request to each item tracking device 102, beacon device 104 and user tracking device 112 initiate a request for location information. After the rules engine 208 receives location information from the various devices, it may determine which of those devices are within 2 miles of a given item tracking device 102a.

Once an appropriate sensor set has been determined, tracking center 108 may request the requested sensor data from item tracking devices 102, beacon devices 104, and user tracking devices 112 that are part of the set (step 424). For example, rules engine 208 may request sensor data directly from devices 102 , 104 , and 112 identified at step 422 . The sensor data retrieved from the set of devices 102, 104, and 112 forms part of the resulting set. For example, continuing the example of the request for temperature information from sensors that are within 2 miles of a specified item tracking device 102a, the rules engine 208 may request information from item tracking devices 102 that were previously identified as being within 2 miles of the location. And beacon device 104 requests temperature information. Temperature information from those devices may form part of the result set. Although steps 422 and 424 have been shown as separate steps, it will be appreciated by those skilled in the art that some portions of these steps may be performed simultaneously. For example, when tracking center 108 sends requests to item tracking devices 102, beacon devices 104, and user tracking devices 112 in an attempt to identify devices that meet the trigger parameters, the requests may also be for expected sensor data. Thus, it is not necessary for the tracking center 108 to send a separate request for this data.

If the requested sensor data is not available from the identified item tracking device 102, beacon device 104, and user tracking device 112 (step 426—No), then a determination is made as to whether the tracking center 108 should attempt to retrieve data from the sensor information database 204 (eg, based on the type of sensor data requested) (step 432). If so, processing may continue to step 408, as described above. If not, the tracking center 108 may send a notification that the requested sensor data is not available (step 434). For example, where a request for sensor data originates at a client 110 , rules engine 208 may generate such a notification and send it to the appropriate client 110 via web server 202 and network 106 .

If the requested sensor data is available (step 426-YES), the tracking center 108 determines whether the requester has authorization to access all retrieved data (step 428). For example, authentication server 206 may interact with sensor information database 204, rules engine 208, and/or client 110 originating the request to make this determination. Authentication server 206 may receive the request, which may include authorization information. Based on this authorization information, the authentication server 206 may determine what portion, if any, of the sensor data contained in the result set that the requestor is authorized to access.

If the requester has access to all sensor data in the result set, then all data is sent to the requester and stored in the sensor information database 204 (step 430). For example, where a user of a client machine 110 has such access rights, all requested sensor data is returned to the client machine 110 where it can be displayed for viewing by the user. If the requester only has access to a portion of the sensor data, or has no access to the data at all, then all sensor data is stored in the sensor information database 204, and only those requests to which the requester is authorized are sent to the requester. Partial data (step 436). For example, if a client 110 only has access to half of the requested sensor data, only that half of the data is returned to the client 110 where it can be displayed for viewing by the user. Those skilled in the art will appreciate that if the user in this example does not have access to any of the requested sensor data, then no data from the result set is returned to the client 110 .

5 is an example graphical user interface displaying sensor data retrieved in response to a request for sensor data, consistent with an embodiment of the invention. Those skilled in the art will appreciate that alternative user interfaces may be utilized that display the retrieved sensor data in different ways.

For example, a user interface may be displayed on client 110 or other client or workstation used by a user to request sensor data from tracking center 108 . In the example of FIG. 5, the request for sensor data is in the form of a Uniform Resource Locator (URL) entered by the user in the address window of a web browser program. For example, the URL indicates that all sensor data corresponding to the sensor identified as ZB764312-Y12345 is to be retrieved from the sensor information database 204 . In other words, in this case the user has requested all sensor data from the aforementioned sensors. In this example, a user may request sensor data directly from the tracking center 108 without the use of an intermediary search engine.

In the context of the flow chart shown in Figure 4, the trigger parameter of this request is the ID number ZB764312-Y12345 of the sensor, so all sensor data meeting this trigger parameter is requested. In response, tracking center 108 may return a web page listing relevant sensor data to the web browsing program. In this case, the tracking center 108 returns location information and temperature information for the identified sensor. Those skilled in the art will appreciate that various labels shown in the user interface of FIG. 5 (eg, "Sensor Location #1", "Sensor Temperature #1", etc.) may be replaced by relevant values in actual use. Those skilled in the art will also appreciate that the requested sensor data may be provided to the user using methods other than web pages. For example, available files provide results to users.

6 is an example graphical user interface for searching sensor data, consistent with an embodiment of the invention. Instead of requesting sensor data directly from the tracking center 108, the user may first search for a hyperlink to a web page with the requested data. The example shown in FIG. 6 shows that a user may search for sensor data belonging to a sensor identified as ZB764312-Y12345 using a search engine, such as that provided by Google ^™ . Those skilled in the art will appreciate that although the user does not request sensor data directly from the tracking center 108 , what is sought after the sensor data will also reside in the tracking center 108 .

FIG. 7 shows example search results of the search performed in FIG. 6 . Specifically, the search resulted in hyperlinks to two web pages. One is a link to the temperature information for sensor ZB764312-Y12345. The other is a link to the location information for sensor ZB764312-Y12345. For example, clicking on a temperature link may cause a request for temperature information for sensor ZB764312-Y12345 to be sent to tracking center 108 where the information may be retrieved from sensor information database 204 . In the context of the flowchart shown in Figure 4, the trigger parameter for this request is the ID number of the sensor ZB764312-Y12345, so all temperature information satisfying this trigger parameter is requested. In response, tracking center 108 may return a web page listing relevant sensor data to the web browsing program. Those skilled in the art will appreciate that the requested sensor data may be provided to the user using methods other than web pages. For example, the available files provide results to the user.

Now that certain features and embodiments of the invention have been described, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. Additionally, although embodiments of the present invention have been described as being associated with data stored in memory and other storage media, those skilled in the art will appreciate that such data may also be stored on or read from other types of computer-readable media, such as A secondary storage device like a hard disk, floppy disk or CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Furthermore, the steps of the disclosed methods may be changed in any way, including reordering steps and/or insertion or deletion steps, without departing from the principles of the invention.

It is therefore intended that the specification and examples be considered by way of example only, with the scope and spirit of the invention being indicated by the appended claims along with their full scope of equivalents.

Claims (11)

1. be used to provide the method for sensing data, comprise:

Reception is to the request of sensing data, and described request comprises trigger parameter;

The information that the device of described trigger parameter is satisfied in search identification wherein, satisfies the described device of described trigger parameter and selects from a plurality of project tracking means;

Retrieve the described sensing data of asking, the described sensing data of asking is corresponding with the described device that satisfies described trigger parameter; And

Return the described sensing data of asking.

2. the method for claim 1, wherein return and describedly ask sensing data to comprise:

Determine whether the user who initiates described request has all described mandates of asking sensing data that the described device of described trigger parameter is satisfied in visit; And

Based on the described described sensing data of asking of determining to provide the described device that satisfies described trigger parameter.

3. the method for claim 1, wherein use at search engine available on the Internet and initiate described request sensing data.

4. the method for claim 1, wherein, described search to information comprises the described information of search data library lookup, and the described retrieval sensing data of asking comprises the described sensing data of asking of clauses and subclauses retrieval corresponding with the described device that satisfies described trigger parameter from described database.

5. the method for claim 1, wherein selecting arrangement from a plurality of project tracking means, a plurality of beacon apparatus and a plurality of usertracking device.

6. the method for claim 1, wherein the search of information is comprised the set of the device of determining to satisfy described trigger parameter, and the retrieval sensing data of asking comprises set request and receiving sensor data from described device.

7. system that is used to provide sensing data comprises:

Client computer can be operable to the request of initiation to sensing data, and described request comprises at least one trigger parameter;

A plurality of project tracking means, each project tracking means of described project tracking means is corresponding with the respective item in a plurality of projects; And

The tracking center can be operable to: receive described request to sensing data; The information that the device of described at least one trigger parameter is satisfied in search identification wherein, satisfies the described device of described at least one trigger parameter and selects from described a plurality of project tracking means; Retrieve the described sensing data of asking, the described sensing data of asking is corresponding with the described device that satisfies described at least one trigger parameter; And, return the described sensing data of asking to described client computer.

8. system as claimed in claim 7, wherein, described tracking center determines whether the user who initiates described request has all described mandates of asking sensing data that the described device of described at least one trigger parameter is satisfied in visit, and based on the described described sensing data of asking of determining to provide the described device that satisfies described at least one trigger parameter.

9. system as claimed in claim 7 wherein, uses at search engine available on the Internet and initiates described request to sensing data.

10. system as claimed in claim 7, wherein, the described information of described tracking center search database lookup, and the clauses and subclauses corresponding with the described device that satisfies described at least one trigger parameter are retrieved the described sensing data of asking from described database.

11. system as claimed in claim 7, wherein, the set of the device of described at least one trigger parameter is determined to satisfy in described tracking center, and from the set request and the receiving sensor data of described device.

Images