Appearance
Overview
Intended Audience
This document is intended to be used by software developers, test engineers, and FAEs.
This solution can support
3,000+DVRs and100,000+trackers.
This document aims to guide IoTHub deployment, device integration, push/request API usage, and alarm reference. It enables customers to access device data, push and pull RTMP data streams, as well as upload files, images, and videos.
- Part 1 Overview, describes the target audience, Jimi IoTHub architecture, and terminology, etc.
- Part 2 Installation, describes deployment host requirements, installation procedures, pushURL configuration, etc.
- Part 3 Integration, describes APIs and alarm type reference for different protocol devices
- Part 4 Testing, involves device configuration and testing
- Part 5 Advanced, describes advanced features such as high availability (HA), LBS services,etc.
- Part 6 Help, includes changelog and FAQ
1 Architecture
This solution provides gateway service, API and message-dispatch services, RTMP service, and file storage service.
1.1 Gateway Service(TCP Server)
Devices communicate with the gateway service over TCP. Since devices have been integrated with JIMI and JT/T protocol, they will report device GPS and alarm data, which will be pushed to the customer's SaaS service (customer SaaS) via HTTP after being parsed by gateway service. Then, SaaS services can store and process data on their own needs.
1.2 RTMP Streaming (RTMP Server)
DVR communicates with media server through RTMP. DVR has been integrated with the streaming media SDK to enable it to push video streams to the media server, so customers can play these videos with browser, VLC player or other media players.
1.3 File Storage (HTTP Server)
Devices communicate with the file storage through HTTP. Devices has been integrated with the upload SDK to enable it to upload images and videos to the file storage service, so customers can download these images and videos through browser or other tools.
2 Advantages
This solution provides Gateway, API, RTMP stream, and file storage services. It supports one-click deployment to the system and authorizes customers to perform secondary development. Moreover, it can be implemented faster through joint delegation and testing with devices through simple configuration.
The gateway service is used to manage connections with devices, parse and forward protocol data;
The API service provides HTTP interfaces for sending commands to devices;
The RTMP streaming or media server is used to stream live videos captured by devices;
The file storage is used to store images and videos captured by devices.
This solution can help customers cut spending on:
Researching and developing TCP servers. As the solution can accommodate up to
100,000+connections, and provide connection management services and Netty development;Commissioning protocol interconnected with devices. Because customers only need to provide a service interface to receive the parsed data from devices (online/offline, heartbeat, GPS location data, alerts, etc.);
Commissioning video streams from interconnected devices;
Deploying new file/storage servers. This solution offers file hosting servers to assist customers to store images and videos captured by devices, and allows devices to upload files to customers' existing file servers through configuration.
3 Terms
| Terms | Description |
|---|---|
| PaaS | Platform-as-a-Service |
| SaaS | Software-as-a-Service |
| IaaS | Infrastructure-as-a-Service |
| Docker | Docker is an open platform for developing, shipping, and running applications. |
| DVR | Digital Video Recorder |
| OBS | Open Broadcaster Software |
| RTMP | Real Time Messaging Protocol |
| IMEI | International Mobile Equipment Identity |
| JT/T 808 | Communication protocol release by Ministry of Transport of China |
| JT/T 1078 | Video communication protocol release by Ministry of Transport of China |
4 IoTHub Support Device Model
| Protocol | Device Model | Gateway Port | Command Delivery |
|---|---|---|---|
| CONCOX | JC400 series JC261 series JC200 VL801 VL802 VL103 LL301 VL512 ... | 21100 | SMS/TF card |
| JT/T 1078/808 | JC450, JC181, JC371, JC120, ... | 21122 | Wifikit.apk |
| JT/T 808 | VL502, VG502, ... | 31506 |
Compared with the protocol docking solution, this integrated solution is more suitable for customers who prefer to focus on SaaS rather than TCP connection services, RTMP streaming and file storage.
