Payment reconciliation in mixed-ownership low-power mesh networks

• US 9,992,658 B2
• Filed: 12/16/2016
• Issued: 06/05/2018
• Est. Priority Date: 04/19/2013
• Status: Active Grant

• Current Assignee: Cubic Corporation, RSAE Labs Incorporated
• Original Assignee: Cubic Corporation
• Inventors: Berenberg, Paul
• Primary Examiner(s): Shah, Chirag
• Assistant Examiner(s): PERSAUD, AMARNAUTH G
• Application Number:
  US15/382,023
• Publication Number:
  US 20170105109A1
• Time in Patent Office: 536 Days
• Field of Search: None
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1435 volume-based
• CPC Class Codes: H04L 12/1453 Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04M 15/50 for cross-charging network operators
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 15/8061 Selecting least cost route depending on origin or type of service
• CPC Class Codes: H04M 15/8214 Data or packet based
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 64/00 Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

Systems and methods that enable scalable, cost-effective payment reconciliation between owners of devices at least temporarily connected in or to a particular low-power, ad hoc mesh network.

Claims

1. A network device for communicating data in a mixed-ownership low-power mesh network, comprising:

a battery;

a wireless interface; and

a processing unit coupled with the battery and the wireless interface, configured to cause the network device to;

track packet traffic routed by the network device to other network devices at least temporarily connected to the mesh network, wherein the packet traffic comprises a plurality of packets that each includes a routing record;

identify an identifier associated with at least one of the other network devices;

append accounting information to a particular routing record each time a packet travels through a particular network device, wherein appending accounting information comprises creating a new entry for a particular one of the other network devices and associating a particular number of units of data with the new entry;

detect a trigger;

aggregate, in response to the detected trigger, data that specifies the network device served as a router for data for at least some of the other network devices that are associated with a particular entity other than an entity associated with the network device;

alter the accounting information;

transfer the altered accounting information over the mesh network at least one of the other network devices that is at least temporarily connected to the mesh network that represents a total number of units of data routed by the network device for each originator network device address, wherein the at least one of the other network devices routes the altered accounting information to a reconciliation server; and

purge the accounting information from the network device.

2. The network device of claim 1, further comprising:

a user readable interface configured to provide a user with information.

3. The network device of claim 1, further comprising:

a global positioning system unit configured to detect a location of the network device.

4. The network device of claim 1, wherein:

each routing record comprises a time to live (TTL) entry; and

the processing unit is further configured to cause the network device to, when no updates are made to the TTL for a given packet, purge the routing record associated with the given packet.

5. The network device of claim 1, wherein the processing unit is further configured to cause the network device to:

add a new record to the routing record for each packet from a new originator network device.

6. The network device of claim 1, wherein the processing unit is further configured to cause the network device to:

detect that a leading router is lost from the routing record associated with a particular packet; and

in response to the detection, purge all records associated with the lost leading router from the routing record associated with the particular packet.

7. The network device of claim 6, wherein the processing unit is further configured to cause the network device to:

prior to purging all the records associated with the lost leading router from the routing history associated with the particular packet, store all the records associated with the lost leading router from the routing record associated with the particular packet in an accounting file.

8. The network device of claim 7, wherein the processing unit is further configured to cause the network device to:

append the accounting file with new records or modifying counter values for the originator network device addresses that are already in the accounting file.

9. The network device of claim 8, wherein the processing unit is further configured to cause the network device to:

reset counters within the routing record associated with the particular packet to zero.

10. A method for communicating data in a mixed-ownership low-power mesh network, comprising:

tracking packet traffic routed by a network device to other network devices at least temporarily connected to the mesh network, wherein the packet traffic comprises a plurality of packets that each includes a routing record;

identifying an identifier associated with at least one of the other network devices;

appending accounting information to a particular routing record each time a packet travels through a particular network device, wherein appending accounting information comprises creating a new entry for a particular one of the other network devices and associating a particular number of units of data with the new entry;

detecting a trigger;

aggregating, in response to the detected trigger, data that specifies the network device served as a router for data for at least some of the other network devices that are associated with a particular entity other than an entity associated with the network device;

altering the accounting information;

transferring the altered accounting information over the mesh network to at least one of the other network devices that is at least temporarily connected to the mesh network that represents a total number of units of data routed by the network device for each originator network device address, wherein the at least one of the other network devices routes the altered accounting information to a reconciliation server; and

purging the accounting information from the network device.

11. The method of claim 10, further comprising:

identifying ownership for each originator network device address;

summing the number of units of data for each originator network device address with shared ownership; and

sending the summed number of units of data to the another network device with an identifier of ownership.

12. The method of claim 10, further comprising:

compressing data that represents a total number of units of data routed by the network device for each originator network device address.

13. The method of claim 12, further comprising:

encrypting and authenticating the data that represents the total number of units of data routed by the network device for each originator node address.

14. The method of claim 10, further comprising:

nullifying data that represents a total number of units of data routed by the network device for at least one particular originator network device address prior to transferring the altered accounting information to the another network device.

15. The method of claim 10, further comprising:

determining ownership of the another network device; and

sending data that represents the total number of units of data routed by the network device for each originator network device address when a fee for routing data by the another network device is determined to be zero.

16. The method of claim 10, further comprising:

receiving notification from the another network device confirming receipt of the data that represents the total number of units of data routed by the network device for each originator network device address.

17. The method of claim 10, further comprising:

continuing monitoring packet traffic routed by the particular network device of the mesh network during the sending; and

identifying originator network device address and number of units of data for each particular packet of the packet traffic during the sending.

18. The method of claim 10, further comprising:

modifying an existing data structure maintained by the particular network device to include one or both of a particular originator network device address and a total number of units of data routed by the particular network device for the particular originator network device address.

19. The method of claim 10, wherein:

the accounting information comprises one or both of data that represents the total number of units of data routed by the particular network device for each originator network device address or data that represents a unique identifier for each originator network device address.