Community internet drive

• US 9,800,464 B2
• Filed: 04/09/2014
• Issued: 10/24/2017
• Est. Priority Date: 01/03/2011
• Status: Active Grant

• Current Assignee: Planetary Data, LLC
• Original Assignee: Planetary Data, LLC
• Inventors: McEntee, Robert Alan
• Primary Examiner(s): Alam, Uzma
• Application Number:
  US14/249,228
• Publication Number:
  US 20140317225A1
• Time in Patent Office: 1,294 Days
• CPC Class Codes: G06F 13/00 Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units interface circuits for specific input/output devices G06F3/00 ; multiprogram control therefor G06F9/46; multiprocessor systems G06F15/16
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: G06F 16/1837 Management specially adapted to peer-to-peer storage networks topology management mechanisms of peer-to-peer networks H04L67/1042
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/53 using third party service providers

Abstract

Provided herein are devices, systems, methods and various means, including those related to providing a community internet drive that may utilize a centrally-managed hub as well as storage devices distributed among various networked machines. In some embodiments, the community internet drive can also include features to enable its users to promote and utilize the user'"'"'s trusted personal relationships while also enabling an open platform for peer-to-peer and/or other types of sharing schemes.

Claims

1. A method of managing data on a machine, comprising:

generating, by a first user machine, a request to be included in a community internet drive, wherein the first user machine is a non-commercial machine used predominately for personal computing by a first user;

transmitting the request to a remote machine;

receiving, from the remote machine, configuration data;

executing the configuration data including partitioning a local storage device of the first user machine into a private portion and a shared portion, wherein the shared portion is included in the community internet drive and the private portion is excluded from the community internet drive;

generating a first user profile associated with the first user, wherein the first user profile identifies a second user to be in a group with the first user;

providing the first user profile to the remote machine;

requesting, by the first user machine, control of a namespace from the remote machine, wherein the namespace provides a reference for access to first user data stored in the shared portion of the local storage drive;

wherein the first user data is associated with the first user and wherein the first user data is encrypted;

receiving, by the first user machine, control of the namespace from the remote machine, wherein the first user machine assigns access to the namespace to other users, the other users associated with machines, wherein control of the namespace is required to publish the first user data under the namespace; and

enabling, by the first user machine, a second user machine associated with the second user to decipher the first user data stored in the shared portion of the local storage device.

2. The method of claim 1 further comprising configuring the first user machine to access decrypted data associated with the second user.

3. The method of claim 2 further comprising, prior to configuring the first user machine to access the decrypted data associated with the second user, sending a share request from the first user machine to the remote machine.

4. The method of claim 1 further comprising sending the second user machine a notification in response to new data being added, by the first machine, to the shared portion of the local storage device.

5. The method of claim 1 further comprising:

receiving a request from the second user machine to decipher the first user data, wherein the request is generated by the second user machine attempting to access the first user data by using the namespace; and

in response to receiving the request from the second user machine to decipher the first user data, enabling the second user machine to decipher the first user data when the second user is in the group with the first user.

6. The method of claim 1, further comprising:

receiving third user data associated with a third user, wherein the third user is unassociated with the group including the first user and the second user; and

storing the third user data in the shared portion of the local storage device, wherein the third user data is encrypted such that the first user machine is unable to decipher the third user data.

7. A system, comprising:

a first user machine that is a non-commercial machine used predominately for personal computing by a first user, comprising;

a local storage device; and

one or more processors configured to;

generate a request to be included in a community internet drive;

cause the request to be transmitted to the remote machine;

receive configuration data provided by the remote machine;

execute the configuration data, including partitioning the local storage device of the first user machine into a private portion and a shared portion, wherein the shared portion is included in the community internet drive and the private portion is excluded from the community internet drive;

generate a first user profile associated with the first user, wherein the first user profile identifies a second user to be in a group with the first user;

cause the first user profile to be provided to the remote machine;

request control of a namespace from the remote machine, wherein the namespace provides a reference for access to first user data stored in the shared portion of the local storage drive;

wherein the first user data is associated with the first user profile and wherein the first user data is encrypted;

receive control of the namespace from the remote machine, wherein control of the namespace is required to publish the first user data under the namespace;

assign access to the namespace to other users, the other users associated with machines;

enable a second user machine associated with the second user to decipher the first user data stored in the shared portion of the local storage device.

8. The system of claim 7, wherein the first user machine is further configured to access decrypted data associated with the second user.

9. The system of claim 8, wherein the first user machine is further configured to receive a notification that the second user machine has accepted an invitation to be in the group with the first user machine prior to the first user machine being configured to access the decrypted data associated with the second user.

10. The system of claim 7 further comprising the first user machine being configured to send the second user machine a notification in response to new data being added, by the first machine, to the shared portion of the local storage device.

11. The system of claim 7 further comprising the first user machine being configured to:

receive a request from the second user machine to decipher the first user data, wherein the request is generated by the second user machine attempting to access the first user data by using the namespace; and

in response to receiving the request from the second user machine to decipher the first user data, enable the second user machine to decipher the first user data when the second user is in the group with the first user.

12. The system of claim 7, wherein the namespace allows assigning of a unique uniform resource identifier (“

URI”

) to the first user data.

13. The system of claim 12, where in the unique uniform resource identifier (“

URI”

) identifies the first user data as a unique asset based on a mount point of the first user data.

14. The system of claim 7, wherein the namespace includes geographic information related to the first user.

15. The system of claim 7, wherein the namespace is generated using subject matter data received from the first user.

16. The system of claim 7, wherein the one or more processors is further configured to:

receive third user data associated with a third user, wherein the third user is unassociated with the group including the first user and the second user;

store the third user data in the shared portion of the local storage device, wherein the third user data is encrypted such that the first user machine is unable to decipher the third user data.