Implementation of cluster control manager for multiple wireless links sharing systems

Transcription

1 Implementation of cluster control manager for multiple wireless links sharing systems Hiroshi Mineno Faculty of Information, Shizuoka University, Japan 1

2 Introduction Heterogeneous network access technologies 2G, 3G cellular systems, Wireless LAN hotspots, PHS Multiple network interfaces Ethernet, W-LAN, Bluetooth, IrDA, PHS PDA Bluetooth Wireless LAN PHS 3G Cellular 2G Cellular Laptop PC Communication is enabled by using the most suitable interfaces and access technologies according to the situation. - Office: Ethernet, W-LAN - Outdoor: 2G, 3G cellular, PHS IrDA Phone 2

3 Related research Mobile computing Flexible network support for mobile hosts (X. Zhao) Provides global connectivity by using multiple interfaces Multiple network interface support by policy-based routing on Mobile IPv6 (R. Wakikawa) Flow-to-interface binding policy to a Mobile IPv6 Heterogeneous network Global connectivity for IPv6 mobile ad hoc networks Globally routable address and -gateway operation Draft-ietf-ipv6-router-selection-02.txt (R. Draves) How to choose a router and how to support load-sharing among equivalent routers Ubiquitous networking 3

4 SHAring multiple paths procedure for a cluster network Environment () enables the sharing of multiple wireless links. Ad hoc cluster network User B -High throughput -High reliability -High connectivity Data-1 Data Data-2 User A Data-3 User D User C Data flow Correspondent host Long-range wireless link ( 2G, 3G cellular, PHS, etc.) Short-range wireless link ( x, Bluetooth, etc.) 4

5 SHAring multiple paths procedure for a cluster network Environment () enables the sharing of multiple wireless links. Ad hoc cluster network User B -High throughput -High reliability -High connectivity Data-1 Data User A Data-2 Data flow Long-range wireless link ( 2G, 3G cellular, PHS, etc.) Data-3 - Autonomous cluster configuration User C - Flexible policy-based control Short-rangetraffic wireless link User D Correspondent host ( x, Bluetooth, etc.) 4

6 Ubiquitous networking with Wireless LAN 2G/3G cellular network PHS network a g User A a Cluster network User B Office PHS User D User C 5

7 Ubiquitous networking with Wireless LAN 2G/3G cellular network PHS network b PHS User D Move User A a User C Cluster network Outdoor 5

8 Ubiquitous networking with Wireless LAN 2G/3G cellular network PHS network 3G cellular a User D Move User A Cluster network Train 5

9 Ubiquitous networking with Wireless LAN 2G/3G cellular network PHS network 3G cellular a User D Move User A Cluster network - Autonomous cluster configuration - Flexible policy-based traffic control Train 5

10 Cluster Control Manager (SCCM) Monitoring and advertising sharable resource information as a terminal profile Link status, OS type, remaining battery, etc. Each terminal profile is broadcast periodically Terminal profiles stored in a cluster table Autonomous cluster configuration Providing suitable resource information to the middleware* Available path, delay, bandwidth information User preferences are uniformly stored as a policy Traffic is dispersed based on the specific policy Flexible policy-based traffic control 6 * middleware is the proxy for implementing as substitute for all applications.

11 Architecture of SCCM Policy User preferences Policy manager - Flexible policy based control - Store preferences as a policy - Provide information from table based on the policy Cluster Control Manager Cluster table Terminal Terminal Profile Terminal Profile profile Shared resource information Cluster controller - Monitor resource info - Periodically broadcast as a terminal profile - Receive terminal profiles and update a cluster table Traffic information Suitable resource information Terminal profile Terminal profile Terminal profile middleware SCCM (on the other host) 7

12 Terminal profile format ID ID CPU_info OS_info Battery_info Net I/F{ I/F{ n } } Terminal profile : : Identify each host s s terminal profile information : : Affect relaying performance : : Laptop PC, PDA, Sensor : : Remaining battery information : : Network interface information NetI/F_name[ i ] : Interface name (eth1, lo, etc.) NetI/F_flags[ i ] : Link status (up, running, etc.) NetI/F_IPaddr[ i ] : IP address (IPv4) NetI/F_Bwidth[ i ] : Logical bandwidth NetI/F_RTT[ i ] : Average round trip time NetI/F_Loss[ i ] : Average packet loss ratio Recv_time : : Received time of of this terminal profile Profile_TTL : : Expiration time of of this terminal profile 8

13 Policy description examples Outgoing traffic rules (local) high low IP address, port : , 53: Own IP address, protocol : , TCP: Own IP address : : Own Packet-to-path Port : POP, SMTP: Own, HTTP: All Protocol : TCP: short delay paths Default : All hosts which have enough battery Forwarding traffic rules (local) High priority : Local traffic Queuing : Yes Incoming traffic rules (correspondent node) Flow-to-path Situation-to-path register to the correspondent node like outgoing traffic rules 9

14 SCCM applied architecture for Web HTTP data HTTP client proxy TCP External link GET REQ (1) HTTP REQ (2) HEAD REQ Web server Partial data IP User demands SCCM Policy HTTP proxy (3) Traffic information Policy manager (7) Sort and combine Header (4) Suitable network Cluster table partial data (size info of resources information Terminal profile GET REQ target file) Dispersion controller Cluster controller (5) Partial data (6) Receive other Broadcast terminal profiles terminal profile UDP Cluster link Partial GET Other hosts within cluster 10

15 SCCM applied architecture for Web HTTP data HTTP client (1) HTTP REQ proxy User demands SCCM Policy HTTP proxy - always (3) Traffic information Policy manager (7) Sort sends and regular GET requests through combine its own external Header link (4) Suitable network Cluster table partial data (size info of resources information Terminal profile GET REQ target file) Dispersion controller Cluster controller (5) Partial data (6) Receive other Broadcast Apply terminal forwarding profiles traffic terminal rules: profile TCP Partial -giving data priority to the local traffic UDP - queuing IP forwarding traffic if the local proxy using its external link External link (2) Cluster link HEAD GET REQ REQ Partial GET Web server Other hosts within cluster Apply outgoing traffic rule: 10

16 Evaluation 1. Dynamically changing cluster topology Whether each SCCM could autonomously communicate the sharable resource information and provide the available shared resource information to the proxy. 2. Changing cluster topology under communication Whether the SCCM could dynamically respond to the change of shared resource information even if the host is under communication. 3. Observing competitor appearance within cluster Whether each mobile host can guarantee a minimum performance by using its own external link. 11

17 Experiment 1 IEEE802.11b Mode: Ad-hoc Bandwidth: 11 Mbps PHS Mode: PIAFS Bandwidth: GET GET REQ REQ GET REQ 1Mbytes 1 Host 1 sends five consecutive HTTP GET requests. Host 1 AP 1 Web server Host 2 Host 3 Cluster network AP 2 AP 3 proxy and SCCM runs on each mobile host. AP: Access Point 12

18 Experiment 1 First request GET REQ [ ] Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: disconnected -Host 3 AP 3: disconnected Host 1 AP 1 Web server Host 2 Host 3 Cluster network AP 2 AP 3 proxy and SCCM runs on each mobile host. AP: Access Point 12

19 Experiment 1 Second request GET REQ [2] Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: connected -Host 3 AP 3: disconnected Host 1 AP 1 Web server Host 2 Host 3 Cluster network AP 2 AP 3 proxy and SCCM runs on each mobile host. AP: Access Point 12

20 Experiment 1 Third request GET REQ [3] Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: connected -Host 3 AP 3: connected Host 1 AP 1 Web server Host 2 Host 3 Cluster network AP 2 AP 3 proxy and SCCM runs on each mobile host. AP: Access Point 12

21 Experiment 1 Fourth request GET REQ [4] Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: connected -Host 3 AP 3: disconnected Host 1 AP 1 Web server Host 2 Host 3 Cluster network AP 2 AP 3 proxy and SCCM runs on each mobile host. AP: Access Point 12

22 Experiment 1 Fifth request GET REQ [5] Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: disconnected -Host 3 AP 3: disconnected Host 1 AP 1 Web server Host 2 AP 2 Whether the SCCM could dynamically respond to the change of shared resource information even if the host is Host 3 under communication. AP 3 Cluster network proxy and SCCM runs on each mobile host. AP: Access Point 12

23 Result 1 Average throughput [Kbps] Throughput Received data size (1,048,576 bytes) Redundant data 320 KBytes Received data size [Kbytes] Elapsed time [sec] 0 13

24 Experiment 2 IEEE802.11b Mode: Ad-hoc Bandwidth: 11 Mbps PHS Mode: PIAFS Bandwidth: 32 Kbps GET REQ Host 1 sends a HTTP GET request. 32 Kbps Host 1 AP 1 Web server Host 2 Cluster network PHS Mode: PIAFS Bandwidth: AP 2 proxy and SCCM runs on each mobile host. AP: Access Point 14

25 Experiment 2 Elapsed time:0-30sec GET REQ 32 Kbps Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: connected Host 1 AP 1 Web server Host 2 Cluster network AP 2 proxy and SCCM runs on each mobile host. AP: Access Point 14

26 Experiment 2 After 30 sec GET REQ 32 Kbps Each host s external link status -Host 1 AP 1: connected -Host 2 AP 2: disconnected Host 1 AP 1 Web server Host 2 AP 2 Whether each SCCM could autonomously communicate the proxy and SCCM Cluster sharable network resource information and provide the available runs on each mobile host. shared resource information to the proxy. AP: Access Point 14

27 Result 2 Average throughput [Kbps] Throughput Received data Throughput of Host 2 s2 relaying data Throughput of Host 1 s1 external link Received data from Host 2 s 2 external link (1,048,576 bytes) Received data from Host 1 s 1 external link Guaranteed performance Received data size [Kbytes] 0 30 Disconnect Host 2 s 2 s external link Elapsed time [sec] 0 15

28 Experiment 3 IEEE802.11b Mode: Ad-hoc Bandwidth: 11 Mbps PHS Mode: PIAFS Bandwidth: 32 Kbps Each host had the same external link as in the previous experiment. 32 Kbps Host 1 AP 1 Web server Host 2 Cluster network PHS Mode :PIAFS Bandwidth :64Kbps AP 2 proxy and SCCM runs on each mobile host. AP: Access Point 16

29 Experiment 3 Elapsed time:0-60 sec GET REQ 32 Kbps Host 1 sent a HTTP GET request and started to download the file. Host 1 AP 1 Web server Host 2 Cluster network AP 2 proxy and SCCM runs on each mobile host. AP: Access Point 16

30 Experiment 3 After 60sec GET REQ 32 Kbps Host 2 sent a HTTP GET request and started to download the file. Host 1 AP 1 Web server GET REQ 512 Kbyte 512 Kbyte Host 2 AP 2 proxy and SCCM runs on each mobile host. Cluster Whether network each mobile host can guarantee a minimum performance by using its own external link. AP: Access Point 16

31 Result 3 Average throughput [Kbps] Only Host 1 Host 1 and Host 2 Only Host Throughput Received data Throughput of Host 2 s2 relaying data Throughput of Host 1 s1 external link Received data from Host 2 s2 external link Received data from Host 1 s 1 external link Competitor appeared Elapsed time [sec] Received data size [Kbytes] 17

32 Conclusion and future research Proposed cluster control manager Autonomous cluster configuration Flexible policy-based traffic control Applied SCCM to Web Possible Web respond to a dynamic change in shared network resources Potential guarantee of each mobile host s performance even when competitors appear within the cluster <Future research> Apply the SCCM to Mobile IP Modify for use in Mobile IP version 6 Support secure communication through the cluster 18

33 Thank you for your attention today.

34 Related research on prototype (1999) Implemented as a library that utilizes TCP for reliable socketlevel communication Web (2002) Doesn t require special software for corresponding web server Customized HTTP proxy for the Mobile IPv4 (2003) Enhanced HA disperses IP datagrams to the registered CoAs Increased benefits of for all applications - Autonomous cluster configuration - Flexible policy-based traffic control