Skip to content

Servers

DMS — Device Management Server

Multi-tenant tracker management with model-targeted firmware jobs, configuration and diagnostics — now including the CMS custom family behind CM107 and CM212, plus central A-GPS assistance.

CMS customModel-targeted OTAA-GPSMulti-tenantFirmware and receiver compatibility required

DMS manages tracker connections, firmware assignments, configuration jobs and device diagnostics across a hierarchy of customer groups. Background jobs expose progress, acknowledgements, cancellation and per-device results. Formerly FCOTA.

The CMS custom family, shown as CMS CUS, supports CM107 (TVC107 hardware) and CM212 (TBC212 / TBC2x2 hardware). Check-ins distinguish the underlying model and report installed application version, SIM identity, modem version when available and update progress. Firmware selection retains model guards; a new product name does not make packages interchangeable.

CMS application downloads are verified and staged before a separate installation command. Configuration and supported command jobs use the same device connection with acknowledgement matching. Phone access keys and private location-data keys belong in their protected provisioning flows.

A separate A-GPS service refreshes and serves centrally cached GPS/BeiDou assistance for supported CC1167Q receiver builds. Trackers fetch assistance without registering an IMEI or customer key. Receiver compatibility matters; assistance does not guarantee a fix or a particular acquisition time.

Provisioned Level 3 trackers suppress ordinary IMEI/ICCID DMS registration and block the normal plaintext management interface. Customer-owned configuration and commands use the encrypted vault route; DMS is not a way to bypass that privacy boundary.

Meet CM107 and CM212

Compare model I/O, Track mode, Bluetooth controls, encryption, licensing and current firmware validation.

Explore Code Monkey trackers →

Features

  • CMS custom / CMS CUS device family for CM107 and CM212, alongside existing ATIOT, Vital and IOTNET families
  • Model-aware firmware targeting for TVC107 and TBC2x2 hardware, retaining package compatibility checks
  • Application, modem/boot and configuration updates where supported by the selected device family
  • CMS application download, verification, staged-ready status and separate install request
  • Bulk firmware assignment with per-device skipped, failed and completed results
  • Background firmware/configuration jobs with progress, acknowledgement matching and cancellation
  • Firmware catalogue with versions, SHA-256 hashes and inherited customer-group visibility
  • CMS check-ins showing application version, model, ICCID, update phase and available modem firmware version
  • Supported remote command and configuration dispatch; diagnostic capabilities vary by family
  • Central A-GPS cache with configurable refresh, expiry checks and a dedicated assistance listener
  • A-GPS admin status: cache availability, download/expiry times, hash and last refresh outcome
  • Tracker registration/import, search, friendly names, group moves and device audit trails
  • Browser configuration builder, roles, API keys, billing and live console updates

See DMS — Device Management Server in action

A look inside DMS — Device Management Server. Hover to lift a shot, click to view it full-size.