How OceanConnect DMP Boosts IoT Device Integration, Security, and Power Savings

Device Access

The platform supports three ways to connect devices: direct protocol access, Agent access, and cloud‑gateway access.

Through the Cloud Inter‑Networking Gateway (CIG), heterogeneous southbound protocols are converted into a unified format that the platform can process via its service bus.

Supported native protocols include LWM2M over CoAP (ideal for NB‑IoT scenarios with low power, low cost, and wide coverage) and MQTT/MQTTS (suitable for low‑bandwidth remote sensors).

Device protocol direct access

Agent access (Agent Lite, Agent Tiny, Agent Rich)

Cloud‑gateway access

Agent Lite

A lightweight gateway that enables direct devices to quickly join the platform, supporting data reporting and command issuance, with multi‑language SDKs (C, Java, Python).

Agent Tiny

A minimal middleware for severely resource‑constrained NB‑IoT modules, allowing rapid device onboarding and data exchange via simple API calls.

Agent Rich

A full‑featured gateway that parses data locally and supports various short‑range wireless protocols (Z‑Wave, ZigBee, Wi‑Fi, Bluetooth).

Northbound API

OceanConnect exposes more than 170 RESTful northbound APIs for third‑party developers, covering device management (CRUD), data collection, command issuance, and message push.

Applications register via the SP Portal to obtain an APP ID and secret, which are used for secure API authentication over HTTPS.

NB‑IoT Power‑Saving Service (DTLS+)

DTLS+ is an optimized Datagram Transport Layer Security protocol that reduces handshake messages, lowering NB‑IoT device power consumption.

In NAT scenarios, frequent IP/port changes force full DTLS renegotiation, increasing power usage; DTLS+ mitigates this by reusing session context based on the five‑tuple.

Compared with standard DTLS, DTLS+ can cut device power consumption by up to 50% and reduce network traffic, improving carrier capacity.

PSM/DRX/eDRX Mode Management

NB‑IoT devices can select among three power‑saving modes based on power source and latency requirements:

PSM : Deep sleep when idle; device only receives downlink data after it initiates uplink transmission.

DRX : Discontinuous reception with short cycles, allowing near‑real‑time downlink for latency‑critical applications.

eDRX : Extended DRX with a paging time window, balancing low power and moderate latency.

The platform cannot directly read device power‑mode from the network, so it must be configured in the IoT platform to adjust downlink scheduling and retransmission strategies.

State transitions among Idle, Connected, and PSM are illustrated below.