US 8,560,274 B2Grant
Portable computing device and method for asset management in a logistics system
Issue Date:2013-10-15
•12 Claims
•8 Drawing Sheets
Abstract
Systems, methods, and computer program products are provided for tracking one or more items. In one exemplary embodiment, there is provided a device for tracking one or more items. The device may include a plurality of sensors for detecting light, temperature, humidity, pressure, and acceleration. The device may also include a memory for storing information received from the plurality of sensors.
Metadata
Assignee
- Fedex Corporate Services, Inc.
Inventors
- Timothy L. Gregory
- Andy N. Lemmon
- John Marshall Veitenheimer
- James Randy Jacobs
- Miley E. Ainsworth
Application Information
Application Number:US 13/565,738
Filing Date:2012-08-02
Priority Date:2009-09-25
Art Unit:2857
Classifications
IPC:
G06F15/00
Patent Drawings (8 sheets)
Description
Cross Reference to Related Applications
[0001] This is a continuation application of U.S. patent application Ser. No. 12/566,876, filed Sep. 25, 2009, which is incorporated herein by reference.
Technical Field
[0002] The present invention generally relates to systems and methods for tracking items. More particularly, the present invention relates to systems and methods for tracking items using a sensor device.
Background
[0003] Asset management has always been an important part of commerce. For example, tracking packages is important to organizations of all kinds, whether it be a company keeping track of inventory to be sold in its stores, or a package delivery provider keeping track of packages being transported through its delivery network. To provide quality service, an organization typically creates and maintains a highly organized network for tracking its packages. Effective management of such networks allows lower cost, reduced delivery time, and enhanced customer service.
[0004] In addition to tracking packages, parties that ship and receive packages may also need information regarding the conditions of the packages such as the temperature and humidity of the package. For example, a customer that has ordered a box of wine may want to monitor the temperature of the contents of the box to determine if the temperature and/or humidity goes above or below a set range. Likewise, the party that ships the package may also want to monitor the conditions of the package to ensure that the content arrives in the proper condition.
[0005] Technological advances have enabled items to be tracked in ways that far exceed the functionality of a simple list. A rich information framework now can be applied to describe the item's interaction with its surroundings, such as transportation and custodial handoffs.
[0006] Bar codes are one way organizations keep track of items. A retailer, for example, may use bar codes on items in its inventory. For example, items to be sold in a retailer's store may each be labeled with a different bar code. In order to keep track of inventory, the retailer typically scans the bar code on each item. In addition, when an item is sold to a consumer, the bar code for that item is scanned.
[0007] Similarly, a package delivery provider may utilize bar codes by associating a bar code with packages to be delivered to a recipient. For example, a package may have a bar code corresponding to a tracking number for that package. Each time the package goes through a checkpoint (e.g., the courier taking initial control of the package, the package being placed in a storage facility, the package being delivered to the recipient, etc.), the package's bar code may be scanned. Bar codes, however, have the disadvantage that personnel must manually scan each bar code on each item in order to effectively track the items.
[0008] Radio-frequency identification (RFID) tags are an improvement over typical bar codes. RFID tags do not require manual scanning that is required by typical bar codes. For example, in a retail context, an RFID tag on an inventory item may be able to communicate with an electronic reader that detects items in a shopping cart and adds the cost of each item to a bill for the consumer. RFID tags have also been used to track things such as livestock, railroad cars, trucks, and even airline baggage. These tags typically only allow for basic tracking and do not provide a way to improve asset management using information about the environment in which the items are tracked.
[0009] Sensor-based tracking systems are also known which can provide more information than RFID systems. Such systems, however, can be expensive, and may provide extraneous and redundant item information.
[0010] Shippers, carriers, recipients, and other parties often wish to know the location, condition, and integrity of shipments before, during, and after transport to satisfy quality control goals, meet regulatory requirements, and optimize business processes. To address these requirements, a system is needed that may monitor data regarding shipments and present this data to a user in real-time or near real-time.
Summary
[0011] In one exemplary embodiment, there is provided a device for tracking one or more items. The device may include a plurality of sensors for detecting light, temperature, humidity, pressure, and acceleration. The device may also include a memory for storing information received from the plurality of sensors.
[0012] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Brief Description of the Drawings
[0013] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments and aspects of the present invention. In the drawings:
[0014] FIG. 1 is a top view of an exemplary sensor device consistent with an embodiment of the present invention;
[0015] FIG. 2 is a three dimensional view of an exemplary sensor device consistent with an embodiment of the present invention;
[0016] FIG. 3 is a three dimensional view of an exemplary sensor device consistent with an embodiment of the present invention;
[0017] FIG. 4 is a top view of an exemplary circuit board used with a sensor device consistent with an embodiment of the present invention;
[0018] FIG. 5 is a bottom view of an exemplary circuit board used with a sensor device consistent with an embodiment of the present invention;
[0019] FIG. 6 illustrates an exemplary computing system that can be used to implement embodiments of the invention; and
[0020] FIG. 7 illustrates a flowchart of an exemplary method for tracking items consistent with an embodiment of the present invention.
Detailed Description
[0021] The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several exemplary embodiments and features are described herein, modifications, adaptations and other implementations are possible, without departing from the spirit and scope of the invention. For example, substitutions, additions or modifications may be made to the components illustrated in the drawings, and the exemplary methods described herein may be modified by substituting, reordering or adding steps to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the proper scope of the invention is defined by the appended claims.
Device Architecture
[0022] FIG. 1 illustrates a top view of an exemplary sensor device 100. As depicted in FIG. 1 , sensor device 100 may comprise a body that surrounds and protects internal operational components. The body may include a wall formed from a plastic material that permits wireless communications. The wireless communications may, for example, be cellular communications and/or low-power wireless mesh networking communications.
[0023] The body of sensor device 100 may be formed from a variety of plastics combinations that may include, for example, metals, metal alloys, plastics, ceramics or a combination of metals, metal alloys, plastics, ceramics. The body may also include an over-molding that surrounds sensor device 100 at the point where the top and bottom housing components come together to create a seam. This aids in providing both a moisture seal and an impact protection guard for the unit.
[0024] Sensor device 100 may also include numerous light sensor lenses. As illustrated in FIG. 1 , sensor device 100 may include light sensor lenses 110 and 120. As illustrated in FIG. 4 , light sensors 320 and 330 may be covered by light sensor lenses 110 and 120, respectively. Light sensor lenses 110 and 120 may allow light to travel through the lens for detection by light sensors as explained in reference to FIGS. 4 and 5 .
[0025] Sensor device 100 may be generally rectangular in shape and may include a nose portion on one side. The nose portion may include sensor port 130. Sensor port 130 may include numerous ports that allow the detection of pressure, temperature, and humidity. As illustrated in FIG. 4 , sensor 310 and sensor 315 may be covered by sensor port 130 and sensor port 130 may allow pressure, temperature, and humidity to flow through the ports for detection by sensor 310 and sensor 315. For example, temperature and pressure may be detected by sensor 310, and temperature and humidity may be detected by sensor 315. Moreover, a single sensor may detect pressure, temperature, and humidity. Conversely, three sensors may exist and each sensor may detect one of pressure, temperature, and humidity. One of ordinary skill would appreciate that any combination of sensors may be used to detect pressure, temperature, and humidity or any other features as desired.
[0026] Sensor port 130 may be placed in the nose portion of sensor device 100 to insulate sensor port 130 from any heat that may be generated from the internal components. Sensor device 100 may include a battery, at least one microcontroller, a global positioning system module, and one or more transceivers as illustrated in FIGS. 4 and 5 . When in use, these components may generate heat, and the generated heat may interfere with the readings detected by sensor 310 and sensor 315. Therefore, sensor port 130 may be located within a nose portion of sensor device 100 to minimize or eliminate the effect that the internal components may have on sensor readings.
[0027] In addition to locating sensor port 130 in the nose portion of sensor device 100, additional measures may be taken to ensure that any heat from the internal components does not effect sensor readings. For example, within the body of sensor device 100, a wall may exist that acts to separate sensor port 130 from the internal components of sensor device 100 (not shown). For example, the wall may be placed between sensor port 130 and the internal components. The wall may be transparent and may block the heat that is generated by the internal components from reaching sensor port 130. This may help to ensure that sensor 310 and sensor 315 housed within sensor port 130 only detect data external to sensor device 100 and do not detect any heat from the internal components.
[0028] Sensor device 100 may also include status and power indicators 140. These indicators may each include a light emitting diode (LED). The LED corresponding to the power indicator may light up when sensor device 100 is in operation. In addition, the LED corresponding to the status indicator may light up during any number of operations including, for example, when sensor device 100 is on, when sensor device 100 is receiving data, or when sensor device 100 is transmitting data. One of ordinary skill would appreciate that a liquid crystal display (LCD), touch screen, or any combination of an LED, LCD, and touch screen may be implemented as status and power indicators 140.
[0029] Sensor device 100 may include numerous electrical components that may provide computing operations for sensor device 100. These components may include one or more microprocessors, a flash file system, Read-Only Memory (ROM), Random-Access Memory (RAM), a battery, a circuit board, a wireless modem, a Global Positioning System (GPS) module, and various input/output (I/O) support circuitry. In addition to the above, other circuitry may also include integrated chips for wireless mesh network communications and digital and/or analog sensors.
[0030] FIG. 2 illustrates a three dimensional view of sensor device 100. As depicted in FIG. 2 , sensor device 100 may include a power switch 210 that turns sensor device 100 on and off. Power switch 210 may be physically recessed from the body of sensor device 100 to prevent accidental triggering by a user. According to one embodiment, power switch 210 may be spring-loaded and monetarily pressed for on and off operations. According to another embodiment, power switch 210 maybe be pressed and held for a predetermined period of time before an “on” or “off” command is registered with the internal components. This period of time may be any appropriate amount of time such as, for example, five seconds. One of ordinary skill would appreciate that predetermined period of time may be any amount of time that is sufficient to indicate to the internal components that an operator of sensor device 100 is turning the device on or off.
[0031] Sensor device 100 may also include a Universal Serial Bus (USB) port 211 for charging sensor device 100. In addition, sensor device 100 may also include external contacts 212 and 213 for charging sensor device 100 via a cradle or other type of external charging device.
[0032] Sensor device 100 also includes light sensors lenses 110 and 120. In addition, sensor device 100 may also include light sensor lens 220, which is located on the bottom portion of sensor device 100. FIG. 2 also illustrates sensor port 130. FIG. 2 also illustrates status and power indicators 140.
[0033] FIG. 3 also illustrates a three dimensional view of sensor device 100. As depicted in FIG. 3 , sensor device 100 may include light sensor lenses 110 and 220, as previously illustrated, and light sensor lens 230. Sensor device 100 may also include a battery door 240 that may be opened and closed as needed to remove and change the battery. The battery may be any appropriate type of battery including, for example, a rechargeable lithium polymer battery cell.
[0034] Accordingly, sensor device 100 may include a total of four light sensor lenses and four corresponding light sensors. One of ordinary skill would appreciate that when sensor device 100 is placed in a package, it may be placed in many different orientations. For example, sensor device 100 may be placed on top of the content of the package. It may also be placed between the content of the package and one of the sides of the package. It may also be placed under the content of the package. Therefore, by including four lights sensors lenses and four light sensors, the location of sensor device 100 within the package is not critical. Sensor device 100 may detect a change in the amount of light within the package regardless of the location of sensor device 100 in comparison to the content of the package. This may result in greater detection of light change and may also eliminate the need for the user of sensor device 100 to place the device in a specific location of the package.
[0035] FIG. 4 includes a circuit board 300 of sensor device 100 that contains numerous components. FIG. 4 illustrates a top view of circuit board 300. Circuit board 300 may include sensor 310 and sensor 315. As previously stated, sensor 310 and sensor 315 may be covered by sensor port 130, and sensor port 130 may allow pressure, temperature, and humidity to flow through the ports for detection by sensor 310 and sensor 315. For example, temperature and pressure may be detected by sensor 310, and temperature and humidity may be detected by sensor 315. Moreover, a single sensor may detect pressure, temperature, and humidity. Conversely, three sensors may exist and each sensor may detect one of pressure, temperature, and humidity. One of ordinary skill would appreciate that any combination of sensors may be used to detect pressure, temperature, and humidity or any other features as desired.
[0036] Circuit board 300 may also include light sensors 320 and 330. In operation, light sensor lenses 110 and 120 may allow light to pass therethrough. This light is then detected by light sensors 320 and 330. Light sensors 320 and 330 may detect the amount of light within a package that contains sensor device 100 and changes in the amount of light. For example, if the package that contains sensor device 100 is opened, light sensors 320 and 330 may detect a change in the amount of light that indicates that the packages has been opened.
[0037] Circuit board 300 may also include a Global Positioning System (GPS) antenna 340, a Subscriber Identity Module (SIM) card 350, and a low-power microprocessor 360. GPS antenna 340 may receive signals from a GPS satellite, and the received signals are used by a GPS module (not shown). The GPS module may be a stand-alone unit or a component of another internal component. SIM card 350 may store the authentication information to allow sensor device 100 to authenticate with network 408, as illustrated in FIG. 6 . Low-power microprocessor 360 may be a low-power, wireless module containing a microcontroller. Circuit board 300 may also include a Global System for Mobile (GSM) wireless communications antenna 370.
[0038] Circuit board 300 may also include a connector 365. Connector 365 may provide a connection to a battery (not shown) that is placed within sensor device 100. The battery may provide the power for operating the electrical components housed within sensor device 100.
[0039] FIG. 5 illustrates a bottom view of circuit board 300. As depicted in FIG. 5 , circuit board 300 may also include light sensors 380 and 385. In addition, circuit board 300 may also include accelerometer 390. Accelerometer 390 may detect a change in the velocity of sensor device 100. For example, if sensor device 100 is located in a package, and the package is located in a parked car, accelerometer 390 would not detect a change in velocity. However, when the car starts moving, accelerometer 390 would sense the corresponding change in velocity.
[0040] Circuit board 300 may also include a high-power microprocessor 395 that may be a high-power, wireless module containing a microcontroller. High-power microprocessor 395 may store the pressure, temperature, humidity, and acceleration data that is detected by sensor 310, sensor 315, and accelerometer 390. In addition, high-power microprocessor 395 may also store data regarding light detected by light sensors 320 and 330. Moreover, high-power microprocessor 395 may also store the data regarding light detected by light sensors 380 and 385.
[0041] As illustrated in FIGS. 4 and 5 , circuit board 300 may include seven sensors 310, 315, 320, 330, 380, 385, and 390. According to one embodiment, light sensor 320 is located on the top portion of circuit board 300 and light sensor 380 is located directly underneath light sensor 320 and on the bottom portion of circuit board 300. Moreover, light sensor 330 is located on the top portion of circuit board 300 and light sensor 385 is located directly underneath light sensor 330 and on the bottom portion of circuit board 300. One of ordinary skill would appreciate that light sensors 320, 330, 380, and 385 may be located in any desired area of circuit board 300. For example, light sensors 320, 330, 380, and 385 may be each located on the top portion of circuit board 300 or the bottom portion of circuit board 300.
[0042] According to the above embodiment, the location of light sensors 320, 330, 380, and 385 may provide for optimal light detection. According to this embodiment, sensor device 100 thus includes four light sensor lenses 110, 120, 220, and 230 respectively connecting to sensors 320, 330, 385, and 380. This provides for accurate detection of changes in the amount of light in the package that houses sensor device 100. As previously stated, sensor device 100 may be placed in a plurality of locations within the package. It may also be placed between the content of the package and one of the sides of the package. It may also be placed under the content of the package. Therefore, by including four lights sensors lenses and four corresponding light sensors, the location of sensor device 100 within the package is not critical. Because sensor device 100 includes four light sensors lenses and four light sensors, sensor device 100 may detect a change in the amount of light within the package regardless of the location of sensor device 100 in comparison to the content of the package. This may result in greater detection of light change and may also eliminate the need for the user of sensor device 100 to place the device in a specific location of the package.
[0043] In operation, when sensor device 100 is turned on by pressing power switch 210, light sensors 320, 330, 380, and 385 may begin to sense a changes in light based, in accordance with a user configuration. In addition, sensor 310 may begin to sense a change in temperature and/or pressure, sensor 315 may begin to sense a change in temperature and/or humidity, and accelerometer 390 may begin to sense acceleration. A user of sensor device 100 may program sensor device 100 to detect data hourly, daily, or at any other interval. For example, a user may configure sensor device 100 to detect data at any set interval.
[0044] As depicted in FIGS. 4 and 5 , low-power microprocessor 360 and high-power microprocessor 395 are located on opposite sides of circuit board 300. One of ordinary skill would appreciate that low-power microprocessor 360 and high-power microprocessor 395 may be located in any desired location on circuit board 300. High-power microprocessor 395 may be viewed as a master processor and low-power microprocessor 360 may be viewed as a slave processor. Microprocessors 360 and 395 are coupled together in a master/slave relationship whereby control of sensor device 100 may be shared between the two processors.
[0045] Microprocessors 360 and 395 may work together to operate sensor device 100 based on the configuration data. High-power microprocessor 395 may control high power functions of sensor device. These functions may include network connectivity, transmitting and/or receiving, persistent storage of recorded data, location data collection (e.g. GPS), high-level power management, and electronics diagnostics that may consume power resources. Low-power microprocessor 360 may control lower power functions. These functions may include sensor data collection, low-level power management, and low-power mesh networking transmitting and/or receiving. By way of example, an ultra, low-level power management solution may involve shutting down the master (high-power) processor. In this case, a well-defined relationship is in place to ensure that smooth transitions occur as management decisions are passed back and forth between microprocessors 360 and 395.
[0046] In addition, an Application Protocol Interface (API) may be used to simplify the interaction between the master microprocessor 395 and slave microprocessor 360 and to aid in the sharing of data generated in or received by sensor 100. This API may be binary in nature and may have two main parts including, for example a header and a payload of data. The API header may consist of, for example, length, sequence, source, destination, and type data. The payload may be a flexible message that depends on what was captured at a point in time during operation of sensor device 100.
[0047] The internal components of sensor device 100 may also include subassemblies for processing, transmitting and/or receiving wireless signals (e.g. transmitter, receiver, and antenna). According to one embodiment, sensor device 100 may support modules for two wireless protocols (not shown). These protocols may support Global System for Mobile (GSM) wireless communications in the range of about 850 to about 1900 MHz and low-power mesh networking in the 2.4 GHz range. One module may located on top of circuit board 300 and the other may located on the bottom of circuit board 300. One of ordinary skill would appreciate that the location of the support modules may be modified. Both modules may be operatively coupled to circuit board 300 and its various components. Although not shown, sensor device 100 may also include components for supporting Bluetooth, WiFi, and ZigBee communication.
[0048] Sensor device 100 is configured according to operation need. By way of example, the sensor device 100 may be configured to collect environmental, security and/or location-based data continuously or at desired intervals. Configuration of data collection and/or reporting may have a direct impact on sensor device 100 power management. For example, there may be operational trade-offs depending on how sensor device 100 is configured, location-based (GPS) services, and other points of interest. Once sensor device 100 receives an operating scenario (e.g. from tracking center 406 in FIG. 6 ), sensor device 100 may be associated with a package for tracking. Sensor device 100 may transmit data to a host system (e.g. tracking center 406 in FIG. 6 ). If sensor device 100 cannot establish a wireless network connection, sensor device 100 may record the data to persistent storage in, for example, memory of high-power microprocessor 395. Once a wireless connection is established, the recorded data is transmitted to tracking center 406 and may be removed from storage. This repetitive pattern is followed until tracking of the package is complete. For example, sensor device 100 may choose to turn itself off when tracking is completed.
[0049] Sensor device 100 may also be configured to minimize the overall power usage to extend the battery life of the device. For example, if sensor device 100 is placed in a package that will be stored in a warehouse for several weeks before shipment, it is important that sensor device 100 has the ability to provide data to tracking center 406 for an extended period of time. Therefore, sensor device 100 may be configured to turn off any combination of the GPS antenna 340, SIM card 350, low-power microprocessor 360, GSM antenna 370, and high-power microprocessor 395 to extend the battery life.
[0050] According to the above example, sensor device 100 may turn off GPS antenna 340, SIM card 350, GSM antenna 370, and high-power microprocessor 395. Even though these elements are off, sensor device 100 may continue to sense changes in, for example, light, temperature, pressure, humidity, and/or acceleration, and sensor device 100 may continue to report this information at predetermined intervals to low-power microcontroller 360. If an event occurs, such as sensor device 100 begins to move, accelerometer 390 may sense this change, report the information to low-power microcontroller 360, and sensor device 100 may selectively turn on one or more of the elements that were previously turned off. Likewise, sensor device 100 may selectively turn on one or more of the elements that were previously turned off based on a change in light, temperature, pressure, and/or humidity.
Computing System
[0051] By way of a non-limiting example, FIG. 6 illustrates a system 400 in which the features and principles of the present invention may be implemented. The number of components in system 400 is not limited to what is shown and other variations in the number of arrangements of components are possible, consistent with embodiments of the invention. The components of FIG. 4 may be implemented through hardware, software, and/or firmware. System 400 may include a sensor device 402 (which corresponds to sensor device 100 in FIG. 1 ), a client 404, a tracking center 406, and a network 408.
[0052] Network 408 provides communications between the various entities depicted in system 400. Network 408 may be a shared, public, or private network and encompass a wide area or local area. Network 408 may be implemented through any suitable combination of wired and/or wireless communication networks (including Wi-Fi networks, GSM/GPRS networks, TDMA networks, CDMA networks, Bluetooth networks, or any other wireless networks). By way of example, network 408 be implemented through a wide area network (WAN), local area network (LAN), an intranet and/or the Internet. Further, the entities of system 400 may be connected to multiple networks 408, such as, for example, to a wireless carrier network, a private data network and the public Internet.
[0053] Sensor device 402 may be a device for use in tracking various items, and may be attached to or included in the items that are to be tracked. For example, sensor device 402 may be attached to or enclosed in a package that is being sent to a recipient using a delivery service such as Federal Express Corporation, (“FedEx”). Alternatively, sensor device 402 may be attached to or enclosed in a container holding inventory being delivered to a retailer. The aforementioned items are exemplary and may comprise any deliverable elements.
[0054] Sensor device 402 may store information associated with an item tracking number for a corresponding item. The item tracking number may be a FedEx tracking number or similar tracking number. In one embodiment, sensor device 402 may be capable of measuring or detecting one or more conditions such as location, temperature, acceleration, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions. Sensor device 402 may also have the ability to directly transmit and receive information to/from tracking center 406 via network 408 (e.g., using known wireless communications means).
[0055] Tracking center 406 may provide a platform for tracking items being delivered to a recipient. Tracking center 406 may be implemented using a combination of hardware, software, and/or firmware, and may be operable to receive and store sensor data from sensor device 402. For example, sensor device 402 may periodically send tracking center 406 sensor data reflecting conditions measured or detected by sensor device 402. Such sensor data may include location, temperature, acceleration, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions.
[0056] Tracking center 406 is also operable to respond to requests for sensor data. For example, a customer may use client 404 to enter a request for sensor data stored at tracking center 406. The request may include one or more triggering parameters, which can be used to find the requested sensor data. Exemplary triggering parameters may include a sensor identification number, item tracking number, location, temperature, acceleration, light level, humidity, pressure, gas level, airflow, vibrations, etc. Accordingly, by way of example, a customer may request temperature measurements within a certain range of a specific location. The distance from the specific location is the triggering parameter in that case.
[0057] When tracking center 406 receives a request for sensor data from a client 408, tracking center 406 may search a database resident at tracking center 406 and return the requested sensor data, if found. Access to the sensor data may be managed or open. For example, if access is managed, client 408 and/or the customer would need to be authenticated before sensor data is made available to client 408 and/or the customer. In addition to or instead of searching a database for sensor data, tracking center 406 may request sensor data directly from sensor device 402.
[0058] Tracking center 406 may also provide updated and/or new programming to provide configuration of sensor device 402. For example, programming may specify the manner in which a device senses environmental conditions. Programming of sensor device 402 may be altered, for example, by storing new or modified instructions in a memory (not shown) located in sensor device 402. Programming changes may be made arbitrarily (e.g., at the discretion of a programmer) or in response to a detected condition. For example, suppose sensor device 402 detects a temperature above a predetermined level. When sensor device 402 reports the temperature to tracking center 406, an alarm or alert may be triggered to bring this information to the attention of personnel associated with tracking center 406. Tracking center 406, in turn, may alter the programming of sensor device 402 to check the temperature more frequently. One of ordinary skill in the art will appreciate that other parameters can be used as the basis for altering programming.
[0059] Moreover, sensor device 402 may be preconfigured to determine programming changes without receiving instructions from tracking center 406. For example, if sensor device 402 determines that the temperature of the device has reached a predetermined threshold, sensor device 402 may change the reporting frequency without first contacting tracking center 406 to receive a programming change to alter the reporting frequency.
[0060] Client 404 provides users with an interface to network 408. By way of example, client 404 may be implemented using any device capable of accessing a data network, such as a general purpose computer or personal computer equipped with a modem or other network interface. Client 404 may also be implemented in other devices, such as a Blackberry™, Ergo Audrey™, mobile phones (with data access functions), Personal Digital Assistant (“PDA”) with a network connection, IP telephony phone, or generally any device capable of communicating over a data network.
[0061] Client 404 may be utilized by users to request sensor data from tracking center 406. For example, a user may subscribe to a service that allows the user to access up-to-date information about one or more sensors. Alternatively, a subscription to a service is not necessary to access the information. In order to request sensor data, the user may enter information on client 404 indicative of the desired sensor data. For example, the user may enter information requesting the current location and temperature of all sensors within a certain radius of a specified sensor. After the customer enters this information, client 404 may send a request to tracking center 104, which in turn may search its database or request the information directly from the sensors. When tracking center 406 finds the requested information, it may send the information back to client 404. As illustrated in FIG. 4 , one sensor device 402 and one client 406 may be connected to network 408. However, one of ordinary skill would appreciate that more than one sensor device and more than one client may be connected to network 408.
Flowchart
[0062] FIG. 5 illustrates a flowchart 500 of an exemplary method for tracking items, consistent with the principles of the present invention. Although the steps of the flowchart are described in a particular order, one skilled in the art will appreciate that these steps may be performed in a modified or different order, or that certain steps may be omitted. Further, one or more of the steps in FIG. 5 may be performed concurrently or in parallel.
[0063] Sensor device 100 is configured based on the requirements of a shipper (step 510). For example, a party may require specific programming (specifying, for example, the manner in which a device detects environmental conditions) for sensor device 100 are to be associated with items to be sent to recipients. Alternatively, sensor device 100 may be configured based on default programming. A shipper who desires to send an item to a recipient may purchase or otherwise acquire sensor device 100 to be attached to or placed in an item to be shipped. A shipper, for example, may be an item delivery company such as FedEx, a retailer, or a manufacturer that makes its own deliveries. One of ordinary skill in the art will appreciate that it is possible that the customer and the shipper are the same entity.
[0064] Sensor device 100 may be activated and associated with the item(s) being shipped (step 520). For example, a courier or other employee of the shipper may turn sensor device 100 on and place it in or attach it to packaging associated with a corresponding item. The courier or other employee may also associate sensor device 100 with an item tracking number. For example, the courier or other employee may cause information to be stored at tracking center 104 that specifies that the item tracking number is currently assigned to an identification number for the item tracking device. Alternatively, no item tracking number is associated with sensor device 100.
[0065] As noted above with reference to FIGS. 2-5 , sensor device 100 may include a plurality of sensors that measure or detect one or more conditions such as location, temperature, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions. Sensor device 100 that includes such sensors periodically report sensor data to tracking center 104 (step 530).
[0066] When tracking center 406 receives sensor data, if that data is indicative of a predetermined condition, tracking center 406 may trigger an appropriate alarm (step 540). For example, suppose sensor device 100 detects a temperature above a certain level. When sensor device 100 reports the temperature level to tracking center 406, an alarm or alert may be triggered to bring this information to the attention of personnel associated with tracking center 406. Personnel may then monitor the situation more closely or take another appropriate action. Alternatively or additionally, the pertinent courier or other party may be notified of the alarm condition via sensor device 100.
[0067] Tracking center 406 may also alter the programming of sensor device 100 if necessary or desired (step 550). In the example of sensor device 100 detecting a temperature above a certain level, tracking center 406 may, in turn, alter the programming of sensor device 100 to check the temperature more frequently. Alternatively, sensor device 100 may be preconfigured to determine programming changes without receiving instructions from tracking center 406. For example, if sensor device 100 determines that the temperature of the device has reached a predetermined threshold, sensor device 100 may change the reporting frequency without first contacting tracking center 406 to receive a programming change to alter the reporting frequency.
[0068] One of ordinary skill in the art will appreciate that other parameters can be used as the basis for altering programming. Moreover, one of ordinary skill in the art will appreciate that programming may be altered for reasons other than the detection of predetermined conditions, and that the programming of the aforementioned devices may be altered without the intervention of tracking center 406.
[0069] Finally, when an item reaches its final destination (e.g., delivered to the recipient), the courier removes and may deactivate sensor device 100 (step 560).
[0070] While 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 of the invention disclosed herein. Furthermore, although embodiments of the present invention have been described as being associated with data stored in memory and other storage mediums, one skilled in the art will appreciate that these aspects can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, or other forms of RAM or ROM. Further, the steps of the disclosed methods may be modified in various ways, including by reordering steps and/or inserting or deleting steps, without departing from the principles of the invention.
[0071] Several different embodiment of sensor device 100 may exist. For example, although one embodiment includes a wireless module that combines GPS and GSM technologies, the two may be separated within the sensor device 100 or not included. In addition, the above embodiments may also apply to other electronic devices such as RFID tags, smart dust motes, smart phones, and accessories for these devices.
[0072] It is intended, therefore, that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims and their full scope of equivalents.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for a package tracking device having a set of sensors, the method comprising:
storing in a memory of the package tracking device a reporting frequency for the package tracking device, wherein the reporting frequency is used to determine how frequently the package tracking device reports particular information derived from sensed input from the set of sensors to a tracking center associated with the tracking device; and
altering, by the package tracking device, the reporting frequency stored in the memory based on a relationship between an environmental condition and a predetermined threshold, wherein the environmental condition is associated with a sensed input of at least one sensor of the set of sensors.
2. The method of claim 1, wherein the reporting frequency is altered based on instructions received from the tracking center.
3. The method of claim 1, wherein the reporting frequency is altered without receiving instructions from the tracking center.
4. The method of claim 1, wherein the environmental condition is the ambient temperature associated with the package tracking device.
5. The method of claim 1, wherein the relationship between the environmental condition and the predetermined threshold is determined by the tracking center.
6. The method of claim 1, wherein the relationship between the environmental condition and the predetermined threshold is determined by the package tracking device.
7. A package tracking device comprising:
a set of sensors;
a memory for storing a reporting frequency for the package tracking device, wherein the reporting frequency is used to determine how frequently the package tracking device reports particular information derived from sensed input from the set of sensors to a tracking center associated with the package tracking device; and
a processor for executing instructions to alter the reporting frequency stored in the memory based on a relationship between an environmental condition and a predetermined threshold, wherein the environmental condition is associated with a sensed input of at least one sensor of the set of sensors.
8. The device of claim 7, wherein the processor alters the reporting frequency based on instructions received from the tracking center.
9. The device of claim 7, wherein the processor alters the reporting frequency without receiving instructions from the tracking center.
10. The device of claim 7, wherein the environmental condition is the ambient temperature associated with the package tracking device.
11. The device of claim 7, wherein the processor alters the reporting frequency based on the tracking center's determination of the relationship between the environmental condition and the predetermined threshold.
12. The device of claim 7, wherein the processor alters the reporting frequency based on the package tracking device's determination of the relationship between the environmental condition and the predetermined threshold.
Patent Citations (252)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5347274(A) | 1994-09-01 | Hassett | Applicant |
| US5389934(A) | 1995-02-01 | Kass | Applicant |
| US5400020(A) | 1995-03-01 | Jones et al. | Applicant |
| US5461365(A) | 1995-10-01 | Schlager et al. | Applicant |
| US5491486(A) | 1996-02-01 | Welles, II et al. | Applicant |
| US5512902(A) | 1996-04-01 | Guthrie et al. | Applicant |
| US5515858(A) | 1996-05-01 | Myllymaki | Applicant |
| US5528247(A) | 1996-06-01 | Nonami | Applicant |
| US5539748(A) | 1996-07-01 | Raith | Applicant |
| US5541845(A) | 1996-07-01 | Klein | Applicant |
| US5550551(A) | 1996-08-01 | Alesio | Applicant |
| US5568119(A) | 1996-10-01 | Schipper | Applicant |
| US5570412(A) | 1996-10-01 | LeBlanc | Applicant |
| US5576716(A) | 1996-11-01 | Sadler | Applicant |
| US5588005(A) | 1996-12-01 | Ali et al. | Applicant |
| US5592173(A) | 1997-01-01 | Lau et al. | Applicant |
| US5608412(A) | 1997-03-01 | Welles, II et al. | Applicant |
| US5623260(A) | 1997-04-01 | Jones | Applicant |
| US5627517(A) | 1997-05-01 | Theimer et al. | Applicant |
| US5629678(A) | 1997-05-01 | Gargano et al. | Applicant |
| US5631827(A) | 1997-05-01 | Nicholls et al. | Applicant |
| US5648770(A) | 1997-07-01 | Ross | Applicant |
| US5652570(A) | 1997-07-01 | Lepkofker | Applicant |
| US5686888(A) | 1997-11-01 | Welles, II et al. | Applicant |
| US5691980(A) | 1997-11-01 | Welles, II et al. | Applicant |
| US5710551(A) | 1998-01-01 | Ridgeway | Applicant |
| US5712619(A) | 1998-01-01 | Simkin | Applicant |
| US5731757(A) | 1998-03-01 | Layson, Jr. | Applicant |
| US5742233(A) | 1998-04-01 | Hoffman et al. | Applicant |
| US5751245(A) | 1998-05-01 | Janky et al. | Applicant |
| US5771001(A) | 1998-06-01 | Cobb | Applicant |
| US5771455(A) | 1998-06-01 | Kennedy, III et al. | Applicant |
| US5774876(A) | 1998-06-01 | Woolley et al. | Applicant |
| US5797091(A) | 1998-08-01 | Clise et al. | Applicant |
| USRE35920(E) | 1998-10-01 | Sorden et al. | Applicant |
| US5826195(A) | 1998-10-01 | Westerlage et al. | Applicant |
| US5835907(A) | 1998-11-01 | Newman | Applicant |
| US5841352(A) | 1998-11-01 | Prakash | Applicant |
| US5844862(A) | 1998-12-01 | Cocatre-Zilgien | Applicant |
| US5850196(A) | 1998-12-01 | Mowers | Applicant |
| US5869819(A) | 1999-02-01 | Knowles et al. | Applicant |
| US5889770(A) | 1999-03-01 | Jokiaho et al. | Applicant |
| US5892441(A) | 1999-04-01 | Woolley et al. | Applicant |
| US5917433(A) | 1999-06-01 | Keillor et al. | Applicant |
| US5948043(A) | 1999-09-01 | Mathis | Applicant |
| US5959575(A) | 1999-09-01 | Abbott | Applicant |
| US5963130(A) | 1999-10-01 | Schlager et al. | Applicant |
| US6002363(A) | 1999-12-01 | Krasner | Applicant |
| US6002982(A) | 1999-12-01 | Fry | Applicant |
| US6009319(A) | 1999-12-01 | Khullar et al. | Applicant |
| US6013007(A) | 2000-01-01 | Root et al. | Applicant |
| US6014080(A) | 2000-01-01 | Layson, Jr. | Applicant |
| US6014090(A) | 2000-01-01 | Rosen et al. | Applicant |
| US6023241(A) | 2000-02-01 | Clapper | Applicant |
| US6032051(A) | 2000-02-01 | Hall et al. | Applicant |
| US6034622(A) | 2000-03-01 | Levine | Applicant |
| US6054928(A) | 2000-04-01 | Lemelson et al. | Applicant |
| US6064336(A) | 2000-05-01 | Krasner | Applicant |
| US6067044(A) | 2000-05-01 | Whelan et al. | Applicant |
| US6072396(A) | 2000-06-01 | Gaukel | Applicant |
| US6078290(A) | 2000-06-01 | McBurney et al. | Applicant |
| US6083248(A) | 2000-07-01 | Thompson | Applicant |
| US6083353(A) | 2000-07-01 | Alexander, Jr. | Applicant |
| US6094168(A) | 2000-07-01 | Duffett-Smith et al. | Applicant |
| US6094642(A) | 2000-07-01 | Stephenson et al. | Applicant |
| US6121922(A) | 2000-09-01 | Mohan | Applicant |
| US6131067(A) | 2000-10-01 | Girerd et al. | Applicant |
| US6141570(A) | 2000-10-01 | O'Neill, Jr. et al. | Applicant |
| US6144303(A) | 2000-11-01 | Federman | Applicant |
| US6148280(A) | 2000-11-01 | Kramer | Applicant |
| US6163696(A) | 2000-12-01 | Bi et al. | Applicant |
| US6171264(B1) | 2001-01-01 | Bader | Applicant |
| US6172640(B1) | 2001-01-01 | Durst et al. | Applicant |
| US6175616(B1) | 2001-01-01 | Light et al. | Applicant |
| US6198390(B1) | 2001-03-01 | Schlager et al. | Applicant |
| US6198431(B1) | 2001-03-01 | Gibson | Applicant |
| US6198930(B1) | 2001-03-01 | Schipper | Applicant |
| US6199045(B1) | 2001-03-01 | Giniger et al. | Applicant |
| US6220509(B1) | 2001-04-01 | Byford | Applicant |
| US6226622(B1) | 2001-05-01 | Dabbiere | Applicant |
| US6231519(B1) | 2001-05-01 | Blants et al. | Applicant |
| US6232916(B1) | 2001-05-01 | Grillo et al. | Applicant |
| US6236358(B1) | 2001-05-01 | Durst et al. | Applicant |
| US6238337(B1) | 2001-05-01 | Kambhatla et al. | Applicant |
| US6243039(B1) | 2001-06-01 | Elliot | Applicant |
| US6243660(B1) | 2001-06-01 | Hsu et al. | Applicant |
| US6246376(B1) | 2001-06-01 | Bork et al. | Applicant |
| US6255942(B1) | 2001-07-01 | Knudsen | Applicant |
| US6263280(B1) | 2001-07-01 | Stingone, Jr. | Applicant |
| US6278936(B1) | 2001-08-01 | Jones | Applicant |
| US6281797(B1) | 2001-08-01 | Forster et al. | Applicant |
| US6292687(B1) | 2001-09-01 | Lowell et al. | Applicant |
| US6292724(B1) | 2001-09-01 | Apsell et al. | Applicant |
| US6292784(B1) | 2001-09-01 | Martin et al. | Applicant |
| US6298306(B1) | 2001-10-01 | Suarez et al. | Applicant |
| US6300875(B1) | 2001-10-01 | Schafer | Applicant |
| US6304856(B1) | 2001-10-01 | Soga et al. | Applicant |
| US6314308(B1) | 2001-11-01 | Sheynblat et al. | Applicant |
| US6317049(B1) | 2001-11-01 | Toubia et al. | Applicant |
| US6323807(B1) | 2001-11-01 | Golding et al. | Applicant |
| US6324213(B1) | 2001-11-01 | Harrison | Applicant |
| US6327533(B1) | 2001-12-01 | Chou | Applicant |
| US6331817(B1) | 2001-12-01 | Goldberg | Applicant |
| US6339397(B1) | 2002-01-01 | Baker | Applicant |
| US6340928(B1) | 2002-01-01 | McCurdy | Applicant |
| US6349257(B1) | 2002-02-01 | Liu et al. | Applicant |
| US6353390(B1) | 2002-03-01 | Beri et al. | Applicant |
| US6353798(B1) | 2002-03-01 | Green et al. | Applicant |
| US6356841(B1) | 2002-03-01 | Hamrick et al. | Applicant |
| US6362778(B2) | 2002-03-01 | Neher | Applicant |
| US6363254(B1) | 2002-03-01 | Jones et al. | Applicant |
| US6363323(B1) | 2002-03-01 | Jones | Applicant |
| US6377810(B1) | 2002-04-01 | Geiger et al. | Applicant |
| US6388612(B1) | 2002-05-01 | Neher | Applicant |
| US6404352(B1) | 2002-06-01 | Ichikawa et al. | Applicant |
| US6407698(B1) | 2002-06-01 | Ayed | Applicant |
| US6411892(B1) | 2002-06-01 | van Diggelen | Applicant |
| US6411899(B2) | 2002-06-01 | Dussell et al. | Applicant |
| US6421538(B1) | 2002-07-01 | Byrne | Applicant |
| US6426719(B1) | 2002-07-01 | Nagareda et al. | Applicant |
| US6427120(B1) | 2002-07-01 | Garin et al. | Applicant |
| US6429810(B1) | 2002-08-01 | De Roche | Applicant |
| US6430602(B1) | 2002-08-01 | Kay et al. | Applicant |
| US6433732(B1) | 2002-08-01 | Dutta et al. | Applicant |
| US6435018(B1) | 2002-08-01 | Murakami et al. | Applicant |
| US6441778(B1) | 2002-08-01 | Durst et al. | Applicant |
| US6442380(B1) | 2002-08-01 | Mohindra | Applicant |
| US6445937(B1) | 2002-09-01 | daSilva | Applicant |
| US6452572(B1) | 2002-09-01 | Fan et al. | Applicant |
| US6453237(B1) | 2002-09-01 | Fuchs et al. | Applicant |
| US6459365(B2) | 2002-10-01 | Tamura | Applicant |
| US6463272(B1) | 2002-10-01 | Wallace et al. | Applicant |
| US6463420(B1) | 2002-10-01 | Guidice et al. | Applicant |
| US6469639(B2) | 2002-10-01 | Tanenhaus et al. | Applicant |
| US6471087(B1) | 2002-10-01 | Shusterman | Applicant |
| US6478736(B1) | 2002-11-01 | Mault | Applicant |
| US6480108(B2) | 2002-11-01 | McDonald | Applicant |
| US6484079(B2) | 2002-11-01 | Buckelew et al. | Applicant |
| US6496695(B1) | 2002-12-01 | Kouji et al. | Applicant |
| US6496775(B2) | 2002-12-01 | McDonald, Jr. et al. | Applicant |
| US6496777(B2) | 2002-12-01 | Tennison et al. | Applicant |
| US6512478(B1) | 2003-01-01 | Chien | Applicant |
| US6513532(B2) | 2003-02-01 | Mault et al. | Applicant |
| US6522871(B1) | 2003-02-01 | Patrick et al. | Applicant |
| US6522889(B1) | 2003-02-01 | Aarnio | Applicant |
| US6529164(B1) | 2003-03-01 | Carter | Applicant |
| US6544193(B2) | 2003-04-01 | Abreu | Applicant |
| US6552652(B2) | 2003-04-01 | Beken | Applicant |
| US6559620(B2) | 2003-05-01 | Zhou et al. | Applicant |
| US6559802(B2) | 2003-05-01 | Goto et al. | Applicant |
| US6569094(B2) | 2003-05-01 | Suzuki et al. | Applicant |
| US6579231(B1) | 2003-06-01 | Phipps | Applicant |
| US6611755(B1) | 2003-08-01 | Coffee et al. | Applicant |
| US6625437(B1) | 2003-09-01 | Jampolsky et al. | Applicant |
| US6640085(B1) | 2003-10-01 | Chatzipetros et al. | Applicant |
| US6650907(B1) | 2003-11-01 | Kamperschroer et al. | Applicant |
| US6656125(B2) | 2003-12-01 | Misczynski et al. | Applicant |
| US6721542(B1) | 2004-04-01 | Anttila et al. | Applicant |
| US6747675(B1) | 2004-06-01 | Abbott et al. | Applicant |
| US6748318(B1) | 2004-06-01 | Jones | Applicant |
| US6772130(B1) | 2004-08-01 | Karbowski et al. | Applicant |
| US6801850(B1) | 2004-10-01 | Wolfson | Applicant |
| US6804606(B2) | 2004-10-01 | Jones | Applicant |
| US6812840(B2) | 2004-11-01 | Gehlot et al. | Applicant |
| US6847892(B2) | 2005-01-01 | Zhou et al. | Applicant |
| US6856804(B1) | 2005-02-01 | Ciotta | Applicant |
| US6924750(B2) | 2005-08-01 | Flick | Applicant |
| US6952645(B1) | 2005-10-01 | Jones | Applicant |
| US6975941(B1) | 2005-12-01 | Lau et al. | Applicant |
| US6976007(B1) | 2005-12-01 | Boucher et al. | Applicant |
| US7002451(B2) | 2006-02-01 | Freeman | Applicant |
| US7034683(B2) | 2006-04-01 | Ghazarian | Applicant |
| US7035856(B1) | 2006-04-01 | Morimoto | Applicant |
| US7113784(B2) | 2006-09-01 | Fujiwara et al. | Applicant |
| US7174173(B1) | 2007-02-01 | Needham et al. | Applicant |
| US7187278(B2) | 2007-03-01 | Biffar | Applicant |
| US7196621(B2) | 2007-03-01 | Kochis | Examiner |
| US7202801(B2) | 2007-04-01 | Chou | Applicant |
| US7212829(B1) | 2007-05-01 | Lau et al. | Applicant |
| US7243080(B2) | 2007-07-01 | Bhadra | Applicant |
| US7253731(B2) | 2007-08-01 | Joao | Applicant |
| US7258276(B2) | 2007-08-01 | Linton et al. | Applicant |
| US7512515(B2) | 2009-03-01 | Vock et al. | Applicant |
| US7552031(B2) | 2009-06-01 | Vock et al. | Applicant |
| US7627666(B1) | 2009-12-01 | DeGiulio et al. | Applicant |
| US7791455(B1) | 2010-09-01 | MacLean, III et al. | Applicant |
| US8019740(B2) | 2011-09-01 | Weng et al. | Applicant |
| US2001/0020204(A1) | 2001-09-01 | Runyon et al. | Applicant |
| US2001/0028304(A1) | 2001-10-01 | I'Anson et al. | Applicant |
| US2001/0044299(A1) | 2001-11-01 | Sandegren | Applicant |
| US2001/0047244(A1) | 2001-11-01 | Harrison et al. | Applicant |
| US2001/0052849(A1) | 2001-12-01 | Jones, Jr. | Applicant |
| US2002/0000930(A1) | 2002-01-01 | Crowson et al. | Applicant |
| US2002/0014955(A1) | 2002-02-01 | Klitsgaard | Applicant |
| US2002/0016171(A1) | 2002-02-01 | Doganata et al. | Applicant |
| US2002/0027507(A1) | 2002-03-01 | Yarin et al. | Applicant |
| US2002/0038182(A1) | 2002-03-01 | Wong et al. | Applicant |
| US2002/0050945(A1) | 2002-05-01 | Tsukishima et al. | Applicant |
| US2002/0057192(A1) | 2002-05-01 | Eagleson et al. | Applicant |
| US2002/0061758(A1) | 2002-05-01 | Zarlengo et al. | Applicant |
| US2002/0070856(A1) | 2002-06-01 | Wolfe | Applicant |
| US2002/0077080(A1) | 2002-06-01 | Greene | Applicant |
| US2002/0087260(A1) | 2002-07-01 | Hancock et al. | Applicant |
| US2002/0087619(A1) | 2002-07-01 | Tripathi | Applicant |
| US2002/0111171(A1) | 2002-08-01 | Boesch et al. | Applicant |
| US2002/0111819(A1) | 2002-08-01 | Li et al. | Applicant |
| US2002/0115453(A1) | 2002-08-01 | Poulin et al. | Applicant |
| US2002/0119789(A1) | 2002-08-01 | Friedman | Applicant |
| US2002/0120475(A1) | 2002-08-01 | Morimoto | Applicant |
| US2002/0143670(A1) | 2002-10-01 | Cushing et al. | Applicant |
| US2002/0165638(A1) | 2002-11-01 | Bancroft et al. | Applicant |
| US2002/0175805(A9) | 2002-11-01 | Armstrong et al. | Applicant |
| US2002/0187025(A1) | 2002-12-01 | Speasl et al. | Applicant |
| US2002/0193121(A1) | 2002-12-01 | Nowak et al. | Applicant |
| US2003/0001742(A1) | 2003-01-01 | Eshelman et al. | Applicant |
| US2003/0003943(A1) | 2003-01-01 | Bajikar | Applicant |
| US2003/0004403(A1) | 2003-01-01 | Drinan et al. | Applicant |
| US2003/0061176(A1) | 2003-03-01 | Hoar | Applicant |
| US2003/0069002(A1) | 2003-04-01 | Hunter et al. | Applicant |
| US2003/0069759(A1) | 2003-04-01 | Smith | Applicant |
| US2003/0084005(A1) | 2003-05-01 | Wong et al. | Applicant |
| US2003/0115978(A1) | 2003-06-01 | Moehnke et al. | Applicant |
| US2003/0151507(A1) | 2003-08-01 | Andre et al. | Applicant |
| US2003/0204452(A1) | 2003-10-01 | Wheeler | Applicant |
| US2004/0034470(A1) | 2004-02-01 | Workman | Applicant |
| US2004/0046637(A1) | 2004-03-01 | Wesby Van Swaay | Applicant |
| US2004/0117108(A1) | 2004-06-01 | Nemeth | Applicant |
| US2005/0071258(A1) | 2005-03-01 | Kumakawa | Applicant |
| US2006/0173444(A1) | 2006-08-01 | Choy et al. | Applicant |
| US2006/0187026(A1) | 2006-08-01 | Kochis | Applicant |
| US2007/0290836(A1) | 2007-12-01 | Ainsworth et al. | Examiner |
| US2008/0021953(A1) | 2008-01-01 | Gil | Applicant |
| US2009/0150114(A1) | 2009-06-01 | Vock et al. | Applicant |
| US2009/0292682(A1) | 2009-11-01 | Robbins | Applicant |
| US2009/0295581(A1) | 2009-12-01 | Paananen et al. | Applicant |
| US2010/0332284(A1) | 2010-12-01 | Hilbush et al. | Applicant |
| EP1037447(A2) | 2000-09-01 | Applicant | |
| EP1189163(A2) | 2002-03-01 | Applicant | |
| GB2329491(A) | 1997-09-01 | Applicant | |
| WO97/41654 | 1997-11-01 | Applicant | |
| WO98/01769 | 1998-01-01 | Applicant | |
| WO98/16045 | 1998-04-01 | Applicant | |
| WO/51391 | 2000-08-01 | Applicant | |
| WO1/50151(A1) | 2001-07-01 | Applicant | |
| WO1/65444(A1) | 2001-09-01 | Applicant | |
| WO1/75700(A2) | 2001-10-01 | Applicant | |
| WO1/97167(A2) | 2001-12-01 | Applicant | |
| WO2/42979(A1) | 2002-05-01 | Applicant | |
| WO2/084618(A1) | 2002-10-01 | Applicant | |
| WO2/101505(A2) | 2002-12-01 | Applicant | |
| WO3/012720(A1) | 2003-02-01 | Applicant |
Non-Patent Literature (25)
- CrossCheck™ AMPS with IQ Event Engine™ Firmware Operation Manual, Trimble Navigation Limited, Nov. 1998.Applicant
- CrossCheck® GSM Mobile Unit Operation Manual, Trimble, Jul. 2001.Applicant
- TAIP/IQEvent Engine Reference, Trimble Navigation Limited, Aug. 1999.Applicant
- ReZolt Corporate Backgrounder RZCORP-111011, www.ReZolt.com, 2011.Applicant
- Venable LLP, Homeland Security Alert, Maritime Transportation Security Act of 2002, Dec. 2002.Applicant
- Frittelli, John F., Port and Maritime Security: Background and Issues for Congress, CRS Report for Congress, Received through the CRS Web, updated May 27, 2005.Applicant
- Environmental Cyberinfrastructure Needs for Distributed Sensor Networks, A Report From a National Science Foundation Sponsored Workshop, Scripps Institute of Oceanography, Aug. 2003.Applicant
- Ruiz-Garcia et al.,“Monitoring Cold Chain Logistics by means of RFID,” from Sustainable Radio Frequency Identification Solutions, Book edited by Cristina Turcu, Feb. 2010.Applicant
- Shirley, Donna et al., “Mars Rovers: Past, Present and Future,” Princeton Space Studies Institute's 20th Anniversary Conference May 1997.Applicant
- MICA Wireless Measurement System, Crossbow Technology, Inc., San Jose, CA.Applicant
- Culler, David et al., “MICA: The Commercialization of Microsensor Motes” | Sensors, Apr. 2002.Applicant
- Kahn, J.M. et al., “Next Century Challenges: Mobile Networking for ‘Smart Dust’”.Applicant
- Wolfe, Michael, “Electronic Cargo Seals: Context, Technologies, and Marketplace,” Jul. 2002.Applicant
- Maestas, Eli et al., “Demonstration of the Radio Frequency Identification Transportation Security and Safety System,” Oct. 15, 2003.Applicant
- “Remote Sensing for Transportation,” Report of a Conference, Washington D.C., Dec. 2000.Applicant
- Horton, Mike et al., “MICA THe Commercialization of Microsensor Motes,” Sensor Technology and Design, Apr. 2002.Applicant
- System Planning Corp. helps evaluate seamless container-security system, The Journal of Commerce, May 2005.Applicant
- Prasad, Lakshman, et al., Application of Shape Analysis to domestic and international security. Institute of Nuclear Materials Management Conference 2002, Orlando, Florida, Jun. 2002.Applicant
- Spencer, B.F. et al., “Smart Sensing Technology: Opportunities and Challenges,”.Applicant
- Hill, Jason, “A Software Architecture Supporting Networked Sensors” Dept. of Electrical Engineering and Computer Scineces, U.C. Berkeley, Fall 2000.Applicant
- Kremens, Robert et al., Low Cost Autonomous Field-Deployable Environment Sensors.Applicant
- Akyildiz, I.F. et al., “Wireless Sensor Networks: a Survey” Computer Networks 38 (2002) 393-422.Applicant
- Office Action mailed Nov. 15, 2011 for U.S. Appl. No. 12/566,876.Applicant
- Response to Office Action filed Mar. 15, 2012 for U.S. Appl. No. 12/566,876.Applicant
- Notice of Allowance mailed Apr. 2, 2012 for U.S. Appl. No. 12/566,876.Applicant