Mobile Data Collector In Wireless Sensor Network

Published Date: 02 Nov 2017

In Wireless Sensor Network to increase network lifetime and reduce the data latency by using Mobile data Collector is the challenge issues. In Existing System Data latency is high because of low speed of mobile data collector to collect the data from the cluster head. In this proposed system event driven Mechanism is introduced the reduce the data latency. When event occur the sensor node send the data to the cluster head, then cluster head give the request to the mobile data collector, after mobile data collector sent the data to the Base station. By analysis this project event driven mechanism increase the lifetime of network, reduce the data latency on the network

Wireless sensor network is a collection of sensor node with limited resource and base station, Sensor node monitor the physical and environmental condition such as temperature, sound, pressure, vehicular motion, and humidity etc.The network consists of a large number of sensor network and smaller number of cluster head and base station. Mobile data collector is a special node with huge memory and moving all over the network..The Mobile data collector travel in network and collect the data from the cluster head, then mobile data collector passes the information through the base station. It can save more energy and reduce the data latency on the network. Event detection mechanism is mainly used for saving more energy and data latency reduced on the network. When event occur mobile data collector going to collect the data from the cluster head, then mobile data collector pass the information to the base station. Suppose cluster head give request to the mobile data collector, then mobile data collector check whether which is nearest cluster head, then mobile data collector going to collect the data from nearest cluster head. when event occur sensor nodes passes the information to the cluster head, otherwise sensor node going to sleep modes.

1.2 wireless sensor networks

Sensors are more expansive and it can save more energy, low power device .It is small size and wireless communication ability is short distances. Sensor nodes typically contain power unit, sensing, processing, storage etc.A wireless sensor network is large number of smaller sensor node and smaller number cluster head and mobile data collector. Wireless sensor network is a wide range of application such as military, envirnomenatal monitoring and agriculture etc..

Base station

Region

Sensor node

Fig 1: Wireless sensor network

Sensor networks applications:

Sensor is consists of many different sensor, and monitor the temperature,pressure,vehicular motion, pressure and noise level etc..

Military applications:

Wireless sensor network is a critical part of military command, communicating the data, storing the data, securely transfer the data and target system.

Environmental system:

Environmental application is used sensing volcanoes, air, sound, vibration level etc.

Health application:

Wireless sensor network is mainly used for health applications, because it can easily identify the patient monitoring in hospital.

1.4 Topology Management for wireless sensor network

Topology management is mainly used for increasing network lifetime and reduces the data latency and avoids the traffic on the network. Suppose every individual sensor nodes passes the information to the base station and battery will be reduced, traffic will be increasing on the network, In most environmental application using mobile data collector. It is high energy, more storage and dynamically collects the data from sensor nodes, then passes the information to the base station. And it can save more energy on the network. Another environmental application is mainly used for sensor node are organized into cluster head. Every sensor node passes the information to the cluster head, then cluster head pass the information to the mobile data collector and it can save more energy on the networks.

1.5 Need of increasing network lifetime:

Wireless sensor network is main challenge increasing network lifetime because sensor nodes send the data to the base station by using one hop communication and it will reduce network lifetime ,traffic will be increasing on the network. In multi-hop communication sensor node send the data to the another node by using multi-hop communication ,which sensor node near the base station ,that sensor node easily going to die on the network.

Base station

Region

Mobile data collector

sensor node

Fig 2 : Mobile Data Collector

1.6 Need of Mobile data collector:

Mobile data collector is more energy and more memory and dynamically to collect the data from a cluster head, then pass the information through the base station .mobile data collector is vital role of increase network lifetime .cluster head give request to the mobile data collector, the mobile data collector dynamically send the data to the base station.

Fig 3: Mobile data collector collect the data from cluster head

1.7 PROJECT DESCRIPTION:

Wireless sensor network is used for increase network life time by using mobile data collector. The Mobile data collector is more energy, more storage and dynamically collects the data from the cluster head. When Event occur ,sensor nodes send the information to the cluster head, the cluster head give the request to the mobile data collector ,then mobile data collector is going to collect the data from the cluster head, then mobile data collector moving to send the data to the base station ,suppose cluster head simultaneous give request to mobile data collector ,then mobile data collector periodic based going to collect the data from the cluster head because it can save more energy and data latency will be reducing on the network. Using ns2 simulator ,this proposed work is done ,then result is term of energy and latency are measured.

CHAPTER 2

LITERATURE SURVEY

An energy efficient data collection protocol for mobile sensor networks

Energy efficient data collection is mainly used for low energy dynamic cluster selection.LEDCS is used for collecting the data from the mobile nodes. When sensor node transmits the data to the sink node, it can used join nearest cluster head. Mobile sensor network is mainly used for cluster based protocol because it can easily to save more energy. When sensor node transmits the data to the cluster head based on velocity and transmit the data to the nearest cluster head.

Hybrid multipath scheme protocol:

In this paper hybrid multipath scheme is mainly used for security and reliable data collection from one source node to destination node. N to 1 multipath discovery protocol is mainly used to find the multiple node disjoint path from all sensor node to base station.

N to 1 discovery protocol main technique is hybrid data collection scheme. The multipath discovery protocol is two phase (I) branch aware flooding (ii) multipath extension of flooding. Branch aware flooding is used to ability of finding extra paths because limiting of nodes sent message between sensor node and neighbor nodes. Multipath extension of flooding is used to find the more node disjoint path of each sensor node at cost of some extra message exchange.

MGKE group based key establishment scheme:

Sensor nodes are static and mobile nodes are moving to collect the data from the cluster head. When mobile node moving to collect the data from the cluster head and attacker can easily modify the data from the sensor node, after passes information to the base station.

So propose this paper is MGKE group based key establishment scheme is used group based sensor deployment.MGKE is mainly used unique pair wise key to connect the neighbor nodes and security.MGKE is very carefully to set the key between sensor node and mobile node because if unauthorized identify the key and easily get the data from the individual sensor node .so, it avoid the every sensor node share the key with one another. Each sensor node sharing the key with one another and create a own group. So each sensor creates one or more groups. Sensor node si shares the key with any other neighbor node sj but if si and sj are same group doesn’t share the key with each other. Each sensor node shared secret key with base station and mobile collector secure collect the data from the sensor node and pass the information to the base station

Time stamp protocol:

Secure group communication is mainly used for confidentiality, authenticity and securely message deliver to the base station. Secure group communication is mainly used to key graphs and group communication main advantage one or more authorized sender,

Authorized receiver and more efficient securely transmit the large groups. Securing uncast communication mainly based on client and server.intially client and server is authenticating because secure group communication used symmetric keys shared each other. if client wants join the group already client and server is used by authentication protocol. So SCP will easily accept the group and server key share the each group member is called individual keys. In group communication, servers transmit the key to all group members and maintain user –keys relation

For example :there are three subgroup, each group three member(n1,n2,n3) (n4,n5,n6)(n7,n8,n9)Each member will give three keys(i) individual key (ii) key for subgroup (iii)key for entire group because if one member leave means it can easily add another member and securely sharing the key transmitting to the data. Secure group is mainly depends on keys server because of securely transmit the key to the user-groups.key server mainly know that key set, user set and user-key relation. Every user is used individual key shared by key server because of confidential communication with the key server.

Rekeying strategies and protocol is mainly used for securely transmit data because if user should join the group, secure group request to the key server.

Join group authenticate between user and server, if is authorized user it will join group suppose if it is not authorized and leave the group. There are three rekeying strategies user oriented, key-oriented, and group-oriented.

User-oriented rekeying is mainly consider on each user create a new key and mainly consider on each new key encrypt individual key.

Key-oriented rekeying is mainly consider on each new key encrypt individual key.

Key-oriented rekeying is mainly used two-rekeying message.

Group –oriented rekeying is mainly considered on each new key encrypt individual and mainly used multiple rekey message.

Randomized dispersive routes:

Data delivery mechanisms main drawback is black hole attack. When using multipath routing attacker can easily get the data .so it avoids multipath routing. if randomly sent the data to the designation and attacker doesn’t get the data easiler.Sensor node sent the data sent randomly and can save more energy .so proposing paper the randomized multipath delivery is used sent the data securely by using multihop routing. Each node randomly select by neighbor nodes. Purely random propagation is mainly based on one –hop neighbour.if sensor node sent the information from the source to designation and mainly based on neighbor list and all sensor node id.when sensor node sent the information to the sink node based on TTL values. Direct random propagation is mainly based on increase efficiency by using two-hop neighbor information.

CHAPTER 3

PROBLEM STATEMENT AND ITS SOLUTION:

3.1 EXISTING SYSTEM:

In Existing system data latency is high because of low speed of mobile data collector to collect the data from the cluster head. Every time mobile data collector dynamically going to collect the data from the cluster head and it will energy will be reduce and data latency will be increasing on the network. So the problems are reducing network lifetime and data latency increasing on the network.

PROPOSED SYSTEM:

In this proposed system event driven mechanism is introduced to reduce the data latency and save more energy on the network. When event occur, sensor node send the data to the cluster head, then cluster head give the request to the mobile data collector, then mobile data collector going to the collect the data from the cluster head, then mobile data collector going to pass the information through the base station. By analysis this project event driven mechanism increase the lifetime of network and data latency will be reduced on the network.

CHAPTER 4

SYSTEM ANALYSIS

4.1 System Specification:

Software Configuration

Operating System : Linux (ubuntu 12.10)

Simulator : NS2

Language : TCL

Graph : Gnu plot

Hardware Configuration

Processor : core 2 Duo

Speed : 2.0 GHZ

Ram : 2 GB

CHAPTER 5

SYSTEM DESIGN

5.1 OVERVIEW OF MODULES:

Event driven mechanism:

When Event occur sensor node send the data to the cluster head.

Cluster head to Mobile Data Collector:

Cluster head give to request to the mobile data collector then mobile data going to collect the data from the cluster head.

Mobile data collector movement

Mobile data collector going to collect the data from the cluster head, then mobile data collector moving to base station.

Mobile data collector to base station

Mobile data collector passes the information to the base station.

periodic data collection

Cluster head give the request to the mobile data collector ,then periodic based mobile data going to collect the from the cluster head.

Flow chart:

start

If event occur or not

Ch request to MDC

MDC collect the data from the Cluster head

MDC moving to base station

MDC TO BS

CH2 request to MDC

CH3 request to MDC

stop

Periodic based collect the data

Fig 4: Flow Diagram

CHAPTER 6

IMPLEMENTATION

6.1 DESCRIPTION OF MODULES

1. Event driven Mechanism:

When Event occur sensor node send the data to the cluster head. otherwise sensor node going to sleep mode.

When event occur sensor node

Transmitting data

Cluster Head

Fig 5: Event Driven Mechanism

2. Cluster head to Mobile Data Collector

Cluster head give to request to the mobile data collector then mobile data going to collect the data from the cluster head.

Cluster head give request to

Mobile Data Collector

Mobile Data Collector Movements

Cluster Head Send the Data to

Mobile Data Collector

Fig 6: Cluster head to mobile data collector

3. Mobile data collector movement

Mobile data collector going to collect the data from the cluster head,then mobile data collector moving to base station.

Mobile Data Collector Moving

TO Base Station

Fig 7: Mobile data collector movements

4. Mobile data collector to base station:

Mobile data collector passes the information to the base station.

Mobile Data Collector Pass

Information

To Sink Node

Fig 7: Mobile data collector to Base station

periodic data collection:

cluster head give the request to the mobile data collector ,then periodic based mobile data going to collect the from the cluster head.

Two Cluster Head give Request to

Mobile Data Collector

Mobile Data Collector

Periodic Based Collect the Data

Mobile Data Collector Moving to Nearest collects the Data from the Cluster Head

Mobile Data Collector passes the information to the Base Station

Fig 8: periodic data collection

CHAPTER 7

SAMPLE CODING

# define options

Set Val (Chan) Channel/Wireless Channel; # channel type

Set Val (prop) Propagation/TwoRayGround; # radio-propagation model

Set Val (netif) Phy/WirelessPhy; # network interface type

Set Val (Mac) Mac/802_11; # MAC type

Set Val (ifq) Queue/Drop Tail/PriQueue; # interface queue type

Set Val (ll) LL; # link layer type

Set Val (ant) Antenna/Omni Antenna; # antenna model

Set Val (ifqlen) 60; # max packet in ifq

Set val (nn) 19;# number of mobile nodes

Set val (rp) DSDV; # routing protocol

Set val(x) 1000; # X dimension of topography

Set val(y) 1000; # Y dimension of topography

set val(stop) 1000 ;# time of simulation end

set ns [new Simulator]

set tracefd [open out.tr w]

set namtrace [open out.nam w]

$ns trace-all $tracefd

$ns namtrace-all-wireless $namtrace $val(x) $val(y)

# set up topography object

set topo [new Topography]

$topo load_flatgrid $val(x) $val(y)

create-god $val(nn)

# configure the nodes

$ns node-config -adhocRouting $val(rp) \

-llType $val(ll) \

-macType $val(mac) \

-ifqType $val(ifq) \

-ifqLen $val(ifqlen) \

-antType $val(ant) \

-propType $val(prop) \

-phyType $val(netif) \

-channelType $val(chan) \

-topoInstance $topo \

-agentTrace ON \

-routerTrace ON \

-macTrace OFF \

-movementTrace ON

for {set i 0} {$i < $val(nn) } { incr i } {

set n($i) [$ns node]

}

# Provide initial location of mobilenodes

$n(0) set X_ 10.0

$n(0) set Y_ 0.0

$n(0) set Z_ 0.0

$n(1) set X_ 50.0

$n(1) set Y_ 0.0

$n(1) set Z_ 0.0

$n(2) set X_ 300.0

$n(2) set Y_ 260.0

$n(2) set Z_ 0.0

$n(3) set X_ 455.0

$n(3) set Y_ 95.0

$n(3) set Z_ 0.0

$n(4) set X_ 520.0

$n(4) set Y_ 200.0

$n(4) set Z_ 0.0

$n(5) set X_ 535.0

$n(5) set Y_ 80.0

$n(5) set Z_ 0.0

$n(6) set X_ 5.0

$n(6) set Y_ 600.0

$n(6) set Z_ 0.0

$n(7) set X_ 420.0

$n(7) set Y_ 85.0

$n(7) set Z_ 0.0

$n(8) set X_ 60.0

$n(8) set Y_ 600.0

$n(8) set Z_ 0.0

$n(9) set X_ 425.0

$n(9) set Y_ 495.0

$n(9) set Z_ 0.0

$n(10) set X_ 380.0

$n(10) set Y_ 380.0

$n(10) set Z_ 0.0

$n(11) set X_ 495.0

$n(11) set Y_ 490.0

$n(11) set Z_ 0.0

$n(12) set X 120.0

$n(12) set Y_ 350.0

$n(12) set Z_ 0.0

$n(13) set X_ 565.0

$n(13) set Y_ 490.0

$n(13) set Z_ 0.0

$n(14) set X_ 468.0

$n(14) set Y_ 35.0

$n(14) set Z_ 0.0

$n(15) set X_ 150.0

$n(15) set Y_ 100.0

$n(15) set Z_ 0.0

$n(16) set X_ 90.0

$n(16) set Y_ 0.0

$n(16) set z_ 0.0

$n(17) set X_ 110

$n(17) set Y_ 600.0

$n(17) set Z_ 0.0

$n(18) set X_ 60.0

$n(18) set Y_ 500.0

$n(18) set Z_ 0.0

# Set a TCP connection and send data between n(5) and n(3)

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(14) $tcp

$ns attach-agent $n(4) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 10.0 "$ftp start"

$ns at 45.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(4) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 60.0 "$ftp start"

$ns at 80.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(4) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 150.0 "$ftp start"

$ns at 190.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(2) $tcp

$ns attach-agent $n(12) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 300.0 "$ftp start"

$ns at 380.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(15) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 400.0 "$ftp start"

$ns at 480.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(18) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 490.0 "$ftp start"

$ns at 530.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(15) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 600.0 "$ftp start"

$ns at 680.0 "$ftp stop"

set tcp [new Agent/TCP/Newreno]

$tcp set class_ 2

set sink [new Agent/TCPSink]

$ns attach-agent $n(12) $tcp

$ns attach-agent $n(2) $sink

$ns connect $tcp $sink

set ftp [new Application/FTP]

$ftp attach-agent $tcp

$ns at 690.0 "$ftp start"

$ns at 780.0 "$ftp stop"

#defining heads

$ns at 0.0 "$n(12) label Sink"

$ns at 0.0 "$n(4) label CH"

$ns at 0.0 "$n(4) delete-mark N12"

$ns at 0.0 "$n(4) add-mark N12 blue circle"

$ns at 0.0 "$n(18) label CH"

$ns at 0.0 "$n(18) delete-mark N12"

$ns at 0.0 "$n(18) add-mark N12 blue circle"

$ns at 0.0 "$n(10) label CH"

$ns at 0.0 "$n(10) delete-mark N12"

$ns at 0.0 "$n(10) add-mark N12 blue circle"

$ns at 0.0 "$n(15) label CH"

$ns at 0.0 "$n(15) delete-mark N12"

$ns at 0.0 "$n(15) add-mark N12 blue circle"

$ns at 0.0 "$n(12) delete-mark N12"

$ns at 0.0 "$n(12) add-mark N12 green circle"

#$ns at 10.0 "$n(14) delete-mark N14"

$ns at 10.0 "$n(14) add-mark N14 red circle"

# Define node initial position in nam

$ns initial_node_pos $n(0) 30

$ns initial_node_pos $n(1) 30

$ns initial_node_pos $n(2) 30

$ns initial_node_pos $n(3) 30

$ns initial_node_pos $n(4) 60

$ns initial_node_pos $n(5) 30

$ns initial_node_pos $n(6) 30

$ns initial_node_pos $n(7) 30

$ns initial_node_pos $n(8) 30

$ns initial_node_pos $n(9) 30

$ns initial_node_pos $n(10) 60

$ns initial_node_pos $n(11) 30

$ns initial_node_pos $n(12) 90

$ns initial_node_pos $n(13) 30

$ns initial_node_pos $n(14) 30

$ns initial_node_pos $n(15) 60

$ns initial_node_pos $n(16) 30

$ns initial_node_pos $n(17) 30

$ns initial_node_pos $n(18) 60

#defining head

# node_(1) starts to move towards node_(0)

$ns at 100.0 "$n(2) setdest 450.0 250.0 3.0"

$ns at 196.0 "$n(2) setdest 100.0 333.0 4.0"

$ns at 530.0 "$n(2) setdest 4.0 10.0 0.5"

# Telling nodes when the simulation ends

for {set i 0} {$i < $val(nn) } { incr i } {

$ns at $val(stop) "$n($i) reset";

}

# ending nam and the simulation

$ns at $val(stop) "$ns nam-end-wireless $val(stop)"

$ns at $val(stop) "stop"

$ns at 800.0 "puts \"end simulation\" ; $ns halt"

proc stop {} {

global ns tracefd namtrace

$ns flush-trace

close $tracefd

close $namtrace

}

$ns run

CHAPTER

8. TESTING

Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation or reliability estimation correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.

8.1. UNIT TESTING

Unit testing is a software verification and validation method in which tests are conducted to find that the individual units of source code are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure.

Test case ID

Test Case

Input

Expected output

Actual Output

Results

1.1

Initial implementation

15 nodes

15 nodes with specified location

15 nodes with specified location

pass

Table 1: Test case for Initial implementation

Test case ID

Test Case

Input

Expected output

Actual output

Results

1.1

Event Detection

Event occur

Source node sent the data to CH

Source node sent the data to CH

Pass

1.2

Request

Cluster head with data

CH request to MDC

CH request to MDC

Pass

1.3

MDC movement

MDC collect the request

MDC moving to collect the data

MDC moving to collect the data

pass

Table 2: Test case for Event Detection

Test Case ID

Test Case

Input

Expected output

Actual output

Results

1.1

MDC collect the data

MDC moving to nearest CH

Cluster head send the data to MDC

Cluster head send the data to MDC

Pass

1.2

MDC sent the Data

MDC near in cluster head

MDC sent the data to Base station

MDC sent the data to base station

Pass

Table 3: Test case for MDC Collect the data

8.2 INTEGRATION TESTING:

Integration testing is a logical extension of unit testing. In its simplest form, two units have already been tested are combined into a component and the interface between them is tested.

A component in this sense refers to an integrated aggregate of more than one unit. In other words, integration testing identifies problems that occur when units are combined. By using a test plan that requires you to test each unit and ensure the viability of each before combining units, you know that any errors discovered when combining units are likely related to the interface between units. This method reduces the number of possibilities for simpler level of analysis.

Test Case ID

Test Case

Input

Expected output

Actual output

Results

1.1

Initial implementation

15 nodes

15 nodes with specified location

15 nodes with specified location

Pass

1.2

Event Detection

Event occur

Source node sent the data to CH

Source node sent the data to CH

Pass

1.3

Request

Cluster head with data

CH request to MDC

CH request to MDC

Pass

1.4

MDC movement

MDC collect the request

MDC moving to collect the data

MDC moving to collect the data

Pass

1.5

MDC collect the data

MDC moving to nearest CH

Cluster head send the data to MDC

Cluster head send the data to MDC

Pass

1.6

MDC sent the Data

MDC near in cluster head

MDC sent the data to Base station

MDC sent the data to Base station

Pass

Table 4: Integration test for increasing network lifetime

CHAPTER 9

RESULT AND ANALYSIS

9. Event Driven Mechanism:

When event detect, sensor node send the data to the cluster head, then cluster head give request to the mobile data collector. Then mobile data collector going to collect the data from the cluster head and it can save more energy and reduce the data latency on the network. Suppose cluster head simultaneously give request to the mobile data collector, then mobile data collector periodic based collect the data from the cluster head.

9.2 SCREEN SHOTS

C:\Users\HOME\Desktop\New folder\terminal.jpg

Figure 7(a): snapshot of Terminal

2. Simulation.

C:\Users\HOME\Desktop\New folder\simulation.jpg

Figure 7(b): snapshot of simulation

3. Event Detection mechanism:

C:\Users\HOME\Desktop\New folder\y1.jpg

Figure 7(c): snapshot of Event Detection Mechanism

C:\Users\HOME\Desktop\New folder\event detection.jpg

Figure 7(d): snapshot of Sensor node send the data to the cluster head

C:\Users\HOME\Desktop\New folder\h1.jpg

Figure 7(e): snapshot of Cluster head give request to Mobile Data Collector

C:\Users\HOME\Desktop\New folder\y1.jpg

Figure 7(f): snapshot of Mobile Data Collector moving to Cluster Head.

C:\Users\HOME\Desktop\New folder\p1.jpg

Figure 7(g): snapshot of Cluster head send the data to Mobile data collector

C:\Users\HOME\Desktop\New folder\saa.jpg

Figure 7(h): snapshot of Mobile data collector moving to Base station

C:\Users\HOME\Desktop\New folder\p6.jpg

Figure 7(i): snapshot of Mobile data collector moving to Base station

C:\Users\HOME\Desktop\New folder\p5.jpg

Figure 7(j): snapshot of Mobile Data collector moving to base station

C:\Users\HOME\Desktop\New folder\p7.jpg

Figure 7(k): snapshot of Mobile data collector send the data to the base station

C:\Users\HOME\Desktop\New folder\p9.jpg

Figure 7(l): snapshot of cluster head give request to Mobile data collector

C:\Users\HOME\Desktop\New folder\p10.jpg

Figure 7(m): snapshot of Cluster head give request to the mobile data collector

C:\Users\HOME\Desktop\New folder\p16.jpg

Figure 7(o): snapshot of Mobile Data collector moving to cluster head

C:\Users\HOME\Desktop\New folder\p20.jpg

Figure 7(p): snapshot of Mobile Data collector send the data to Base station

9.2 Analysis:

The graph represents in fig has simulation time on x-axis and data latency on y-axis .From the graph it is evident that data latency on our proposed method better than existing method.

C:\Users\HOME\Desktop\New folder\data latency.jpg

Fig: 8(a) Data Latency

C:\Users\HOME\Desktop\New folder\energy level.jpg

Fig: 8(b): Energy Level

CHAPTER 10

CONCLUSION

Energy is the main concern for wireless senor network. The proposed method user Mobile data collector to collect the data .whenever an event is detected then only cluster head give request to mobile data collector, then mobile data collector collect the data .So mobile data collector helps to avoid unnecessary energy consumptions as well as it increases the data latency.

CHAPTER 11

FUTURE ENHANCEMENT

In future it will extend to secure data collection by using mobile data collector. When event occur, sensor node send the data to cluster head, then cluster head request to mobile data collector, after mobile data collector check whether it is original request or malicious request, if it original request mobile data collector going to collect the data from the cluster head.