Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

device categories - initial draft #70

Closed
wants to merge 3 commits into from
Closed

device categories - initial draft #70

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
96ae4f0
initial draft
mlagally Feb 25, 2021
c4b57d1
adding categories
mlagally Mar 4, 2021
c88bf91
adding categories
mlagally Mar 4, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 74 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -595,6 +595,80 @@ <h3 id="profile-description-methodology">Methodology</h3>
</section>
</section>

<section id="device-categoriesdevices">
<h2>Device Categories</h2>
<p>
In a deployment of WoT conforming to the <a href="https://www.w3.org/TR/wot-architecture/#architecture-abstract">WoT Abstract Architecture</a>
we see different device types with typical characteristics.
They range (sorted in the order of footprint and capabilities)
from small embedded <em>node</em> devices to <em>gateways</em> or <em>hubs</em>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small does not imply resource constrained. Constrained or resource constrained embedded devices (like field devices) is more common.

to powerful <em>edge</em> devices and <em>cloud</em> servers.
Interoperability between these devices implies that a core set of features and functionalities
is available on <em>all</em> of them.
</p>

<p>The following device categories describe the footprint and characteristics of typical representants of these classes.
This is used to identify the possible features and use cases for these device classes.</p>

<p>
We are aligned with the classes defined in https://tools.ietf.org/html/rfc7228 for constrained devices,
however put the bounds on typical sizes of RAM / Flash in the real world.
Note that this is not a strict categorisation, categories may overlap and not all memory may be available for user applications.</p>

<table>
<tr>
<th>Category</th>
<th>data size (RAM)</th>
<th>code size (Flash, ROM, ...)</th>
<th>Typical Representant</th>
</tr>
<tr>
<td>Class-0, C0</td>
<td><< 10 KiB</td>
<td><< 100 KiB</td>
<td>unsecure sensor nodes</td>
</tr>
<tr>
<td>Class-1, C1</td>
<td>~ 10 KiB</td>
<td>~ 100 KiB</td>
<td>secure sensor node</td>
</tr><tr>
<td>Class-2, C2</td>
<td>~ 64 KiB</td>
<td>~ 256 KiB</td>
<td>nodeMCU</td>
</tr>
</tr><tr>
<td>Class-3, C3</td>
<td>~ 64-256 KiB</td>
<td>~ 256 KiB - several MBs</td>
<td>ISP gateway</td>
</tr>
</tr><tr>
<td>Class-4, C4</td>
<td>~ 256 KiB - several MB</td>
<td>~ 1 MB - several MB</td>
<td>gateway</td>
</tr>
</tr><tr>
<td>Class-5, C5</td>
<td>~ 1 GB</td>
<td>~ 1 GB</td>
<td>edge</td>
</tr>
</tr><tr>
<td>Class-6, C6</td>
<td>~ several GB</td>
<td>~ several GB</td>
<td>cloud</td>
</tr>
</table>

</p>
</section>



<!-- <a>Core Profile</a> -->

Expand Down