JT/T 808 protocol cloud gateways connect devices to IoT Platform over TCP or TLS using the JT/T 808-2019 protocol. TLS is recommended for higher security and supports one-way authentication, OCSP, and bidirectional secure connections.
Regions and instances
JT/T 808 protocol cloud gateways are available only for Exclusive Enterprise Edition instances in the China (Shanghai) regions.
Features
Gateway features
|
Feature |
Description |
|
Custom port numbers |
Default port: 7999. Custom port range: 1024 to 65535. |
|
One-party authentication |
IoT Platform manages device registration, authentication, and unregistration. Create a one-party authentication cloud gateway product, import devices in batches, and register them over the JT/T 808 protocol to connect. |
|
Third-party authentication |
The developer manages device registration, authentication, and unregistration through FC functions and grants IoT Platform permission to call them. Create FC functions for device authentication, then create a third-party authentication cloud gateway product and authorize IoT Platform to call those functions. IoT Platform uses them to automatically create and connect devices. |
|
Transport protocol |
Supports TCP and TLS. Do not use TCP over the public network. Use a leased line for TCP connections. |
|
X.509-based device authentication |
Supports server-side one-way and bidirectional authentication to verify device identities. |
|
SM certificate |
When a device uses TLS protocol version 1.3, it supports SM certificates. It also supports the SM2, SM3, and SM4 Chinese cryptographic algorithms and the SM SSL security protocol. Note Only single SM certificates and the TLS_SM4_GCM_SM3 and TLS_SM4_CCM_SM3 cipher suites are supported. Dual SM certificates (TLCP protocol) are not supported. |
|
OCSP |
Supports OCSP for device and server certificates. |
Connection and communication over the JT/T 808 protocol
Devices connect to and communicate with IoT Platform using the standard JT/T 808 data format.
The default connection timeout is 180 seconds. IoT Platform disconnects a device if no data or heartbeat is received within this period.
The following table lists supported messages from the JT/T 808-2019 protocol.
|
Message |
Message type |
|
Terminal general acknowledgement |
0x0001 |
|
Platform general acknowledgement |
0x8001 |
|
Terminal heartbeat |
0x0002 |
|
Terminal registration |
0x0100 |
|
Terminal registration acknowledgement |
0x8100 |
|
Terminal unregistration |
0x0003 |
|
Terminal authentication |
0x0102 |
|
Downlink data pass-through |
0x8900 |
|
Uplink data pass-through |
0x0900 |
|
Location information report |
0x0200 |
|
Batch location data upload |
0x0704 |
Device connection setup
One-party authentication
-
Create a JT/T 808 protocol cloud gateway product. Set Authentication Type to One-party Authentication and configure other parameters as needed.
-
Create a JT/T 808 protocol cloud gateway device. Import devices in batches with the Manufacturer ID, Terminal Model, and Terminal ID.
IoT Platform concatenates the uploaded Manufacturer ID, Terminal Model, and Terminal ID values to create a device name in the format of
${Manufacturer ID}_${Terminal Model}_${Terminal ID}. -
Configure the cloud gateway access domain name on the device:
-
If a device has a configured endpoint, create a CNAME record that maps its hostname to the cloud gateway URL. For more information about DNS configuration, see Alibaba Cloud DNS.
-
If a device has no configured endpoint, set the cloud gateway URL as its endpoint.
-
-
(Optional) Configure the rules engine to forward device messages to your server.
Third-party authentication
-
Create an FC service and create an FC function for third-party device authentication.
The FC authentication function's request and response parameters must comply with the specifications defined in Create an MQTT protocol cloud gateway product. You can specify a custom function name.
-
Create a JT/T 808 protocol cloud gateway product. Set Authentication Type to Third-party Authentication, select the FC service and function you created for Device Authentication FC Service and Device Authentication FC Function, and configure other parameters as needed.
-
After the product is created, IoT Platform automatically creates and authenticates a device on its first connection. The device name concatenates the manufacturer, deviceModel, and deviceId request parameters from the FC authentication function, using the format
${manufacturer}_${deviceModel}_${deviceId}. -
(Optional) Configure the rules engine to forward device messages to your server.
Connection flow
The following figures show the device connection flow. Upstream and downstream messaging is covered in the Message communication section.
One-party authentication
Third-party authentication
Message communication
Cloud gateway devices communicate with IoT Platform using the standard JT/T 808-2019 protocol.
Upstream communication: device to server
Forward device registration, unregistration, and data messages to your server through the rules engine's data forwarding or AMQP subscription features.
Configure rules in Message forwarding.
Downstream communication: server to device
Call the RRpc API operation to send a message to a device and receive a synchronous response.