You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/technology/connectivity/networking.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
-
###IP networking
1
+
## IP networking
2
2
3
3
IP Networking in Mbed OS is layered in three clearly defined API levels. The diagram below shows the layers next to the closest matching [OSI model](https://en.wikipedia.org/wiki/OSI_model) layers.
The following sections introduce the APIs and technologies implemented in each level.
8
8
9
-
####Socket API
9
+
### Socket API
10
10
11
11
The Socket API is the common API among all IP connectivity methods. All network stacks in Mbed OS provide the same Socket API, making applications portable among different connectivity methods or even stacks.
12
12
13
-
In the OSI model, the Socket API relates to layer 4, the Transport layer. In Mbed OS, the Socket API supports both [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol) and [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) protocols.
13
+
In the OSI model, the Socket API relates to layer 4, the Transport layer. In Mbed OS, the Socket API supports both TCP and UDP protocols.
14
14
15
15
Refer to [Socket API](network-socket.html) reference for usage instructions.
16
16
17
-
####IP stacks
17
+
### IP stacks
18
18
19
19
Mbed OS has three options to select for the IP stack. The connectivity modules provides two built-in IP stacks or an external IP stack.
20
20
@@ -32,7 +32,7 @@ The following table summarizes different stacks, use cases and their limitations
|External IP module|Depends on the module|(Save RAM/Flash)|Depends on the module. Usually poor match to Socket API|
34
34
35
-
#####Configuring the IP stack interface
35
+
#### Configuring the IP stack interface
36
36
37
37
Depending on the Layer 3, Network layer, protocol used, there are different ways to configure the interface. It also depends on the stack used, which configurations are supported on each link layer.
38
38
@@ -44,7 +44,7 @@ Depending on the Layer 3, Network layer, protocol used, there are different ways
44
44
|Nanostack|Ethernet|IPv6|static or [RFC 4862](https://tools.ietf.org/html/rfc4862) IPv6 Stateless Address Autoconfiguration. No DHCPv6 support|
45
45
|Nanostack|IEEE 802.15.4|6LoWPAN|Thread or 6LoWPAN-ND+RPL|
46
46
47
-
####Network interfaces
47
+
### Network interfaces
48
48
49
49
Network intefaces are the application level APIs where users choose the driver, connectivity method and IP stack. Each connectivity methods requires different configuration,so these APIs are not interchangeable. The application developer must choose one. Choosing the interface also automatically pulls in the network stack as a dependency.
50
50
@@ -60,29 +60,29 @@ Mbed OS implements the following network interface APIs:
60
60
61
61
Refer to [Network Interface](network-interfaces.html) API reference for usage instructions.
62
62
63
-
####Network driver
63
+
### Network driver
64
64
65
65
The network driver is a generic term to describe different APIs for connecting networking device to the IP stack or Socket API. Below is a description of each driver API.
Ethernet drivers are implemented using the stack-independent EMAC API. Because the Ethernet driver requires no configuration, it does not implement any controlling interface for the application.
There are two types of Wi-Fi drivers in Mbed OS, depending on which protocol layer it implements. Wi-Fi drivers are either a special case of Ethernet driver or external IP stacks. Wi-Fi drivers require configuration from an application and, therefore, implement both the low level EMAC API or Network stack API and the high level controlling interface API called `WiFiInterface`.
Cellular drivers have the same two separate cases as Wi-Fi. If they use an external IP stack, the driver implements the Network stack API. If they use the internal IP stack, LwIP, then they implement the Serial PPP driver.
0 commit comments