(existing (N1) or newly (N2) created) will be updated. After the completion of the DBT
update, the mobile receiver x is then able to receive the multicast packet from the nLMR.
In case 3 shown in Figure 5.3 , both of the roaming messages will cause a DBT update
because the receiver x sending the Rm_out message is the last one connected to M2 and
will cause N3 to be no longer a BNR. And the Rm_in message for the receiver x will be
the first receiver connected to M3 which will cause new multicast branch in the DBT.
This case roaming process will cause N3 to be no longer a BNR and also N2 (previously
a BNR) will update its MFT table.
Figure 5.3 Roaming process (case 3)
Nodes |
MFTs | |
Before x roaming |
After x roaming | |
S (Source) |
MTI | IP_N1 |
unchanged |
V1 |
MTI | IP_N2 &IP_M |
unchanged |
N2 |
MTI | IP_N3 , IP_M5 MTI |
| IP_Mi , IP_M3, IP_M5 |
N3 |
MTI | IP_M1 & IP_M2 |
non BNR |
Roaming messages (Rm_in, Rm_out)
Moving Direction
This proposed protocol has been presented as a contribution to the COST 290 Final
Report and was included as a book chapter in the book published by Springer Lecture
Notes in Computer Science Series [70].
5.5 Scalable Ad hoc Recursive Multicast (SARM) protocol
SARM is an extension to the previously proposed protocol SReM taking into
consideration the mobility feature in all multicast nodes. In ad hoc networks, the ability to
keep hosts connected and re-establish new route because of node movement is the main
challenge. In the proposed protocol, it has been proposed a solution to re-establish new
108