Method and system for proximity-based content sharing

• US 10,476,554 B2
• Filed: 06/13/2011
• Issued: 11/12/2019
• Est. Priority Date: 06/13/2011
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Gartner, Jeff, Javed, Rabail
• Primary Examiner(s): Pan, Yuwen
• Assistant Examiner(s): Sherif, Fatuma G
• Application Number:
  US13/159,189
• Publication Number:
  US 20120315846A1
• Time in Patent Office: 3,074 Days
• Field of Search: 455 411, 455 412, 455425, 455411
• CPC Class Codes: H04B 5/48 Transceivers
• CPC Class Codes: H04B 5/72 for local intradevice communication
• 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

Abstract

A system includes a combined NFC and Bluetooth interface that can interact with one or more other devices that also include the combined NFC and Bluetooth interface. A processor in the device executes an application that includes a thin client and a security wrapper. The thin client can package content in a packet with security settings and send the packet to the other device. Further, the thin client can accept packets from other devices. Based on one or more user settings and/or a level of trust between the devices, the thin client can determine if the packet should be accepted or rejected. If accepted, the thin client can store the content, located within the packet, for the user.

Claims

1. A method for managing packets in a device, comprising:

a processor executing a thin client receiving a packet from either a near field communication (NFC) or a Bluetooth interface, wherein the packet is received from another device in spatial proximity, wherein the packet comprises an identifier that identifies at least one of a conference or meeting of a group of people, wherein the identifier that identifies the at least one of the conference or meeting of the group of people is used by the thin client to determine if the packet should be rejected,

storing one or more user settings in a setting database;

storing secure content received over either the NFC interface or the Bluetooth interface in a quarantine database;

storing content received over either the NFC interface or the Bluetooth interface in an information database;

determining if the packet should be rejected based on the device and the other device being in spatial proximity and based on the identifier; and

applying the following rules;

if the packet should be rejected, the thin client erases the packet; and

if the packet should not be rejected, the thin client stores content in the packet into the information database.

2. The method as defined in claim 1, wherein the device is one of a communication device or a broker.

3. The method as defined in claim 2, wherein the processor executing the thin client further:

receiving a proximity signal from the other device;

determining if there is content in an information database to push to the other device in response to receiving the proximity signal;

if there is no content to push, ignoring the proximity signal; and

if there is content to push, the processor executing the thin client creating a packet to be sent over either the NFC interface or the Bluetooth interface, sending the packet to either the NFC interface or the Bluetooth interface, and either the NFC interface or the Bluetooth interface pushing the packet to the other device.

4. The method as defined in claim 1, wherein the device is a separate device that brokers messages between a plurality of separate communication devices.

5. The method as defined in claim 1, wherein the identifier that identifies the at least one of the conference or meeting of the group of people is an in-person meeting of the group of people.

6. The method as defined in claim 5, wherein the identifier for the in-person meeting of the group of people is a meeting topic that identifies an individual meeting topic for closely spaced meeting rooms.

7. The method as defined in claim 6, wherein the meeting topic further identifies materials pertaining to the in-person meeting of the group of people.

8. A content sharing device, comprising:

a near field communication (NFC) interface and/or

a Bluetooth interface;

a memory;

a processor in communication with the memory, and the NFC interface or the Bluetooth interface, the processor (a) receives a packet from either the NFC interface or the Bluetooth interface, wherein the packet is received from another device in spatial proximity, wherein the packet comprises an identifier that identifies at least one of a conference or meeting of a group of people, and wherein the identifier that identifies the at least one of the conference or meeting of the group of people is used by the processor to determine if the packet should be rejected, and (b) executes one or more modules, the modules comprising;

a settings database that stores one or more user settings;

a quarantine database that stores secure content received over either the NFC interface or the Bluetooth interface;

an information database that stores content received over either the NFC interface or the Bluetooth interface; and

a thin client in communication with the settings database, the quarantine database, and the information database, wherein the thin client;

determines if the packet should be rejected based on the content sharing device and the other device being in spatial proximity and based on the identifier; and

applies the rules;

if the packet should be rejected, the thin client erases the packet; and

if the packet should not be rejected, the thin client stores content in the packet into the information database.

9. The content sharing device as defined in claim 8, wherein the content sharing device is a communication device or a broker.

10. The content sharing device as defined in claim 9, wherein the thin client further:

receives a proximity signal from the other device;

in response to receiving the proximity signal, determines if there is content in the information database to push to the other device;

if there is no content to push, ignores the proximity signal;

if there is content to push, creates a packet to be sent over either the NFC or Bluetooth interface to the other device; and

sends the packet to either the NFC or Bluetooth interface.

11. The content sharing device as defined in claim 10, wherein the thin client further:

determines if the packet should be quarantined; and

stores the packet in the quarantine database.

12. The content sharing device as defined in claim 8, further comprising a user interface in communication with the processor, wherein the user interface:

provides information about the packet to a user; and

receives a signal from the user indicating the user wants to store the content in the packet.

13. The content sharing device of claim 8, wherein the content sharing device layers, in a hierarchical structure, information about materials or content, based on a trust relationship between parties in the conference or meeting, of the group of people in order to manage document versioning between the parties in the conference or meeting, of the group of people.

14. A content sharing device, comprising:

a wireless interface;

a memory;

a processor in communication with the memory, and the wireless interface, the processor (a) receives a packet from wireless interface, wherein the packet is received from another device in spatial proximity, wherein the packet comprises an identifier that identifies at least one of a conference or meeting of a group of people, wherein the identifier that identifies the at least one of the conference or meeting of the group of people is used by the processor to determine if the packet should be rejected, and (b) executes one or more modules, the modules comprising;

a settings database that stores one or more user settings;

a quarantine database that stores secure content received over the wireless interface;

an information database that stores content received over the wireless interface; and

a thin client in communication with the settings database, the quarantine database, and the information database, wherein the thin client;

determines if the packet should be rejected based on the content sharing device and the other device being in spatial proximity and based on the identifier; and

applies the rules;

if the packet should be rejected, the thin client erases the packet; and

if the packet should not be rejected, the thin client stores content in the packet into the information database.

15. The content sharing device as defined in claim 14, wherein the identifier for the conference or meeting of a group of people is an in-person meeting of a group of people.

16. The content sharing device as defined in claim 15, wherein the identifier for the in-person meeting of the group of people is for a meeting topic that identifies different meeting topics in differently closely spaced meeting rooms.

17. The content sharing device as defined in claim 16, wherein the meeting topic further identifies materials pertaining to the in-person meeting of the group of people.

18. The content sharing device as defined in claim 14, wherein the thin client further:

receives a proximity signal from the other device;

in response to receiving the proximity signal, determines if there is content in the information database to push to the other device;

if there is no content to push, ignores the proximity signal;

if there is content to push, creates a packet to be sent over either the wireless interface to the other device; and

sends the packet to the wireless interface.

19. The content sharing device as defined in claim 18, wherein the thin client further:

determines if the packet should be quarantined; and

stores the packet in the quarantine database.

20. The content sharing device as defined in claim 14, further comprising a user interface in communication with the processor, wherein the user interface:

provides information about the packet to a user; and

receives a signal from the user indicating the user wants to store the content in the packet.