Chapter 4
Standard: JT/T 808-2013

Business Process

Terminal registration (0x0100), authentication (0x0102), periodic location reporting (0x0200), and OTA firmware upgrade.

Business Process

4.1 Terminal Registration
#

The complete business interaction flow for terminal installation and platform registration is depicted in Fig. 1:

Fig. 1: Business Flowchart of Terminal Registration
text
  โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”                         โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
  โ”‚   OBD Terminal Device    โ”‚                         โ”‚     Platform Server      โ”‚
  โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜                         โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
               โ”‚                                                    โ”‚
               โ”‚  (1) Request registration with device info         โ”‚
               โ”‚      (Message: 0x0100 Terminal Registration)       โ”‚
               โ”‚โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€>โ”‚
               โ”‚                                                    โ”‚
               โ”‚                                                    โ”‚  (2) Device registration
               โ”‚                                                    โ”‚      & Auth Key generation
               โ”‚                                                    โ”‚
               โ”‚  (3) Return base key (authentication key)          โ”‚
               โ”‚      (Message: 0x8100 Registration Response)       โ”‚
               โ”‚<โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”‚
               โ”‚                                                    โ”‚
               โ”‚  (4) Store base key permanently in FLASH           โ”‚
               โ”‚  (Used for 0x0102 Login Authentication)            โ”‚
               โ”‚                                                    โ”‚

Registration Workflow Steps:

1
Step 1 โ€” Registration Request: The terminal carries device credentials (Province ID, City ID, Manufacturer ID, Model, Terminal ID, License Plate Color & Number) and transmits 0x0100 to the platform.
2
Step 2 โ€” Platform Verification: The platform validates the terminal identity against its database, generates an authentication base key, and issues 0x8100 containing the token.
3
Step 3 โ€” Permanent Key Storage: The returned authentication token is permanently saved in the terminal's on-board non-volatile FLASH memory.

4.2 Firmware Upgrade (FOTA)
#

The platform initiates remote firmware upgrades via message 0x8108. When receiving the upgrade notification:

1
The terminal switches to the designated FTP/HTTP server and inspects the remote firmware build version.
2
If the current firmware build is identical to that recorded on the server, the upgrade is skipped.
3
If the remote build is newer, the firmware binary is downloaded automatically and flashed into memory.

4.3 Data Reporting
#

NOTE: Critical vehicle information and unsent telemetry acquired by the terminal will be safely buffered in FLASH memory during the upgrade process and uploaded to the platform server once the upgrade and reboot are complete.
1
Step 1 โ€” Login Authentication: The terminal establishes a TCP/UDP socket with the platform and immediately submits its stored authentication base key (0x0102).
2
Step 2 โ€” Regular Encrypted Telemetry: Once authenticated, the terminal commences periodic transmission of location information (0x0200), OBD telemetry data stream (0x0900), and alarms.