Service Profile
Overview
At present, OneNET supports MQTT, EDP, NBIOT, MODBUS and HTTP, but has yet to provide support for access to other protocol types, such as the fire protection agreement GB/T 26875.3-2011. In smart home scenarios, there are near field communication devices based on ZIGBEE or Bluetooth, which cannot be directly connected to OneNET at present. At this time, OneNET Protocol Gateway can quickly realize device access (without direct access to the OneNET platform), and build a two-way data channel between the device and the OneNET platform.
Scenarios
Devices only support specific protocols, which are not supported by OneNET.
Due to hardware resource limitations, devices cannot directly connect to the OneNET platform.
Devices which are equipped with non-TCP or UDP protocols cannot directly connect to the OneNET platform.
For devices which have been integrated into user's private service, the user wants to connect them to the OneNET platform without modifying the firmware.
Iot Protocol Gateway Notes
OneNET Protocol Gateway enables user-defined protocol devices to access the OneNET platform, and realizes two-way communication between the devices and the platform. Its architecture is shown in the following figure:
Terms in the figure are explained as follows:
| Term | Description |
|---|---|
| Device | User (custom private protocol) device |
| IoT Protocol Gateway | Gateway for short, which connects user device to OneNET applications. |
| ACC Service | OneNET MQTT access service |
| Custom Service | Connect the Gateway to user private service |
Legends
Blue rectangles in the figure indicate the internal modules of the Protocol Gateway, including solid blue rectangles representing an internal gateway that doesn’t require secondary development, and dashed blue rectangles representing a gateway that provides module interface and default implementation, and developers can choose to implement the interface function as needed.
Gray rectangles in the figure indicate protocol conversion and user extension modules, including solid gray rectangles that developers must implement, and dotted gray rectangles that can be selectively added as needed.
Core Modules
Protocol Hub: establishes connection and data communication between device and Gateway, and supports multiple communication protocols (currently supports only TCP).
Custom Protocol Encoder/Decoder: a user-defined protocol codec module that provides translation between data in device user-defined protocol format and gateway data.
Gateway Manager: a gateway management module, where:
Config: a gateway parameter and device configuration module that is responsible for reading gateway instance related configuration and OneNET device information, and provides a default implementation for reading through configuration files.
Session Manager: a Session management module for devices and connections that is responsible for managing the relations between device and Gateway and between device and Channel, etc.
Gateway Data Transformer & Handler: a gateway data conversion and processing module that provides translation and processing between internal gateway data and data in MQTT protocol format.
MQTT Adaptor: responsible for MQTT codec, and connection and data communication between Gateway and OneNET MQTT access service.
Extension Modules
Security & Policy: a security and policy module for device authentication and authority management; Logging: a log module to print gateway service running logs; Metric: a performance statistics module to output gateway service running status and performance statistics;
Custom Channel Handlers: Custom Channel Handlers, which can be added to realize custom functions;
Data Cache & Distributuion: a data cache and distribution module which provides extended functions such as data caching and reading;
CMD Data Processor: a command data processing module which provides extended functions such as offline command caching and processing;
API: an API module which provides OneNET API SDK by default to extend more custom functions.