Method and system for proximity-based content sharing
First Claim
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.
18 Assignments
0 Petitions
Accused Products
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.
-
Citations
20 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. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
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. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
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. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
Specification