Events based asset location and management system

• US 10,681,490 B2
• Filed: 07/17/2018
• Issued: 06/09/2020
• Est. Priority Date: 09/03/2014
• Status: Active Grant

• Current Assignee: CloudLeaf, Inc
• Original Assignee: CloudLeaf, Inc
• Inventors: Kulkarni, Raghavendra, Narahari, Sharath, Roopreddy, Ravindar
• Primary Examiner(s): Tran, Congvan
• Application Number:
  US16/037,391
• Publication Number:
  US 20180332434A1
• Time in Patent Office: 693 Days
• Field of Search: 4554561- 6
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/33 for indoor environments, e.g. buildings
• CPC Class Codes: H04W 4/35 for the management of goods or merchandise
• CPC Class Codes: H04W 4/38 for collecting sensor information
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals

Abstract

An asset location and management system, the system including multiple reader nodes, each reader node having a Bluetooth Low Energy (BLE) radio in communication with a plurality of peripheral devices, a local service module and a communications manager in communication with a cloud server. The system further including the cloud server having a communication module, a process flow library to describe how peripheral devices are expected to move through a facility, a rules library describing trigger events associated with one or more peripheral device and identifying a corresponding action for each trigger event, and a real-time compute engine to generate a sequence of events based on the data from the peripheral devices and the process flow library.

Claims

1. An asset location and management system comprising:

at least one cloud server; and

multiple reader nodes, each reader node comprising;

at least one BLE radio configured to communicate with a plurality of peripheral devices, wherein each peripheral device of the plurality of peripheral devices is associated with and monitors a physical location or a physical state of a respective asset of a plurality of assets;

a local services module in communication with the at least one BLE radio and configured to analyze data associated with each asset of the plurality of assets; and

a communications manager in communication with the local services module and configured to communicate with the at least one cloud server, and

wherein the at least one cloud server comprises;

a communications module for receiving, from the communications manager of at least one of the multiple reader nodes, an analyzed data set associated with at least one asset of the plurality of peripheral devices in communication with the at least one BLE radio of that reader node, wherein the analyzed data set includes physical location data;

a process flow library describing how distinct types of assets are expected to move through a facility;

a rules library describing a plurality of trigger events associated with the distinct types of assets and identifying a corresponding action for each trigger event; and

a real-time compute engine configured to generate a sequence of events based in part on the analyzed data set associated with the at least one asset and a determined type of the at least one asset and determine, using the process flow library, whether the at least one asset is traveling in an expected manner.

2. The system of claim 1, wherein an event in the generated sequence of events comprises an entry to an area of interest, an exit from an area of interest, a hand-off between areas of interest, a boundary event, a visit event, an asset moving in a manner that is not allowed, or a location state.

3. The system of claim 1, wherein the real-time compute engine is configured to evaluate the generated sequence of events to identify an occurrence of one or more trigger events and to initiate a corresponding action associated with any occurring trigger event.

4. The system of claim 1, wherein the analyzed data set further includes physical state data and wherein a trigger event of the plurality of trigger events comprises at least one of:

a physical state transition, a temperature crossing a threshold, a temperature out of range, a weight crossing a threshold, a temperature duration, a light level, a motion, an orientation from a gyroscope, a pressure crossing a threshold, a sensed current from a current transmitter, a relay output from a contact sensor, an inventory level, a dwell time, or a shock.

5. The system of claim 1, wherein a corresponding action for a trigger event of the plurality of trigger events comprises generating an in-app alert, generating an e-mail message, generating a text message, causing an affected asset or peripheral device to produce an output, activating an alarm, rerouting an asset, initiating replenishment of a material, or initiating a line stoppage.

6. The system of claim 1, wherein the real-time compute engine comprises a business insight module configured to analyze the generated sequence of events and the analyzed data set associated with the at least one asset to derive a business insight, wherein the business insight comprises at least one of:

a statistic regarding an asset or a given location, an asset count at a given location, a comparison between current and historic inventory levels at a given site, a comparison between a current asset level and a historic asset level, an asset level at a given supplier, a statistic for a category of assets, or a parameter associated with an asset.

7. The system of claim 1, wherein a peripheral device of the plurality of peripheral devices comprises a leaf node, an asset tag, a sensor, a wearable device, a bar code device, or an alarm.

8. The system of claim 1, wherein the corresponding local services module is configured to determine a corresponding physical location of each of the assets associated with the plurality of peripheral devices in communication with the at least one BLE radio.

9. The system of claim 1, further comprising a peripheral device discovery module configured to parse a received advertisement from a new peripheral device and identify the new peripheral device.

10. The system of claim 9, further comprising a peripheral device configuration module configured to parse information provided by the identified new peripheral device to:

(i) retrieve, from a peripheral device capabilities repository, relevant characteristics of the identified new peripheral device;

(ii) create a peripheral profile for the identified new peripheral device; and

(iii) configure the identified new peripheral device.

11. The system of claim 10, wherein configuration of the identified new peripheral device includes setting alerts and trigger events associated with data from the identified new peripheral device.

12. The system of claim 1, wherein the at least one cloud server further comprises a peripheral device hand-off and load-balancing module configured to coordinate communications with a particular peripheral device as it moves and transitions between two or more of the multiple reader nodes.

13. An asset location and management system comprising:

a communications module for receiving, from a reader node of a plurality of reader nodes, a stream of data associated with at least one of a plurality of peripheral devices in communication with the at least one of the plurality of reader nodes, wherein the at least one of the plurality of peripheral devices is associated with and monitors a physical location and a physical state of an asset, and wherein the stream of data includes physical location data of the asset;

a process flow library describing how distinct types of assets are expected to move through a facility;

a rules library describing a plurality of trigger events associated with the distinct types of assets and identifying a corresponding action for each trigger event; and

a real-time compute engine configured to generate a sequence of events based in part on the stream of data associated with the asset and a determined type of the asset and determine, using the process flow library, whether the asset is traveling in an expected manner.

14. The system of claim 13, wherein an event in the generated sequence of events may comprise an entry to an area of interest, an exit from an area of interest, a hand-off between areas of interest, a boundary event, a visit event, an asset moving in a manner that is not allowed, or a location state.

15. The system of claim 13, wherein the real-time compute engine is configured to evaluate the generated sequence of events to identify an occurrence of one or more trigger events and to initiate a corresponding action associated with any occurring trigger event.

16. The system of claim 13, wherein the stream of data further includes physical state data and wherein a trigger event of the plurality of trigger events comprises a physical state transition, a temperature crossing a threshold, a temperature out of range, a weight crossing a threshold, a temperature duration, a light level, a motion, an orientation from a gyroscope, a pressure crossing a threshold, a sensed current from a current transmitter, a relay output from a contact sensor, an inventory level, a dwell time, or a shock.

17. The system of claim 13, wherein a corresponding action for a trigger event of the plurality of trigger events comprises at least one of:

generating an in-app alert, generating an e-mail message, generating a text message, causing an affected asset or peripheral device to produce an output, activating an alarm, rerouting an asset, initiating replenishment of a material, or initiating a line stoppage.

18. The system of claim 13, wherein the real-time compute engine comprises a business insight module configured to analyze the generated sequence of events and the stream of data from the at least one of the plurality of peripheral devices to derive a business insight, wherein the business insight comprises at least one of:

a statistic regarding an asset or a given location, an asset count at a given location, a comparison between current and historic inventory levels at a given site, a comparison between a current asset level and a historic asset level, an asset level at a given supplier, a statistic for a category of assets, or a parameter associated with an asset.

19. The system of claim 13, wherein a peripheral device may be a leaf node, an asset tag, a sensor, a wearable device, a bar code device or an alarm.

20. The system of claim 13, further comprising a peripheral device discovery module configured to parse a received advertisement from a new peripheral device and identify the new peripheral device.

21. The system of claim 20, further comprising a peripheral device configuration module configured to parse information provided by the identified new peripheral device to:

(i) retrieve, from a peripheral device capabilities repository, relevant characteristics of the identified new peripheral device;

(ii) create a peripheral profile for the identified new peripheral device; and

(iii) configure the identified new peripheral device.

22. The system of claim 21, wherein configuration of the new peripheral device includes setting alerts and trigger events for the stream of data from the new peripheral device.