tag:blogger.com,1999:blog-38294949216648995622024-03-05T23:13:47.778-08:00ilabsAnonymoushttp://www.blogger.com/profile/14545770648325591855noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3829494921664899562.post-70481145534715654252016-12-07T00:32:00.000-08:002016-12-07T00:32:44.691-08:00NarrowBand IoT <div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: justify;">
</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
NB-IoT is one of the latest technology in Internet of Things (IoT). This can change the face of the IoT application with less resource to build an IoT application.Three Years ago, i wrote one article "Evolution in Long Term Evolution (E-LTE)" about the relevance of IoT device connectivity to the backbone, In that article , i mentioned the importance of the best IoT connectivity to the Backbone and also i recommend the Telecom based technology to support IoT Device like LTE , WCDMA technologies. NB-IoT is the solution for all the connectivity problems in IoT. This can be reduce the human effort drastically for connectivity and posses wide range of application diversity.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgm4vucg3WNRlwBIZbPaVp2D8ZuYWwxPn99XQ1Z9R_-OR-sZIU3Yr-DQE01APOfCK2-J7qtcpDh5t4rdVMDxNCygPPXTUWMgZZzQRCce0q7-16PkRioCdq7v7dN-xj3_RQiqF3zLPjTGlzE/s1600/NB-IoT_blog_article_image_0.PNG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgm4vucg3WNRlwBIZbPaVp2D8ZuYWwxPn99XQ1Z9R_-OR-sZIU3Yr-DQE01APOfCK2-J7qtcpDh5t4rdVMDxNCygPPXTUWMgZZzQRCce0q7-16PkRioCdq7v7dN-xj3_RQiqF3zLPjTGlzE/s320/NB-IoT_blog_article_image_0.PNG" width="320" /></a></div>
<div style="text-align: justify;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEige15KH-5ES9fRRmBWF5YdIcDYs9HavllQ6z9r_RrHRb9yNTOgahg3GiPzN0xQ5kOMN_H2xl6yZEJ9I21SwSHIKXAYv1p9OIWYdsLxNALohAscbDtp8a0aGvGgBDY_7OoQs-Yj1PaCaq2i/s1600/Iot.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="152" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEige15KH-5ES9fRRmBWF5YdIcDYs9HavllQ6z9r_RrHRb9yNTOgahg3GiPzN0xQ5kOMN_H2xl6yZEJ9I21SwSHIKXAYv1p9OIWYdsLxNALohAscbDtp8a0aGvGgBDY_7OoQs-Yj1PaCaq2i/s320/Iot.png" width="320" /></a> This technology is developed by 3GPP (3rd Generation Partnership Program) to enable a wide range of devices and service to be connected using the cellular telecommunication bands. This technology uses a dedicated spectrum for the IoT range of devices and it will reduce the congestion with other connectivity</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
This enables a unified way of communication between the IoT devices and the IoT Backbone. There are few vendors were actively participated in past few years in this project, among them, some of them successfully developed NB-IoT supported chip, Have a look at it...</div>
<div style="text-align: justify;">
</div>
<div style="text-align: justify;">
</div>
<table class="wikitable"><tbody>
<tr><th style="text-align: center;"><br /></th><th style="text-align: center;">U-blox</th>
<th style="text-align: center;"><br /></th>
<th style="text-align: center;"><br /></th>
<th style="text-align: center;"><br /></th>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;">https://www.u-blox.com/en/narrowband-iot-nb-iot</td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;">Its Really Interesting... :) fun too..</td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
</tr>
<tr>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td>
<td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"><br /></td><td style="text-align: center;"> </td><td style="text-align: center;"> </td></tr>
</tbody></table>
<br />
<table class="wikitable"><tbody>
<tr><td> </td><td><br /></td><td><br /></td><td><br /></td><td><br /></td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td>dasdasddddddddddddddddddddddddddddddddddddddddddddddddddddddd</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr>
</tbody></table>
</div>
Anonymoushttp://www.blogger.com/profile/14545770648325591855noreply@blogger.com0tag:blogger.com,1999:blog-3829494921664899562.post-83908253671773084982015-12-20T22:35:00.000-08:002015-12-20T22:35:03.777-08:00Interoperabilty Issues Between TinyOS and ZigBee Devices<div dir="ltr" style="text-align: left;" trbidi="on">
<style type="text/css">p { margin-bottom: 0.21cm; }a:link { }</style>
<br />
<div align="center" style="margin-bottom: 0cm; margin-left: 0.55cm; text-indent: -0.52cm;">
<span style="font-size: small;"><i><b>XBee IEEE 802.15.4
ZigBee OEM Stack Interoperability Issues with TinyOS IEEE
802.15.4 Stack</b></i></span></div>
<div align="right" style="font-weight: normal; margin-bottom: 0cm; margin-left: 0.55cm; text-indent: -0.52cm;">
<span style="font-size: small;"><i> <span style="font-size: xx-small;">Limitations
of ZigBee Stack Implemenation on IEEE 802.15.4 </span></i></span>
</div>
<ol><div align="right" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
“<span style="font-size: xx-small;"><i>From OpenZB Forum”</i></span></div>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">The main Problems of
porting the stack over the IEEE 802.15.4 lower layer stack is
<i><b>lack of specification details of hardware and software </b></i>
regarding important aspects of the beacon enabled mode and
the cluster tree model.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"><i><b>Synchronization
Techniques</b></i> in Cluster Tree Developments is an another
issue. For building a cluster network, s<i><b>ynchronization </b></i>
is very much required especailly between the ZR , ZC and ZED
if all the devices are working under one PAN ID. Moreover
, if a node is not properly sychronized there is a
possiblity of collisions in the GTS slots(It provides guaranted
time for each device is intent to connect to the network) :
Stack Overflow is the result of this problem.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;"><i><b>XBee
</b></i></span></span></span><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;">is
a ZigBee Alliance Group devices and its using the ZigBee
Compaint IEEE 802.15.4 stack for the Wireless Communication.
TinyOS is not a ZigBee, but the micaz mote device we are
using here is a ZigBee Alliance Group device. That doesnt means
that its possible to make communication between these two,
for that we need a ZigBee IEEE 802.15.4 Stack in TinyOS
for building the ZigBee Protocol Stack in it. </span></span></span></span>
</div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm; text-decoration: none;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">CC2420 Radio chipset
which is used to switch the time for transmitting and
receiving data throught radio is <i><span style="text-decoration: none;"><b>192
mico seconds,</b></span></i> that is different from the other
stack , especially in allianced group devices like OEM.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">In addition, the processing
power available in the motes microconrtoller revealed to be
quite limited to comply with the most demanding IEEE
802.15.4 timing constraints, especailly from small beacon
orders (BO < 3) and superframe orders (SO <3). This turns
these <i><b> Superframe configuration impossible to deploy</b></i>,
considering that the mote must also have availablity for
processing other task.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">ZigBee Protocol stack
have some processing <i><b> limtation in ATMega128R</b></i>F,only
smarter and faster microconrtoller overcome this difficulty.
Open ZB forum expect to overcome this in near future.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">The deafult <i><b>TinyOS
Scheduler</b></i> does not support tasks prioritization and
non pre-emptive. Typically there are two different kinds of
interrupt event in TinyOS: timers and radio, these events
are captured by event handler that normally post a task to
the FIFO task queue, which significantly impacts the
behaviour of the protcol stack.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">The <i><b> interference
between IEEE 802.15.4 and 802.15.4 radio channels</b></i> ,
confirmed using a <i><b>FFT spectrum analyser</b></i> had
inpredicatable effects on the resutls.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">Physical Layer Related
problems.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">Interference between radio
channels (Overcome the interference between these two standards
by using the only IEEE 802.154. channel(channeks 26 in the
2480 MHz frequency band) that is completely outside the IEEE
802.11 frequency Spectrum).</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">RSSI -based localization in
accuracy (Problem Solved in Open ZB).</span></div>
</li>
</ol>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<br />
</div>
<ol start="12">
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">Synchronized data request/
reply method used in the XBee ZigBee Alliance Group device
due to accomadation of the large collection devices in the
network.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"><i><b>Timer Slot
Registration techniques</b></i><i> </i> for a frame in TinyOS
and XBee devices is have a lot of difference. Like In
TinyOS , DESTINATION device is send frame to the SOURCE
device is by using BROADCASTING timeslot channel. But in XBee
only BROADCASTING frame is allow to pass through the channel. </span>
</div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">TinyOS does'nt have any
<i><b>Super Frame Scheduling Mechanism </b></i> for handling
multiple packet from the SOURCE Devices.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">The tinyos stack is NOT
<i><b>multi-lingual nor is it very flexible</b></i>. You basically
compile with a group of defines set that determines exactly what
kind of packets one is interested in. This is an artifact of TinyOS
motes being extremely resource constrained.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">TinyOS not following any
accurate <i><b>simulation model for IEE 802.15.4 and ZigBee
protocol focusing on the Guranteed Timse Slot (GTS) mechanism
</b></i>and ZigBee hierarichal routing strategy in becon enabled
cluster-tree Wireless Sensor Network.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">To implement an <i><b>energy
efficient beacon enabled routing mechansim </b></i> in TinyOS
is really a challenging task.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">XBee uses <span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;">16
Channels with the </span></span></span><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;">band
gap of the 5MHz [ 2MHz] and </span></span></span><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;"><i><b>
16 Array orthogonal DSSS </b></i></span></span></span><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;">
for maintaing the dynamic timeslot allocation for frames from
the devices.TinyOS or OpenZB doesn't have any kind of
mechanism like that and its using </span></span></span><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;"><i><b>Time
Division based Frame Synchronization Techniques [TDMA].</b></i></span></span></span></span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm; text-decoration: none;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"><span style="color: black;"><span style="text-decoration: none;"><span style="font-family: Liberation Serif, serif;">ZigBee
Compliant IEEE 802.15.4 Stack is differ from depending up
on its Specification and Networking Topologies.</span></span></span>
</span>
</div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">In ZigBee Wrieless Sensor
Technology mainly three networking topolgies were using for
costructing a sensor network. According to the current
IEEE802.15.4/ZigBee specification , synchronization techniques in
each toplogies is different from one another on beacon enabled
mode. OpenZB forum says that, they were successfully resolve
this issue by applying an Time Division Based Synchronization
Techniques.</span></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;">OpenZB forum build ZigBee
Stack top over a <i><b>modified IEEE 802.15.4</b></i> in which
is very much compatable with their stack. So we cant expect
that this device is communicate with the exsiting ZigBee
Alliance Group device like XBee.<br /> </span>
</div>
</li>
<li><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"><i>I am Stilll working
on OpenZB implemenation in Micaz mote device, because vendors
saying that this device is ZigBEE Alliance group device and
it have OEM Modified IEEE complaint stack on its bottom layer
of the stack. So it can support the ZigBEE protocol stack.</i></span></div>
</li>
</ol>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
“<span style="font-size: small;"><i> These are some
issues facing while building an interoperable ZigBEE Stack
over IEEE 802.15.4 -TinyOS -Micaz device. IEEE 802.15.4 ZigBEE
Compliant Stack, Synchronization Scheduling Mechanism, Suitable
Superframe allocation method for Avoiding the frame collision
and Guranteed GTS for devices are some MAJOR ISSUES </i>“</span></div>
<br /><div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<br /></div>
<div align="justify" style="font-style: normal; font-weight: normal; margin-bottom: 0cm;">
<span style="font-size: small;"> </span></div>
</div>
Anonymoushttp://www.blogger.com/profile/14545770648325591855noreply@blogger.com0