Multicast- -Enabled Landmark Enabled Landmark Multicast (M- - - PowerPoint PPT Presentation

▶
multicast enabled landmark enabled landmark multicast m
SMART_READER_LITE
LIVE PREVIEW

Multicast- -Enabled Landmark Enabled Landmark Multicast (M- - - PowerPoint PPT Presentation

Oct 03, 2023 140 likes •402 views

Multicast- -Enabled Landmark Enabled Landmark Multicast (M- -LANMAR) : LANMAR) : (M Implementation and scalability Implementation and scalability YunJung Yi, Mario Gerla, JS Park, Yi, Mario Gerla, JS Park, Yeng Yeng Lee, SW Lee Lee, SW

slide-1
SLIDE 1

Multicast Multicast-

  • Enabled Landmark

Enabled Landmark (M (M-

  • LANMAR) :

LANMAR) : Implementation and scalability Implementation and scalability

YunJung YunJung Yi, Mario Gerla, JS Park, Yi, Mario Gerla, JS Park, Yeng Yeng Lee, SW Lee Lee, SW Lee Computer Science Dept Computer Science Dept University of California, Los Angeles University of California, Los Angeles

slide-2
SLIDE 2

The AINS Scenario The AINS Scenario

FLIR FLIR

slide-3
SLIDE 3

LANMAR LANMAR

  • Key insight:

Key insight: nodes move in teams/swarms nodes move in teams/swarms

  • Each team is mapped into a

Each team is mapped into a logical subnet logical subnet

  • IP

IP-

  • like Node address

like Node address = <subnet, host> = <subnet, host>

  • Address compatible with IPv6

Address compatible with IPv6

  • Team leader

Team leader (Landmark) (Landmark) elected in each group elected in each group

Logical Subnet Logical Subnet Landmark Landmark

slide-4
SLIDE 4

LANMAR (cont) LANMAR (cont)

Three main components in LANMAR:

Three main components in LANMAR:

(1)

(1) “local ” routing “local ” routing algorithm that keeps accurate algorithm that keeps accurate routes within local scope < k hops (e.g., Distance routes within local scope < k hops (e.g., Distance Vector) Vector)

(2)

(2) Landmark selection Landmark selection within each logical group within each logical group

(3)

(3) Landmark routes Landmark routes advertised to all nodes advertised to all nodes

Logical Subnet Logical Subnet Landmark Landmark

slide-5
SLIDE 5

LANMAR (cont) LANMAR (cont)

A packet to

A packet to “local” destination “local” destination is routed directly using is routed directly using local tables local tables

A packet to

A packet to remote destination remote destination is routed to is routed to corresponding Landmark corresponding Landmark

Once the packet is

Once the packet is “in sight” of Landmark “in sight” of Landmark, the direct , the direct route is found in local tables. route is found in local tables. Main benefit: Main benefit: routing O/H reduction routing O/H reduction => => scalability scalability

Logical Subnet Logical Subnet Landmark Landmark

slide-6
SLIDE 6

LANMAR Review LANMAR Review

Logical Subnet Logical Subnet Landmark Landmark

LM1 LM2 LM3

source source dest dest

Long haul routing local routing

  • 1. Node address = {subnet ID, Host ID}
  • 2. Lookup local routing table to locate dest fail
  • 3. Look up landmark table to find destination subnet LM1
  • 4. Send a packet toward LM1
slide-7
SLIDE 7

Scalable Ad hoc Scalable Ad hoc multicasting multicasting

  • Multicast (

Multicast (ie ie, transmit same message to all , transmit same message to all member of a group) critical in battlefield member of a group) critical in battlefield

  • “Multiple

“Multiple unicast unicast” does not scale ” does not scale

  • Current ad hoc

Current ad hoc multicast solutions: multicast solutions: inappropriate inappropriate

They do not exploit affinity team model

They do not exploit affinity team model

multicast tree approach is “fragile” to mobility;

multicast tree approach is “fragile” to mobility;

no congestion control; no reliable end to end delivery

no congestion control; no reliable end to end delivery

  • Proposed approach:

Proposed approach:

TEAM Multicast

TEAM Multicast

slide-8
SLIDE 8

swarm swarm

Command post Command post

Swarm Swarm Leader Leader

UAVs:

  • equipped with video, chemical sensors
  • read data from ground sensors
  • “fuse” sensor data inputs
  • multicast fused data to other teams

Team Multicasting

slide-9
SLIDE 9

Multicast example Multicast example

Attack! Attack! Attack! Attack! Attack!

Command Post All Task Force Nodes

slide-10
SLIDE 10

Tw o Tw o-

  • tier team multicast: M

tier team multicast: M -

  • LANMAR

LANMAR

  • Extension of LANMAR enabling

Extension of LANMAR enabling multicast multicast

  • Inter

Inter-

  • team

team communication: communication: unicast unicast tunneling from the source to the tunneling from the source to the representative of each subscribed team representative of each subscribed team

  • Intra

Intra-

  • team

team communication: scoped communication: scoped flooding flooding within a team within a team

slide-11
SLIDE 11

Source node LM2 LM3 Subscribed Teams LM4 Tunneling to landmarks Flooding Flooding Scope = 2 Scope = 2

M-LANMAR

slide-12
SLIDE 12

Advantages of M Advantages of M-

  • LANMAR

LANMAR

  • Reduced control traffic overhead

Reduced control traffic overhead

  • Scalable

Scalable to thousands of nodes to thousands of nodes

  • Enhanced

Enhanced Congestion control and Congestion control and Reliability Reliability (because of TCP control on (because of TCP control on unicast unicast tunnels) tunnels)

slide-13
SLIDE 13

M M-

  • LANMAR multicast

LANMAR multicast

slide-14
SLIDE 14
slide-15
SLIDE 15

M M-

  • LANMAR Implementation

LANMAR Implementation

User level

User level M M-

  • LANMAR daemon

LANMAR daemon on Linux

  • n Linux

M

M-

  • LANMAR daemon functions:

LANMAR daemon functions:

LANMAR routing

LANMAR routing

Group membership management

Group membership management

Packet forwarding engine for tunneling and scoped flooding

Packet forwarding engine for tunneling and scoped flooding

Compatible with any conventional multicast

Compatible with any conventional multicast application ( application (eg eg, , vic vic = = vi video deo c conferencing tool from

  • nferencing tool from

UCB) UCB)

slide-16
SLIDE 16

Testbed Testbed configuration configuration

3 teams (= 3 IPv4 subnets), 1 sender, 3 receivers

3 teams (= 3 IPv4 subnets), 1 sender, 3 receivers

Dell P4 laptop with Lucent Orinoco 802.11b

Dell P4 laptop with Lucent Orinoco 802.11b pcmcia pcmcia card card

CBR traffic (512B/packet, 5~15 packets/sec)

CBR traffic (512B/packet, 5~15 packets/sec)

Protocols:

Protocols: ODMRP; M ODMRP; M-

  • LANMAR

LANMAR

Sender

slide-17
SLIDE 17

LANMAR Addressing in IPv4

  • Each LANMAR group is an IPv4 subnet

Each LANMAR group is an IPv4 subnet

  • The address of a node then has format as <group

The address of a node then has format as <group-

  • ID, node

ID, node-

  • ID>

ID>

x x x x x x x x LANMAR Group ID Node ID Subnet Mask x x x x x x x x x x x x x x x xx x x x x x x x

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0

slide-18
SLIDE 18

LANMAR Addressing in IPv6

  • “

“Limited Limited-

  • Scope

Scope” ” IPv6 address format proposed in IETF IPv6 address format proposed in IETF Internet draft (<draft Internet draft (<draft-

  • templin

templin-

  • lsareqts

lsareqts-

  • 00.txt)

00.txt)

48 bits 16 bits 64 bits

  • LANMAR addressing: Keep the unique network ID field as

LANMAR addressing: Keep the unique network ID field as it is. Use the middle 16 bits to store group IDs. it is. Use the middle 16 bits to store group IDs.

48 bits 16 bits 64 bits

Group-ID Node ID Network ID

Subnet Mask 0000 … 000 11 … 11 00000000 … 0000000

slide-19
SLIDE 19

Experimental Results: Experimental Results: Delivery Ratio and Control Overhead Delivery Ratio and Control Overhead

0.0 0.2 0.4 0.6 0.8 1.0 1.2 5 10 15 Sending rate (packet/sec) Delivery ratio M-LANMAR delivery ratio ODMRP delivery ratio

  • M-LANMAR has higher Delivery Ratio than ODMRP: unicast

tunneling helps reliable data delivery as it incorporates RTS/CTS/ACK)

  • M-LANMAR has higher control overhead

0.0 0.5 1.0 1.5 2.0 2.5 5 10 15 Sending rate (packet/sec) Control Overhead M-LANMAR control overhead ODMRP control overhead

slide-20
SLIDE 20

Scalability Scalability

  • Objective: test M

Objective: test M-

  • LANMAR scalability

LANMAR scalability

  • Compared with

Compared with

ODMRP

ODMRP

Flooding

Flooding

  • Simulation Environment

Simulation Environment

QualNet

QualNet

1000 nodes

1000 nodes forming forming 36 teams 36 teams on

  • n 6000 x 6000 m

6000 x 6000 m2 field field

CBR traffic (

CBR traffic (512 bytes 512 bytes/packet, 1packet/sec) /packet, 1packet/sec)

slide-21
SLIDE 21

Simulation Results Simulation Results

  • As the number of multicast groups increases

As the number of multicast groups increases

ODMRP suffers from large control overhead and collisions

ODMRP suffers from large control overhead and collisions

M

M-

  • LANMAR achieves high delivery ratio (by

LANMAR achieves high delivery ratio (by unicast unicast tunneling and flooding) tunneling and flooding)

slide-22
SLIDE 22

Multiple Multiple Unicast Unicast v.s v.s. Mesh . Mesh Structure Structure

  • Builds a mesh

Builds a mesh between landmarks between landmarks

Load Balancing

Load Balancing

Better Reliability

Better Reliability source landmark

0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 2 m/s 10 m/s 15 m/s 20 m/s Mobility (meter/sec) Delivery Ratio

Team Multicast-Multiple Uni Team Mutlicast-MESH

slide-23
SLIDE 23

Reliable Multicast Reliable Multicast Support Support

Reliable Adaptive Lightweight Multicast (RALM)

Reliable Adaptive Lightweight Multicast (RALM)

Source continually monitors the channel

Source continually monitors the channel condition condition

No congestion

No congestion: the source transmits at “native” rate : the source transmits at “native” rate

Congestion

Congestion detected detected (i.e., packet loss feedback via (i.e., packet loss feedback via NACK): the source falls back to “send NACK): the source falls back to “send-

  • and

and-

  • wait”

wait” mechanism (source stops upon receiving a NACK; it mechanism (source stops upon receiving a NACK; it resumes when it receives an ACK ) resumes when it receives an ACK )

  • Combining with M

Combining with M-

  • LANMAR

LANMAR

Only landmarks return feedback (e.g. NACK/ACK) to

Only landmarks return feedback (e.g. NACK/ACK) to the source the source

Prevents unnecessary feedback implosion

Prevents unnecessary feedback implosion

slide-24
SLIDE 24

Simulation Results w ith RALM Simulation Results w ith RALM “Reliable Multicast” “Reliable Multicast”

(1000 nodes, 3 teams for each group, 5 (1000 nodes, 3 teams for each group, 5 multicast groups) multicast groups) Delivery Ratio

0.2 0.4 0.6 0.8 1 1.2 512 1024 1280 1689.6 2560 5120

Offered Load (Bytes/sec) Delivery Ratio

M- LANMAR w/ UDP ODMRP w/ UDP M- LANMAR w/ RALM ODMRP w/ RALM

ODMRP suffers from feedback implosion; congestion is unacceptable

slide-25
SLIDE 25

Conclusions and Future Work Conclusions and Future Work

  • M

M-

  • LANMAR is a scalable multicast protocol

LANMAR is a scalable multicast protocol designed for large ad designed for large ad-

  • hoc networks with affinity

hoc networks with affinity team model. team model.

  • M

M-

  • LANMAR implemented in LINUX.

LANMAR implemented in LINUX.

  • M

M-

  • LANMAR improved reliability in data delivery

LANMAR improved reliability in data delivery shown in experimental results. shown in experimental results.

  • M

M-

  • LANMAR scalability in large

LANMAR scalability in large-

  • scale networks

scale networks shown via simulation shown via simulation

  • Related study in progress

Related study in progress

Reliability issues in regular and team multicast

Reliability issues in regular and team multicast

Team dynamics: inter

Team dynamics: inter-

  • team, intra

team, intra-

  • team scenarios

team scenarios