Autonomous sharing of data between geographically proximate nodes

Patent metadata

Field	Value
Publication number	US-11032684-B2
Application number	US-201615193343-A
Country	US
Kind code	B2
Filing date	Jun 27, 2016
Priority date	Jun 27, 2016
Publication date	Jun 8, 2021
Grant date	Jun 8, 2021

Abstract

A communication system may include a plurality of geographically proximate nodes that communicate via one or more range-limited wireless technologies such as BLUETOOTH® low energy (BLE). An origin node may generate and communicate a first message responsive to detecting an event occurrence. The message may include an identifier associated with the origin node, data indicative of the event occurrence, a hop count, a maximum hop count, and a number of designated recipient nodes within the communication system. A first designated recipient node may, upon receiving the first message, attempt to confirm the event occurrence included in the first message. Upon confirming the event occurrence, the first designated recipient node may communicate a notification to an external third party. If unable to confirm the event occurrence, the first designated recipient node may generate and communicate a second message to a second designated recipient node included in the first message.

First claim

What is claimed:

1. A messaging node communicatively coupled to a first network and a second network, the messaging node comprising:
a processor; and
memory, including instructions which, when executed by the processor, cause the processor to:
determine an event occurrence, the event occurrence associated with a first recipient node connected to the messaging node via the first network;
transmit, via the first network, a first message to the first recipient node, wherein the first message includes: data representative of the event occurrence, and an identifier associated with a first recipient node, and wherein the first message further includes data indicative of a hop count and data indicative of a maximum hop count;
compare the data indicative of the hop count included in the first message with the data indicative of the maximum hop count included in the first message;
confirm the event occurrence in the data representative of the event occurrence;
classify an event occurrence type based on the data representative of the event occurrence;
determine a priority associated with the event occurrence type;
generate a second message, the second message including at least one of: the data representative of the event occurrence, the classified occurrence type, or the determined priority associated with the event occurrence type;
determine a message class for the second message based on at least one of: the classified occurrence type or the determined priority associated with the event occurrence type; and
selectively transmit the generated second message, via the second network to a second recipient node based on the determined message class, wherein the second message is transmitted to at least the second recipient node only when the hop count included in the first message is less than the maximum hop count included in the first message, and wherein the second message is not transmitted to a third recipient node based on the determined message class.

2. The messaging node of claim 1 , wherein the processor is further to:
verify authentication data included in the first message corresponds to the second recipient node; and
generate authentication data that corresponds to the first recipient node for inclusion in the second message.

3. The messaging node of claim 1 , wherein the processor is further to:
autonomously and selectively transmit the generated second message to the second recipient node, wherein the second recipient node is autonomously selected based at least in part on the determined event occurrence type.

4. The messaging node of claim 1 , wherein the processor is further to:
autonomously and selectively transmit the generated second message to the second recipient node, the second recipient node autonomously selected based at least on the determined message class.

5. The messaging node of claim 1 , wherein the second message includes data indicative of one or more media files that include information indicative of the event occurrence.

6. The messaging node of claim 1 , wherein each of the messaging node, the first recipient node, the second recipient node, and the third recipient node is communicably coupled to at least one other node via a BLUETOOTH® low energy wireless communications interface.

7. The messaging node of claim 6 , wherein each of the messaging node, the first recipient node, the second recipient node, and the third recipient node are communicably coupled to the at least one other node via a BLUETOOTH® low energy advertising channel.

8. The messaging node of claim 1 , wherein each of the messaging node, the first recipient node, the second recipient node, and the third recipient node further include at least one sensor, the at least one sensor to provide a signal that includes the data indicative of the event occurrence.

9. The messaging node of claim 8 :
wherein the at least one sensor provides a signal that includes data indicative of an event occurrence sensed by the at least one sensor;
wherein the processor further generates a message that includes the data indicative of the event occurrence sensed by the at least one sensor; and
wherein the processor further communicates the generated second message to the second recipient node.

10. A messaging node communicatively coupled to a first network and a second network, the messaging node comprising:
a transceiver;
a processor; and
memory, including instructions which, when executed by the processor, cause the processor to:
determine an event occurrence, the event occurrence associated with a first recipient node connected to the messaging node via the first network;
cause the transceiver to transmit, via the first network, a first message to the first recipient node, wherein the first message includes: data representative of the event occurrence, and an identifier associated with a first recipient node, and wherein the first message further includes data indicative of a hop count and data indicative of a maximum hop count;
compare the data indicative of the hop count included in the first message with the data indicative of the maximum hop count included in the first message;
confirm the event occurrence in the data representative of the event occurrence;
classify an event occurrence type based on the data representative of the event occurrence;
determine a priority associated with the event occurrence type;
generate a second message, the second message including at least one of: the data representative of the event occurrence, the classified occurrence type, or the determined priority associated with the event occurrence type;
determine a message class for the second message based on at least one of: the classified occurrence type or the determined priority associated with the event occurrence type; and
cause the transceiver to selectively transmit the generated second message, via the second network to a second recipient node based on the determined message class, wherein the second message is transmitted to at least the second recipient node only when the hop count included in the first message is less than the maximum hop count included in the first message, and wherein the second message is not transmitted to a third recipient node based on the determined message class.

11. The messaging node of claim 10 , wherein the processor is further to:
verify authentication data included in the first message corresponds to the second recipient node; and
generate authentication data that corresponds to the first recipient node for inclusion in the second message.

12. The messaging node of claim 10 , wherein the processor is further to:
cause the transceiver to autonomously and selectively tra nsmit the generated second message to the second recipient node, wherein the second recipient node is autonomously selected based at least in part on the determined event occurrence type.

13. The messaging node of claim 10 , wherein the processor is further to:
cause the tra nsceiver to autonomously and selectively transmit the generated second message to the second recipient node, the second recipient node autonomously selected based at least on the determined message class.

14. The messaging node of claim 10 , wherein the second message includes data indicative of one or more media files that include information indicative of the event occurrence.

15. The messaging node of claim 10 , wherein each of the messaging node, the first recipient node, the second recipient node, and the third recipient node is communicably coupled to at least one other node via a BLUETOOTH® low energy wireless communications interface

Assignees

• Intel Corp

Inventors

• Booth Cory J
• Jordan Adam
• Payne Michael J
• Zafiroglu Alexandra C
• Ekandem Joshua
• Chhabra Jasmeet

Classifications

• H04L45/20

  Hop count for routing purposes, e.g. TTL · CPC title

• H04W4/70 Primary

  Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

• H04W4/80

  Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication · CPC title