13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

184 G. Cal<strong>in</strong>escu< nodeID, pieceID, coord<strong>in</strong>ates 1 , coord<strong>in</strong>ates 2 , counter >. Any node y receiv<strong>in</strong>gsuch a message evaluates if it has neighbors <strong>in</strong> the rigid piece, and if yes, asabove, it can compute two sets S 1 and S 2 of nodes <strong>in</strong> the rigid piece which couldbe the common neighbors with v - assum<strong>in</strong>g v has coord<strong>in</strong>ates coord<strong>in</strong>ates 1 orcoord<strong>in</strong>ates 2 with respect to the rigid piece. At least one of S 1 and S 2 is a setof col<strong>in</strong>ear po<strong>in</strong>ts, and if both are, they co<strong>in</strong>cide. That set of col<strong>in</strong>ear po<strong>in</strong>ts isthe set of neighbors common to y and v <strong>in</strong> the rigid piece.All cases are taken care of and we conclude:Theorem 3. There is a distributed algorithm which, under the assumption thatevery node can estimate the distance to every adjacent node, computes for everynode v the set of its 2-hop neighbors N 2 (v) and the l<strong>in</strong>ks <strong>in</strong> between N 1 (v) andN 2 (v) with a total of O(n) messages each of size O(log n) bits.5 Updat<strong>in</strong>g the 2-Hop NeighborhoodsIn this section we discuss the message complexity of updat<strong>in</strong>g the 2-hop neighborhoodsdue to changes <strong>in</strong> network topology. We do not address updat<strong>in</strong>g thevirtual backbone as this was done <strong>in</strong> [2]. The proposed protocol is straightforwardand does not use the virtual backbone. We assume geographical knowledgeis available <strong>in</strong> this section.Before leav<strong>in</strong>g the network, a node u uses its knowledge to let its 2-hopneighborhs know the fact it is leav<strong>in</strong>g as described below. First the node ucomputes a maximal <strong>in</strong>dependent set (MIS) <strong>in</strong> the graph <strong>in</strong>duced <strong>by</strong> its 2-hopneighborhs. Then u computes at most one “connector” node for each MIS node.As before, MIS is a dom<strong>in</strong>at<strong>in</strong>g set, and us<strong>in</strong>g an area argument, has constantsize. Node u prepares an < ID, position, leav<strong>in</strong>g, relay > message, with its ownID and position, the fact that it is leav<strong>in</strong>g the network, and the full list of relaynodes. Each node, after receiv<strong>in</strong>g such a message, make a note that u is leav<strong>in</strong>gand updates its 2-hop neighborhood accord<strong>in</strong>gly, and, if it f<strong>in</strong>ds itself <strong>in</strong> the listof relay nodes, rebroadcast the message once.When a node v jo<strong>in</strong>s the network, it will broadcasts its ID and position.Every exist<strong>in</strong>g node which receives this message will rebroadcast the ID andposition of v. Every node y receiv<strong>in</strong>g such a message, will update its stored 2-hopneighborhood to reflect the presence of v. Ify is adjacent to v, it will broadcastits ID and position. If y is a 2-hop neighbor of v, it selects a common neighborx and asks x to relay to v the position and ID of y. The total bit complexity ofmessage is O(q log n), where q is the size of the 2-hop neighborhood of v, and itcannot be improved <strong>by</strong> more than a constant factor s<strong>in</strong>ce v must f<strong>in</strong>d out theIDs of the nodes <strong>in</strong> its 2-hop neighborhood.6 ConclusionsThe virtual backbone of Alzoubi, Wan, and Frieder [2,21] can be constructedwithout any geographical knowledge: their algorithm “operates” directly on the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!