Skip to content

Commit 3c96e05

Browse files
committed
Update iot-overview-device-connectivity for adaptive cloud
1 parent 30dd80b commit 3c96e05

File tree

3 files changed

+3691
-3
lines changed

3 files changed

+3691
-3
lines changed

articles/iot/iot-overview-device-connectivity.md

Lines changed: 42 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,31 @@ ms.custom:
1717

1818
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.
1919

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+
2029
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.
2130

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:
2332

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+
---
2537

2638
## Primitives
2739

40+
# [Edge-based solution](#tab/edge)
41+
42+
43+
# [Cloud-based solution](#tab/cloud)
44+
2845
Azure IoT devices use the following primitives to exchange data with cloud services. Devices use:
2946

3047
- *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
3653

3754
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).
3855

56+
---
57+
3958
## Device-facing cloud endpoints
4059

60+
# [Edge-based solution](#tab/edge)
61+
62+
63+
# [Cloud-based solution](#tab/cloud)
64+
4165
An Azure IoT hub exposes a collection of per-device endpoints that let devices exchange data with the cloud. These endpoints include:
4266

4367
- *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
5579

5680
To learn more about implementing automatic reconnections to endpoints, see [Manage device reconnections to create resilient applications](./concepts-manage-device-reconnections.md).
5781

82+
---
83+
5884
## Device connection strings
5985

6086
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
6591

6692
## Authentication
6793

94+
# [Edge-based solution](#tab/edge)
95+
96+
97+
# [Cloud-based solution](#tab/cloud)
98+
6899
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).
69100

70101
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
78109

79110
All data exchanged between a device and an IoT hub is encrypted.
80111

112+
---
113+
81114
To learn more about security in your IoT solution, see [Security architecture for IoT solutions](iot-security-architecture.md).
82115

83116
## Protocols
84117

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+
85124
An IoT device can use one of several network protocols when it connects to an IoT Hub or DPS endpoint:
86125

87126
- [MQTT](https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.pdf)
@@ -100,7 +139,7 @@ To learn more about how to choose a protocol for your devices to connect to the
100139
- [Communicate with DPS using the HTTPS protocol (symmetric keys)](../iot-dps/iot-dps-https-sym-key-support.md)
101140
- [Communicate with DPS using the HTTPS protocol (X.509)](../iot-dps/iot-dps-https-x509-support.md)
102141

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).
142+
---
104143

105144
## Connection patterns
106145

0 commit comments

Comments
 (0)