Peer-to-peer communication of non-common data

• US 9,277,006 B2
• Filed: 03/29/2010
• Issued: 03/01/2016
• Est. Priority Date: 11/25/2009
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: El Khayat, Ibtissam, Lepropre, Pierre
• Primary Examiner(s): Parry, Chris
• Assistant Examiner(s): HOULIHAN, STEPHEN J
• Application Number:
  US13/510,984
• Publication Number:
  US 20130204936A1
• Time in Patent Office: 2,164 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments

Abstract

In individualized data communication of a data entity (200) between peers of a group, the data entity (200) includes at least one common data piece (210) and at least one non-common data piece (220). The at least one common data piece (210) is shared by all peers of the group, whereas the at least one non-common data piece (220) is shared by a subgroup of the group. A non-common data identifier (600) is used to identify the at least one non-common data piece (220). By receiving the non-common data identifier (600), one peer of the group may determine whether another peer of the group is sharing the same non-common data piece (220).

Claims

1. A method of communicating a data entity in a group of peers, wherein the data entity comprises at least one common data piece shared by all peers of the group and at least one non-common data piece shared only by a subgroup of the group of peers, wherein the peers of the group attempt to obtain the at least one common data piece or have the at least one common data piece available, and wherein only the peers of the subgroup try to obtain the at least one non-common data piece or have the at least one non-common data piece available, wherein the method comprises:

a first peer of the group receiving a descriptive file of the data entity, the descriptive file comprising;

at least one identifier of a direct type having a one-to-one relation to the at least one common data piece; and

at least one identifier of a placeholder type associated with descriptive data of the at least one non-common data piece;

the first peer of the group receiving a non-common data identifier from a second peer of the group, the non-common data identifier identifying at least one non-common data piece;

the first peer of the group determining, based on the non-common data identifier and the descriptive data, whether the second peer belongs to the subgroup sharing the at least one non-common data piece.

2. The method of claim 1 comprising the first peer, in response to determining that the second peer belongs to the subgroup sharing the non-common data piece, requesting the at least one non-common data piece from the second peer.

3. The method of claim 1 wherein the non-common data identifier comprises a hash value calculated on the basis of the at least one non-common data piece.

4. The method of claim 3 wherein the hash value is a hash value of an individual hash value of the at least one non-common data piece.

5. The method of claim 1 wherein the non-common data identifier comprises a position indicator, the position indicator indicating the position of the at least one non-common data piece in a sequence of the at least one common data piece and the at least one non-common data piece.

6. The method of claim 5 wherein the non-common data identifier identifies a plurality of consecutive non-common data pieces and the position indicator indicates a range of the consecutive non-common data pieces in the sequence.

7. The method of claim 1 further comprising:

the first peer providing, for each other peer of the group, a corresponding sharing information bitfield;

storing sharing information indicating whether one of the peers belongs to the subgroup sharing the non-common data piece in the sharing information bitfield for the corresponding peer.

8. The method of claim 7 wherein the sharing information bitfield comprises a bit corresponding to the at least one non-common data piece, a value of the bit indicating whether the corresponding peer belongs to the subgroup sharing the non-common data piece.

9. The method of claim 1 further comprising:

the first peer providing, for each other peer of the group, a corresponding availability information bitfield;

receiving an availability indicator associated with the at least one of the peers, the availability indicator indicating whether the at least one non-common data piece is available at the corresponding peer;

storing availability information in the availability information bitfield indicating whether the at least one non-common data piece is available at the corresponding peer.

10. The method of claim 9 wherein the availability indicator also indicates whether the at least one common data piece is available at the corresponding peer.

11. The method of claim 9 wherein the storing availability information comprises storing availability information indicating that the non-common data piece is available at one of the peers in response to:

the received availability indicator associated with the corresponding peer indicating that the non-common data piece is available at this peer; and

the received non-common data identifier associated with the corresponding peer indicating that the peer belongs to the subgroup sharing the non-common data piece.

12. The method of claim 1 further comprising:

the first peer, if the non-common data piece is locally available at the first peer, generating a local availability indicator indicating that the non-common data piece is locally available;

the first peer transmitting the local availability indicator to at least one other peer determined to belong to the subgroup sharing the non-common data piece.

13. The method of claim 1 further comprising:

the first peer receiving the at least one common data piece;

the first peer verifying the at least one common data piece based on the associated identifier of the direct type;

the first peer retrieving the descriptive data of the at least one non-common data piece;

the first peer receiving the at least one non-common data piece;

the first peer verifying the non-common data piece based on the retrieved descriptive data.

14. The method of claim 13 further comprising the first peer calculating a local non-common data identifier on the basis of the descriptive data of the at least one non-common data piece.

15. The method of claim 14 further comprising the first peer transmitting the local non-common data identifier to at least one other peer of the group.

16. The method of claim 15 further comprising:

the first peer comparing the local non-common data identifier to the received non-common data identifier.

19. The method of claim 1, wherein different versions of said data entity are respectively shared amongst different subgroups of the group of peers, wherein each different version has:

the same common data pieces that are shared amongst all peers of the group; and

different non-common data pieces that are specific to that version and that are only shared amongst the peers in the corresponding subgroup.

17. A first peer device of a group of peers, the group of peers communicating a data entity, wherein the data entity comprises at least one common data piece shared by all peers of the group and at least one non-common data piece shared only by a subgroup of the group of peers, wherein the peers of the group attempt to obtain the at least one common data piece or have the at least one common data piece available, and wherein only the peers of the subgroup try to obtain the at least one non-common data piece or have the at least one non-common data piece available, the first peer device comprising:

an interface configured to communicate with other devices of the group of peers;

a processor operatively connected to the interface;

wherein the interface is configured to receive a descriptive file of the data entity, the descriptive file comprising;

at least one identifier of a direct type having a one-to-one relation to the at least one common data piece; and

at least one identifier of a placeholder type associated with descriptive data of the at least one non-common data piece;

wherein the interface is further configured to receive a non-common data identifier from a second peer of the group, the non-common data identifier identifying at least one non-common data piece;

wherein the processor is configured to determine, based on the non-common data identifier and the descriptive data, whether the second peer belongs to the subgroup sharing the non-common data piece.

18. The device of claim 17 wherein the processor is further configured to, in response to determining that the second peer belongs to the subgroup sharing the non-common data piece, request the non-common data piece from the second peer via the interface.

20. A method of sharing different versions of the same item of content amongst different respective subgroups of peers in a peer-to-peer (P2P) network, the method implemented by a first peer in the P2P network and comprising:

receiving a descriptive file that is specific to a first one of the different versions of the item of content, wherein the descriptive file describes different pieces into which the item of content has been subdivided, the descriptive file comprising;

at least one identifier that directly identifies at least one common data piece of the item of content that is common to all versions of the item of content and that is shared amongst all peers in the P2P network;

at least one identifier that does not directly identify any particular piece of the item of content, but rather refers to descriptive data, wherein the descriptive data describes at least one non-common data piece that is specific to the first one of the different versions and that is shared amongst only peers in a first one of the subgroups;

receiving from a second peer in the P2P network a non-common data identifier that indicates to which of the different subgroups the second peer belongs; and

determining, based on the non-common data identifier and the descriptive data, whether the second peer belongs to the first subgroup sharing the at least one non-common data piece described by the descriptive file.