jerbi jerbi | 19 Nov 17:16 2014
Picon

code source du protocole LEACH.

Please, I'm looking for code source du protocole LEACH.
 by
<div><div>
<div dir="ltr">Please, <span class="" lang="en"><span class="">I'm looking for </span></span>code source du protocole LEACH. <br>
</div>
<div class="" dir="ltr">&nbsp;by</div>
</div></div>
lukas lee | 19 Nov 11:10 2014
Picon

IEEE ISSNIP 2015 Call for Papers, April 7-9, 2015, Singapore

============================


IEEE ISSNIP 2015 Call for Papers (EXTENDED PAPER DEADLINES), Demos/Videos, and Tutorial Proposals




Venue & Dates:


April 7-9, 2015, Singapore




Conference Website:


http://www.issnip2015.org




============================


Important Dates 


============================


Abstract Submission Deadline: 1 Dec 2014 [*Extended]


Paper Submission Deadline: 8 Dec 2014 [*Extended]


Paper Acceptance Notification: 10 Jan 2015


Camera-Ready Manuscript Deadline: 7 Feb 2015




Demo and Video Submission Deadline: 19 Dec 2014


Demo and Video Notification: 2 Jan. 2015




Tutorial Proposal Deadline: 17 Nov 2014


Tutorial Notification: 1 Dec 2014




============================


Conference Scope


============================


The IEEE 10th International Conference on Intelligent Sensors, Sensor Networks and Information Processing (ISSNIP) will be held in Singapore, from 7th to 9th April 2015. This conference in the series is co-sponsored by IEEE and the Australian Research Council's Research Network on ISSNIP, and the Institute for Infocomm Research as chief patron. IEEE ISSNIP 2015 will consist of technical tracks, a demo and video track, workshops, and tutorials. The technical tracks will focus on both the theory and application of intelligent sensors, sensor networks, and information processing in sensor networks; the demo and video track will showcase emerging sensor technologies and promising applications; the workshops will focus on emerging technology and research topics of a distinct emphasis; the tutorials will cover the state-of-the-art and future technical progress in sensor research. In addition, the industry-oriented International Exhibition & Conference on Internet of Things (IoT Asi

a 2015) and the research-oriented International Conference on Recent Advances in Internet of Things 2015 (RIoT 2015) will be co-located with IEEE ISSNIP 2015 to showcase the latest IoT trends in the industry and research, respectively.




============================


Call for Papers 


============================


The massive data streams and diverse modalities of digital information sources being captured at incredible rates have enriched the confluence of intelligent sensors, ubiquitous computing, networking technologies, wireless sensor networks, data mining, machine learning, and data visualization. The emerging technology also has boosted many promising applications in environmental sensing, urban mobility, transportation, emergency response, social networks, healthcare, security, IT infrastructure, and smart-city applications. However, the technical challenges involved in these emerging applications lie in the intersection of multiple disciplines. Thus, IEEE ISSNIP 2015 will include three technical tracks, intelligent sensors, sensor networks, and information processing, to focus on different topics in sensor research.




The track on Intelligent Sensors aims at attracting major advances and breakthroughs in sensor technologies, design of circuits and systems, energy sources, packaging technologies, and microsystem integration. The intelligent sensor ideally offers sensing and actuating capabilities combined with on-node computation and communication functions, while implemented in extremely miniaturized form factor and operating in an energy-autonomous manner. The need for intelligent sensors opens up many technical challenges and opportunities. 




The track on Sensor Networks is designed to attract diverse participation from researchers and practitioners working at the leading edge of wireless and wired sensor network development. As sensor networks can now provide a rich and varied source of data streams, the need for reliable sensor information, as well as for sensing infrastructure and analytical sense-making tools that are able to make informed decisions, creates many new challenges.




The track on Information Processing focuses on techniques for the analysis and interpretation of data that is generated by sensor networks, as well as the use of such techniques in practical application domains. Sensor networks can provide a rich and varied source of data streams, ranging from simple periodic measurements to complex video and multimedia streams. These data streams need to be processed by the resource constraints of sensing platforms, which may involve real-time, distributed and in-network processing. These processing tasks are creating new challenges in the fields of signal processing, machine learning, computational intelligence and data analytics.




Original contributions on all topics related to intelligent sensors, sensor networks, and information processing in sensor networks are welcomed. Areas of interest include, but are not limited to, the following:


- Internet of Things (IoT)


- Cloud Computing and Data Management 


- Big Data Analysis and Visualization 


- Participatory Sensing and Crowd Sourcing 


- Network Scheduling and Optimization 


- Sustainable and Energy-Aware Networking 


- Protocols and Standards in Internet of Things 


- Fault Tolerance and Reliability 


- Security, Privacy, and Trust 


- Middleware for Sensor Systems 


- Sensor Network Management and Control 


- Sensor Fusion, Tracking, and Localization 


- Data Mining, Pattern Recognition, and Machine Intelligence 


- Smart Sensors: Optical, Nano 


- Sensor Networks and IoT Applications 


- Smart Grids, Smart Cities, and Smart Environments




============================


Paper Submission Instructions


============================


Submitted papers must be written in English, and be in standard IEEE conference paper format (double-column, 10-point font), not exceeding six pages total (including figures and appendices). However, one additional page is allowed at a charge -- an overlength page charge is payable by the authors for each accepted paper that requires a 7th page in the final camera-ready manuscript. Standard IEEE conference paper templates in LaTeX and Microsoft Word formats can be found athttp://www.ieee.org/conferences_events/conferences/publishing/templates.html. Either the A4 or the US Letter paper size may be used. Authors should adhere closely to the formatting style of the templates. Papers with a non-compliant format will be summarily rejected without handling by the peer-review process. 




Papers must be submitted through EDAS (http://edas.info/N18587) for peer-review. Accepted papers will be scheduled presentations at the conference. Due to the limited number of rooms at the conference venue, a portion of the accepted papers will be presented as posters. The IEEE ISSNIP 2015 Technical Program Committee will decide which papers will be presented in oral (lecture type) sessions and which papers as posters, and the decisions will be announced to the authors. Choice between oral and poster presentations will be totally independent of the review scores and of the paper quality. Instructions on the preparation and submission of papers can be found on the "Authors" page of the conference website (http://www.issnip2015.org).




============================


Call for Demos and Videos 


============================


IEEE ISSNIP 2015 will feature a Demo and Video Track as a forum for researchers and developers from academia and industry to showcase deployed and working systems, emerging sensor technologies and promising applications in the areas of intelligent sensors, sensor networks, and information processing in sensor networks. To this end, IEEE ISSNIP 2015 solicits demonstrations presenting recent original results or ongoing research. The actual demonstration can be in the form of a physical demonstration, a video presentation, or a combination of both.Video presentations are suitable for showcasing working systems that are deployed in remote locations.




============================


Demo and Video Submission Instructions 


============================


Demonstration abstracts of no more than 2 pages using the IEEE two-column format should be submitted through EDAS: http://edas.info/N18587. The manuscript templates and usage instructions can be found athttp://www.ieee.org/publications_standards/publications/authors/authors_journals.html#sect2. The extended abstract should provide a short abstract, a figure of the system to be demonstrated, comprehensive description of the system and conclusion. For video presentations, a URL or web link to the video should also be included in the extended abstract. Authors may follow the guidelines athttp://www.ieee.org/publications_standards/publications/authors/mm_video.pdf to prepare video presentations. Accepted abstracts will be published in IEEE Xplore, subject to the terms of the IEEE Conference Publication Program.




============================


Call for Tutorial Proposals 


============================


We are soliciting proposals for tutorials for IEEE ISSNIP 2015. Tutorials will be scheduled for the morning of the last day of the conference (9 Apr 2014). Each tutorial will have a 3-hour time slot with an additional tea break for 30 minutes. 




Tutorial proposal Submission Instructions


If you are interested to conduct a tutorial, please submit a proposal with the following information:


- The title of the tutorial.


- The name, address, and a short biography (up to 200 words) of the presenter(s) of the tutorial. Please provide a summary of relevant past experience, particularly in teaching or lecturing, and in research on the topic of the tutorial.


- A brief description (up to 1 page) of the topic addressed in the tutorial, and the reasons why the topic is of interest at this time.


- A brief outline of the tutorial.


Please submit your tutorial proposals via the online form on IEEE ISSNIP 2015 website.




============================


Conference Committee


============================


General Chair:


- Hwee Pink TAN, Institute for Infocomm Research, Singapore


- Marimuthu PALANISWAMI, University of Melbourne, Australia




Technical Programme Chairs:


- Yu-Chee TSENG, National Chiao Tung University, Taiwan


- Hongyi WU, University of Louisiana at Lafayette, USA


- Lawrence WONG, National University of Singapore, Singapore




Technical Track Chairs--Track 1: Intelligent Sensors:


- J. Andrew YEH, National Tsing Hua University, Taiwan


- Jason PNG, Institute for High Power Computing, Singapore




Technical Track Chairs--Track 2: Sensor Networks:


- Chih-Wei YI, National Chiao Tung University, Taiwan


- Edith Cheuk-Han NGAI, Uppsala University, Sweden


- Salil KANHERE, University of New South Wales, Sydney, Australia


- Mo LI, Nanyang Technological University, Singapore




Technical Track Chairs-Track3: Information Processing:


- Dusit NIYATO, Nanyang Technological University, Singapore


- Rajaraman KANAGASABAI, Institute for Infocomm Research, Singapore


- Rachel CARDELL-OLIVER, The University of Western Australia, Australia


- Christopher Andrew LECKIE, The University of Melbourne, Australia




Publications Chairs:


- Jayavardhana LAKSHMINARASIMHA, University of Melbourne, Australia




Sincerely,




IEEE ISSNIP 2015 General Chairs:


Hwee Pink TAN, Institute for Infocomm Research, Singapore


Marimuthu PALANISWAMI, University of Melbourne, Australia

<div><div dir="ltr">

<p class="p1"><span>============================</span></p>
<p class="p3"><br></p>
<p class="p1">IEEE ISSNIP 2015 Call for Papers (EXTENDED PAPER DEADLINES), Demos/Videos, and Tutorial Proposals</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Venue &amp; Dates:</p>
<p class="p3"><br></p>
<p class="p1">April 7-9, 2015, Singapore</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Conference Website:</p>
<p class="p3"><br></p>
<p class="p2"><span class="s1"><a href="http://www.issnip2015.org/">http://www.issnip2015.org</a></span></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Important Dates&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Abstract Submission Deadline: 1 Dec 2014 [*Extended]</p>
<p class="p3"><br></p>
<p class="p1">Paper Submission Deadline: 8 Dec 2014 [*Extended]</p>
<p class="p3"><br></p>
<p class="p1">Paper Acceptance Notification: 10 Jan 2015</p>
<p class="p3"><br></p>
<p class="p1">Camera-Ready Manuscript Deadline: 7 Feb 2015</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Demo and Video Submission Deadline: 19 Dec 2014</p>
<p class="p3"><br></p>
<p class="p1">Demo and Video Notification: 2 Jan. 2015</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Tutorial Proposal Deadline: 17 Nov 2014</p>
<p class="p3"><br></p>
<p class="p1">Tutorial Notification: 1 Dec 2014</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Conference Scope</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">The IEEE 10th International Conference on Intelligent Sensors, Sensor Networks and Information Processing (ISSNIP) will be held in Singapore, from 7th to 9th April 2015. This conference in the series is co-sponsored by IEEE and the Australian Research Council's Research Network on ISSNIP, and the Institute for Infocomm Research as chief patron. IEEE ISSNIP 2015 will consist of technical tracks, a demo and video track, workshops, and tutorials. The technical tracks will focus on both the theory and application of intelligent sensors, sensor networks, and information processing in sensor networks; the demo and video track will showcase emerging sensor technologies and promising applications; the workshops will focus on emerging technology and research topics of a distinct emphasis; the tutorials will cover the state-of-the-art and future technical progress in sensor research. In addition, the industry-oriented International Exhibition &amp; Conference on Internet of Things (IoT Asi</p>
<p class="p1">a 2015) and the research-oriented International Conference on Recent Advances in Internet of Things 2015 (RIoT 2015) will be co-located with IEEE ISSNIP 2015 to showcase the latest IoT trends in the industry and research, respectively.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Call for Papers&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">The massive data streams and diverse modalities of digital information sources being captured at incredible rates have enriched the confluence of intelligent sensors, ubiquitous computing, networking technologies, wireless sensor networks, data mining, machine learning, and data visualization. The emerging technology also has boosted many promising applications in environmental sensing, urban mobility, transportation, emergency response, social networks, healthcare, security, IT infrastructure, and smart-city applications. However, the technical challenges involved in these emerging applications lie in the intersection of multiple disciplines. Thus, IEEE ISSNIP 2015 will include three technical tracks, intelligent sensors, sensor networks, and information processing, to focus on different topics in sensor research.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">The track on Intelligent Sensors aims at attracting major advances and breakthroughs in sensor technologies, design of circuits and systems, energy sources, packaging technologies, and microsystem integration. The intelligent sensor ideally offers sensing and actuating capabilities combined with on-node computation and communication functions, while implemented in extremely miniaturized form factor and operating in an energy-autonomous manner. The need for intelligent sensors opens up many technical challenges and opportunities.&nbsp;</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">The track on Sensor Networks is designed to attract diverse participation from researchers and practitioners working at the leading edge of wireless and wired sensor network development. As sensor networks can now provide a rich and varied source of data streams, the need for reliable sensor information, as well as for sensing infrastructure and analytical sense-making tools that are able to make informed decisions, creates many new challenges.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">The track on Information Processing focuses on techniques for the analysis and interpretation of data that is generated by sensor networks, as well as the use of such techniques in practical application domains. Sensor networks can provide a rich and varied source of data streams, ranging from simple periodic measurements to complex video and multimedia streams. These data streams need to be processed by the resource constraints of sensing platforms, which may involve real-time, distributed and in-network processing. These processing tasks are creating new challenges in the fields of signal processing, machine learning, computational intelligence and data analytics.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Original contributions on all topics related to intelligent sensors, sensor networks, and information processing in sensor networks are welcomed. Areas of interest include, but are not limited to, the following:</p>
<p class="p3"><br></p>
<p class="p1">- Internet of Things (IoT)</p>
<p class="p3"><br></p>
<p class="p1">- Cloud Computing and Data Management&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Big Data Analysis and Visualization&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Participatory Sensing and Crowd Sourcing&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Network Scheduling and Optimization&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Sustainable and Energy-Aware Networking&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Protocols and Standards in Internet of Things&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Fault Tolerance and Reliability&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Security, Privacy, and Trust&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Middleware for Sensor Systems&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Sensor Network Management and Control&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Sensor Fusion, Tracking, and Localization&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Data Mining, Pattern Recognition, and Machine Intelligence&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Smart Sensors: Optical, Nano&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Sensor Networks and IoT Applications&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">- Smart Grids, Smart Cities, and Smart Environments</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Paper Submission Instructions</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Submitted papers must be written in English, and be in standard IEEE conference paper format (double-column, 10-point font), not exceeding six pages total (including figures and appendices). However, one additional page is allowed at a charge -- an overlength page charge is payable by the authors for each accepted paper that requires a 7th page in the final camera-ready manuscript. Standard IEEE conference paper templates in LaTeX and Microsoft Word formats can be found at<a href="http://www.ieee.org/conferences_events/conferences/publishing/templates.html"><span class="s5">http://www.ieee.org/conferences_events/conferences/publishing/templates.html</span></a>. Either the A4 or the US Letter paper size may be used. Authors should adhere closely to the formatting style of the templates. Papers with a non-compliant format will be summarily rejected without handling by the peer-review process.&nbsp;</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Papers must be submitted through EDAS (<a href="http://edas.info/N18587"><span class="s5">http://edas.info/N18587</span></a>) for peer-review. Accepted papers will be scheduled presentations at the conference. Due to the limited number of rooms at the conference venue, a portion of the accepted papers will be presented as posters. The IEEE ISSNIP 2015 Technical Program Committee will decide which papers will be presented in oral (lecture type) sessions and which papers as posters, and the decisions will be announced to the authors. Choice between oral and poster presentations will be totally independent of the review scores and of the paper quality. Instructions on the preparation and submission of papers can be found on the "Authors" page of the conference website (<a href="http://www.issnip2015.org/"><span class="s5">http://www.issnip2015.org</span></a>).</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Call for Demos and Videos&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">IEEE ISSNIP 2015 will feature a Demo and Video Track as a forum for researchers and developers from academia and industry to showcase deployed and working systems, emerging sensor technologies and promising applications in the areas of intelligent sensors, sensor networks, and information processing in sensor networks. To this end, IEEE ISSNIP 2015 solicits demonstrations presenting recent original results or ongoing research. The actual demonstration can be in the form of a physical demonstration, a video presentation, or a combination of both.Video presentations are suitable for showcasing working systems that are deployed in remote locations.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Demo and Video Submission Instructions&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Demonstration abstracts of no more than 2 pages using the IEEE two-column format should be submitted through EDAS:&nbsp;<a href="http://edas.info/N18587"><span class="s5">http://edas.info/N18587</span></a>. The manuscript templates and usage instructions can be found at<a href="http://www.ieee.org/publications_standards/publications/authors/authors_journals.html#sect2"><span class="s5">http://www.ieee.org/publications_standards/publications/authors/authors_journals.html#sect2</span></a>. The extended abstract should provide a short abstract, a figure of the system to be demonstrated, comprehensive description of the system and conclusion. For video presentations, a URL or web link to the video should also be included in the extended abstract. Authors may follow the guidelines at<a href="http://www.ieee.org/publications_standards/publications/authors/mm_video.pdf"><span class="s5">http://www.ieee.org/publications_standards/publications/authors/mm_video.pdf</span></a>&nbsp;to prepare video presentations. Accepted abstracts will be published in IEEE Xplore, subject to the terms of the IEEE Conference Publication Program.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Call for Tutorial Proposals&nbsp;</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">We are soliciting proposals for tutorials for IEEE ISSNIP 2015. Tutorials will be scheduled for the morning of the last day of the conference (9 Apr 2014). Each tutorial will have a 3-hour time slot with an additional tea break for 30 minutes.&nbsp;</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Tutorial proposal Submission Instructions</p>
<p class="p3"><br></p>
<p class="p1">If you are interested to conduct a tutorial, please submit a proposal with the following information:</p>
<p class="p3"><br></p>
<p class="p1">- The title of the tutorial.</p>
<p class="p3"><br></p>
<p class="p1">- The name, address, and a short biography (up to 200 words) of the presenter(s) of the tutorial. Please provide a summary of relevant past experience, particularly in teaching or lecturing, and in research on the topic of the tutorial.</p>
<p class="p3"><br></p>
<p class="p1">- A brief description (up to 1 page) of the topic addressed in the tutorial, and the reasons why the topic is of interest at this time.</p>
<p class="p3"><br></p>
<p class="p1">- A brief outline of the tutorial.</p>
<p class="p3"><br></p>
<p class="p1">Please submit your tutorial proposals via the online form on IEEE ISSNIP 2015 website.</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">Conference Committee</p>
<p class="p3"><br></p>
<p class="p1">============================</p>
<p class="p3"><br></p>
<p class="p1">General Chair:</p>
<p class="p3"><br></p>
<p class="p1">- Hwee Pink TAN, Institute for Infocomm Research, Singapore</p>
<p class="p3"><br></p>
<p class="p1">- Marimuthu PALANISWAMI, University of Melbourne, Australia</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Technical Programme Chairs:</p>
<p class="p3"><br></p>
<p class="p1">- Yu-Chee TSENG, National Chiao Tung University, Taiwan</p>
<p class="p3"><br></p>
<p class="p1">- Hongyi WU, University of Louisiana at Lafayette, USA</p>
<p class="p3"><br></p>
<p class="p1">- Lawrence WONG, National University of Singapore, Singapore</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Technical Track Chairs--Track 1: Intelligent Sensors:</p>
<p class="p3"><br></p>
<p class="p1">- J. Andrew YEH, National Tsing Hua University, Taiwan</p>
<p class="p3"><br></p>
<p class="p1">- Jason PNG, Institute for High Power Computing, Singapore</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Technical Track Chairs--Track 2: Sensor Networks:</p>
<p class="p3"><br></p>
<p class="p1">- Chih-Wei YI, National Chiao Tung University, Taiwan</p>
<p class="p3"><br></p>
<p class="p1">- Edith Cheuk-Han NGAI, Uppsala University, Sweden</p>
<p class="p3"><br></p>
<p class="p1">- Salil KANHERE, University of New South Wales, Sydney, Australia</p>
<p class="p3"><br></p>
<p class="p1">- Mo LI, Nanyang Technological University, Singapore</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Technical Track Chairs-Track3: Information Processing:</p>
<p class="p3"><br></p>
<p class="p1">- Dusit NIYATO, Nanyang Technological University, Singapore</p>
<p class="p3"><br></p>
<p class="p1">- Rajaraman KANAGASABAI, Institute for Infocomm Research, Singapore</p>
<p class="p3"><br></p>
<p class="p1">- Rachel CARDELL-OLIVER, The University of Western Australia, Australia</p>
<p class="p3"><br></p>
<p class="p1">- Christopher Andrew LECKIE, The University of Melbourne, Australia</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Publications Chairs:</p>
<p class="p3"><br></p>
<p class="p1">- Jayavardhana LAKSHMINARASIMHA, University of Melbourne, Australia</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">Sincerely,</p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p3"><br></p>
<p class="p1">IEEE ISSNIP 2015 General Chairs:</p>
<p class="p3"><br></p>
<p class="p1">Hwee Pink TAN, Institute for Infocomm Research, Singapore</p>
<p class="p3"><br></p>
<p class="p1">Marimuthu PALANISWAMI, University of Melbourne, Australia</p> 		 	   		  </div></div>
Muhammad Musaddiq | 19 Nov 10:51 2014
Picon

DCT image Compression

Has anybody implemented DCT in TinyOS? 
 
Regardz
Muhammad Musaddiq

<div><div>
<div dir="ltr"><span>Has anybody implemented DCT in TinyOS?&nbsp;</span></div>
<div></div>
<div>&nbsp;</div>
<div><div>Regardz
<br>Muhammad Musaddiq
<br><br>
</div></div>
</div></div>
Jisha Mary Jose | 19 Nov 07:36 2014
Picon

how to simulate attacks in TOSSIM

Hi,

I am doing a project work on secure data dissemination in wireless sensor networks. I have t simulate attacks like DoS and pollution attacks in TOSSIM. How to do this?

Please Please help me.. its very urgent.. i cant find any help online...

Regards,

Jisha Mary Jose
......jMj......
<div><div dir="ltr">
<div class="gmail_default">Hi,<br><br>
</div>
<div class="gmail_default">I am doing a project work on secure data dissemination in wireless sensor networks. I have t simulate attacks like DoS and pollution attacks in TOSSIM. How to do this?<br><br>
</div>
<div class="gmail_default">Please Please help me.. its very urgent.. i cant find any help online...<br><br clear="all">
</div>
<div><div class="gmail_signature"><div dir="ltr">Regards,<br><br>Jisha Mary Jose<br>......jMj......</div></div></div>
</div></div>
Michael Rink | 14 Nov 09:37 2014
Picon

at45db LogStorageP.nc

Hi developers,

while using the LogStorage component of the at45db chip,
in circular mode with a volume consisting of n pages,
I observed the following:

I. After erasing the chip, writing n-1 pages,
and triggering a reset of the mote, no further writing
or reading is possible.
The reason seems to be procedure locateLastRecord()
in tinyos-main/tos/chips/at45db/LogStorageP.nc.

496 void locateLastRecord() {
497   if (firstPage == lastPage)
498     {
499       /* We walked all the way back to the last page, and it's not
500          valid. The log-volume invariant is not holding. Fail out. */
501          endRequest(FAIL);
502          return;
503     }
      ...

For a dirty workaround I replaced
      if (firstPage == lastPage)
with
      if ( (firstPage == lastPage) && (metadata.pos/PAGE_SIZE != lastPage) )
but this probably violates some assumptions or invariants.

II. After erasing the chip and writing x pages,
the following number y of pages can be read:
  If x <  n, then  y = x.
  If x >= n, then  y = n - 2.
That means that if I write at least n pages, then I lose
the n-th and (n-1)-th "newest" ones.

I am aware that these observation
are possibly due to errors
in my test application but
maybe you can give me some hint --
I am grateful for any help.

Best regards,
Michael Rink
He Dajiang (I2R | 6 Nov 13:57 2014
Picon

tinyos not running in micaz board

Hi all,

We've made sensor board based on micaz architecture. The board does not work even for the simple Blink
application; we managed to flash firmware into the board by using tinyos make tools (make micaz
reinstall.x ...).
However, if we bypass tinyos and flash simple blinking code into the board (SET and CLEAR the MCU pins
linking to the led), it can function and hardare leds blink. I take a look at app.c of tinyos blink app,
before Blink__booted function is called, there are some other hardware, platform, and software init
functions being called. Can I ask questions to the creators of tinyos, what are the checkings tinyos does
when booting up? I guess some of the checkings failed on my board so that tinyos Blink app does not run in my board.

Thx & Regards
dajiang

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are
not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any
purpose, or disclose its contents to any other person. Thank you."

Fahimeh Ashrafy | 3 Nov 09:39 2014
Picon

compile ToSSIM

Hello guys

I've just downloaded the XubunTOS image provided by the TinyOs team ( http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_%28with_TinyOS_from_tp-freeforall/prod_repository%29_in_VirtualBox) and while trying to compile the simple BLINK app with TOSSIM support I get this:

mkdir -p simbuild/micaz
placing object files in simbuild/micaz
writing XML schema to app.xml
compiling BlinkAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=100000 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"XubunTOS\" -DIDENT_USERHASH=0x184e7486L -DIDENT_TIMESTAMP=0x54573467L -DIDENT_UIDHASH=0xed24784cL -Wno-nesc-data-race BlinkAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml
In file included from /home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/ActiveMessageC.nc:57,
from /home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/MainC.nc:72,
from BlinkAppC.nc:56:
In component `TossimPacketModelC':
/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/TossimPacketModelC.nc:140: conflicting types for `PacketAcknowledgements.wasAcked'
/home/user/top/t2_cur/tinyos-2.x/tos/interfaces/PacketAcknowledgements.nc:85: previous declaration of `PacketAcknowledgements.wasAcked'
make: *** [sim-exe] Error 1

Could anyone help me?
Thanks a lot
<div><div dir="ltr">Hello guys<br><br>I've just downloaded the XubunTOS image provided by the TinyOs team (
<a href="http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_%28with_TinyOS_from_tp-freeforall/prod_repository%29_in_VirtualBox">http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_%28with_TinyOS_from_tp-freeforall/prod_repository%29_in_VirtualBox</a>)
and while trying to compile the simple BLINK app with TOSSIM support I get
this:<br><br>mkdir -p simbuild/micaz<br>  placing object files in simbuild/micaz<br>  writing XML schema to app.xml<br>  compiling BlinkAppC to object file sim.o<br>ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=100000 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"XubunTOS\" -DIDENT_USERHASH=0x184e7486L -DIDENT_TIMESTAMP=0x54573467L -DIDENT_UIDHASH=0xed24784cL -Wno-nesc-data-race BlinkAppC.nc   -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml<br>In file included from /home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/ActiveMessageC.nc:57,<br>                 from /home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/MainC.nc:72,<br>                 from BlinkAppC.nc:56:<br>In component `TossimPacketModelC':<br>/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/TossimPacketModelC.nc:140: conflicting types for `PacketAcknowledgements.wasAcked'<br>/home/user/top/t2_cur/tinyos-2.x/tos/interfaces/PacketAcknowledgements.nc:85: previous declaration of `PacketAcknowledgements.wasAcked'<br>make: *** [sim-exe] Error 1<br><br>Could anyone help me?
<br>Thanks a lot<br>
</div></div>
Lynda Algerienne | 28 Oct 18:17 2014
Picon

Mote to mote communication


Hello,

I am trying to simulate mote to mote communication between two XM1000 sensors.


I did not get any error but it appears that the second mote did not receive any message. 
I tried to measure Rssi and print any message for checking the reception but I did not get anything.

Could you please help me

Best regards,
<div><div dir="ltr">
<br><div>Hello,</div>
<div><br></div>
<div>I am trying to simulate mote to mote communication between two XM1000 sensors.</div>
<div><br></div>
<div>I followed&nbsp;<a href="http://www.tinyos.net/dist-2.0.0/tinyos-2.x/doc/html/tutorial/lesson3.html">http://www.tinyos.net/dist-2.0.0/tinyos-2.x/doc/html/tutorial/lesson3.html</a>
</div>
<div><br></div>
<div>I did not get any error but it appears that the second mote did not receive any message.&nbsp;</div>
<div>I tried to measure Rssi and print any message for checking the reception but I did not get anything.</div>
<div><br></div>
<div>Could you please help me</div>
<div><br></div>
<div>Best regards,</div>
</div></div>
Sebastian Scheibe | 28 Oct 15:58 2014
Picon
Picon

packet loss at PppRouter base station

Hello everyone, I'm analysing the PppRouter application due to determined packet loss of about 0.8-1% in a one-hop network consisting of one base station (PppRouter) and one network node (UDPEcho or CoapBlip) using Blip2.0. I work with UCMote Mini hardware, but the problem also appears with a Tmote node as base station. In my test network I use the following shell script to ping the network node periodically (10 pings, 10 seconds break, 10 pings, ...), TestPing.sh: #!/bin/bash COUNT=10 for ((i=1;;)) do ping6 -c $COUNT fec0::7 #send 10 ping requests to destination sleep 10 done I used Wireshark to record the IP packets on the serial PPP Interface as well as an external packet Sniffer for sniffing the wireless interface. I found out that all lost packets (sent from my PC) have been dropped on the PppRouter base station before being forwarded to the network node. So there is no evidence that packets might have been lost due to interferences on the wireless channel or for some other reason on the network node. For debugging purposes I installed the tos-pppd.patch to be able to print out debug messages to my PPP daemon console. I'd like to point out that all of these problems also occur without this tos-pppd.patch. After spending a lot of time with printing out debug messages I could identify three reasons why packets have been dropped: 1) Approx. 0.40 percent of received packets are dropped because they are not "approved". /apps/PppRouter/RplBorderRouterP.nc (line 32): if statement "if (pkt->ip6_inputif == ROUTE_IFACE_PPP)" is true, but it shouldn't be! This leads in /tos/lib/net/blip/IPForwardingEngineP.nc (lines 312-313) to the packet drop. I could observe that this often happens bursty, so sometimes 7 directly in series sent ping request messages are dropped. But the problem also appears with one packet out of 10. 2) for approx. 0.09 percent of received packets no free buffer is available. /tos/lib/ppp/HdlcFramingP.nc (lines 486-488): The HdlcFramingP interface tries to put received frames in a buffer, which isn't available. Did anyone notice this kind of problem before? Why does it happen? 3) Approx. 0.37 percent of received packets contain a routing header which isn't allowed. /tos/lib/net/blip/IPPacketC.nc (from line 30) the IPPacket.findHeader command returns an offset to a header which we can't handle yet in /tos/lib/net/blip/IPForwardingEngineP.nc (from line 284) so line 289 produces the packet drop. I commented out the return instruction in line 289, so every packet apparently containing a routing header anyway was forwarded and answered correctly by the network node. So for this point, I could diminish the amount of packet loss. It works fine, but I'm not sure if this is a clean solution.


Furthermore I tried to find out if any of these problems also occur with CoAP.
I used a script, which sends CoAP messages periodically to a network node and measures the response time. /opt/tinyos-2.x/support/sdk/c/coap/examples/TestCoap.sh:

#!/bin/bash
num=1

while true
do
   echo "Run $num"
   date +%d.%m.%Y-%k:%M:%S
   temp=$(($(date +%s%N)/1000000)) #save start time
   
   ./coap-client coap://[fec0::7]/l    

   temp2=$((($(date +%s%N)/1000000)-$temp)) #calculate response time
   echo "Resp-Time: $temp2"
   sleep 5
     num=$(( $num + 1 ))
done

In this setting approximately 0.6 percent of sent CoAP requests are lost due to failed packet approval (see 1) above). Neither routing header problems nor buffer problems occurred in CoAP.
Did anyone notice any of these problems at the PppRouter base station before? Does anyone know how to cope with these problems? Thanks for your help!
Best regards, Sebastian
<div>Hello everyone,

I'm analysing the PppRouter application due to determined packet loss of about 0.8-1% in a one-hop network consisting of one base station (PppRouter) and one network node (UDPEcho or CoapBlip) using Blip2.0.
I work with UCMote Mini hardware, but the problem also appears with a Tmote node as base station. In my test network I use the following shell script to ping the network node periodically (10 pings, 10 seconds break, 10 pings, ...), TestPing.sh:

#!/bin/bash
COUNT=10
for ((i=1;;))
do
    ping6 -c $COUNT fec0::7 #send 10 ping requests to destination
    sleep 10
done

I used Wireshark to record the IP packets on the serial PPP Interface as well as an external packet Sniffer for sniffing the wireless interface. I found out that all lost packets (sent from my PC) have been dropped on the PppRouter base station before being forwarded to the network node. So there is no evidence that packets might have been lost due to interferences on the wireless channel or for some other reason on the network node. For debugging purposes I installed the tos-pppd.patch to be able to print out debug messages to my PPP daemon console. I'd like to point out that all  of these problems also occur without this tos-pppd.patch.
After spending a lot of time with printing out debug messages I could identify three reasons why packets have been dropped:

1) Approx. 0.40 percent of received packets are dropped because they are not "approved".  

/apps/PppRouter/RplBorderRouterP.nc (line 32): if statement "if (pkt-&gt;ip6_inputif == ROUTE_IFACE_PPP)" is true, but it shouldn't be! This leads in /tos/lib/net/blip/IPForwardingEngineP.nc (lines 312-313) to the packet drop. 
I could observe that this often happens bursty, so sometimes 7 directly in series sent ping request messages are dropped. But the problem also appears with one packet out of 10. 

2) for approx. 0.09 percent of received packets no free buffer is available.

/tos/lib/ppp/HdlcFramingP.nc (lines 486-488): The HdlcFramingP interface tries to put received frames in a buffer, which isn't available. Did anyone notice this kind of problem before? Why does it happen?

3) Approx. 0.37 percent of received packets contain a routing header which isn't allowed.

/tos/lib/net/blip/IPPacketC.nc (from line 30) the IPPacket.findHeader command returns an offset to a header which we can't handle yet in /tos/lib/net/blip/IPForwardingEngineP.nc (from line 284) so line 289 produces the packet drop. I commented out the return instruction in line 289, so every packet apparently containing a routing header anyway was forwarded and answered correctly by the network node.
So for this point, I could diminish the amount of packet loss. It works fine, but I'm not sure if this is a clean solution. <br><br><br>Furthermore I tried to find out if any of these problems also occur with CoAP.<br>I used a script, which sends CoAP messages periodically to a network node and measures the response time. /opt/tinyos-2.x/support/sdk/c/coap/examples/TestCoap.sh:<br><br>#!/bin/bash<br>num=1<br><br>while true<br>do <br>&nbsp;&nbsp; echo "Run $num"<br>&nbsp;&nbsp; date +%d.%m.%Y-%k:%M:%S<br>&nbsp;&nbsp; temp=$(($(date +%s%N)/1000000)) #save start time<br>&nbsp; &nbsp;<br>&nbsp;&nbsp; ./coap-client coap://[fec0::7]/l&nbsp;&nbsp; &nbsp;<br><br>&nbsp;&nbsp; temp2=$((($(date +%s%N)/1000000)-$temp)) #calculate response time<br>&nbsp;&nbsp; echo "Resp-Time: $temp2"<br>&nbsp;&nbsp; sleep 5<br>&nbsp;&nbsp;&nbsp; &nbsp;num=$(( $num + 1 ))<br>done<br><br>In this setting approximately 0.6 percent of sent CoAP requests are lost due to failed packet approval (see 1) above). Neither routing header problems nor buffer problems occurred in CoAP.<br>Did anyone notice any of these problems at the PppRouter base station before? Does anyone know how to cope with these problems?

Thanks for your help!
<br>Best regards,
Sebastian
<br>
</div>
edgar dominguez | 28 Oct 01:38 2014
Picon

Ubuntu tinyos serial <at> /dev/ttyUSB1:57600: resynchronising

hi i'm asking for help, i been trying to run the MicReadStreamTest ( from zsze-wsn ) on eclipse using a micaz mote and a mib520, but when i run it all i receive is this :
serial <at> /dev/ttyUSB1:57600: packet too long
serial <at> /dev/ttyUSB1:57600: resynchronising
serial <at> /dev/ttyUSB1:57600: bad packet

im a novice user... if you could use easy words to explain i will appreciate it
<div><div dir="ltr">
<div>hi i'm asking for help, i been trying to run the MicReadStreamTest ( from zsze-wsn ) on eclipse using a micaz mote and a mib520, but when i run it all i receive is this :</div>
<div>serial <at> /dev/ttyUSB1:57600: packet too long</div>
<div>serial <at> /dev/ttyUSB1:57600: resynchronising</div>
<div>serial <at> /dev/ttyUSB1:57600: bad packet</div>
<div><br></div>
<div>im a novice user... if you could use easy words to explain i will appreciate it</div> 		 	   		  </div></div>
laptopcss | 27 Oct 13:51 2014
Picon
Picon

Platform suggestion (more memory than TelosB and TinyOS support)

Hello together,
 
currently I am working with IRIS motes and TelosB under TinyOS 2.x. Due to many implementations around efficient data transmission and security support we run out of memory for further developments.
 
Thus, we are looking for new platforms with more memory and TinyOS 2.x support. It would be nice to have different sensors (e.g., light, humidity, temperature) already included on the platform
Can anyone point me to a special platform and price lists?
 
Thanks, Conny
<div><div><div>
<div>Hello together,</div>

<div>&nbsp;</div>

<div>currently I am working with IRIS motes and TelosB under TinyOS 2.x. Due to many implementations around efficient data transmission and security support we run out of memory for further developments.</div>

<div>&nbsp;</div>

<div>Thus, we are looking for new platforms with more memory and TinyOS 2.x support. It would be nice to have different sensors (e.g., light, humidity, temperature) already included on the platform</div>

<div>Can anyone point me to a special platform and price lists?</div>
&nbsp;

<div>Thanks, Conny</div>
</div></div></div>

Gmane