EVALUATION OF MOBILE CDN WITH BASED SEAMLESS MOBILITY SUPPORT

Transcription

1 International Journal of Mechanical Engineering and Technology (IJMET) Volume 9, Issue 13, December 2018, pp , Article ID: IJMET_09_13_0911 Available online at eme.com/ijmet/issues.asp?jtype=ijmet&vtype= =9&IType=13 ISSN Print: and ISSN Online: IAEME Publication Scopus Indexed EVALUATION OF MOBILE CDN WITH PMIPV6- BASED SEAMLESS MOBILITY SUPPORT Tae-Kook Kim Department of Information and Communications Engineering, Tongmyong University, Busan, Republic of Korea ABSTRACT Network-based mobility management enables the same functionality as Mobile IP, but it does not need to modify the host's TCP/IP Protocol stack. Moreover, a content delivery network (CDN) is a large distributed system of servers deployed in multiple data centers on the internet. Currently, the use of mobile devices is becoming popular and the demand for mobile internet services is also increasing. In this paper, a PMIPv6-based Mobile CDN is proposed that supports mobility under the internet network. The proposed method reduces the total traffic in the network and provides seamless mobility for users. Therefore, the proposed method is expected to be useful for providing services such as content delivery in wireless environments. Keywords: Content Delivery Network (CDN), Proxy Mobile IPv6 (PMIPv6), Mobility, Handover. Cite this Article: Tae-Kook Kim, Evaluation of Mobile CDN with Pmipv6-Based Seamless Mobility Support, International Journal of Mechanical Engineering and Technology, 9(13), 2018, pp et/issues.asp?jtype=ijmet&vtype=9&itype e=13 1. INTRODUCTION The rapid growth in internet penetration has increased the demand for multimedia services such as images and video clips. Thus, a content delivery network (CDN) is widely used to efficiently distribute the network s traffic load [1]. The exponential increase in the use of mobile devices, such as smart phones and tablet PCs, has increased demandd for mobile internet services. Hence, interest in the use of Mobile CDN, which offers servicess on the move, has been increasing. Table 1 shows features of Typical CDN and Mobile CDN [2]. In Mobile CDN, the users locations are mobile; hence, surrogate servers need to be installed near the base station to provide stable services to the users. Mobile CDN has the additional function of providing conventional Stationary CDN services for mobile users. Because of services from the CDN, the locations of the mobile devices of users change according to their movement. Therefore, the distribution of IJMET/index.asp 869 editor@iaeme.com

2 Evaluation of Mobile CDN with Pmipv6-Based Seamless Mobility Support information about the content and the locations of the users on the move needs to be efficiently connected to seamlessly support the multimedia services. This study uses a network-based PMIPv6, which supports mobility under the internet network to describe the execution result of the evaluation of the Mobile CDN research. In PMIPv6, the mobility management of the mobile node (MN) is conducted using mobility management components of mobile access gateway (MAG) and local mobility anchor (LMA) that have hierarchical structures. Under the proposed PMIPv6-based Mobile CDN, the CDN servers are linked with MAG or LMA. Using the location information following changes in the locations of mobile devices in MAG or LMA, content retention verification in the CDN server and content retention verification information in the adjacent CDN server are linked. This process allows the users to seamlessly enjoy the service reception from the CDN server, while the CDN maintains its original function of efficiently distributing the network s traffic load. The proposed method verifies the possibility of seamless reception of the service by generating temporary traffic. Table 1 Features of Typical CDN and Mobile CDN Features Typical CDN Mobile CDN Content type static; dynamic; static; dynamic; Users locations fixed mobile Surrogate servers fixed fixed Surrogate servers close to Internet Service close to Base Stations Replicas maintenance medium high Services application services geo-location oriented Content outsourcing cooperative/uncooperative cooperative push-based 2. RELATED WORKS 2.1. Overview of CDN A CDN is a system that allocates replicas of its contents over servers that are geographically scattered and placed typically close to sites with high demand to reduce latency and network bandwidth requirements. Figure 1 shows the traditional scheme of network distribution and Figure 2 shows the CDN scheme of network distribution [3]. CDN is an overlay network constructed from the origin server and distributed CDN servers. The origin server contains all the contents, while the distributed CDN servers are proactively updated by the origin server. The contents are pushed to the CDN servers and then transmitted to the users from the nearest CDN server. Figure 1 Traditional scheme of network distribution IJMET/index.asp 870 editor@iaeme.com

3 Tae-Kook Kim Figure 2 CDN scheme of network distribution For CDN, several techniques have been proposed such as contents placement, server selection, and server placement. Contents placement is related to optimally replicating the outsourced content in the CDN servers. For a given set of CDN servers, it is important to determine the CDN servers in which the outsourced contents should be replicated. By distributing the replicas in the CDNs, network overload can be decreased and the reliability of the contents can be assured. Additionally, allocating the most appropriate CDN server is a critical issue because the nearest server may not be the best CDN server for servicing the user request. Typical techniques to select the best server use certain metrics, such as network proximity, user perceived latency, distance, and CDN server load, to direct the user to the CDN server that can best serve the request [4]. To select the most appropriate CDN server for delivering the contents, most CDN providers use Domain Name System (DNS) redirection while some use URL rewriting [5]. To deliver contents to users with quality-of-service guarantees, CDN service providers must ensure that CDN servers are strategically placed across the network. Notably, predominant CDN service providers, such as Akamai and Limelight, are not network operators; they are third-party providers. They deploy their CDN infrastructure outside the network of a network operator as an overlay network [6] Overview of PMIPv6 The foundation of PMIPv6 is based on MIPv6, which extends Mobile IPv6 (MIPv6) signaling and reinvents many concepts such as Home Agent (HA) functionality [7]. Table 2 Features of MIPv6 and PMIPv6 Features MIPv6 PMIPv6 Mobility management type Host-based mobility Network-based mobility Mobility scope Global mobility Localized mobility Functionally HA (Home Agent) LMA Topologically AR (Access Router) MAG MN modification Yes No Location registration Binding update message Proxy binding update MN address HoA or CoA HoA (always) Table 2 shows the features of MIPv6 and PMIPv6 [8]. PMIPv6 is proposed to provide network-based mobility management support to the MN in a topologically localized domain. Thus, the MN is not involved in any mobility-related signaling. The proxy mobility agent in the serving network executes mobility-related signaling instead of the MN. Moreover, PMIPv6 can support not only IPv4 but also IPv6 by specifying some extensions for supporting the IPv4 tunneling mechanism and specific encapsulation modes. IJMET/index.asp 871 editor@iaeme.com

4 Evaluation of Mobile CDN with Pmipv6-Based Seamless Mobility Support Figure 3 Overview of PMIPv6 Figure 3 provides an overview of PMIPv6 [7], [8]. When the MN gets into its PMIPv6 domain and performs access authentication, the serving network guarantees that the MN is always on its home network and can acquire its Home Address (HoA) from any access network; i.e., the serving network allocates a unique home network prefix (MN-HNP) to the MN such that the prefix always follows it wherever it moves within the PMIPv6 domain. From the perspective of the MN, the entire PMIPv6 domain appears as its home network. Accordingly, there is no need to configure the Care of Address (CoA) at the MN. PMIPv6 does not require the MN to know anything about mobility protocols. Another advantage of this protocol is the reduction of signaling overhead over the wireless link that is particularly beneficial to low-bandwidth links. Additionally, the mobility-related signaling is accelerated as PMIPv6 is used over the wired network, which is assumed to be less prone to error and has lower latencies compared with wireless link. Each time the MN changes its point of attachment, it sends a Proxy Binding Update (PBU) message to LMA, whereas its globally perceived IP address remains intact and effective for routing outside the domain. Thus, handoff latency is reduced as the binding update terminates at LMA in a local domain rather than at the HA and correspondent nodes, which may reside at the other end of the internet. 3. PROXY MOBILE IPV6-BASED MOBILE CDN The PMIPv6-based Mobile CDN is proposed that supports mobility under the internet network. It reduces the total traffic in the network and provides seamless mobility for users Proposed Architecture of PMIP-CDN In this section, the architecture of the proposed PMIP-CDN designed to provide efficient mobility management and contents delivery is described [2]. There are two functional entities in the PMIPv6 network architecture: MAG and LMA. MAG is the entity that performs the mobility-related signaling on behalf of the MN attached to its access links, while LMA within the backbone network maintains a collection of routes for each MN connected to the PMIPv6 domain [9]. PMIP-CDN comprises Low-Level-servers (LL-servers), High-Level-servers (HLservers), and Request Routing DNS (RR-DNS). LL-servers and HL-servers connected to MAG and LMA are used to cache and forward contents [2, 10, 11, 12]. The contents are sorted in decreasing order of popularity, and more objects are stored in this order as the storage constraint allows. IJMET/index.asp 872 editor@iaeme.com

5 Tae-Kook Kim Figure 4 Architecture of the proposed PMIPv6-CDN RR-DNS is a DNS-based redirection system connected to LMA that can redirect requests of the MN to the most appropriate LL-server. One way to select the most appropriate server is based on the status information of the LL-server provided by the monitoring system and the location information of the MN provided by LMA. To select the best LL-server for the user request, RR-DNS interacts with LMA and the monitoring system to get information of the MN s location as well as the status of the servers and the network. RR-DNS also contains a list of all contents available at the servers that are updated by LL-server and HL-server Basic Procedure of PMIP-CDN In this subsection, the basic procedure of delivering contents in a PMIP-CDN based on the PMIP-CDN architecture is described. When the MN is attached to MAG, MAG sends a PBU to LMA. After receiving the PBU message, LMA assigns a MN-HNP for the MN and creates a BCE (Binding Cache Entry) that binds the Proxy-CoA of MAG with MN-HNP [7]. The following procedure is followed: LMA sends an updated binding information of MN-ID to RR-DNS. Through this update, it is assumed that all the entities, including PMIP-CDN, recognize the MN-ID. After address configuration, the MN sends a content request to the origin server. Then, the origin server redirects the content request to RR-DNS, which is in the same domain as the MN [13]. RR-DNS selects the best server for the MN using information, such as server status and location information, provided by the monitoring system and LMA. RR-DNS gives the IP address of the best LL-server to the MN. Then, the MN retrieves the content by sending the HTTP request. In the case of cache miss, LL-server fetches the content from the origin server or HL-server and forwards it to the MN. 4. PERFORMANCE EVALUATION PIMPv6-based Mobile CDN is proposed and evaluated by integrating the features of Mobile CDN shown in Table 1 and PMIPv6 shown in Table 2. The throughput of the proposed PMIP- CDN and conventional CDN are compared and analyzed using a computer simulation. The simulation called OPNET network simulator is used, and the throughput is measured during handoff between MAGs. IJMET/index.asp 873 editor@iaeme.com

6 Evaluation of Mobile CDN with Pmipv6-Based Seamless Mobility Support Figure 5 shows the simulation configuration of PMIP-CDN. The network comprises LMA, MAG, the origin server, HL-server, LL-server, and the mobile device. MAG is a mobile router with wired and wireless interface. Its function is same as that of PMIPv6 and is directly connected to LL-server of the CDN. LMA serves the function as for PMIPv6 and is directly connected to HL-server of the CDN. For the simulation, the origin server sends out a 1-Mbps traffic to the MN, and the throughput is compared when the MN handoffs from MAG1 to MAG2. The values of the parameters used in the simulation are shown in Table 3. And Table 4 shows the IP address settings. Figure 6 compares content date handoffs of conventional PMIPv6 and the proposed PMIP- CDN. The results show that conventional PMIPv6 is disconnected when the user is on the move, and then the session is connected through the CDN process. In addition, data are not received during the reconnection process. However, from the second panel of Figure 6, the proposed PMIP-CDN allows seamless data reception because PMIP-CDN brings the data in advance from nll-server. This confirms that the proposed method provides seamless mobility and improves the throughput. Table 3 Values of parameters used in the simulation Parameter Value Description T LUE 10 ms MN attachment and AAA (Authentication, authorization, and accounting) authentication T WIRELESS 10 ms Delay between MN and MAG T MtL 10 ms Delay between MAG and LMA T LtHL 5 ms Delay between LMA and HL-server T MtLL 5 ms Delay between MAG and LL-server Data rate Modulation Transmit Power Packet reception power threshold AP (Access Point) beacon interval 11 Mbps DSSS (Direct Sequence Spread Spectrum) W 95 dbm 0.1 s Figure 5 Configuration of the simulation IJMET/index.asp 874 editor@iaeme.com

7 Tae-Kook Kim Table 4 IP address settings Parameter IP Subnet Wireless interface of MAG C class Ethernet interface of MAG C class Wireless interface of MAG C class Ethernet interface of MAG C class Ethernet 1 interface of LMA C class Ethernet 2 interface of LMA C class Figure 6 Comparison of the throughput performances of conventional PMIPv6 and the proposed PMIP-CDN 5. CONCLUSION Here, we proposed and evaluated a PMIPv6-based Mobile CDN that supports seamless mobility. The proposed method generated temporary traffic to confirm the possibility of seamless data reception of the service. We also proved the performance of this method by checking traffic fluctuations when the user is on the move. The proposed method provides seamless mobility in CDN and can be used in future applications, e.g., real-time content transmission. ACKNOWLEDGMENTS This work was supported by the National Research Foundation of Korea(NRF) grant funded by the Korea government(msip : Ministry of Science, ICT & Future Planning) (No. 2017R1C1B ). IJMET/index.asp 875 editor@iaeme.com

8 Evaluation of Mobile CDN with Pmipv6-Based Seamless Mobility Support REFERENCES [1] Kim, Taekook, and Eui-Jik Kim. "Hybrid storage-based caching strategy for content delivery network services." Multimedia Tools and Applications 74(5), 2015, pp [2] Kim, Taekook, et al. "Novel architecture for a mobile content delivery network based on proxy mobile IPv6." IEICE Transactions on Fundamentals of Electronics, Communications and Computer Sciences 97(3), 2014, pp [3] Kim, Taekook, and Eui-Jik Kim. "View pattern-based adaptive streaming strategy for mobile content delivery services." Multimedia Tools and Applications 75(20), 2016, pp [4] Tariq, Muhammad Mukarram Bin, Ravi Jain, and Toshiro Kawahara. "Mobility aware server selection for mobile streaming multimedia content distribution networks." Web content caching and distribution. Springer, Dordrecht, 2004, pp [5] R. Rajapriyan and N. Kumar, Load-Balanced Migration of Social Media to Content Clouds. International Journal of Civil Engineering and Technology, 8(3), 2017, pp [6] Vakali, Athena, and George Pallis. "Content delivery networks: Status and trends." IEEE Internet Computing 7(6), 2003, pp [7] Gundavelli, Sri, et al. Proxy mobile ipv6. No. RFC [8] Kong, Ki-Sik, et al. "Mobility management for all-ip mobile networks: mobile IPv6 vs. proxy mobile IPv6." IEEE Wireless communications 15(2), [9] Soto, Ignacio, et al. "PMIPv6: A network-based localized mobility management solution." [10] Saravanan P, Arunkumar S, Subramaniyaswamy V, and Logesh R, Enhanced Web Caching Using Bloom Filter For Local Area Networks, International Journal of Mechanical Engineering and Technology 8(8), 2017, pp [11] Krishnan, S., et al. Localized routing for proxy mobile IPv6. No. RFC [12] Kailash, Chander. "An analysis of intelligent agent framework for proxy mobile IPv6 (IAF-PMTPv6)." Int. J. Adv. Technol 3, 2012, pp [13] Dilley, John, et al. "Globally distributed content delivery." IEEE Internet Computing 6(5), 2002, pp [14] Tariq, MM Bin, and Atsushi Takeshita. "Management of cacheable streaming multimedia content in networks with mobile nodes." Global Telecommunications Conference, GLOBECOM'02. IEEE. Vol. 3. IEEE, [15] Huang, Chung-Ming, and Chao-Hsien Lee. "Layer 7 multimedia proxy handoff using anycast/multicast in mobile networks." IEEE transactions on mobile computing 6(4), 2007, pp [16] Jiang, Yingyin, Min-You Wu, and Wei Shu. "Web prefetching: Costs, benefits and performance." Proceedings of the 7th international workshop on web content caching and distribution (WCW2002). Boulder, Colorado [17] Cho, Kideok, et al. "How can an ISP merge with a CDN?." IEEE Communications Magazine 49(10), 2011, pp IJMET/index.asp 876 editor@iaeme.com