Overview of JD Smart IoT System Architecture and JOYLINK Protocol

JD's Smart IoT system consists of a central core that links cloud, mobile, and smart devices, offering modular hardware options such as networking, compute, audio, and vision modules; the cloud side provides IoT Hub, IFTTT engine, streaming, voice, and machine‑vision services.

The core connects to third‑party systems and products via direct core access, third‑party cloud, or JD's private SaaS platform.

Device access methods include direct core connection, REST API with optional SDKs, AI control endpoints, and SaaS platform integration; smart devices maintain long‑lived TCP/IP connections, while controllers typically use short‑lived HTTPS with an auxiliary push channel.

All device discovery, control, OTA, and status updates are implemented through JD's JOYLINK SDK, with documentation and open‑source code available at https://smartdev.jd.com/docCenterDoc/index.

The supporting system comprises seven major components: Products Dev (hardware development platform), Products Manager (product lifecycle management), Ops (core operation platform), DA/AI (data analysis and AI), Dev tools (debugging and scripting), Application Manager (scene scripts and apps), and System Set (configuration and permission control).

JOYLINK is the application‑layer protocol for the IoT system, with versions 2.0 (byte‑coded for compact packets) and 3.0 (JSON‑based for flexibility). It runs over TCP/IP and provides gateway mapping for non‑IP devices, supporting wireless (KNX, ZigBee, BLE) and wired (NB‑IoT, Wi‑Fi) connections.

Device provisioning for Wi‑Fi devices includes one‑key configuration (using multicast address or packet length encoding), SoftAP, thunderConfig, and BLE‑assisted methods, each with specific encoding and security considerations.

Security relies on certificate‑based authentication, device private keys stored in secure chips, ECDH P256 key exchange, and AES‑128 symmetric encryption for normal communication.

Service discovery and message routing use device‑registered functions and tags, supporting both active declaration and passive query, with a registration mechanism for application‑layer messages.

Long‑connection maintenance uses periodic heartbeats (≈35 s interval). Direct device‑to‑cloud heartbeats scale with device count, while a gateway‑proxy approach reduces traffic to a single heartbeat per interval.

Standardized services provide mandatory and optional function sets for devices, with script‑based or registration‑based command mapping, and an IFTTT engine that parses scripts, monitors events, analyzes logic, and executes actions.

The platform is highly open: mobile SDKs cover device configuration, authorization, control, sharing, scenes, and dynamic pages; device side offers networking, audio, vision, and gateway modules; cloud side provides HTTPS control, status, permission APIs, and natural‑language voice interfaces.

Detailed documentation can be downloaded from the original source.