Multiprotocol Access Product Introduction

Profile Architecture Resource model Protocol applications Definitions

QuickStart

Account and Login

Account Registration Account Authentication

Products and Devices

Create Product Create single device Create devices in batch Export devices in batch

Data Stream and Data Point

User Guide

Rule Engine

Service Introduction Rule Configuration Basic Data Format SQL

HTTP push

Service Introduction Service configuration Development Guide SDK

Security Authentication

Overview token Algorithm Algorithm Examples

Application Management

Service Introduction Controls Introduction Operating Instructions

Development Guide

EDP

Device

Files and tools Protocol introduction Development Process FAQ

API

API Usage SDK API list

New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Upload file Get file Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey

TCP transparent transmission

Device

Files and tools Protocol introduction Development Process

API

API Usage SDK API List

New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload data point Upload file Get file Send command Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey

MQTT

Device

Files and tools Protocol introduction Development Process FAQ

API

API Usage SDK API List

New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Delete device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload data point Upload file Get file Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey Publish message Query subscription topic equipment Query device subscription topic Query product topic

Modbus

Device

Files and tools Protocol introduction Development Process

API

API Usage SDK API List

New device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Send command Query command status Query command response Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey

HTTP

API Usage SDK List of Protocol Interfaces

New device Register Device Update device Query device details Query device details in batch Query device statuses in batch Remove Device New data stream Update data stream Query data stream Query data stream in batch Delete data stream Query device history data Query device data in batch Upload Data Points Upload file Get file Query device history command New trigger Update trigger Query trigger Delete trigger Add apikey Update apikey Query apikey Delete apikey

FAQ

List of Platform Addresses Technology category Business category OCP category

Architecture

The architecture of the multiprotocol access product is shown in the figure below:

Device access

OneNET provides secure and stable device access services, and supports a variety of protocols such as MQTT, Modbus, HTTP and TCP.

In industrial modbus communication scenarios, it is recommended to use the DTU+Modbus protocol for access.
In scenarios involving real-time communication with the device, it is recommended to use the MQTT protocol for access.
In scenarios of data reporting only, the HTTP/HTTPS protocol can be used for access.
In custom protocol access scenarios, it is recommended to use the TCP + script for access.

For details, refer to the “Development Guide” of the device.

Device management

In response to different application scenarios, the OneNET platform has a variety of device management functions, e.g. lifecycle management, online status monitoring, online debugging, and data management.

For details, refer to the “Introduction” manual.

API

OneNET provides a variety of HTTP/HTTPS-based open API interfaces, which can be used for device management, data query, device command interaction and other operations. Users can also build applications at upper levels based on personalized needs.

HTTP push

With regard to some scenarios involving high real-time requirements, OneNET has a function of data push, to filter out the data that is frequently and periodically reported by the device and push the real-time data that users care about through the HTTP/HTTPS to users’ application servers.

For details, please refer to HTTP Push.

Security authentication

OneNET has an authentication mechanism for user resource access security, product-level and device-level keys with different granularities, and supports user-defined key access permissions, thus maximizing the security of access to user devices and applications.

For details, please refer to the Security Authentication.

Application incubation environment

Provide users with simple application generation tools to rapidly generate simple applications.

个搜索结果，搜索内容 “”

0 个搜索结果，搜索内容 “”