blocks|key|1246633|text|您可以考虑使用IoT集线器https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins的设备双胞胎|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1246634|使用设备双胞胎：|1246635|将特定于设备的元数据存储在云中。例如，自动售货机的部署位置。|unordered-list-item|1246636|从设备应用程序中报告诸如可用功能和条件等当前状态信息。例如，设备通过蜂窝或WiFi连接到您的WiFi集线器。|1246637|同步设备应用程序和后端应用程序之间长期运行的工作流的状态。例如，当解决方案后端指定要安装的新固件版本时，设备应用程序报告更新过程的各个阶段。|1246638|查询设备元数据、配置或状态。|1246639|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins^0|D|25|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|12|8|@]|9|@]|C|$]]|$1|K|3|L|5|H|7|13|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|14|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

You can consider using Device Twin of IoT Hub
<a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins</a>

Use device twins to:

<ul>
<li>Store device-specific metadata in the cloud. For example, the deployment location of a vending machine.</li>
<li>Report current state information such as available capabilities and conditions from your device app. For example, a device is connected to your IoT hub over cellular or WiFi.</li>
<li>Synchronize the state of long-running workflows between device app and back-end app. For example, when the solution back end specifies the new firmware version to install, and the device app reports the various stages of the update process.</li>
<li>Query your device metadata, configuration, or state.</li>
</ul>

blocks|key|1246699|text|IoT集线器为您提供了通过各种协议连接设备的能力。首选协议是消息传递协议，如MQTT或AMQP，但也支持HTTPS。但是，使用IoT集线器，您不会从设备请求数据。该设备将将数据发送到IoT集线器。您必须选择使用IoT集线器来实现该功能：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1246700|只要有数据要发送，设备就会连接到IoT集线器，并将数据推送到IoT集线器。|unordered-list-item|1246701|该设备不单独发送任何数据，但始终或至少定期连接到IoT集线器。然后，您可以通过IoT集线器向设备发送云消息，请求发送数据。然后，设备以第一个选项中的相同方式发送数据。|1246702|当数据随后被发送到IoT集线器时，您需要将其推送到持久存储的某个地方--默认情况下，IoT集线器只保存1天的消息。这方面的备选办法是：|1246703|创建一个blob存储帐户并直接从IoT集线器推到它，使用一个自定义端点，这可能是最简单和最便宜的。但是，取决于如何访问数据，blob可能不是最好的选择。|offset|length|1246704|创建函数应用程序，使用EventHubTrigger创建函数，将其连接到IoT集线器，并通过将其输出到任何类型的数据接收器(如SQL、CosmosDB、表存储)来处理传入的数据。|1246705|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-custom^0|0|0|0|0|U|5|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Y|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|10|8|@]|9|@$K|11|L|12|1|13]]|A|$]]|$1|M|3|N|5|D|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

IoT Hub provides you with the ability to connect your devices over various protocols. Preferred protocols are messaging protocols, such as MQTT or AMQP, but HTTPS is also supported. Using IoT hub, you do not request data from the device, though. The device will send the data to the IoT Hub. You have to options to implement that with IoT Hub:

<ul>
<li>The device connects to the IoT Hub whenever it has some data to be sent, and pushes the data up to IoT Hub</li>
<li>The device does not send any data on its own, but stays always or at least regularly connected to IoT Hub. You then can send a cloud to device message over IoT Hub to the device, requesting the data to be sent. The device then sends the data the same way it would in the first option.</li>
</ul>

When the data then has been sent to IoT Hub, you need to push it somewhere where it is persistently stored - IoT Hub only keeps messages for 1 day by default. Options for this are:

<ul>
<li>Create a blob storage account and push to that directly from IoT Hub using a <a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-custom" rel="nofollow noreferrer">custom endpoint</a> This would probably be the easiest and cheapest. Dependening on how you need to access your data, a blob might not be the best option, though</li>
<li>Create a function app, create a function with an EventHubTrigger, connect it to IoT Hub and let the function process incoming data by outputting it into any kind of data sink, such as SQL, CosmosDB, Table Storage...</li>
</ul>

blocks|key|9008|text|您还没有提到使用哪个Azure+IoT集线器级别层。基本上，有两个价格组，如Basic和Standard，它们的成本和能力都有很大的不同。基本层只提供设备与Azure+IoT集线器之间的单向通信服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|9009|基于此，可以为您的业务用例使用以下方案：|9010|1.基本层(无事件驱动解决方案)设备根据需要周期性地向Azure+IoT集线器推送一条遥测和非遥测消息，其中非遥测消息通过服务总线队列/主题路由到Azure函数。这个非遥测管道的责任是在数据库中持久化一个真实的设备状态.请注意，600万条消息每月只需花费50美元。后端应用程序可以随时查询此数据库的设备状态。|9011|2.标准的Tier+(事件驱动解决方案)在这个场景中，您可以使用Azure+IoT集线器的设备双胞胎来在云后端(由@HelenLo描述)存储真实的设备状态。设备可以通过C2D消息、更改所需属性、调用方法或基于设备边缘触发器对用于更新状态的操作(所报告的属性)触发。Azure+IoT集线器具有为多个设备运行计划好的工作的功能。|offset|length|9012|在此解决方案中，后端应用程序可以在任何时候将ExportDevicesAsync的作业调用到blob存储，请参阅更多详细信息这里。请注意，600万条消息将花费每月250美元。|style|BOLD|9013|正如您可以看到的，每个场景都需要根据设备和Azure+IoT集线器之间的通信能力来构建不同的设备逻辑模型。注意，这些通信有一些限制，请参阅更多详细信息这里。|9014|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-jobs|1|https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-bulk-identity-mgmt|2|https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-quotas-throttling^0|0|0|0|4D|2|0|0|M|I|1Q|2|1|0|23|2|2|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@$H|15|I|16|1|17]]|A|$]]|$1|J|3|K|5|6|7|18|8|@$H|19|I|1A|L|M]]|9|@$H|1B|I|1C|1|1D]]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@$H|1F|I|1G|1|1H]]|A|$]]|$1|P|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]]]

You have not mentioned which the Azure IoT Hub scale tier is used. Basically there are two price groups such as Basic and Standard with a significant different cost and capabilities. The Basic tier offers only services for one-way communications between the devices and Azure IoT Hub.

Based on that, the following scenarios can be used for your business case:

1. Basic Tier (non event-driven solution)
The device pushs periodicaly a telementry and non-telemetry messages based on the needs to the Azure IoT Hub, where the non-telemetry messages are routed to the Azure Function via the Service Bus Queue/Topic. Responsibility for this non-telemetry pipe is to persist a real device state in the database. Note, that the 6M messages will cost only $50/month. The back-end application can any time to query this database for devices state.

2. Standard Tier (event-driven solution) In this scenario you can use a Device Twin of the Azure IoT Hub to enable storing a real-device state in the cloud-backend (described by @HelenLo). The device can be triggered by C2D message, changing a desired property, invoking a method or based on the device edge trigger to the action for updating a state (reported properties).
The Azure IoT Hub has a capabilities to run your scheduled <a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-jobs" rel="nofollow noreferrer">jobs</a> for multiple devices. 
In this solution, the back-end application can call any time a job for ExportDevicesAsync to the blob storage, see more details <a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-bulk-identity-mgmt" rel="nofollow noreferrer">here</a>. Note, that the 6M messages will cost $250/month.

As you can see the above each scenario needs to build a different device logic model based on the communications capabilities between the devices and Azure IoT Hub and back. Note, there are some limitations for these communications, see more details <a href="https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-quotas-throttling" rel="nofollow noreferrer">here</a>.

In my case I have 1000+ of devices that stores activity inside. I need to send a http get request to this device to get those data in csv or json format and save it in a storage hosted on azure. 
Cab IOT hub require data using get request and can it be scheduled to read daily/weekly? 
What other azure services would you suggest to facilitated this scheduled reads?

Can Azure IOT hub be used to read(Get) data from some devices?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在我的例子中，我有存储活动的设备的1000+。我需要向这个设备发送一个http请求，以csv或json格式获取这些数据，并将其保存在一个托管在azure上的存储中。Cab IOT集线器需要使用get请求的数据，可以安排每天/每周阅读吗？您还建议提供哪些其他的蔚蓝服务来帮助您进行预定的阅读？

问Azure IOT集线器可以用于从某些设备读取(获取)数据吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Azure IOT集线器可以用于从某些设备读取(获取)数据吗？EN