--- /dev/null
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
+<title>TinyOS 802.15.4 Frames</title>
+<meta name="author" content="Jonathan Hui, Philip Levis, and David Moss" />
+<style type="text/css">
+
+/*
+:Author: David Goodger
+:Contact: goodger@users.sourceforge.net
+:date: $Date$
+:version: $Revision$
+:copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+*/
+body {
+ font-family: Times;
+ font-size: 16px;
+}
+
+.first {
+ margin-top: 0 ! important }
+
+.last {
+ margin-bottom: 0 ! important }
+
+.hidden {
+ display: none }
+
+a.toc-backref {
+ text-decoration: none ;
+ color: black }
+
+blockquote.epigraph {
+ margin: 2em 5em ; }
+
+dd {
+ margin-bottom: 0.5em }
+
+/* Uncomment (& remove this text!) to get bold-faced definition list terms
+dt {
+ font-weight: bold }
+*/
+
+div.abstract {
+ margin: 2em 5em }
+
+div.abstract p.topic-title {
+ font-weight: bold ;
+ text-align: center }
+
+div.attention, div.caution, div.danger, div.error, div.hint,
+div.important, div.note, div.tip, div.warning, div.admonition {
+ margin: 2em ;
+ border: medium outset ;
+ padding: 1em }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+ color: red ;
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.hint p.admonition-title, div.important p.admonition-title,
+div.note p.admonition-title, div.tip p.admonition-title,
+div.admonition p.admonition-title {
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.dedication {
+ margin: 2em 5em ;
+ text-align: center ;
+ font-style: italic }
+
+div.dedication p.topic-title {
+ font-weight: bold ;
+ font-style: normal }
+
+div.figure {
+ margin-left: 2em }
+
+div.footer, div.header {
+ font-size: smaller }
+
+div.line-block {
+ display: block ;
+ margin-top: 1em ;
+ margin-bottom: 1em }
+
+div.line-block div.line-block {
+ margin-top: 0 ;
+ margin-bottom: 0 ;
+ margin-left: 1.5em }
+
+div.sidebar {
+ margin-left: 1em ;
+ border: medium outset ;
+ padding: 0em 1em ;
+ background-color: #ffffee ;
+ width: 40% ;
+ float: right ;
+ clear: right }
+
+div.sidebar p.rubric {
+ font-family: sans-serif ;
+ font-size: medium }
+
+div.system-messages {
+ margin: 5em }
+
+div.system-messages h1 {
+ color: red }
+
+div.system-message {
+ border: medium outset ;
+ padding: 1em }
+
+div.system-message p.system-message-title {
+ color: red ;
+ font-weight: bold }
+
+div.topic {
+ margin: 2em }
+
+h1 {
+ font-family: Arial, sans-serif;
+ font-size: 20px;
+}
+
+h1.title {
+ text-align: center;
+ font-size: 32px;
+}
+
+h2 {
+ font-size: 16px;
+ font-family: Arial, sans-serif;
+}
+
+h2.subtitle {
+ text-align: center }
+
+h3 {
+ font-size: 12px;
+ font-family: Arial, sans-serif;
+}
+
+hr {
+ width: 75% }
+
+ol.simple, ul.simple {
+ margin-bottom: 1em }
+
+ol.arabic {
+ list-style: decimal }
+
+ol.loweralpha {
+ list-style: lower-alpha }
+
+ol.upperalpha {
+ list-style: upper-alpha }
+
+ol.lowerroman {
+ list-style: lower-roman }
+
+ol.upperroman {
+ list-style: upper-roman }
+
+p.attribution {
+ text-align: right ;
+ margin-left: 50% }
+
+p.caption {
+ font-style: italic }
+
+p.credits {
+ font-style: italic ;
+ font-size: smaller }
+
+p.label {
+ white-space: nowrap }
+
+p.rubric {
+ font-weight: bold ;
+ font-size: larger ;
+ color: maroon ;
+ text-align: center }
+
+p.sidebar-title {
+ font-family: sans-serif ;
+ font-weight: bold ;
+ font-size: larger }
+
+p.sidebar-subtitle {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+p.topic-title {
+ font-weight: bold }
+
+pre.address {
+ margin-bottom: 0 ;
+ margin-top: 0 ;
+ font-family: serif ;
+ font-size: 100% }
+
+pre.line-block {
+ font-family: serif ;
+ font-size: 100% }
+
+pre.literal-block, pre.doctest-block {
+ margin-left: 2em ;
+ margin-right: 2em ;
+ background-color: #eeeeee;
+ border-color: #000000;
+ border-width: thin;
+ font-size: 14px
+}
+
+span.classifier {
+ font-family: sans-serif ;
+ font-style: oblique }
+
+span.classifier-delimiter {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+span.interpreted {
+ font-family: sans-serif }
+
+span.option {
+ white-space: nowrap }
+
+span.option-argument {
+ font-style: italic }
+
+span.pre {
+ white-space: pre }
+
+span.problematic {
+ color: red }
+
+table {
+ margin-top: 0.5em ;
+ margin-bottom: 0.5em }
+
+table.citation {
+ border-left: solid thin gray ;
+ padding-left: 0.5ex }
+
+table.docinfo {
+ margin: 2em 4em;
+}
+
+table.footnote {
+ border-left: solid thin black ;
+ padding-left: 0.5ex }
+
+td, th {
+ padding-left: 0.5em ;
+ padding-right: 0.5em ;
+ vertical-align: top }
+
+th.docinfo-name, th.field-name {
+ font-weight: bold ;
+ text-align: left ;
+ white-space: nowrap;
+ }
+
+h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
+ font-size: 100% }
+
+tt {}
+
+ul.auto-toc {
+ list-style-type: none }
+
+</style>
+</head>
+<body>
+<div class="document" id="tinyos-802-15-4-frames">
+<h1 class="title">TinyOS 802.15.4 Frames</h1>
+<table class="docinfo" frame="void" rules="none">
+<col class="docinfo-name" />
+<col class="docinfo-content" />
+<tbody valign="top">
+<tr class="field"><th class="docinfo-name">TEP:</th><td class="field-body">125</td>
+</tr>
+<tr class="field"><th class="docinfo-name">Group:</th><td class="field-body">Core Working Group</td>
+</tr>
+<tr class="field"><th class="docinfo-name">Type:</th><td class="field-body">Documentary</td>
+</tr>
+<tr><th class="docinfo-name">Status:</th>
+<td>Draft</td></tr>
+<tr class="field"><th class="docinfo-name">TinyOS-Version:</th><td class="field-body">2.x</td>
+</tr>
+<tr><th class="docinfo-name">Author:</th>
+<td>Jonathan Hui, Philip Levis, and David Moss</td></tr>
+<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">2-Feb-2007</td>
+</tr>
+<tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1</td>
+</tr>
+<tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-04-03</td>
+</tr>
+<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
+</tr>
+</tbody>
+</table>
+<div class="note">
+<p class="first admonition-title">Note</p>
+<p class="last">This memo documents a part of TinyOS for the TinyOS Community, and
+requests discussion and suggestions for improvements. Distribution
+of this memo is unlimited. This memo is in full compliance with
+TEP 1.</p>
+</div>
+<div class="section">
+<h1><a id="abstract" name="abstract">Abstract</a></h1>
+<p>This memo documents the frame format for 802.15.4 packets in TinyOS
+2.0.</p>
+</div>
+<div class="section">
+<h1><a id="introduction" name="introduction">1. Introduction</a></h1>
+<p>802.15.4 is a data-link and physical packet format for
+low-power wireless networks that is used in many TinyOS platforms.
+The TinyOS 2.0 active message layer adds a packet field for higher-level
+protocol dispatch. This document describes the two TinyOS 2.0 frame format
+for 802.15.4 networks. The first format is for isolated TinyOS networks;
+the second format is for networks that share the spectrum with 6lowpan
+networks[1]_.</p>
+</div>
+<div class="section">
+<h1><a id="id1" name="id1">2. 802.15.4</a></h1>
+<p>802.15.4 supports several different source and destination addressing
+modes, and so has a variable sized packet header.[2]_ A TinyOS device MUST
+support packet frames with 16-bit short source and destination addresses.
+A TinyOS device MAY support additional 802.15.4 frame formats.</p>
+</div>
+<div class="section">
+<h1><a id="frame-format" name="frame-format">3. Frame Format</a></h1>
+<p>TinyOS has two 802.15.4 frame formats. The first format, the T-Frame, is
+for TinyOS networks which do not share their channel with other wireless
+networking archtiectures. This frame format assumes that TinyOS can use
+every bit of the packet and does not need to state that it is a TinyOS packet.
+T-Frame stands for "TinyOS Frame."</p>
+<p>The TinyOS 802.15.4 T-frame format is as follows:</p>
+<pre class="literal-block">
++-------------------+---------+------------------------------+--------------+
+| 802.15.4 Header | AM type | data | 802.15.4 CRC |
++-------------------+---------+------------------------------+--------------+
+</pre>
+<p>AM type is a single byte field which indicates which active message type
+the payload contains.</p>
+<p>The second format, the I-Frame, is for TinyOS networks which share their
+channel with 6lowpan networks. 6lowpan reserves a series of codes for the
+first byte of the payload for non-6lowpan packets. In order to interoperate
+with 6lowpan networks, TinyOS I-Frames specify such a field. I-Frame stands
+for "Interoperable Frame."</p>
+<p>The TinyOS 802.15.4 I-frame format is as follows:</p>
+<pre class="literal-block">
++-------------------+---------+---------+--------------------+--------------+
+| 802.15.4 Header | 6lowpan | AM type | data | 802.15.4 CRC |
++-------------------+---------+------------------------------+--------------+
+</pre>
+<p>AM type is the same as in a T-frame. 6lowpan is the IANA-assigned code
+to identify this as a TinyOS packet. At this time, the exact value of
+this code has not been determined. To inform 6lowpan that this is not
+a 6lowpan packet, the code used MUST be in the range of 192-55.</p>
+</div>
+<div class="section">
+<h1><a id="implementation" name="implementation">4. Implementation</a></h1>
+<p>An implementation of the T-Frame can be found in tinyos-2.x/tos/chips/cc2420.</p>
+<p>An implementation of the I-Frame will soon be found in
+tinyos-2.x/tos/chips/cc2420.</p>
+</div>
+<div class="section">
+<h1><a id="author-addresses" name="author-addresses">5. Author Addresses</a></h1>
+<div class="line-block">
+<div class="line"><br /></div>
+<div class="line">Jonathan Hui</div>
+<div class="line">657 Mission St. Ste. 600</div>
+<div class="line">Arched Rock Corporation</div>
+<div class="line">San Francisco, CA 94105-4120</div>
+<div class="line"><br /></div>
+<div class="line">phone - +1 415 692 0828</div>
+<div class="line">email - <a class="reference" href="mailto:jhui@archedrock.com">jhui@archedrock.com</a></div>
+<div class="line"><br /></div>
+<div class="line">Philip Levis</div>
+<div class="line">358 Gates Hall</div>
+<div class="line">Stanford University</div>
+<div class="line">Stanford, CA 94305-9030</div>
+<div class="line"><br /></div>
+<div class="line">phone - +1 650 725 9046</div>
+<div class="line">email - <a class="reference" href="mailto:pal@cs.stanford.edu">pal@cs.stanford.edu</a></div>
+<div class="line"><br /></div>
+<div class="line">David Moss</div>
+<div class="line">Rincon Research</div>
+<div class="line"><br /></div>
+<div class="line"><br /></div>
+<div class="line"><br /></div>
+</div>
+</div>
+</div>
+</body>
+</html>
--- /dev/null
+====================================================================
+TinyOS 802.15.4 Frames
+====================================================================
+
+:TEP: 125
+:Group: Core Working Group
+:Type: Documentary
+:Status: Draft
+:TinyOS-Version: 2.x
+:Author: Jonathan Hui, Philip Levis, and David Moss
+
+:Draft-Created: 2-Feb-2007
+:Draft-Version: $Revision$
+:Draft-Modified: $Date$
+:Draft-Discuss: TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu>
+
+.. Note::
+
+ This memo documents a part of TinyOS for the TinyOS Community, and
+ requests discussion and suggestions for improvements. Distribution
+ of this memo is unlimited. This memo is in full compliance with
+ TEP 1.
+
+Abstract
+====================================================================
+
+This memo documents the frame format for 802.15.4 packets in TinyOS
+2.0.
+
+1. Introduction
+====================================================================
+
+802.15.4 is a data-link and physical packet format for
+low-power wireless networks that is used in many TinyOS platforms.
+The TinyOS 2.0 active message layer adds a packet field for higher-level
+protocol dispatch. This document describes the two TinyOS 2.0 frame format
+for 802.15.4 networks. The first format is for isolated TinyOS networks;
+the second format is for networks that share the spectrum with 6lowpan
+networks[1_].
+
+2. 802.15.4
+====================================================================
+
+802.15.4 supports several different source and destination addressing
+modes, and so has a variable sized packet header.[2_] A TinyOS device MUST
+support packet frames with 16-bit short source and destination addresses.
+A TinyOS device MAY support additional 802.15.4 frame formats.
+
+3. Frame Format
+====================================================================
+
+TinyOS has two 802.15.4 frame formats. The first format, the T-Frame, is
+for TinyOS networks which do not share their channel with other wireless
+networking archtiectures. This frame format assumes that TinyOS can use
+every bit of the packet and does not need to state that it is a TinyOS packet.
+T-Frame stands for "TinyOS Frame."
+
+The TinyOS 802.15.4 T-frame format is as follows::
+
+ +-------------------+---------+------------------------------+--------------+
+ | 802.15.4 Header | AM type | data | 802.15.4 CRC |
+ +-------------------+---------+------------------------------+--------------+
+
+AM type is a single byte field which indicates which active message type
+the payload contains.
+
+The second format, the I-Frame, is for TinyOS networks which share their
+channel with 6lowpan networks. 6lowpan reserves a series of codes for the
+first byte of the payload for non-6lowpan packets. In order to interoperate
+with 6lowpan networks, TinyOS I-Frames specify such a field. I-Frame stands
+for "Interoperable Frame."
+
+The TinyOS 802.15.4 I-frame format is as follows::
+
+ +-------------------+---------+---------+--------------------+--------------+
+ | 802.15.4 Header | 6lowpan | AM type | data | 802.15.4 CRC |
+ +-------------------+---------+------------------------------+--------------+
+
+AM type is the same as in a T-frame. 6lowpan is the IANA-assigned code
+to identify this as a TinyOS packet. At this time, the exact value of
+this code has not been determined. To inform 6lowpan that this is not
+a 6lowpan packet, the code used MUST be in the range of 192-55.
+
+
+4. Implementation
+====================================================================
+
+An implementation of the T-Frame can be found in tinyos-2.x/tos/chips/cc2420.
+
+An implementation of the I-Frame will soon be found in
+tinyos-2.x/tos/chips/cc2420.
+
+5. Author Addresses
+====================================================================
+
+
+|
+| Jonathan Hui
+| 657 Mission St. Ste. 600
+| Arched Rock Corporation
+| San Francisco, CA 94105-4120
+|
+| phone - +1 415 692 0828
+| email - jhui@archedrock.com
+|
+| Philip Levis
+| 358 Gates Hall
+| Stanford University
+| Stanford, CA 94305-9030
+|
+| phone - +1 650 725 9046
+| email - pal@cs.stanford.edu
+|
+| David Moss
+| Rincon Research
+|
+|
+|
projects / tinyos-2.x.git / commitdiff