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-development.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,13 @@ The following diagram shows a high-level view of the components in a typical edg
21
21
22
22
:::image type="content" source="media/iot-overview-device-development/iot-edge-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting asset connectivity areas." border="false":::
23
23
24
-
Assets typically have built-in firmware that that implements standard protocols. For example, a robotic arm might be an OPC UA client and a security video might implement ONVIF. Azure IoT Operations includes various connectors that can use these protocols to assets, and translate messages from the assets into MQTT messages. You can create your own, custom connectors to connect to assets that use protocols not natively supported by Azure IoT Operations.
24
+
Assets typically have built-in firmware that that implements standard protocols. For example, a robotic arm might be an OPC UA client and a security video camera might implement ONVIF. Azure IoT Operations includes various connectors that can use these protocols to communicate with assets and translate messages from the assets into MQTT messages. Some assets can receive messages enabling you to perform operations on them such as:
25
+
26
+
- Pan or tilt a security camera.
27
+
- Change the logging level on a robotic arm.
28
+
- Initiate a firmware update.
29
+
30
+
You can create your own, custom connectors to connect to assets that use protocols not natively supported by Azure IoT Operations.
25
31
26
32
# [Cloud-based solution](#tab/cloud)
27
33
@@ -80,7 +86,7 @@ Examples of specialized hardware and operating systems include:
80
86
81
87
[Eclipse ThreadX](https://github.com/eclipse-threadx/rtos-docs) is a real time operating system for IoT and edge devices powered by MCUs. Eclipse ThreadX is designed to support highly constrained devices that are battery powered and have less than 64 KB of flash memory.
82
88
83
-
[Azure Sphere](/azure-sphere/product-overview/what-is-azure-sphere) is a secure, high-level application platform with built-in communication and security features for internet-connected devices. It comprises a secured, connected, crossover MCU, a custom high-level Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
89
+
[Azure Sphere (Integrated)](/azure-sphere/product-overview/what-is-azure-sphere?view=azure-sphere-integrated) is a secure, high-level application platform with built-in communication and security features for internet-connected devices. It comprises a secured, connected, crossover MCU, a custom high-level Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
84
90
85
91
### Device primitives
86
92
@@ -175,6 +181,8 @@ Containerization is a way to package and run your code in a lightweight, isolate
175
181
176
182
Azure IoT Operations containerizes all its connectors, brokers, and other components that run on the edge. Azure IoT Edge deploys to a Kubernetes cluster, which is a container orchestration platform. Deploy any custom connectors or other components that you create to the Kubernetes cluster.
177
183
184
+
You can view a solution that uses Azure IoT Edge as an edge-based gateway to IoT Hub as a hybrid solution that includes elements of both edge-based and cloud-based solutions.
185
+
178
186
# [Cloud-based solution](#tab/cloud)
179
187
180
188
If you use containers, such as in Docker, to run your device code you can deploy code to your devices by using the capabilities of the container infrastructure. Containers also let you define a runtime environment for your code with all the required library and package versions installed. Containers make it easier to deploy updates and to manage the lifecycle of your IoT devices.
0 commit comments