mzr: a multicast protocol for mobile ad hoc networks

29
MZR: A Multicast Protocol for Mobile Ad Hoc Networks Vijay Devarapalli Nokia research Cente r 313 Fairchild Drive, Mountain View, CA 94 043 Deepinder Sidhu Maryland Center for Telecom R esearch University of Maryland Baltim ore County 1000 Hilltop Circle, Baltimore,MD 21250 2001. IEEE International Conference on, Volume: 3 報報報 報報報 報報報報 報報報 報報報報報報報

Upload: mikayla-ward

Post on 31-Dec-2015

34 views

Category:

Documents


0 download

DESCRIPTION

MZR: A Multicast Protocol for Mobile Ad Hoc Networks. Deepinder Sidhu Maryland Center for Telecom Research University of Maryland Baltimore County 1000 Hilltop Circle, Baltimore,MD 21250. Vijay Devarapalli Nokia research Center 313 Fairchild Drive, Mountain View, CA 94043. - PowerPoint PPT Presentation

TRANSCRIPT

MZR: A Multicast Protocol for Mobile Ad Hoc Networks

Vijay Devarapalli

Nokia research Center

313 Fairchild Drive,

Mountain View, CA 94043

Deepinder Sidhu

Maryland Center for Telecom Research

University of Maryland Baltimore County

1000 Hilltop Circle,

Baltimore,MD 21250

2001. IEEE International Conference on, Volume: 3

報告人:劉旭濃 淡江大學 研究所 在職專班二年級

Outline

Introduction to MZR (Multicast routing protocol based on Zone Routing).

Related Work.ZRP (Zone Routing Protocol)MZR (Multicast routing protocol based

on Zone Routing)SimulationConclusions

MZR : Multicast routing protocol based on Zone Routing

Source-Initiated.On-Demand.Create Tree by Zone Routing Mechanism.Independent of Underlying Unicast Protoc

ol.Topology Change Localized.

Related Work (ODMRP)

On-Demand Multicast Routing Protocol.Mesh Based.Mesh Created between Sender and Receiver.Mesh Created Using Forwarding Group.Excessive Overhead incurred in Keeping the

Forwarding Group Current.The Global Flooding of JOIN-REQUEST

Packet.

Related Work (AMRoute)

Adhoc Multicast Routing Protocol.Share Tree Based.Tree Involve only Group Member.Tree Links are Created as Unicast Tunnels.Depends Heavily on Underlying Unicast Prot

ocol.

Routing Protocol in Ad Hoc Network

Pure Proactive : 1.Overhead of keep routing information current. 2.Topological changes widely in the network.Pure Reactive : 1.Route Information delay . 2.Global Flooding-Search Procedure.

ZRP : Zone Routing Protocol(Hybrid)

Define Radius of Zone (Hops).Get Zone Information (Border Nodes,Neig

hbors).Get IntraZone Routing Table.Route-Request through Border Node.Route-Reply from Nodes Outside.Get InterZone Routing Table.

ZRP : Zone Routing Protocol

Define Radius of Zone (Each Node).

Transmission Radius set to “2” hops.

A

G

S

F

E

B

C

D

Current Node Zone

Board Nodes of Zone

ZRP : Zone Routing Protocol

Get Zone Information and Routing Table.(Each Node)

A

G

S

F

E

B

C

D

NextHop Dest.

S A

S B

S F

B C

B D

F E

F G

ZRP : Zone Routing Protocol

Route-Request through Border Node (Unicast).

A

G

S

F

E

B

C

D

R

I’s Routing Table

NextHop Dest.

J R

H

I

J

ZRP : Zone Routing Protocol.

Route-Reply and Routing Table.

A

G

S

F

E

B

C

D

R

H

I

NextHop Dest.

D R

S’s Routing Table D’s Routing Table H’s Routing Table I’s Routing Table

NextHop Dest.

H R

NextHop Dest.

I R

NextHop Dest.

J R

J

Why ZRP

A Hybrid Routing Protocol.

→Proactive and Reactive.Proactive Procedure (IntraZone).

→Limit the Scope.Reactive Procedure (InterZone).

→Flooding Search through Board Node.

MZR: Protocol Description

Proactive Protocol: →Run inside Zone, maintain an up-to-date

routing table.

Reactive Protocol: →On-Demand and initiate by source to

create multicast tree.

MZR:Multicast Tree Creation

Multicast routing entry : Session_ID Source_ID,Group_ID Pair Upstream Node ID A List of Downstream Node IDMessage cache.Tree Creation : 1. Initiate inside zone. 2. Extend to entire network.

MZR:Multicast Tree Creation (Inside Zone)

Source send TREE-CREATE to each node through unicast.

Node set reverse route entry (route inactive).Member send TREE-CREATE-ACK back to

Source through reverse route path.Set Downstream nodes list when received T

REE-CREATE-ACK (route active).

MZR:Multicast Tree Creation (Inside Zone)

A

G

S

F

E

B

C

Member node

Route node

Source node

TREE-CREATE

TREE-CREATE-ACK

Ses_ID Sou_ID Grp_ID Up_ID Dwn_ID

23 S 45 Null Null

23 S 45 S Null

23 S 45 C Null

S

C

D

D

23 S 45 Null A B C

23 S 45 S D

23 S 45 C Null

S

C

D

TREE-CREATE

TREE-CREATE-ACK

MZR:Multicast Tree Creation (Extend to Entire Network)

Source send TREE-PROPAGATE to border nodes through unicast with TTL=Zone Radius.

Border nodes send TREE-CREATE to zone nodes (Like Tree Create inside Zone).

Border node send TREE-CREATE-ACK back to source for zone nodes.

Border nodes send TREE-PROPAGATE to it’s border nodes.

Multiple routing zone.

MZR:Multicast Tree Creation (Extend to Entire Network)

A

P S

N

E

B

J

D

C

O

F

G

R

Q

H

I

K

L

MT

Member node

Route node

Source node

TREE-CREATE

TREE-CREATE-ACKTREE-PROPAGATE

MZR: Tree Maintenance - tree refresh

Route entry lifetime.Source send TREE-REFRESH every

REFRESH-INTERVAL down the tree.Node reset timer and resend the packet. Stop sending if finish data transmission.Ensure tree is maintained during multicast.

MZR: Tree Maintenance - reaction to link break

The downstream node have to detecting link break and reconfiguring the tree.

Send JOIN-REQUEST to all zone nodes with TTL=Zone Radius.

1.Zone node send JOIN-ACK and add multicast route entry.

2.Send JOIN-PROPAGATE to border nodes and another JOIN-REQUEST will be send by border node to it’s zone nodes.

Branch reconstruction localize.

MZR: Tree Maintenance - reaction to link break

A

H

C

F

E

B

G

D

IJ

Member node

Route node

Multicast path

JOIN-REQUEST

JOIN-ACK

1.Node E move.

2.Link A to E and E to F break.

3.Node A send JOIN-REQUEST to

all zone nodes.

4.Node G reply JOIN-ACK to A.

5.Multicast path create from G to

A.

MZR: Tree Maintenance - tree prunes

Node send TREE-PRUNE to it’s upstream node.

Upstream node remove from multicast route entry.

Route node send TREE-PRUNE if the list of downstream node is empty.

Simulation Environment

50 Mobile nodes.500m x 500m grid.Simulation execute for 300 seconds.Wireless link capacity 2Mbps.Transmission range 100mSource generate multicasting data

64Kbps.Packet size 500bytes.Zone radius = two hops.

Packet Delivery Ratio for three active sessions as the mobility increase

0

0.2

0.4

0.6

0.8

1

1.2

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Node Speed(m/sec)

Packe

t D

eliv

ery

Ratio

Tree 20Tree 25Tree 47

Session ID

Total routing overhead as the node mobility increases ;pause time of 10 secs

0

0.05

0.1

0.15

0.2

0.25

0.3

0.35

0.4

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Node Speed(m/sec)

Routing O

verh

ead

Total routing overhead as the group size changes;pause time of 10 secs and a uniform speed of 5m/sec

0

0.1

0.2

0.3

0.4

0.5

0.6

0 5 10 15 20 25 30 35 40 45 50

Group Size

Routing O

verh

ead

Total routing overhead as the simulation proceeds for different group size;pause time of 10 secs and

a speed of 5m/sec

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

5 20 35 50 65 80 95 110 125 140 155 170 185 200 215 230 245 260 275 290

Simulation Time (seconds)

Routing O

verh

ead

5 10 20

30 40 50

Group Size

Total packet delivery ratio as the group changes;pause time of 10 secs and a speed of 5m/sec

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

0 5 10 15 20 25 30 35 40 45 50

Group Size

Packe

t D

eliv

ery

Ratio

CONCLUSIONS

Proactive protocol inside Zone and Reactive on entire network.

Topology changed localize.MZR does not depend on any underlying uni

cast routing protocol.Instead of flooding using border node.Performance analysis, Routing overhead, Th

roughput