How OceanConnect IoT Platform Handles Immediate, Cached, and Batch Commands

OceanConnect Command Delivery Mechanisms

Today we discuss how the Huawei OceanConnect IoT platform implements its command issuance mechanisms.

Two Command Issuance Modes

Immediate Issuance : The command is sent instantly; if the device is offline or does not receive the command, the issuance fails. This mode suits scenarios requiring real‑time command execution, such as turning street lights on/off or opening gas valve shutters. The application must ensure the timing of issuance.

Cached Issuance : The platform stores the command in a queue after receipt. When the device comes online, the platform sequentially delivers the queued commands. This mode is appropriate for scenarios with less stringent real‑time requirements, like configuring water‑meter parameters.

The platform also supports an expireTime (TTL) parameter when sending commands to the IoT management platform:

expireTime=0: Immediate issuance.

expireTime>0: Cached issuance.

Command Flow Diagrams

Immediate command issuance flow:

DRX/eDRX mode command issuance flow:

PSM mode command issuance flow:

Batch Command Issuance

The platform also supports batch command issuance, which is a cached command feature useful for controlling multiple devices simultaneously. Five batch command types are available:

DeviceList – send commands based on a device list.

DeviceType – send commands based on device type.

DeviceArea – send commands based on geographic area.

GroupList – send commands based on device groups.

Broadcast – broadcast commands to all devices.

Implementation diagram for batch commands:

Detailed module functions for batch command issuance:

Key point: Batch command issuance uses the cached command mechanism, linking it to the platform's cached delivery feature.

That concludes today’s five‑minute tutorial. Stay tuned after the holidays for more practical NB‑IoT application insights.