CN112261066A - Method for supporting COAP (chip on Board) equipment by cloud service platform - Google Patents
Method for supporting COAP (chip on Board) equipment by cloud service platform Download PDFInfo
- Publication number
- CN112261066A CN112261066A CN202011499256.3A CN202011499256A CN112261066A CN 112261066 A CN112261066 A CN 112261066A CN 202011499256 A CN202011499256 A CN 202011499256A CN 112261066 A CN112261066 A CN 112261066A
- Authority
- CN
- China
- Prior art keywords
- iot
- coap
- iot edge
- module
- cloud
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y20/00—Information sensed or collected by the things
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y30/00—IoT infrastructure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method for a cloud service platform to support a COAP device, which comprises the following steps: creating an IoT Hub at Portal, and selecting project quota to support IoT Edge at an IoT center; creating an IoT Edge device; deploying an IoT Edge Host; creating a Container Registry; deploying a COAP Module; and using the COAP Module in the IoT Edge device to manage the equipment of the COAP protocol through a cloud interface. The invention deploys the existing COAP equipment to the cloud, breaks through the problem that the traditional IoT equipment is difficult to be arranged to the cloud, saves the cost of data storage and equipment management, and improves the safety, thereby keeping pace with the development of the technology of the Internet of things.
Description
Technical Field
The invention relates to the technical field of Internet of things, in particular to a method for a cloud service platform to support a COAP device.
Background
In recent years, with the development of the internet of things, many IoT devices, such as temperature and humidity sensors, appear on the market, some of the devices upload data to a designated server through the COAP protocol, and some of the devices are stored in a local storage. Whether stored in the server or the local storage, the following problems occur:
1. the stored data is inconvenient to read;
2. the storage size is limited;
3. the disaster is not easy to recover;
4. the management cost is expensive.
With the rapid development of cloud computing technology in recent years, the problems can be solved at the cloud end, but most of the existing cloud platforms are based on a TCP protocol, so that the COAP protocol devices are difficult to deploy to the cloud end.
Disclosure of Invention
In view of this, the present invention provides a solution for migrating a COAP protocol device to a cloud based on a cloud platform, aiming at the problem that a large number of existing COAP protocol devices are difficult to deploy to the cloud. The device end can communicate with the IoT Hub only by modifying a small amount of reported information, such as server addresses and device identification information, so that the device can be remotely managed through a mobile phone App or a webpage.
In order to achieve the above object, the present invention provides a method for a cloud Service platform to support a COAP device, which mainly includes the following steps:
s1, creating an IoT Hub at Portal, selecting project quota to support an IoT Edge device at an IoT Hub, the IoT Hub comprising: a base layer, a standard layer; wherein the base layer enables telemetry from device to cloud, per-device authentication, message routing and event grid integration, device provisioning services, and monitoring and diagnostics; the standard layer enables cloud-to-device messaging, device twinning, module twinning, and device management, and IoT Edge support;
preferably, selecting the project quota at the IoT hub supports the IoT Edge device with the following options:
；
s2, creating the IoT Edge device supported by the IoT center quota project;
wherein the IoT Edge device includes three components:
IoT Edge module: the system is used for running services, third-party services and user-defined codes; deploying an IoT Edge module to an IoT Edge device to execute in a local manner;
IoT Edge Runtime: means for running on and managing deployments to each IoT Edge device; IoT Edge Runtime uses custom logic and cloud logic on IoT Edge devices; the IoT Edge Runtime sits on the IoT Edge device and performs management and communication operations. The runtime performs a number of functions:
(1) installing and updating a workload on a device;
(2) maintaining an IoT Edge security standard on a device;
(3) ensuring that the IoT Edge module is always running;
(4) reporting the module operation condition to the cloud for remote monitoring;
(5) managing communications between a downstream device and an IoT Edge device, between modules on the IoT Edge device, and between the IoT Edge device and a cloud;
cloud interface: for remotely monitoring and managing the IoT Edge device through a cloud interface;
s3, deploying an IoT Edge Host, installing the IoT Edge Runtime on the IoT Edge Host, and configuring and connecting to the Iot Edge device to monitor a COAP Module port of the IoT Edge device;
preferably, the IoT Edge Host is a small device like Raspberry Pi and/or a large device like an industrial server;
the IoT Edge Host runs the IoT Edge Runtime, monitors the COAP port, receives data sent by the IoT equipment, forwards the data to the IoT Hub, and extracts unprocessed messages in the cloud message queue to forward the messages to the IoT equipment according to the equipment ID in the data packet;
preferably, the IoT Edge Host is deployed to a local PC;
preferably, the linux routing device and/or the cloud virtual machine, the Module image is deployed in the Docker and/or the Container;
s4, creating a Container Registry for rapidly generating, pushing and running a Docker Container image in a native mode;
s5, deploying a COAP Module, and receiving the COAP data uploaded by the IoT equipment, forwarding the COAP data to the IoT Hub, and extracting unprocessed messages in a cloud message queue according to the equipment ID in the COAP data packet and forwarding the unprocessed messages to the IoT Edge equipment;
s6, using the COAP Module in an IoT Edge device, and managing the equipment of the COAP protocol through the cloud interface;
in the step S3, installing an IoT Edge Runtime on the IoT Edge Host, where the operating environment of the IoT Edge Runtime is a Windows and/or Linux system;
in the step S4, in the method for creating a Container Registry, the method for quickly generating includes: a registry name and a set of resources are entered, the registry name being unique among them and containing alphanumeric characters.
Further, in the step S5, the method for deploying the COAP Module includes: installing a Docker and a Visual Stdio Code on a local compiling computer, wherein the Docker of the local compiling computer generates a COAP Module after compiling;
the IoT Edge module is an execution unit, is realized in a way of Docker compatible containers, and runs service logic at the Edge; preferably, a plurality of modules are configured to communicate with each other, creating a data processing pipeline; preferably, custom modules are developed or certain services are packaged into modules to provide insights at the edge in an offline fashion.
Further, in the step S6, the method for using the COAP Module in the IoT Edge device includes: the IoT Edge device runs a COAP Module and an Edge Hub, uploads COAP data to an IoT Edge Host port, and records a device ID and a source IP address in the data for reverse control equipment; and monitoring data received by the IoT Hub, finding the IP address of the equipment to be controlled according to the equipment ID, and sending the control information to the corresponding equipment.
The cloud interface has difficulty managing the software lifecycle of millions of IoT devices, which are often of different brands and models, or are geographically dispersed. Workloads are created and configured for a particular type of device, deployed to all devices, and monitored to capture any behavioural anomalies of the device. These activities cannot be done on a device-by-device basis and must be performed on a large scale; IoT Edge seamlessly integrates with IoT solution accelerators, providing a control plane that meets the solution needs. The cloud service allows:
(1) creating and configuring a workload running on a particular type of device;
(2) sending a workload to a set of devices;
(3) a workload running on a field device is monitored.
The present invention uses IoT edges to move cloud analytics and custom business logic to devices, which can focus on business insights rather than data management. By packaging the business logic into standard containers, the IoT solution is scaled horizontally, and these containers can then be deployed to any device and all of these devices monitored from the cloud; analytics may improve the business value in IoT solutions, but not all analytics need to be done in the cloud; if it is desired to respond to an emergency as quickly as possible, the workload may be detected at the edge running an exception. If it is desired to reduce bandwidth costs and avoid transmitting raw data for a number of TBs, the data can be cleaned and aggregated locally and then only the findings sent to the cloud for analysis.
Compared with the prior art, the invention has the beneficial effects that: the existing COAP protocol equipment is deployed to the cloud, the problem that the traditional IoT equipment is difficult to arrange to the cloud is solved, the waste is changed into the treasure, the waste of resources is avoided, the cost of data storage and equipment management is saved, the safety is improved, and therefore the development of the technology of the Internet of things is kept up and promoted.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention.
In the drawings:
fig. 1 is a flowchart of a method for a cloud service platform to support a COAP device according to the present invention;
fig. 2 is a working framework diagram of a method for supporting a COAP device by a cloud service platform according to the present invention.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The present invention uses IoT edges to move cloud analytics and custom business logic to devices, which can focus on business insights rather than data management. By packaging the business logic into standard containers, the IoT solution is scaled horizontally, and these containers can then be deployed to any device and all of these devices monitored from the cloud; analytics may improve the business value in IoT solutions, but not all analytics need to be done in the cloud; if it is desired to respond to an emergency as quickly as possible, the workload may be detected at the edge running an exception. If the bandwidth cost is reduced and the original data of the TB are prevented from being transmitted, the data can be cleaned and aggregated locally, and then only the finding solution is sent to the cloud for analysis;
the embodiment of the invention provides a method for a cloud service platform to support a COAP device, which is shown in figure 1 and comprises the following steps:
s1, creating an IoT Hub at Portal, selecting project quota to support an IoT Edge device at an IoT Hub, the IoT Hub comprising: a base layer, a standard layer; wherein the base layer enables telemetry from device to cloud, per-device authentication, message routing and event grid integration, device provisioning services, and monitoring and diagnostics; the standard layer enables cloud-to-device messaging, device twinning, module twinning, and device management, and IoT Edge support;
preferably, selecting the project quota at the IoT hub supports the IoT Edge device with the following options:
；
the lot hub provides two layers, a base layer and a standard layer, which differ in the number of functions supported; the base layer enables partial functions and is suitable for an IoT solution which only needs one-way communication, namely from the device to the cloud; the standard layer enables all functions, which is necessary for any IoT solution that needs to use the bi-directional communication function. In the process of carrying out the IoT center project quota, the invention carries out certain quota support on the basic layer and the standard layer, and aims to support two-way communication, allow networking and offline equipment states, be completely inquired in the cloud and be remotely controlled; if an IoT solution requires data to be collected from the device first and then analyzed centrally, it may be appropriate to use the base layer; if an IoT device needs to be remotely controlled using a more advanced configuration, or some workload needs to be distributed to the device itself, the standard layer should be considered;
s2, creating the IoT Edge device supported by the IoT center quota project;
wherein the IoT Edge device includes three components:
IoT Edge module: the system is used for running services, third-party services and user-defined codes; deploying an IoT Edge module to an IoT Edge device to execute in a local manner;
IoT Edge Runtime: means for running on and managing deployments to each IoT Edge device; IoT Edge Runtime allows custom logic and cloud logic to be used on IoT Edge devices; the IoT Edge Runtime sits on the IoT Edge device and performs management and communication operations. The runtime performs a number of functions:
(1) installing and updating a workload on a device;
(2) maintaining an IoT Edge security standard on a device;
(3) ensuring that the IoT Edge module is always running;
(4) reporting the module operation condition to the cloud for remote monitoring;
(5) managing communications between a downstream device and an IoT Edge device, between modules on the IoT Edge device, and between the IoT Edge device and a cloud;
cloud interface: for remotely monitoring and managing the IoT Edge device through a cloud interface;
preferably, clicking and adding an IoT Edge device in the IoT Hub-IoT Edge, inputting a device ID, keeping the default of the rest devices, and clicking and saving;
s3, deploying an IoT Edge Host, installing the IoT Edge Runtime on the IoT Edge Host, and configuring and connecting to the Iot Edge device to monitor a COAP Module port of the IoT Edge device;
preferably, the IoT Edge Host is a small device like Raspberry Pi and/or a large device like an industrial server, and can be transformed according to the amount of data to be processed; if the data to be processed is not large, a small device like a Raspberry Pi is used, and if a resource-intensive workload is to be run, an industrial server is used.
The IoT Edge Host runs the IoT Edge Runtime, monitors the COAP port, receives data sent by the IoT equipment, forwards the data to the IoT Hub, extracts unprocessed messages in the cloud message queue according to the equipment ID in the data packet and forwards the messages to the IoT equipment, and therefore the equipment can be controlled reversely.
Preferably, the IoT Edge Host is deployed to a local PC, and the PC has high configuration and strong interaction capability with other devices;
preferably, the linux routing device and/or the cloud virtual machine, the Module image is deployed in Docker and/or Container, and the IoT Edge can run in the linux virtual machine and/or the cloud virtual machine, and when a user wants to enhance an existing infrastructure by using Edge intelligence, the virtual machine is often used as the IoT Edge device;
s4, creating a Container Registry for rapidly generating, pushing and running a Docker Container image in a native mode;
preferably, the creating Container Registry selects "creating resource", enters "Container Registry" in the search filter of "new" tab or "Container Registry" in english, enters values in "Registry name" and "resource group", the Registry name must be unique in it and contains alphanumeric characters;
s5, deploying a COAP Module, configured to receive COAP data uploaded by the IoT device, forward the COAP data to the IoT Hub, and extract an unprocessed message in a cloud message queue according to a device ID in a COAP packet and forward the message to the IoT Edge device;
preferably, a docker and a Visual Stdio Code are installed on a compiling computer, a responsibility device of a modification module is a copodule, the copodule appears in a local docker after compiling, an image which can be pushed to your acr is marked through a docker tag command, the user and the acr are logged in, the local image is pushed to the acr of the user through the docker push, and the image can be seen to be in the acr of the user after the portal is opened;
s6, using the COAP Module in an IoT Edge device, and managing the equipment of the COAP protocol through the cloud interface;
in the step S3, installing an IoT Edge Runtime on the IoT Edge Host, where the operating environment of the IoT Edge Runtime is a Windows and/or Linux system;
the initial installation is completed, only one edgeAgent module is provided, the phenomenon is normal, and other modules are installed by the edgeAgent;
the IoT Edge module is an execution unit, is realized in a way of Docker compatible containers, and runs service logic at the Edge; preferably, a plurality of modules are configured to communicate with each other, creating a data processing pipeline; preferably, custom modules are developed or certain services are packaged into modules, providing insight at the edge in an offline fashion;
in the step S4, in the method for creating a Container Registry, the method for quickly generating includes: a registry name and a set of resources are entered, the registry name being unique among them and containing alphanumeric characters.
In the step S5, the method for deploying the COAP Module includes: installing a Docker and a Visual Stdio Code on a local compiling computer, wherein the Docker of the local compiling computer generates a COAP Module after compiling and deploying;
the IoT Edge module is an execution unit, is realized in a way of Docker compatible containers, and runs service logic at the Edge; preferably, a plurality of modules are configured to communicate with each other, creating a data processing pipeline; preferably, custom modules are developed or certain services are packaged into modules to provide insights at the edge in an offline fashion.
In the step S6, the method for using the COAP Module in the IoT Edge device includes: the IoT Edge equipment runs a COAP Module and an Edge Hub, uploads COAP data to an IoT Edge Host port, and monitors the data received by the IoT Hub;
the cloud interface has difficulty managing the software lifecycle of millions of IoT devices, which are often of different brands and models, or are geographically dispersed. Workloads are created and configured for a particular type of device, deployed to all devices, and monitored to capture any behavioural anomalies of the device. These activities cannot be done on a device-by-device basis and must be performed on a large scale; referring to FIG. 2 of the drawings, a cloud service allows:
(1) creating and configuring a workload running on a particular type of device;
(2) sending a workload to a set of devices;
(3) monitoring a workload running on a field device;
preferably, an IoT Hub- > IoT Edge device- > setting module is clicked, after deployment is started, the edgeAgent runs, and for a short while, when the linux shell runs the sudo iotridge list, it can be seen that both the coapmode and the Edge Hub are already running, the page is refreshed after the coapmode and the edgeHub are running, the simulation IoT device uploads COAP data to a port 1209 of the IoT Edge Host, data received by the IoT Hub is monitored, and the device can upload data to the IoT Edge device through the COAP device and can receive the data on the IoT Hub.
Compared with the prior art, the invention has the beneficial effects that: the existing COAP protocol equipment is deployed to the cloud, the problem that the traditional IoT equipment is difficult to arrange to the cloud is solved, the cost of data storage and equipment management is saved, the safety is improved, and the development pace of the technology of the Internet of things is kept up.
So far, the technical solutions of the present invention have been described in connection with the preferred embodiments shown in the drawings, but it is easily understood by those skilled in the art that the scope of the present invention is obviously not limited to these specific embodiments. Equivalent changes or substitutions of related technical features can be made by those skilled in the art without departing from the principle of the invention, and the technical scheme after the changes or substitutions can fall into the protection scope of the invention.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention; various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (3)
1. A method for supporting a COAP device by a cloud service platform is characterized by comprising the following steps:
s1, creating an IoT Hub, and selecting project quota to support an IoT Edge device in an IoT center, wherein the IoT center comprises: a base layer, a standard layer; wherein the base layer enables telemetry from device to cloud, per-device authentication, message routing and event grid integration, device provisioning services, and monitoring and diagnostics; the standard layer enables cloud-to-device messaging, device twinning, module twinning, and device management, and IoT Edge support;
s2, creating the IoT Edge device supported by the IoT center quota project;
wherein the IoT Edge device includes three components:
IoT Edge module: the system is used for running services, third-party services and user-defined codes; deploying an IoT Edge module to an IoT Edge device to execute in a local manner;
IoT Edge Runtime: means for running on and managing deployments to each IoT Edge device;
cloud interface: for remotely monitoring and managing the IoT Edge device through a cloud interface;
s3, deploying an IoT Edge Host, installing the IoT Edge Runtime on the IoT Edge Host, and configuring and connecting to the Iot Edge device to monitor a COAP Module port of the IoT Edge device;
s4, creating a Container Registry for rapidly generating, pushing and running a Docker Container image in a native mode;
s5, deploying a COPA Module, and receiving COAP data uploaded by an IoT device, forwarding the COAP data to the IoT Hub, and extracting unprocessed messages in a cloud message queue according to a device ID in a COAP data packet and forwarding the unprocessed messages to the IoT Edge device;
s6, using the COPA Module in an IoT Edge device, and managing the COAP device through the cloud interface;
in the step S3, installing an IoT Edge Runtime on the IoT Edge Host, where the operating environment of the IoT Edge Runtime is a Windows and/or Linux system;
in the step S4, in the method for creating a Container Registry, the method for quickly generating includes: a registry name and a set of resources are entered, the registry name being unique among them and containing alphanumeric characters.
2. The method according to claim 1, wherein in the step of S5, the method for deploying the COAP Module comprises: and installing a Docker and a Visual Stdio Code on the local compiling computer, wherein the Docker of the local compiling computer generates a COAP Module after compiling.
3. The method of claim 1, wherein in the step of S6, the method for using the COAP Module in the IoT Edge device comprises: the IoT Edge device runs the COAP Module and the Edge Hub, uploads COAP data to an IoT Edge Host port, and monitors the data received by the IoT Hub.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011499256.3A CN112261066A (en) | 2020-12-18 | 2020-12-18 | Method for supporting COAP (chip on Board) equipment by cloud service platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011499256.3A CN112261066A (en) | 2020-12-18 | 2020-12-18 | Method for supporting COAP (chip on Board) equipment by cloud service platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112261066A true CN112261066A (en) | 2021-01-22 |
Family
ID=74225021
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011499256.3A Pending CN112261066A (en) | 2020-12-18 | 2020-12-18 | Method for supporting COAP (chip on Board) equipment by cloud service platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112261066A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113114482A (en) * | 2021-03-08 | 2021-07-13 | 中国—东盟信息港股份有限公司 | Container-based hybrid cloud management system and method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020123179A1 (en) * | 2018-12-13 | 2020-06-18 | Microsoft Technology Licensing, Llc | INTERNET OF THINGS (lOT) DEVICE AND SOLUTION CERTIFICATION AS A SERVICE |
| CN112073417A (en) * | 2020-09-09 | 2020-12-11 | 德明通讯（上海）有限责任公司 | Method and system for accessing Internet of things equipment to Microsoft cloud |
-
2020
- 2020-12-18 CN CN202011499256.3A patent/CN112261066A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020123179A1 (en) * | 2018-12-13 | 2020-06-18 | Microsoft Technology Licensing, Llc | INTERNET OF THINGS (lOT) DEVICE AND SOLUTION CERTIFICATION AS A SERVICE |
| CN112073417A (en) * | 2020-09-09 | 2020-12-11 | 德明通讯（上海）有限责任公司 | Method and system for accessing Internet of things equipment to Microsoft cloud |
Non-Patent Citations (5)
| Title |
|---|
| MICROSOFT: ""Microsoft Azure IoT Reference Architecture"", 《HTTPS://DOCS.MICROSOFT.COM/EN-US/ARCHIVE/BLOGS/WRIJU/AZURE-IOT-REFERENCE-ARCHITECTURE》 * |
| 网友: ""Azure IoT Edge入门(1)-(3)"", 《HTTPS://WWW.CNBLOGS.COM/SHUZHENYU/P/12358747.HTML》 * |
| 网友: ""Creating and Configuring Azure IoT Hub"", 《HTTPS://JOHNADALI.COM/2020/02/22/CREATING-AND-CONFIGURING-AZURE-IOT-HUB/》 * |
| 网友: ""Does the Azure IoT Hub support the CoAP protocol"", 《HTTPS://STACKOVERFLOW.COM/QUESTIONS/40993836/DOES-THE-AZURE-IOT-HUB-SUPPORT-THE-COAP-PROTOCOL/41012679#41012679》 * |
| 网友: ""Sending/Receiving CoAP Requests In Cloud(or Azure IoT HUB)"", 《HTTPS://STACKOVERFLOW.COM/QUESTIONS/42171578/SENDING-RECEIVING-COAP-REQUESTS-IN-CLOUD-OR-AZURE-IOT-HUB/42198126#42198126》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113114482A (en) * | 2021-03-08 | 2021-07-13 | 中国—东盟信息港股份有限公司 | Container-based hybrid cloud management system and method |
| CN113114482B (en) * | 2021-03-08 | 2022-06-14 | 中国—东盟信息港股份有限公司 | Container-based hybrid cloud management system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112799789B (en) | Node cluster management method, device, equipment and storage medium | |
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| CN109245931B (en) | Log management and monitoring alarm realization method of container cloud platform based on kubernets | |
| US10379842B2 (en) | Edge computing platform | |
| US11704577B1 (en) | High performance machine learning inference framework for edge devices | |
| US10382294B2 (en) | Platform for capturing, processing, storing, and presentation of generic sensor data from remote arbitrary locations | |
| CN105934916B (en) | Orchestrating and managing services to deployed devices | |
| CN101099345B (en) | Interpreting an application message at a network element using sampling and heuristics | |
| WO2017172454A1 (en) | System interaction monitoring and component scaling | |
| CN104160376A (en) | Offline provisioning of virtual machines | |
| Romero-Gázquez et al. | Software architecture solution based on SDN for an industrial IoT scenario | |
| US20220006854A1 (en) | Microservice manager and optimizer | |
| CN103490941A (en) | Real-time monitoring on-line configuration method in cloud computing environment | |
| US10931513B2 (en) | Event-triggered distributed data collection in a distributed transaction monitoring system | |
| US10650079B2 (en) | Resource cache classification using machine learning | |
| US20200293310A1 (en) | Software development tool integration and monitoring | |
| CN111966465B (en) | Method, system, equipment and medium for modifying host configuration parameters in real time | |
| US11265693B2 (en) | System of actions for IoT devices | |
| CN110377590A (en) | Data collection system, method and computer readable storage medium based on Internet of Things | |
| CN109361525A (en) | Restart method, apparatus, controlling terminal and medium that distributed deployment services more | |
| US10489179B1 (en) | Virtual machine instance data aggregation based on work definition metadata | |
| CN116055524A (en) | Interaction method, processor and device for Internet platform and Internet of things equipment | |
| CN116915827A (en) | Data transmission method and device of internet of things edge gateway, electronic equipment and medium | |
| CN111984505A (en) | Operation and maintenance data acquisition engine and acquisition method | |
| CN112261066A (en) | Method for supporting COAP (chip on Board) equipment by cloud service platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210122 |