diff --git a/docs/api/api.md b/docs/api/api.md index a3f21812f1..1b47b921df 100644 --- a/docs/api/api.md +++ b/docs/api/api.md @@ -153,7 +153,7 @@ The [Mbed OS RTOS](rtos.html) capabilities include managing objects such as thre Ethernet -6LoWPAN Mesh +Mesh Wi-Fi diff --git a/docs/api/networkinterfaces/MeshInterface.md b/docs/api/networkinterfaces/MeshInterface.md index 2008f15f57..27ba692eab 100644 --- a/docs/api/networkinterfaces/MeshInterface.md +++ b/docs/api/networkinterfaces/MeshInterface.md @@ -1,4 +1,4 @@ -

6LoWPAN Mesh

+

Mesh

![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.png)MeshInterface class hierarchy diff --git a/docs/reference/technology/connectivity/connectivity.md b/docs/reference/technology/connectivity/connectivity.md index 2ece0a6fa8..f3016c5d42 100644 --- a/docs/reference/technology/connectivity/connectivity.md +++ b/docs/reference/technology/connectivity/connectivity.md @@ -62,11 +62,11 @@ Typical applications of BLE are health care, fitness trackers, beacons, smart ho To learn how to use BLE on Mbed OS, please refer to the [Bluetooth overview](../apis/ble.html). -#### IP-based mesh (Thread and Wi-SUN) +#### IP-based mesh (Thread and 6LoWPAN-ND) As a technology designed with large-scale deployment in mind, mesh is optimized for long battery life and low cost. -**Thread** is designed for indoor use, with a range of only a few meters. **Wi-SUN** has a range of up to one kilometer, and is therefore better suited for external use. Both technologies have a low throughput of up to 200 kbps and experience delays. +**Thread** is designed for indoor use, with a range of only a few meters. **6LoWPAN-ND** has a range of up to one kilometer, and is therefore better suited for external use. Both technologies have a low throughput of up to 200 kbps and experience delays. Mesh networks are self-healing, with no single point of failure. They are more suitable for limited spaces because of the expense in infrastructure setup and maintenance. diff --git a/docs/reference/technology/connectivity/networking.md b/docs/reference/technology/connectivity/networking.md index a22a0ee9fa..d6eae315c0 100644 --- a/docs/reference/technology/connectivity/networking.md +++ b/docs/reference/technology/connectivity/networking.md @@ -90,4 +90,4 @@ On Mesh networks, Nanostack uses IEEE 802.15.4 radios for transmitting and recei This driver type has no other use cases, so it is implemented in C using a Nanostack-specific API. -Please see the [6LoWPAN Mesh technology section](mesh-tech.html) and [Porting a new RF driver for the 6LoWPAN stack](../porting/lora-port.html) for more information. +Please see the [Mesh technology section](mesh-tech.html) and [Porting a new RF driver for the 6LoWPAN stack](../porting/lora-port.html) for more information. diff --git a/docs/reference/technology/mesh/quick_start_intro.md b/docs/reference/technology/mesh/quick_start_intro.md index d0736fcddd..488fa76899 100644 --- a/docs/reference/technology/mesh/quick_start_intro.md +++ b/docs/reference/technology/mesh/quick_start_intro.md @@ -1,4 +1,4 @@ -

6LoWPAN Mesh

+

Mesh

This guide provides design guidelines for developing an application on top of the 6LoWPAN mesh solution. The APIs and technologies are not discussed in detail here. @@ -36,7 +36,7 @@ A 6LoWPAN host is a type of node that does not route any packets. It has only on A 6LoWPAN sleepy host is a 6LoWPAN host that is periodically allowed to sleep and turn off its radio. -#### Different types of 6LoWPAN mesh networks +#### Different types of mesh networks 6LoWPAN-based mesh networks cannot be described as a uniform standardized network type, such as Wi-Fi. Depending on the business requirements and use cases the network may have different setups and requirements. @@ -57,13 +57,3 @@ In a mesh/tree network, all nodes are configured as 6LoWPAN routers. In a 6LoWPAN network, RPL protocol is used for forming the routing topology. Every node selects a primary parent for routing so the result looks like a tree. This network type allows to cover large areas because each node extends the range of the network. However, the packet is retransmitted on every hop, which means that the transfer capacity of the network decreases as the size of the network increases. - -##### Example networks - -![Example networks](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/examples.png) - -In the further chapters, we provide recommendations for three different network sizes: - -- A sensor network for an apartment. -- A sensor/actuator network for a building. -- A sensor/actuator network for a city. diff --git a/docs/reference/technology/mesh/thread_intro.md b/docs/reference/technology/mesh/thread_intro.md index 5d2ef28e2c..1413d38eb3 100644 --- a/docs/reference/technology/mesh/thread_intro.md +++ b/docs/reference/technology/mesh/thread_intro.md @@ -33,10 +33,10 @@ The key elements of Mbed OS are: Mbed Thread is implemented in the Nanostack library, which also supports the 6LoWPAN protocol. In Mbed OS, the Thread stack runs in its own RTOS thread using an internal event scheduler. Mbed OS provides the [Mesh C++ API](../apis/mesh-api.html) for building Thread applications. -- To connect to the Thread network, use the [Mbed Mesh API](../apis/mesh-api.html) or [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h). +- To connect to the Thread network, use the [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h). - For the socket communication over the Thread network, use the [Mbed sockets API](../apis/network-socket.html). -Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/sal-stack-nanostack/nanostack) has the following header files: +Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/sal-stack-nanostack/nanostack) has the following header files(): - `thread_management_if.h` for initializing the stack and managing the network data. - `thread_commissioning_api.h` for implementing an on-mesh or a native Thread commissioner.