symbols forming a superframe when the superframe
order (SO) is equal to 0, and BO is Beacon Order that
means how often the beacon is to be transmitted.
aBaseSuperframeDuration is around 960 symbols
recommended in (IEEE, 2011), BO is one value from
0 to 15 and SO is one value from 0 to BO. The active
period, defined by SuperframeDuartion (SD), is cal-
culated by:
].[2 symbolsionframeDurataBaseSuperSD
SO
(2)
2.2 Process When Beacon Frame Is
Lost
Even though we extensively research, no literature
describing the process when Beacon frame is not suc-
cessfully received has been found. Only both of
IEEE802.15.4 and IEEE802.15.4e standards (IEEE,
2011), (IEEE, 2012) describes process for the case in
which GTSs are allocated in the superframe. Based
on standards, if a device requesting GTSs fails to re-
ceive Beacon frame, it has to hold its transmission
during GTSs within the superframe. Even though it
was assigned with GTSs in the previous superframe,
it need to hold transmissions in the current super-
frame. Since a Beacon frame contains the information
on superframe structure like period of CAP, the allo-
cation of GTS, and so on, and the superframe struc-
ture can vary in every superframe, if a device fails to
receive a Beacon frame, it can be assumed that it
needs better to hold its transmissions during the su-
perframe to prevent from collisions with other sched-
uled transmissions. This is ensured for the cases that
the net-work parameters like the number of devices,
traffic loads, etc. are frequently fluctuated.
Moreover, based on the standards, if an
aMaxLostBeacons number of Beacon frames are not
successfully received at a device, the device declares
synchronization loss and starts orphan channel scan
after discarding all buffered packets. That is, the de-
vice restart to associate with new piconet and this pro-
cess waists lots of time.
Overall, the losses of Beacon frames cause hold-
ing devices’ transmissions as well as the synchroni-
zation loss, and as consequences it severely degrades
the network performances.
3 PROPOSED PROTOCOL
As mentioned in Section 2, the loss of Beacon frame
makes devices to hold their transmissions during
whole superframe period. In addition, aMaxLostBea-
cons time of Beacon frame losses causes re-associa-
tion process starting from scanning process. Both of
holding transmission and starting re-association pro-
cess degrades performances of LR-WPANs. Even
though many studies proposes methods to switch
channels to reduce beacon loss, Beacon frames are
still lost due to channel characteristics such as noise,
interference, fading and so on. While preventing from
losing Beacon frames has been studied a lot, there is
no study on enhancement for the process when a Bea-
con frame is lost. Therefore, in this paper, we try to
propose a backward-compatible and effective en-
hanced protocol.
The basic ides of the proposed protocol is to al-
lows a device not receiving a Beacon frame (herein-
after it is called ‘failed-device’) to transmit its queued
data not only in CAP, but also in Inactive period only
if the device cannot wait GTSs in the next upcoming
superframe because of delay constraints of the queued
data frames. Since every superframe is guaranteed to
have at least minimum CAP period which is around 7
slots, all failed-devices can safely transmit their data
during the minimum CAP period.
3.1 Protocol Operations
The detailed process of the proposed protocol for a
failed-device is as follows.
At the moment a device expects to receive a Bea-
con frame, if the frame is not received, the device de-
clares to fail to receive a Beacon frame. Then, it
checks if it has a data that was scheduled to be trans-
mitted in a GTS. If it has ones, the device checks if
the queued data can be held by the next upcoming su-
perframe. If the transmission can be held, the device
holds the data and wait for the next Beacon frame.
However, if the data is delay-constraint traffic, so that
it need to be transmitted in the current superframe, it
transmit the data during CAP. Before transmitting the
data, the device forms data frame by setting Frame
Type field to 100 in binary number. Binary number
100 is not used in IEEE802.15.4 standard and is used
to indicate that the data is transmitted by the rule of
the proposed protocol. Then, the data frames are
transmitted only during the possible minimum CAP
period.
Based on IEEE802.15.4 standard, the minimum
CAP period is defined as maximum number of slots
assigned for CFP minus the number of slots in a su-
perframe. Therefore, during CAP
min
, the failed-device
can safely transmit its data because CAP
min
is a guar-
anteed period.
At the end of 16 slots which is at the end of current
superframe period, if the device still has queued data
to be transmitted in the current superframe, it keeps
Performance Improvement in Beacon-enabled LR-WPAN-based Wireless Sensor Networks
91