Академический Документы
Профессиональный Документы
Культура Документы
fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
1
I. I NTRODUCTION
In a multi-hop wireless network, nodes cooperate in relaying/routing traffic. An adversary can exploit this cooperative
nature to launch attacks. For example, the adversary may first
pretend to be a cooperative node in the route discovery process.
Once being included in a route, the adversary starts dropping
packets. In the most severe form, the malicious node simply
stops forwarding every packet received from upstream nodes,
completely disrupting the path between the source and the
destination. Eventually, such a severe Denial-of-Service (DoS)
attack can paralyze the network by partitioning its topology.
Even though persistent packet dropping can effectively
degrade the performance of the network, from the attackers
standpoint such an always-on attack has its disadvantages.
First, the continuous presence of extremely high packet loss
rate at the malicious nodes makes this type of attack easy to be
detected [25]. Second, once being detected, these attacks are
easy to mitigate. For example, in case the attack is detected
T. Shu is with the Department of Computer Science and Engineering,
Oakland University, Rochester, MI, USA (e-mail: shu@oakland.edu). M.
Krunz is with the Department of Electrical and Computer Engineering, the
University of Arizona, Tucson, AZ, USA (e-mail: krunz@email.arizona.edu).
The work of T. Shu was supported in part by NSF under Grant CNS1343156. The work of M. Krunz was supported by NSF (Grants CNS-1016943
and IIP-1265960) and by ARO (Grant W911NF-13-1-0302). Any opinions,
findings, conclusions, or recommendations expressed in this paper are those
of the author(s) and do not necessarily reflect the views of NSF or ARO.
A preliminary version of this paper was presented in ACM WiSec 2012
Conference, Tucson, AZ, April 2012.
but the malicious nodes are not identified, one can use the
randomized multi-path routing algorithms [28][29] to circumvent the black holes generated by the attack, probabilistically
eliminating the attackers threat. If the malicious nodes are
also identified, their threats can be completely eliminated by
simply deleting these nodes from the networks routing table.
A malicious node that is part of the route can exploit its
knowledge of the network protocol and the communication
context to launch an insider attackan attack that is intermittent, but can achieve the same performance degradation
effect as a persistent attack at a much lower risk of being
detected. Specifically, the malicious node may evaluate the
importance of various packets, and then drop the small amount
that are deemed highly critical to the operation of the network.
For example, in a frequency-hopping network, these could
be the packets that convey frequency hopping sequences for
network-wide frequency-hopping synchronization; in an ad
hoc cognitive radio network, they could be the packets that
carry the idle channel lists (i.e., white spaces) that are used
to establish a network-wide control channel. By targeting
these highly critical packets, the authors in [21], [24], [25]
have shown that an intermittent insider attacker can cause
significant damage to the network with low probability of
being caught. In this paper, we are interested in combating
such an insider attack. In particular, we are interested in the
problem of detecting the occurrence of selective packet drops
and identifying the malicious node(s) responsible for these
drops.
Detecting selective packet-dropping attacks is extremely
challenging in a highly dynamic wireless environment. The
difficulty comes from the requirement that we need to not
only detect the place (or hop) where the packet is dropped, but
also identify whether the drop is intentional or unintentional.
Specifically, due to the open nature of wireless medium,
a packet drop in the network could be caused by harsh
channel conditions (e.g., fading, noise, and interference, a.k.a.,
link errors), or by the insider attacker. In an open wireless
environment, link errors are quite significant, and may not
be significantly smaller than the packet dropping rate of the
insider attacker. So, the insider attacker can camouflage under
the background of harsh channel conditions. In this case, just
by observing the packet loss rate is not enough to accurately
identify the exact cause of a packet loss.
The above problem has not been well addressed in the
literature. As discussed in Section II, most of the related works
preclude the ambiguity of the environment by assuming that
malicious dropping is the only source of packet loss, so that
there is no need to account for the impact of link errors. On
the other hand, for the small number of works that differentiate
between link errors and malicious packet drops, their detection
algorithms usually require the number of maliciously-dropped
packets to be significantly higher than link errors, in order to
achieve an acceptable detection accuracy.
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
2
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
3
Fig. 1.
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
4
B. Adversarial Model
The goal of the adversary is to degrade the networks
performance by maliciously dropping packets while remaining
undetected. We assume that the malicious node has knowledge
of the wireless channel, and is aware of the algorithm used
for misbehavior detection. It has the freedom to choose what
packets to drop. For example, in the random-drop mode, the
malicious node may drop any packet with a small probability
pd . In the selective-mode, the malicious node only drops
packets of certain types. A combination of the two modes may
be used. We assume that any node on PSD can be a malicious
node, except the source and the destination. In particular, there
can be multiple malicious nodes on PSD .
We consider the following form of collusion between malicious nodes: A covert communication channel may exist
between any two malicious nodes, in addition to the path
connecting them on PSD . As a result, malicious nodes can
exchange any information without being detected by Ad or
any other nodes in PSD . Malicious nodes can take advantage
of this covert channel to hide their misbehavior and reduce the
chance of being detected. For example, an upstream malicious
node may drop a packet on PSD , but may secretely send this
packet to a downstream malicious node via the covert channel.
When being investigated, the downstream malicious node can
provide a proof of the successful reception of the packet. This
makes the auditor believe that the packet was successfully
forwarded to the downstream nodes, and not know that the
packet was actually dropped by an upstream attacker.
C. Problem Statement
Under the system and adversary models defined above,
we address the problem of identifying the nodes on PSD
that drop packets maliciously. We require the detection to be
performed by a public auditor that does not have knowledge
of the secrets held by the nodes on PSD . When a malicious
node is identified, the auditor should be able to construct a
publicly verifiable proof of the misbehavior of that node. The
construction of such a proof should be privacy preserving, i.e.,
it does not reveal the original information that is transmitted
on PSD . In addition, the detection mechanism should incur
low communication and storage overheads, so that it can be
applied to a wide variety of wireless networks.
link error
malicious drop
+ link error
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
0
-300
-200
-100
100
200
300
Packet separation
Fig. 2.
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
5
(3)
sji
ji
s1i
1i
=
=
=
=
..
.
=
=
..
.
=
=
encryptkeyK (sKi )
sKi ||MACkeyK (
sKi )
encryptkeyK1 (sK1i ||Ki )
sK1i ||MACkeyK1 (
sK1i )
encryptkeyj (sji ||j+1i )
sji ||MACkeyj (
sji )
encryptkey1 (s1i ||2i )
s1i ||MACkey1 (
s1i )
(4)
1i
key1
1i
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
(6)
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
6
c
s(j) =
sjiji .
(7)
i=1,bji =0
e(s
, g) = e(
(j)
H2 (i||j)cji ur , v).
(8)
i=1,bji =0
j =
M
1
i=0
|j (i) fc (i)|
.
fc (i)
(10)
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
7
c
e(s(j) , g) = e
sjiji , g
= e
= e
= e
= e
= e
i=1,bji =0
M
xcji
{H2 (i||j)uri }
i=1,bji =0
M
x
cji
{H2 (i||j)uri }
i=1,bji =0
M
H2 (i||j)cji ucji ri , g
H2 (i||j)cji ur , g x
(j)
i=1,bji =0
M
i=1,bji =0
, g
x
i=1,bji =0
M
, g
H2 (i||j)cji ur , v .
(j)
(11)
So Theorem 1 holds.
Theorem 2: The construction specified in Section IV-B is
secure under the collusion model defined in Section III-B, i.e.,
an adversary that does not receive a packet Pi cannot claim
receiving this packet in its bj by forging a HLA signature for
a random linear combination of the received packets, even if
this adversary colludes with any other malicious node in PSD .
Proof: For a given node nj , our construction essentially
follows the BLS-signature-based HLA construction described
in [27]. Under the implicitly assumed condition of no collusion between attackers, the authors in [27] proved that the
construction is secure, i.e., no adversary can forge a response
to a random challenge if it does not know the HLA signature
of each packet in the linear combination. So here, we only
need to show that collusion between malicious nodes does not
give the attacker more information about the HLA signature
of the packets. This can be shown by observing the following
novel properties of our HLA construction:
1) For a packet Pi , the signature scheme specified in (3)
dictates that its HLA signature sji is not only tied to the
packet sequence number (i), but also related to the node
index (j) that is relaying the packet. This means that for
the same packet, each hop on PSD is given a different
HLA signature. The verification scheme in (8) accounts
for both i and j. In the no-collusion case, by treating
the concatenation of (i||j) as a meta packet sequence
number, the security of our construction can be proved
in the same way as that in [27].
2) The way that the HLA signatures are distributed to nodes
on PSD , as specified in (4), dictates that an upstream
node nj cannot get a copy of the HLA signature sj i
of a downstream node nj , where j < j K, unless
the downstream node nj receives the signature sj i first
on PSD and then sends it through the covert channel to
the upstream node nj . Therefore, there is no way for
a downstream malicious node to get any information
on its HLA signature if the upstream attacker drops the
packet. As a result, the secret information exchange on
the covert channel does not help the adversary to get
more information on its HLA signature than the scenario
where there is no collusion.
Combining the above arguments, Theorem 2 is proved.
Theorem 3: The proposed scheme ensures that the packetreception bitmap reported by a node in PSD is truthful.
The validity of Theorem 3 is straightforward, because Theorem 2 guarantees that the node cannot understate its packet
loss information. At the same time, from our discussion in
Section IV-B4, it is clear that a malicious node cannot overstate
its packet loss either. So a node must report its actual packet
reception information truthfully to Ad .
Theorem 4: Our HLA construction is publicly verifiable and
privacy preserving, i.e., the auditor Ad does not require the
secret key of the HLA scheme to verify a nodes response.
In addition, Ad cannot determine the content of the packets
transmitted over PSD from the information submitted by
nodes.
Proof: Public verifiability is clear from the construction of the
scheme. The privacy-preserving property is guaranteed by the
application of the secure hash function H1 . More specifically,
instead of directly computing the HLA signature for a packet
Pi , our construction computes the signature for the image of
the packet ri = H1 (Pi ). During the auditing phase, Ad can
collect a set of linear combinations of ri s. So it is possible
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
8
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
9
B. Results
1) Random Packet Dropping: The detection accuracy is
shown in Figure 4 as a function of the malicious randomdrop rate PM . In each subfigure, there are two sets of curves,
representing the proposed algorithm and the optimal ML
scheme, respectively. In each set of curves, the one in the
middle represents the mean, and the other two represent the
95% confidence interval. In general, the detection accuracy of
both algorithms improves with PM (i.e., the detection error
decreases with PM ). This is not surprising, because malicious
packet drops become more statistically distinguishable as the
attacker starts to drop more packets. In addition, this figure
shows that for th = 10%, the proposed algorithm provides
slightly higher false-alarm rate (subfigure (c)) but significantly
lower miss-detection probability (subfigure (b)) than the ML
scheme. A low miss-detection probability is very desirable in
our context, because it means a malicious node can be detected
with a higher probability. The slightly higher false-alarm rate
should not be a problem, because a false alarm can be easily
recognized and fixed in the post-detection investigation phase.
Most importantly, the overall detection-error probability of
the proposed scheme is lower than that of the ML scheme
(subfigure (a)). We are especially interested in the regime
when PM is comparable to the average packet loss rate due
0.01
to link errors, given by PGBPGB
+PBG = 0.01+0.5 0.02. This
regime represents the scenario in which the attacker hides
its drops in the background of link errors by mimicking the
channel-related loss rate. In this case, the ML scheme cannot
correctly differentiate between link errors and malicious drops.
For example, when PM = 0.01, the ML scheme results in
Pmd = 80% and Pf a = 23%. This is close to arbitrarily
ruling that every packet loss is due to link error only, leading
to an overall detection-error rate of 50% (see subfigure (a)).
Our proposed algorithm, on the other hand, achieves a much
better detection accuracy, because its Pmd and Pf a are both
lower than those under the ML scheme. As a result, when
PM = 0.01, the total detection-error rate of the proposed
algorithm is about 35%. When PM is increased to 0.04,
Perror of the proposed scheme reduces to only 20%, which
is roughly half of the error rate of the ML scheme at the
same PM . Remembering that the detection-error rate of the
ML scheme is the lowest among all detection schemes that
only utilize the distribution of the number of lost packets,
the lower detection-error rate of the proposed scheme shows
that exploiting the correlation between lost packets helps in
identifying the real cause of packet drops more accurately. The
effect of exploiting the correlation is especially visible when
the malicious packet-drop rate is comparable with the link
error rate. Meanwhile, we also note that the 95% confidence
interval of the proposed scheme is wider than that of the
ML scheme. This is because the decision variable j in the
proposed scheme is a second-order function of the random
packet loss process, while the decision variable in the ML
scheme (i.e., number of lost packets) is a first order function of
the same packet loss process. As a result, the decision variable
of the proposed scheme possesses more randomness than that
of the ML scheme, as reflected by the wider 95% confidence
interval.
In Figure 5, we plot the detection accuracy as a function of
the size of the packet-loss bitmap (M ). It can be observed that
Perror for the proposed scheme decreases with M . However,
as M becomes sufficiently large, e.g., M = 30 in our case,
a further increase in the size of the bitmap does not lead to
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
10
0.4
0.8
M=30
0.5
ML scheme
0.7
ML scheme
0.4
0.3
0.2
0.6
0.5
0.4
Proposed scheme
0.3
0.2
0.2
0.15
0.1
0.02
0.04
0.06
0.08
0.1
0.12
0.14
ML scheme
0
0.02
0.06
0.08
0.1
0.12
0.05
0.14
0.02
0.04
0.06
0.08
0.1
0.12
0.14
Fig. 4.
PM=0.04, PGB=0.01,
PBG=0.5
ML scheme
0.45
0.4
0.35
0.3
0.25
0.2
0.15
Proposed scheme
0.1
0.05
10
15
20
25
30
35
40
45
0.4
50
55
0.8
0.6
0.5
0.4
0.3
0.2
20
30
BG
0.3
0.25
0.2
0.15
0.1
40
50
60
ML scheme
0.05
10
20
GB
Proposed scheme
Proposed scheme
0
10
60
0.35
ML scheme
0.7
0.1
P =0.04, P =0.01
M
GB
PBG=0.5
0.9
Missdetection Probability
0.5
Falsealarm Probability
0.55
30
40
50
60
Fig. 5.
0.45
0.7
ML scheme
0.35
0.3
0.25
0.2
0.15
Proposed scheme
0.1
0.01
0.015
0.02
0.025
0.03
0.035
0.04
0.045
PGB
0.05
0.8
0.6
PM=0.1, PBG=0.5,
0.5
M=30
ML scheme
0.7
Falsealarm Probability
Missdetection Probability
0.4
Fig. 6.
0.04
Detectionerror Probability
0.25
0.1
Proposed scheme
Detectionerror Probability
BG
0.3
0.1
Proposed scheme
PGB=0.01,
P =0.5, M=30
0.35
Falsealarm Probability
PGB=0.01, PBG=0.5,
0.6
PGB=0.01,
PBG=0.5, M=30
0.9
Missdetection Probability
Detectionerror Probability
0.7
0.4
0.3
0.2
Proposed scheme
0.1
0
0.01
0.6
Proposed scheme
0.5
0.4
ML scheme
0.3
0.2
0.015
0.02
0.025
0.03
0.035
0.04
PGB
0.045
0.05
0.1
0.01
0.015
0.02
0.025
0.03
0.035
0.04
0.045
0.05
PGB
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
11
varied in the simulation. Finally, we use the same GilbertElliot model as previous simulations to generate the wireless
channel.
Figure 10.(a) plots detection accuracy as a function of the
control packet dropping rate. It can be observed that under
the correlated control and data packet losses, the proposed
scheme achieves significantly better detection accuracy than
the ML scheme for all tested control packet dropping rates, a
similar trend to those observed when such correlation is not
considered (e.g., see the random packet drops in Figure 4.(a)).
Meanwhile, it can also be observed from Figures 10.(a) and
4.(a) that, compared with the results of uncorrelated packet
drops, the detection-error probability under correlated packet
losses is in general smaller, indicating that the correlation
between control and data packet losses may help to improve
the detection accuracy. This is true for both schemes. This
is because such correlation further amplifies the distinction
between the statistics of the wireless channel and the malicious
packet drops, making the detection easier.
We study the detection accuracy as a function of average
number of data packets transmitted between two consecutive
control packets (Ldata ) in Figure 10.(b). It can be observed
that this parameter has little impact on the ML scheme,
because under a given control packet loss rate, the overall
(control+data) packet loss rate does not change with Ldata .
ML scheme relies on detecting the number of lost packets,
and thus is not affected by Ldata . In contrast, the proposed
scheme may benefit from a larger Ldata : even if the average
detection accuracy does not improve much, its 95% confidence
interval shrinks significantly with Ldata . This is explained by
comparing the packet loss patterns of the wireless channel and
the correlated packet drops. Specifically, on average 2 packets
are lost in a row in a wireless link error (this is given by
1/(1 PBG ) = 1/0.5 = 2), while on average Ldata packets
are lost under each malicious drop. Therefore, the distinction
between the above two packet-loss patterns increases with
Ldata . The proposed scheme exploits such a distinction in
patterns and thus can benefit from larger Ldata .
In Figure 10.(c) we plot the detection-error probability as
a function of channel state transition parameter PGB . It can
be observed that the detection accuracy deteriorates with the
increase of PGB , because it becomes more and more difficult
to decide the actual source of packet loss when link error rate
approaches the malicious packet dropping rate. Once again,
the proposed scheme consistently achieves higher detection
accuracy than ML scheme in all simulated cases.
4) Block-Based Detection: In this series of simulations,
we study the detection accuracy of block-based algorithms
as a function of block size. Figure 11.(a) plots the detection
accuracy for random packet drops under two packet drop
probabilities: high (PM = 0.08) and low (PM = 0.01).
The performance of the ML scheme is also plotted in the
same figure for comparison. In general, it shows that for
both cases the detection error increases with the block size.
This is expected, as a larger block size hides more details
of packet losses, and therefore makes the actual correlation
of lost packets more difficult to calculate. Meanwhile, the
benefits of blocked-based algorithm is also observed: it is able
to trade computation complexity for better detection accuracy.
For example, under low packet dropping rate, it shows that the
block-based algorithm can reduce the computation overhead of
the baseline HLA detection by 10 folds, and still be able to
achieve better detection accuracy than the ML scheme. At high
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
12
0.6
ML scheme
0.5
0.4
0.3
Proposed scheme
0.2
0.28
0.9
PGB=0.01, PBG=0.5,
0.26
0.8
M=50
0.24
Falsealarm Probability
Missdetection Probability
Detectionerror Probability
0.7
ML scheme
0.7
0.6
0.5
0.4
0.3
Proposed scheme
0.2
ML scheme
P =0.01, P =0.5,
0.22
GB
BG
M=50
0.2
0.18
0.16
0.14
0.12
0.1
0.1
0.1
0.08
Proposed scheme
0
1.5
2.5
3.5
4.5
2.5
3.5
4.5
3.5
4.5
0.2
0.4
ML scheme
0.35
0.3
% of maliciously
dropped packets = 10%
PGB=0.01, PBG=0.5
0.25
0.2
0.15
Proposed scheme
0.1
0.18
0.8
ML scheme
0.7
Falsealarm Probability
Missdetection Probability
0.6
0.5
% of maliciously dropped
packets =10%
PGB=0.01, PBG=0.5
0.4
0.3
0.2
Proposed scheme
0.1
ML scheme
0.16
0.14
0.12
0.1
0
10
15
20
25
30
35
40
45
Proposed scheme
0.1
10
50
15
20
25
30
35
40
45
0.08
10
50
15
20
25
30
35
40
45
50
0.045
0.05
0.09
0.1
Fig. 8.
0.7
0.8
0.35
0.6
0.7
Missdetection Probability
0.4
ML scheme
0.3
No. of maliciously
dropped packets = 3
PBG=0.5, M=50
0.25
0.2
0.15
0.1
0.05
0
0.01
Proposed scheme
0.015
0.02
0.025
0.03
0.035
0.04
0.045
0.5
0.4
ML scheme
0.3
0.2
Proposed scheme
0.1
0
0.015
0.02
0.025
Proposed scheme
0.5
0.4
0.3
0.2
0.03
0.035
0.04
0.045
0
0.01
ML scheme
0.05
0.015
0.02
0.025
0.03
PGB
GB
0.6
No. of maliciously
dropped packets = 3
PBG=0.5, M=50
0.1
0.1
0.01
0.05
Falsealarm Probability
Detectionerror Probability
2.5
0.9
0.05
Detectionerror Probability
Detection accuracy vs. number of maliciously dropped packets (selective packet-drop case).
0.45
0.035
0.04
PGB
0.4
0.25
0.25
0.2
0.15
Detectionerror Probability
0.3
0.35
Detectionerror Probability
0.35
Detectionerror Probability
1.5
0.5
0.2
ML scheme
0.15
0.1
Proposed scheme
BG
0.05
P =0.5, M=50, L
BG
=5
data
ML scheme
0.2
0.15
0.1
0.1
Proposed scheme
Proposed scheme
0.05
1.5
0.05
0.1
0.15
0.2
0.25
Ldata
10
0.05
0.02
0.03
0.04
0.05
0.06
0.07
PGB
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
0.08
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
13
0.5
0.55
0.5
0.5
0.45 ML scheme (PM=0.01)
ML scheme (P =0.08)
0.4
0.35
P =0.04,
M
PGB=0.01,
PBG=0.5,
0.4
Detectionerror probability
0.45
Detectionerror probability
Detectionerror probability
0.55
ML scheme
M=60
0.35
0.3
P =0.01,
GB
P =0.5, M=30
0.25
0.3
P =0.01
BG
0.2
PM=0.08
1
10
0.25
Block size
Fig. 11.
1.5
2.5
3.5
4.5
ML scheme
(3 packet drops/50 packets)
0.3
0.25
P =0.01,
GB
P =0.5, M=50
0.2
BG
0.15
0.1
5
Block size
0.05
10
Block size
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI
10.1109/TMC.2014.2330818, IEEE Transactions on Mobile Computing
14
15361233 (c) 2013 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See
http://www.ieee.org/publications_standards/publications/rights/index.html for more information.