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
java python
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

Overview of Rule Engine Services

Rule Engine is the core service that OneNET provides users for data transfer, which enables users to filter and distribute device messages in IoT Suite. In this way, users can customize data filtering rules, convert data formats, and forward data to follow-on products, thus obtaining more services.

Data Source Selection

Rule Engine supports processing and forwarding messages from a product in IoT Suite, and supports processing the following message sources:

  • Device data point message: new data points uploaded by device

  • Device lifecycle event: creation, deletion, online and offline event messages throughout device lifecycle

  • Device image properties update event: device image properties update event message (coming soon)

Message Processing

Rule Engine supports SQL statement-based custom processing rules for json data contents from selected message sources.

At present, the system message source inputs the rule engine according to the system fixed basic message format; users can define SQL editing based on the basic message format for the extraction and restructuring of json data; users can define SQL statement for message handling, as shown in the figure below:

Message Forwarding

Rule Engine supports forwarding customized messages to back-end services. Currently, the back-end services supported are as follows:

  • Message queue (MQ)

    The high-performance and high-availability message middleware is conducive to the stable and efficient application service access to device messages.

  • Short Message Service (SMS)

    Triggers a fixed template SMS containing user-defined parameters

  • Storage Service (coming soon)

    Data storage service based on MySQL database

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

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