EP1633079A1

Method for managing elements of a peer-group

Abstract

For the creation and self-organization of peer-groups the JXTA protocol may be used, which includes messages such as peer or peer-group advertisements and services such as the discovery service. Conventional peer-groups of this type are static and need restart after any modification, e.g. a new service. A method for dynamically managing hardware and/or software elements, e.g. services, utilized and/or offered by such peer-groups comprises detecting a change within a peer-group (OZ), creating a new peer-group identifier, publishing within the peer-group a first peer-group advertisement message (PGA1) that includes the current and the new peer-group identifier and pointers to current services including the detected modification, accepting the new peer-group identifier by the other peer-group members, and publishing a second peer-group advertisement message (PGA2) in the superordinate peer-group (NPG), wherein both advertisement messages may be identical. Thus, peer-groups may operate continuously while peers modify, add or delete services.

EP1633079A1, drawing sheet 1
Sheet 1 of 5

Term

Term ended

Projected expiry passed 1 September 2024, 2.1 years ago.

  1. Priority and filed
  2. Published
  3. Projected expiry
  4. Today

10 claims: 9 independent, 1 dependent

  1. 1
    A method for managing software and/or hardware elements of a peer-group, the peer-group having a first group identifier assigned and comprising two or more peers, wherein a peer is a software element being associated with one or more hardware elements and has the first group identifier locally stored, characterized in including the following steps:- a first peer being a member of said peer-group (OZ) detecting a modification on a software or hardware element of the peer-group (OZ);- the first peer automatically generating a second group identifier;- the first peer sending out (S1) a first message (PGA) to the other members of the peer-group, the first message containing at least the first and second group identifiers and a pointer to said modified software or hardware element;- peers being members of said peer-group receiving said message, comparing the received first group identifier with their locally stored first group identifier and, upon both group identifiers being identical, replacing their locally stored first group identifier with the second group identifier;and - a peer being a member of said peer-group sending out (S2) a second message to members of a second peer-group, the second message containing at least the first and second group identifiers and a pointer to said modified software or hardware element.
  2. 3
    Method according to any of claims 1-2, wherein the first message also contains a list of software and hardware elements of the peer-group, and the peers being members of said peer-group store a local copy of a list of software and hardware elements of the peer-group, and upon reception of the first message update their local copy of said list.
  3. 4
    Method according to any of claims 1-3, wherein the first and second messages are XML formatted and the first and second group identifiers are stored in a separate section (GID_HISTORY) of the message.
  4. 5
    Method according to any of the preceding claims, wherein the peers belong to Wide Area Network.
  5. 6
    Method according to any of the preceding claims, wherein the first and second message contains also one or more further previous group identifiers.
  6. 7
    Method according to any of the preceding claims, wherein the peer-group uses the JXTA protocol.
  7. 8
    Method according to any of the preceding claims, wherein the peers send out peer advertisement messages, and upon reception of said second peer group identifier include it into their peer advertisement messages.
  8. 9
    Method according to any of the preceding claims, wherein the first peer sends the first message (S1) only if it is authorized by a security mechanism.
  9. 10
    A network element being a peer in a peer-to-peer network, the peer being a member of a peer-group defined by a unique group identifier, comprising - means for storing a current group identifier;- means for storing a peer identifier;- means for detecting modification of a software or hardware element relating to the current peer-group;- means for generating a new group identifier upon said detection of modification of software or hardware element;- means for sending a peer-group advertisement message to other peers, the message containing a data section specifying the current and the new group identifier and a pointer to said modified software or hardware element;- means for receiving a peer-group advertisement message sent by another peer;- means for comparing the stored current group identifier with the current group identifier contained in said received peer-group advertisement message, and for indicating both being identical;and - means for overwriting upon said indication the current group identifier with the received new group identifier.