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-management.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,16 +27,14 @@ In an edge-based IoT solution, asset management refers to processes such as regi
27
27
- Asset, tags and events creation
28
28
- Data flow endpoint creation
29
29
- Asset and data flow endpoints secrets management
30
-
- Asset updates
31
-
- Asset monitoring
32
30
- Enabling and disabling assets
33
31
34
-
In an edge-based IoT solution, an MQTT broker enables bidirectional edge/cloud communication, and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge. For example, you can:
32
+
In an edge-based IoT solution, *command and control* refers to the processes that let you send commands to assets and receive responses from them. For example, you can:
35
33
36
34
- Control the cameras pan, tilt, and zoom.
37
35
- Capture snapshots from a video stream and publish them to an MQTT topic.
38
36
- Publish OPC UA machine status events to the MQTT broker.
39
-
-Shut down the lights of a building to save energy.
37
+
-Turn off the lights of a building to save energy.
40
38
41
39
## Primitives
42
40
@@ -51,6 +49,7 @@ An edge-based IoT solution can use the following primitives for asset management
51
49
-*Schema registry* that lets you define and manage the schema for your assets. Data flows use schemas to deserialize and serialize messages.
52
50
-*Akri services* that let you deploy and configure connectivity protocols, such as OPC UA and ONVIF, at the edge. Akri services use the asset and asset endpoint resources in Azure Device Registry to model the different device and protocol connections in your environment.
53
51
-*Secret Store extension* to sync the secrets down from the cloud and store them on the edge as Kubernetes secrets. Azure IoT Operations uses Azure Key Vault as the managed vault solution on the cloud, and uses [Azure Key Vault Secret Store extension for Kubernetes](/azure/azure-arc/kubernetes/secret-store-extension) to sync the secrets.
52
+
-*Sites* that group Azure IoT Operations instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates sites and assigns Azure IoT Operations instances to them. To learn more, see [What is Azure Arc site manager (preview)?](/azure/azure-arc/site-manager/overview).
54
53
55
54
To learn more, see [What is asset management in Azure IoT Operations](../iot-operations/discover-manage-assets/overview-manage-assets.md) and [Configure data flows in Azure IoT Operations](../iot-operations/connect-to-cloud/howto-create-dataflow.md).
56
55
@@ -63,9 +62,13 @@ To learn more, see [What is asset management in Azure IoT Operations](../iot-ope
63
62
- Asset registration in a single unified registry that enables edge and cloud management.
64
63
- Defining asset tags and events to enable data flow from OPC UA servers to the MQTT broker.
65
64
66
-
## Asset endpoint secrets management
65
+
## Data flow endpoint creation
67
66
68
-
## Asset monitoring
67
+
## Asset and data flow endpoints secrets management
68
+
69
+
## Command and control
70
+
71
+
The MQTT broker enables bidirectional edge/cloud communication, and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge.
0 commit comments