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: articles/iot/iot-overview-device-connectivity.md
+42-3Lines changed: 42 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,14 +17,31 @@ ms.custom:
17
17
18
18
This overview introduces the key concepts around how devices connect to the cloud in a typical Azure IoT solution. The article also introduces optional infrastructure elements such as gateways and bridges. Each section includes links to content that provides further detail and guidance.
19
19
20
+
# [Edge-based solution](#tab/edge)
21
+
22
+
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the connectivity between the assets and the IoT edge environment shown in the diagram:
23
+
24
+
<!-- Art Library Source# ConceptArt-0-000-032 -->
25
+
:::image type="content" source="media/iot-overview-device-connectivity/iot-edge-connectivity-architecture.svg" alt-text="Diagram that shows the high-level IoT edge-based solution architecture highlighting device connectivity areas." border="false" lightbox="media/iot-overview-device-connectivity/iot-edge-connectivity-architecture.svg":::
26
+
27
+
# [Cloud-based solution](#tab/cloud)
28
+
20
29
IoT Central applications use the IoT Hub and the Device Provisioning Service (DPS) services internally. Therefore, the concepts in this article apply whether you're using IoT Central to explore an IoT scenario or building your solution by using IoT Hub and DPS.
21
30
22
-
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the connectivity between the devices and the IoT cloud services, including gateways and bridges, shown in the diagram.
31
+
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the connectivity between the devices and the IoT cloud services, including gateways and bridges shown in the diagram:
23
32
24
-
:::image type="content" source="media/iot-overview-device-connectivity/iot-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting device connectivity areas." border="false":::
33
+
<!-- Art Library Source# ConceptArt-0-000-032 -->
34
+
:::image type="content" source="media/iot-overview-device-connectivity/iot-cloud-connectivity-architecture.svg" alt-text="Diagram that shows the high-level IoT cloud-based solution architecture highlighting device connectivity areas." border="false" lightbox="media/iot-overview-device-connectivity/iot-cloud-connectivity-architecture.svg":::
35
+
36
+
---
25
37
26
38
## Primitives
27
39
40
+
# [Edge-based solution](#tab/edge)
41
+
42
+
43
+
# [Cloud-based solution](#tab/cloud)
44
+
28
45
Azure IoT devices use the following primitives to exchange data with cloud services. Devices use:
29
46
30
47
-*Device-to-cloud* messages to send time series telemetry to the cloud. For example, temperature data collected from a sensor attached to the device.
@@ -36,8 +53,15 @@ Azure IoT devices use the following primitives to exchange data with cloud servi
36
53
37
54
To learn more, see [Device-to-cloud communications guidance](../iot-hub/iot-hub-devguide-d2c-guidance.md) and [Cloud-to-device communications guidance](../iot-hub/iot-hub-devguide-c2d-guidance.md).
38
55
56
+
---
57
+
39
58
## Device-facing cloud endpoints
40
59
60
+
# [Edge-based solution](#tab/edge)
61
+
62
+
63
+
# [Cloud-based solution](#tab/cloud)
64
+
41
65
An Azure IoT hub exposes a collection of per-device endpoints that let devices exchange data with the cloud. These endpoints include:
42
66
43
67
-*Send device-to-cloud messages*. A device uses this endpoint to send device-to-cloud messages.
@@ -55,6 +79,8 @@ The advantage of using DPS is that you don't need to configure all of your devic
55
79
56
80
To learn more about implementing automatic reconnections to endpoints, see [Manage device reconnections to create resilient applications](./concepts-manage-device-reconnections.md).
57
81
82
+
---
83
+
58
84
## Device connection strings
59
85
60
86
A device connection string provides a device with the information it needs to connect securely to an IoT hub. The connection string includes the following information:
@@ -65,6 +91,11 @@ A device connection string provides a device with the information it needs to co
65
91
66
92
## Authentication
67
93
94
+
# [Edge-based solution](#tab/edge)
95
+
96
+
97
+
# [Cloud-based solution](#tab/cloud)
98
+
68
99
Azure IoT devices use TLS to verify the authenticity of the IoT hub or DPS endpoint they're connecting to. The device SDKs rely on the device's trusted certificate store to include the DigiCert Global Root G2 TLS certificate they currently need to establish a secure connection to the IoT hub. To learn more, see [Transport Layer Security (TLS) support in IoT Hub](../iot-hub/iot-hub-tls-support.md) and [TLS support in Azure IoT Hub Device Provisioning Service (DPS)](../iot-dps/tls-support.md).
69
100
70
101
Azure IoT devices can use either shared access signature (SAS) tokens or X.509 certificates to authenticate themselves to an IoT hub. X.509 certificates are recommended in a production environment. To learn more about device authentication, see:
@@ -78,10 +109,18 @@ Azure IoT devices can use either shared access signature (SAS) tokens or X.509 c
78
109
79
110
All data exchanged between a device and an IoT hub is encrypted.
80
111
112
+
---
113
+
81
114
To learn more about security in your IoT solution, see [Security architecture for IoT solutions](iot-security-architecture.md).
82
115
83
116
## Protocols
84
117
118
+
# [Edge-based solution](#tab/edge)
119
+
120
+
Industrial IoT scenarios often use the [open platform communications unified architecture (OPC UA)](https://opcfoundation.org/about/opc-technologies/opc-ua/) industry standard open interface. To enable connectivity to the Azure cloud, use Azure IoT Operations. To learn more, see [What is Azure IoT Operations?](../iot-operations/get-started/overview-iot-operations.md).
121
+
122
+
# [Cloud-based solution](#tab/cloud)
123
+
85
124
An IoT device can use one of several network protocols when it connects to an IoT Hub or DPS endpoint:
@@ -100,7 +139,7 @@ To learn more about how to choose a protocol for your devices to connect to the
100
139
-[Communicate with DPS using the HTTPS protocol (symmetric keys)](../iot-dps/iot-dps-https-sym-key-support.md)
101
140
-[Communicate with DPS using the HTTPS protocol (X.509)](../iot-dps/iot-dps-https-x509-support.md)
102
141
103
-
Industrial IoT scenarios often use the [open platform communications unified architecture (OPC UA)](https://opcfoundation.org/about/opc-technologies/opc-ua/) industry standard open interface. To enable connectivity to the Azure cloud, use Azure IoT Operations. To learn more, see [What is Azure IoT Operations?](../iot-operations/get-started/overview-iot-operations.md).
0 commit comments