Skip to content

Commit 1e00bf2

Browse files
committed
Adding first section
1 parent 8a6f79a commit 1e00bf2

File tree

2 files changed

+21
-16
lines changed

2 files changed

+21
-16
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The following diagram shows a high-level view of the components in a typical clo
2828
<!-- Art Library Source# ConceptArt-0-000-032 -->
2929
:::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":::
3030

31-
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 or IoT Hub.
31+
IoT Central applications use the IoT Hub and the Device Provisioning Service (DPS) services internally. Therefore, the concepts in a cloud-based IoT solution apply whether you're using IoT Central or IoT Hub.
3232

3333
---
3434

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

Lines changed: 20 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -23,30 +23,35 @@ The following diagram shows a high-level view of the components in a typical edg
2323

2424
### [Cloud-based solution](#tab/cloud)
2525

26-
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.
27-
28-
The following diagram shows a high-level view of the components in a typical edge-based IoT solution. This article focuses on the device management and control components of a cloud-based IoT solution:
26+
The following diagram shows a high-level view of the components in a typical cloud-based IoT solution. This article focuses on the device management and control components of a cloud-based IoT solution:
2927

3028
<!-- Art Library Source# ConceptArt-0-000-032 -->
3129
:::image type="content" source="media/iot-overview-device-management/iot-cloud-management-architecture.svg" alt-text="Diagram that shows the high-level IoT cloud-based solution architecture highlighting device management areas." border="false" lightbox="media/iot-overview-device-management/iot-cloud-management-architecture.svg":::
3230

33-
In Azure IoT, device management refers to processes such as provisioning and updating devices. Device management includes the following tasks:
31+
IoT Central applications use the IoT Hub and the Device Provisioning Service (DPS) services internally. Therefore, the concepts in a cloud-based IoT solution apply whether you're using IoT Central or IoT Hub.
32+
33+
---
34+
35+
In Azure IoT, asset and device management refers to processes such as provisioning and updating assets or devices. Asset and device management includes the following tasks:
3436

35-
- Device registration
36-
- Device provisioning
37-
- Device deployment
38-
- Device updates
39-
- Device key management and rotation
40-
- Device monitoring
41-
- Enabling and disabling devices
37+
- Asset or device registration.
38+
- Asset or device provisioning.
39+
- Asset or device deployment.
40+
- Asset or device updates.
41+
- Asset or device key management and rotation.
42+
- Asset or device monitoring.
43+
- Enabling and disabling assets or devices.
44+
- Define the asset endpoints that connect assets to your edge runtime environment.
45+
- Define asset tags and events to enable data flow from OPC UA servers to the MQTT broker.
4246

43-
In Azure IoT, *command and control* refers to the processes that let you send commands to devices and receive responses from them. For example, you can send a command to a device to:
47+
In Azure IoT, *command and control* refers to the processes that let you send commands to assets and devices and receive responses from them. For example, you can send a command to:
4448

4549
- Set a target temperature.
4650
- Request maximum and minimum temperature values for the last two hours.
47-
- Set the telemetry interval to 10 seconds.
48-
49-
---
51+
- Set the sensor data interval to 10 seconds.
52+
- Control the camera pan, tilt, and zoom.
53+
- Capture snapshots from a video stream and publish them to an MQTT topic.
54+
- Shut down the lights of a building to save energy.
5055

5156
## Primitives
5257

0 commit comments

Comments
 (0)