V. Chikarmane, C.L. Williamson, R.B. Bunt, W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture," ACM/Baltzer Mobile Networks and Applications, 3(4):365-379, Jan. 1999.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....Note that the AB protocol provides reliable delivery without requiring routing support for MHs, e.g. Mobile IP, much like our proposal. Multicast protocols that rely on Mobile IP are generally targeted at dif ferent application domains and provide unreliable, best effort, unsequenced delivery [13, 21]. In particular, 7 no messages are delivered during a cell switching and messages possibly lost will not be recovered in the new cell. With respect to the use of Mobile IP, note also that: i) it would not solve the problem of recovering from lost messages; ii) it would make it more difficult to ....

....are assumed to be independent. All MHs receive multicasts (Nr = 100) whereas a subset of them with Ns= 10 members may generate 512 byte messages. Message generation is a Poisson process, i.e. times between the generation of successive messages are random variables exponentially distributed [3, 13, 18, 20]. Each sender generates, on the average, 8 messages sec corresponding to a bit rate of approximately 33 Kbps. We consider a wireless bandwidth of 1 Mbps and a wired bandwidth of 10 and 100 Mbps, respectively. In particular, we assume that coordinators are interconnected by a high speed wired LAN ....

V. Chikarmane, C. Williamson, R. Bunt, and W. Mackrell. Multicast support for mobile hosts using mobile IP: Design issues and proposed architecture. ACM/Baltzer Journal of Mobile Networks and Applications, 3(4):365- 379, 1998.

....only important but necessary when considering mobile access. 1 Introduction: Multicast in Mobile Environments The IETF defines two approaches to multicast at the IP level, namely bidirectional tunneling and remote subscription. Other techniques for unreliable multicast have also been adopted in [4, 5, 6, 7]. The solution adopted in [4] and later on refined in [5] has scalability problems and assumes that group membership is static, which is hardly true when considering mobile environments. 6] and [7] deals with problems such as tunnel convergence, but does not deal with packet loss and ....

....and remote subscription. Other techniques for unreliable multicast have also been adopted in [4, 5, 6, 7] The solution adopted in [4] and later on refined in [5] has scalability problems and assumes that group membership is static, which is hardly true when considering mobile environments. [6] and [7] deals with problems such as tunnel convergence, but does not deal with packet loss and performance issues. Commonly used reliable protocols include the scalable reliable multicast (SRM) 2] and the reliable multicast transport protocol (RMTP) 3] On the one hand, SRM is based on an ....

V. Chikarmane, C. Williamson, R. Bunt. W.Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture", ACM/Baltzer Mobile Networking and Applications, 1997

....longer work. A case in the point is a video conference application. This may not be able to know that although two distinct datagrams may have different source addresses, these have actually been originated by the same mobile source. More work on multicast at the transport level may be found in [Chikarmane, 97] and [Harrison 96] where the basic idea consists of using mobile IP s HA functionality to send multicast datagrams to the MHs. The authors introduced the concept of a Designated Multicast Service Provider (DMSP) in order to overcome the problems risen from the use of tunnels, such as the tunnel ....

V. Chikarmane, C. Williamson, R. Bunt. W.Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture", ACM/Baltzer Mobile Networking and Applications, 1997.

....specially in wireless environments. Multicast in Wireless Environments. Mobile IP offers two approaches to multicasting in a mobile environment, namely, bi directional tunneling and remote subscription. Furthermore, support for unreliable multicast in mobile environments are presented in [7, 8, 9, 10]. In [11] a Reliable Multicast data Distribution Protocol (RMDP) is presented. It relies on the use of Forward Error Correction (FEC) and Automatic Retransmission reQuest (ARQ) information to provide reliable transfer. Redundant information is inserted into the FEC often enabling a receiver to ....

V. Chikarmane, C. Williamson, R. Bunt, W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture", ACM/Baltzer Mobile Networking and Applications, 1997.

....handoff, and battery life of a mobile device is limited. Thus, when we design a multicast routing protocol for wireless mobile networks, the characteristics mentioned above should be carefully considered. Several multicast routing protocols for wireless mobile networks have been proposed [6,11,17,18]. Although the protocols solve several problems inherent in multicast routing proposals for 444 SUH, SHIN AND KWON static hosts, they still have problems such as non optimal delivery path, datagram duplication, etc. In this paper, we propose an efficient multicast routing protocol using a ....

....to the mobile host. The current IETF mobile IP specification also briefly proposes two approaches for supporting multicast service to mobile hosts [16 18] foreign agent based multicast (referred to as remote subscription) and home agent based multicast (referred to as bi directional tunneling) [6,11]. In foreign agent based multicast, a mobile host has to subscribe to multicast groups whenever it moves to a foreign network (see figure 1(a) It is very simple scheme and does not require any encapsulations. This scheme has the advantages of offering an optimal routing path and nonexistence of ....

[Article contains additional citation context not shown here]

V. Chikarmane and C.L. Williamson, Multicast support for mobile host using mobile IP: design issues and proposed architecture, Mobile Networks and Applications (1998) 365--379.

....is long if compared to the timeouts used at the transport level. Finally, the problem of recovering from missing messages would remain. Multicast protocols that rely on Mobile IP are generally targeted at different application domains and provide unreliable, best effort, unsequenced delivery [XP97, CWBM98]. In particular, no messages are delivered during a cell switching and messages possibly lost will not be recovered in the new cell. In such framework, lost messages may be recovered by means of usual recovery schemes, e.g. NACK and retransmission [PSLB97, PGM00] To reduce retransmissions ....

V. Chikarmane, C. Williamson, R. Bunt, W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture", ACM/Baltzer Mobile Networks and Applications, vol.3, n.4, pp. 365-379, 1998.

....In [3] they propose an IP multicast extension, which helps to deliver multicast messages to and from mobile hosts. Their approach is based on the Columbia Mobile IP protocol [11] and mainly focuses on Distance Vector Multicast Routing (DVMRP) More recent work, such as by Chikarmane et al. [5] and by Xylomenos et al. 15] considers Mobile IPv4 for mobility support. In [1] Acharya and Badrinath give a more general guideline for structuring protocols for delivering multicast messages in a mobile environment. Our paper differs from these publications in two issues. First, we focus on ....

....in two issues. First, we focus on the multicast protocol PIM DM and investi gate PIM DM specific interoperation issues. Second, we use Mobile IPv6 for mobility support. Providing multicast to from mobile IPv6 hosts is in various aspects different than with mobile IPv4 hosts. 1 For example, [5] describes the tunnel convergence problem, which occurs when multiple Mobile IP tunnels end at the same foreign agent. This problem is not relevant in Mobile IPv6, since it does not employ foreign agents. 2 Mobile IPv6 Today s version of the Internet Protocol does not support any mobility of ....

[Article contains additional citation context not shown here]

V. Chikarmane, C. L. Williamson, R. B. Bunt, and W. L. Mackrell. Multicast support for mobile hosts using Mobile IP: Design issues and proposed architectures. Mobile Networks and Applications, 3(4), 1998.

....wireless multicast systems developed. Forwarding pointers and location independent addressing to support mobility has been discussed in [11] but the multicast service is unreliable. Host View Management Protocol (HVMP) has been developed that provides reliable multicast for mobile nodes [10]. However, it does not allow dynamic group membership. Reference [13] proposed a protocol that allows dynamic group changes and reliable multicast message delivery with different network architecture. Multicast tunnelling is proposed to forward multicast packets from one foreign network to another ....

....that is called home address. Agent discovery may require more advertisements solicitations messages. Remote subscription is inefficient for dynamic membership and location change of mobile nodes. Bi directional tunnelling multicast may cause the tunnel convergence problem with packet duplication [10] (Fig. 1) Internet Multicast group Foreign Network MH Home Network FA HA MH Foreign Agent Mobile Host Home Agent Mobile Host Figure 1. Bi directional Tunneled Multicast Method 1.2 Motivation of the research To improve Mobile IP in terms of the three approaches, this paper proposes a ....

V. Chikarmane, Garey L. Williamson, Wayne L. Mackrell and Richard B. Bunt, Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture, Department of Computer Science, University of Saskatchewan, Saskatoon, May 1997.

....For example a TTL set for one region maybe inappropriate for another. Once the MH migrates out of a region, the speci ed TTL value earlier maybe too small. Further, since multicast groups are not unique, two MHs belonging to two di erent groups using the same address may receive unwanted packets [67]. Another problem outlined by Chikarmane et al. 67] is the use of a multicast address such as 224.0.0.1, which means multicast to all hosts on this LAN . There are three interpretations for delivery: 1) all hosts on the LAN including visitors, 2) all hosts belonging to LAN only, or (3) all ....

....for another. Once the MH migrates out of a region, the speci ed TTL value earlier maybe too small. Further, since multicast groups are not unique, two MHs belonging to two di erent groups using the same address may receive unwanted packets [67] Another problem outlined by Chikarmane et al. [67] is the use of a multicast address such as 224.0.0.1, which means multicast to all hosts on this LAN . There are three interpretations for delivery: 1) all hosts on the LAN including visitors, 2) all hosts belonging to LAN only, or (3) all hosts on the LAN and those that are away. If choice (1) ....

V. Chikarmane, C. L. Williamson, R. B. Bunt, and W. L. Mackrell, \Multicast support for mobile hosts using mobile IP: Design issues and proposed architecture. ," ACM/Baltzer Mobile Network and Applications, vol. 3, no. 4, pp. 365-379, 1999.

....c fl1997 ACM. the multicast delivery tree unchanged can cause inefficient, incorrect, or even failure of multicast message delivery. An approach for mobile multicast was proposed in [1] and revised in [2] but this proposal is not based on IETF Mobile IP and is limited in terms of scalability [8]. The current version of Mobile IP [18] proposes two approaches to support mobile multicast, which we call remote subscription and bi directional tunnelling. In remote subscription, the onus is on the mobile host to resubscribe to its desired multicast groups while at a foreign network. The ....

....continue to track reverse paths to the MH assuming that the MH is on its home network. Thus the multicast routes that are established are always with reference to the MH s home network and are incorrect when the MH is at a foreign network. A new approach to mobile multicast is described in [8]. Its details are summarized in the following two sections. 3 Our Approach to Mobile Multicast: MoM Our protocol addresses the problem of multicast to mobile hosts in an IP internetwork. Adapting a static host multicast mechanism such as that provided by IGMP and DVMRP to support mobile hosts as ....

[Article contains additional citation context not shown here]

V. Chikarmane, C. Williamson, R. Bunt and W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture ", ACM/Baltzer Mobile Networking and Applications, 1997, (to appear).

....message. If a co located address is not used, then the home address must be used. This can cause problems with some multicast routing protocols, however, since some multicast routers are required to drop any packets originating from a path which is different from that used to send packets on (see [CWBM96] This would mean that a MH connected in such a way can receive multicast datagrams but may have trouble sending them. In addition, if the MH is highly mobile, then packets will be lost due to the large set up time associated with multicast subscription. This option requires no special ....

....the reverse route from the MH to the HA are multicast packets encapsulated with a unicast header. It is assumed that the HA is a multicast router and knows how to decapsulate and deliver the packets. The third option is remote multicast extension. This is an option proposed by Vineet Chikarmane [CWBM96] This option requires a lot of sophistication on behalf of mobile routers on the foreign network (hereafter called foreign agents) Packets from an MH are handled via a bi directional tunnel as in option two. However, multicast packets destined for MHs are delivered 21 to the multicast address ....

[Article contains additional citation context not shown here]

Vineet Chikarmane, Carey L. Williamson, Richard B. Bunt, and Wayne L. Mackrell. Multicast support for mobile hosts using mobile ip: Design issues and proposed architecture. Technical report, Dept. of Computer Science, University of Saskatchewan, October 1996.

No context found.

V. Chikarmane, C.L. Williamson, R.B. Bunt, W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture," ACM/Baltzer Mobile Networks and Applications, 3(4):365-379, Jan. 1999.

No context found.

V. Chikarmane, C.L. Williamson, R.B. Bunt, W. Mackrell, "Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture," ACM/Baltzer Mobile Networks and Applications, 3(4):365-379, Jan. 1999.

No context found.

V. Chikarmane, Garey L. Williamson, Wayne L. Mackrell and Richard B. Bunt, Multicast Support for Mobile Hosts Using Mobile IP: Design Issues and Proposed Architecture, Department of Computer Science, University of Saskatchewan, Saskatoon, May 1997.

No context found.

Vineet Chikarmane. Multicast support for mobile hosts using Mobile IP: Design issues and proposed architecture.. Mobile Networks and Applications. 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC