PEER TO PEER NETWORKING AND SHARING SYSTEMS AND METHODS

• US 20140196140A1
• Filed: 02/14/2012
• Published: 07/10/2014
• Est. Priority Date: 02/14/2012
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Gong, Michelle X.
• Granted Patent: US 9,294,562 B2
• Time in Patent Office: Days
• US Class Current: 726/10
• CPC Class Codes: H04L 12/5692 Selection among different networks
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers

Abstract

An embodiment includes peer-to-peer (P2P) pairing protocols that mutually authenticate both end points and do not rely upon a backend server or a central certificate provisioning server. An embodiment provides a persistent control path for sending inter-peer control information (e.g., synchronization messages). Another inter-peer path includes an “on-demand” data path enabled when a unit determines content is ready for sharing. After the content is shared, the data path may be deconstructed, which saves resources on both sides and makes the framework more scalable. Also, embodiments include graphical user avatars to whereby a first peer shares content with a second peer by dragging content over the avatar.

Claims

1. At least one storage medium having instructions stored thereon for causing system to perform a method comprising a first compute node:

establishing a persistent control path with a second compute node;

establishing an on-demand data path with the second compute node; and

communicating control information to the second compute node via the persistent control path while simultaneously communicating content to the second compute node via the on-demand data path.

2. The at least one medium of claim 1, the method comprising promptly disabling the established on-demand data path after communicating the content to the second compute node while simultaneously maintaining the persistent control path after communicating the control information to the second compute node.

3. The at least one medium of claim 1, the method comprising establishing the on-demand data path with the second compute node based on determining the content exists and is ready to be communicated to the second compute node.

4. The at least one medium of claim 1, the method comprising establishing the persistent control path and the on-demand data path with the second compute node via a peer-to-peer network, wherein the network is not contained within a single local network.

5. The at least one medium of claim 1, the method comprising establishing the persistent control path and the on-demand data path with the second compute node via a peer-to-peer network and not via a centralized server.

6. The at least one medium of claim 1, the method comprising:

receiving a second certificate corresponding to the second compute node;

determining the second certificate is recognized by the first compute node;

communicating a first certificate, corresponding to the first compute node, to the second compute node; and

establishing the persistent control path with the second compute node based on both of the first and second certificates.

7. The at least one medium of claim 1, the method comprising:

receiving a second certificate corresponding to the second compute node;

communicating a first certificate, corresponding to the first compute node, to the second compute node;

determining one of the first and second certificates is not recognized by one of the first and second compute nodes; and

based on determining one of the first and second certificates is not recognized by one of the first and second compute nodes, engaging in pairing that includes communicating a secret between the first and second compute nodes via an out-of-band channel and authenticating the second node based on the secret.

8. The at least one medium of claim 7, wherein authenticating the second compute node based on the secret includes authenticating the second compute node without using a central certificate server.

9. The at least one medium of claim 7, the method comprising the first node, during a subsequent session with the second node:

receiving another instance of the second certificate corresponding to the second compute node;

communicating another instance of the first certificate, corresponding to the first compute node, to the second compute node;

determining both of the first and second additional instances are respectively recognized by the first and second compute nodes; and

based on determining both of the first and second additional instances are respectively recognized by the first and second compute nodes, skipping pairing and establishing additional instances of the persistent control path and on-demand data path with the second compute node.

10. The at least one medium of claim 7, wherein the secret is included in one of a quick response (QR) code, near field communication (NFC), or an out-of-band channel communication.

11. The at least one medium of claim 7, the method comprising engaging in the pairing based on one of the first and second compute nodes accepting a pairing invitation.

12. The at least one medium of claim 1, the method comprising receiving a graphical user interface (GUI) element, which corresponds with the second compute node, from the second compute node based on establishing the persistent control path with the second compute node.

13. The at least one medium of claim 12, the method comprising communicating the content to the second compute node based on dragging a GUI element corresponding with the content to the GUI element corresponding to the second compute node.

14. The at least one medium of claim 1, wherein the control information includes networking synchronization information and the content includes one of video, music, and pictures.

15. (canceled)

16. (canceled)

17. An apparatus comprising a first compute node that further comprises:

at least one processor; and

control logic, coupled to the at least one processor, to;

establish a persistent control path with a second compute node;

establish an on-demand data path with the second compute node; and

communicate control information to the second compute node via the persistent control path while simultaneously communicating content to the second compute node via the on-demand data path.

18. The apparatus of claim 17, wherein the control logic is to promptly disable the established on-demand data path after communicating the content to the second compute node while simultaneously maintaining the persistent control path after communicating the control information to the second compute node.

19. The apparatus of claim 17, wherein the control logic is to:

receive a second certificate corresponding to the second compute node;

communicate a first certificate, corresponding to the first compute node, to the second compute node;

determine one of the first and second certificates is not recognized by one of the first and second compute nodes;

based on determining one of the first and second certificates is not recognized by one of the first and second compute nodes, engage in pairing that includes communicating a secret between the first and second compute nodes via an out-of-band channel and authenticating the second node based on the secret.

20. The apparatus of claim 19, wherein authenticating the second compute node based on the secret includes authenticating the second compute node without using a central certificate server.

21. The apparatus of claim 19, wherein the secret is included in one of a quick response (QR) code, near field communication (NFC), or an out-of-band channel communication.

22. The apparatus of claim 19, wherein the control logic is to engage in the pairing based on one of the first and second compute nodes accepting a pairing invitation.

23. The apparatus of claim 17, wherein the control logic is to receive a graphical user interface (GUI) element, which corresponds with the second compute node, from the second compute node based on establishing the persistent control path with the second compute node.

24. The apparatus of claim 23, wherein the control logic is to communicate the content to the second compute node based on dragging a GUI element corresponding with the content to the GUI element corresponding to the second compute node.

25. (canceled)