Member Join Sample Clauses
Member Join. The next case for group key agreement is when a new member joins. When a new member joins to group, key tree should be updated. If the new member is
(a) shows an example of member M4 joining to a group. New member M4 is attached to node N<1,1> and new nodes N<2,2> and N<2,3> are attached to node N<1,1>. Member M2 is associated with node N<2,2> and member M4 is associated with node M<2,3>. Then keys K<1,1> and K<0,0> should be updated. Update process follows the group key agreement in the above subsection. N<0, 0> N<1, 0> N<1, 1> M2 N<2, 0> N<2, 1> N<0, 0> N<1, 0> N<1, 1> N<2, 0> N<2, 1> M1 M3 N<2, 2> N<2, 3> M2 M4 N<0, 0> N<0, 0> N<1, 0> N<1, 1> N<1, 0> N<1, 1> M2 N<2, 0> N<2, 1> N<2, 2> N<2, 3> N<2, 0> N<2, 1> M1 M3 M2 M4 M1 M3 M1 M3 (a) (b)
(a) Member join (b) Member leave
Member Join. Join is the procedure invoked by a user who wishes to become a member of a multicast group. In HGKM, users are categorized into passive and active users. Also, active users can only join virtual clusters. Therefore, there are three scenarios: an active user joins the system, a passive user joins a cluster and a passive user joins an existing virtual cluster. These scenarios are illustrated in Figure 3.2.
Member Join. In this stage, user nodes can join a group with fewer than five members. When the number of group members (n) is less than 5 (regardless of whether the group is empty or not, it is sufficient to check if the nodes are in a free state), a broadcast is sent to all users who have not joined the group, and empty positions are recorded as list[i] = 0,that represents that the i-th position is vacant. When a new user completes registration with the TA, obtains user ID and timestamp, and joins the group, the list[i] = 0 is set, indicating that this vacant position has been filled by a user.