Abstract: A first peer device receives distinct first and second metadata. The first metadata includes a common identifier having a one-to-one relationship with a common data piece of a data entity. The common data piece is common to the first peer device, a second peer device, and a third peer device. The second metadata includes one or more non-common identifiers. Each of the one or more non-common identifiers has a one-to-one relationship with a non-common data piece of the data entity that is common to a group of peer devices including the first peer device and excluding the third peer device. The first peer device also receives a third identifier from the second peer device. The first peer device determines whether the second peer device is in the group of peer devices based on whether the third identifier is included in the one or more non-common identifiers.

Abstract: A first peer device receives distinct first and second metadata. The first metadata includes a common identifier having a one-to-one relationship with a common data piece of a data entity. The common data piece is common to the first peer device, a second peer device, and a third peer device. The second metadata includes one or more non-common identifiers. Each of the one or more non-common identifiers has a one-to-one relationship with a non-common data piece of the data entity that is common to a group of peer devices including the first peer device and excluding the third peer device. The first peer device also receives a third identifier from the second peer device. The first peer device determines whether the second peer device is in the group of peer devices based on whether the third identifier is included in the one or more non-common identifiers.

Abstract: For individualized data communication of a data entity (200) to at least a first recipient and a second recipient, a descriptive file (100) is provided, which is supplemented by at least one identifier of a placeholder type. The descriptive file (100) also includes at least one identifier of a direct type, which is associated with a corresponding data piece (210) of the data entity (200). The identifier of the placeholder type is in turn associated with descriptive data (120) of an individualized data piece (220). By providing different types of the descriptive data (120) for different recipients, the identifier of the placeholder type may be used as a reference to different types of personalized content in the individualized data piece (220). This individualization may be obtained without modifying an identifier section (110) of the descriptive file (100).

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).

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).

Abstract: For individualized data communication of a data entity (200) to at least a first recipient and a second recipient, a descriptive file (100) is provided, which is supplemented by at least one identifier of a placeholder type. The descriptive file (100) also includes at least one identifier of a direct type, which is associated with a corresponding data piece (210) of the data entity (200). The identifier of the placeholder type is in turn associated with descriptive data (120) of an individualized data piece (220). By providing different types of the descriptive data (120) for different recipients, the identifier of the placeholder type may be used as a reference to different types of personalized content in the individualized data piece (220). This individualization may be obtained without modifying an identifier section (110) of the descriptive file (100).