Asset Management Via Virtual Tunnels

• US 20170063788A1
• Filed: 11/11/2016
• Published: 03/02/2017
• Est. Priority Date: 04/28/2011
• Status: Active Grant

• Current Assignee: Lantronix Incorporated
• Original Assignee: Lantronix Incorporated
• Inventors: Miller, Daryl R., Wagstaff, David L.
• Granted Patent: US 9,680,796 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 63/0236 Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes

Abstract

An asset management system is presented. The management system includes monitoring devices able to provide asset data across firewalls without requiring reconfiguration of the firewalls. The asset data pass through a forwarding service that instantiates a virtual tunnel comprising a communication channel between the monitoring devices and remote asset management engines. The asset management engines can also be located behind firewalls. As the management engines aggregate asset data, the engines can present one or more alerts via a management interface.

Claims

1-20. -20. (canceled)

21. An asset management system comprising:

a plurality of asset monitoring devices located behind firewalls under control of different third party entities, each monitoring device configured to sense an asset status of an asset;

a device server configured to receive the asset status of the asset from the monitoring device;

a forwarding service implemented on a network server, the forwarding service including an asset-side network address configured to receive an asset status message representative of the asset status of the asset through the firewall, and a management-side network address configured to receive the asset status message from the asset-side network address through a virtual tunnel; and

an asset management engine in communication with the management-side network address, the asset management engine configured to receive the asset status message and to compare data within the asset status message to criteria stored within an alert database to determine if an alert should be generated.

22. The system of claim 21, wherein the asset status message reflects a status of at least one of the following:

a fuel, a food stuff, a resource, a temperature, and a piece of equipment,

23. The system of claim 21, wherein the asset management engine is further configured to transmit the alert to a management interface.

24. The system of claim 21, wherein the forwarding service comprises a cloud-based service.

25. The system of claim 21, wherein the asset-side network address comprises at least one of the following:

a fixed network address, a URL, and a domain.

26. The system of claim 21, wherein the management-side network address comprises at least one of the following:

a fixed network address, a URL, and a domain.

27. The system of claim 21, wherein the asset monitoring device lacks a requirement to alter the firewall behavior to transmit the asset status message to the asset-side network address.

28. The system of claim 21, wherein asset status message communications between the asset monitoring device and the management engine via the forwarding services lacks a requirement for a Virtual Private Network (VPN).

29. The system of claim 21, wherein at least one of the plurality of asset monitoring devices located behind firewalls is disposed on an asset transport wherein the asset status message is representative of a mobile asset local to the asset transport.

30. The system of claim 29, wherein the mobile asset status message comprises at least one of the following types of data:

a location, a position, a heading, a quantity, and a cost.

31. The system of claim 21, wherein the asset status message comprises at least one of the follow types of data:

competitor data, cost data, inventory data, account data, and alert data.

32. The system of claim 21, wherein the management interface comprises a web interface.

33. The system of claim 21, wherein the management interface comprises an API.

34. The system of claim 21, wherein the management interface comprises at least one of the following:

a cell phone, a computer, a tablet, an application, and a voice-based interface.

35. The system of claim 21, wherein the asset management engine comprises the forwarding service.

36. The system of claim 21, wherein the virtual tunnel comprises a bi-directional data exchange channel between the management engine and the asset monitoring device.

37. The system of claim 21, wherein the virtual tunnel comprises a secured tunnel.

38. The system of claim 21, wherein the forwarding service is configured to manage a plurality of distinct virtual tunnel objects, each object representative of a separately managed virtual tunnel.

39. The system of claim 38, wherein the forwarding service is configured to provide access to the virtual tunnel objects in exchange for a fee.

40. The system of claim 21, wherein the asset monitoring devices are geographically distributed.

41. The system of claim 21, wherein the forwarding service is further configured to control traffic comprised of incoming asset status messages using a load balancing technique.

42. The system of claim 41, wherein the load balancing technique is based on one or more criteria selected from the group consisting of message content, message priority, message urgency, authorization data contained in the message, authentication data contained in the message, message source, and alarm data contained in the message.

43. The system of claim 42, wherein the message source may reflect at least one of the group consisting of a station identifier, store identifier, and an originating address.

44. The system of claim 21 further comprising a virtual tunnel database, the virtual tunnel database including parameters associated with configuring the virtual tunnel stored in the virtual tunnel database.

45. The system of claim 44, wherein the forwarding service is configured to identify port assignments in the transport layer header of the asset status message.

46. The system of claim 45, wherein the forwarding service is configured to configure the virtual tunnel in accordance with parameters stored in the virtual tunnel databased related to the identified port assignments.