RCMS Cellular Data Usage Guide for RobustOS, RobustOS Pro, and EV8100
Package contents, reporting behavior, and approximate monthly cellular data usage
Purpose and scope
This guide brings together the RCMS cellular data usage information for devices running RobustOS, RobustOS Pro, and the EV8100. It explains the approximate monthly usage profiles, the fields included in each package, and when each package is sent.
Estimation assumptions
Figures are approximate and assume an ideal connection without packet loss or additional reconnects. They describe RCMS-related package usage and do not represent all cellular traffic generated by a device or the exact amount billed by a mobile operator. Actual usage may vary with network conditions, reconnects, device configuration, operator session rules, and session rounding.
Why are the estimates different?
RCMS reports different sets of information for devices running RobustOS, RobustOS Pro, and the EV8100. Package types, included fields, and reporting schedules can vary. Some packages are sent periodically, such as Dynamic and Keepalive packages; others are triggered by events, such as a status report after reconnection or a Call package after telephone activity. These differences affect the amount of data sent, so the estimates are specific to each operating system or product.
The EV8100 runs RobustOS Pro and is shown separately because its RCMS reporting includes product-specific information and package types, including Battery and Call. Its Battery Package is sent periodically, while Call Packages are triggered by telephone activity. Static Status and Dynamic packages can also contain different fields across products. For general devices running RobustOS Pro, use the RobustOS Pro figures; for the EV8100, use the EV8100 figures.
About the estimates: Monthly totals are approximate. Package contents and reporting behavior explain why usage can differ, but the available package details do not allow every monthly total to be reproduced exactly.
Monthly usage profiles
The same profile names use the same keepalive, data collection, and data upload intervals across RobustOS, RobustOS Pro, and EV8100. The estimated monthly totals differ by operating system or product.
| Profile | Keepalive interval | Data collection interval | Data upload interval | RobustOS | RobustOS Pro | EV8100 |
|---|---|---|---|---|---|---|
| Default | 600 seconds | 60 minutes | 60 minutes | 3 MB | 3 MB | 3 MB |
| Low usage | 600 seconds | 60 minutes | 60 minutes | 3 MB | 3 MB | 3 MB |
| Medium usage | 300 seconds | 30 minutes | 60 minutes | 5 MB | 5 MB | 6 MB |
| High usage | 60 seconds | 10 minutes | 60 minutes | 16 MB | 18 MB | 23 MB |
Default and Low usage have the same configuration shown above, so their estimates are also the same. The EV8100 monthly estimates include Dynamic, Keepalive, and Battery package traffic. Static Status and Call packages are event-triggered; their frequency depends on reconnects, manual requests, or call activity. GPS reporting follows its own setting.
Package comparison
The table summarizes package sizes and default reporting behavior. A dash means that the package type is not listed for that operating system or product.
| Package | RobustOS | RobustOS Pro | EV8100 |
|---|---|---|---|
| Static Status Report | Approx. 18 KB; sent on RCMS reconnection after reboot or RCMS App restart, and on a manual Full Status Report request | Approx. 9 KB; same listed triggers | Approx. 4.18 KB; same listed triggers |
| Dynamic | Approx. 2 KB; collect/upload every 60 minutes by default | Approx. 2 KB; collect/upload every 60 minutes by default | Approx. 1.63 KB; collect/upload every 60 minutes by default |
| GPS | Approx. 174 bytes; upload every 60 minutes by default | Approx. 174 bytes; upload every 60 minutes by default | Approx. 174 bytes; upload every 60 minutes by default |
| Keepalive | Approx. 182 bytes; every 600 seconds by default | Approx. 224 bytes; every 600 seconds by default | Approx. 350 bytes; every 600 seconds by default |
| Battery | — | — | Approx. 630 bytes; collect/upload every 60 minutes by default |
| Call | — | — | Approx. 2.43 KB per call operation; event-triggered |
Dynamic data collection and upload intervals are configured separately. When the collection interval is shorter than the upload interval, multiple collected samples may be included in a later upload.
Package contents by operating system or product
The tables below list the fields included in the packages for RobustOS, RobustOS Pro, and the EV8100. A package's reporting interval or trigger determines how often its data contributes to usage.
RobustOS
RobustOS is Robustel’s proprietary, Linux-kernel-based router operating system used on Robustel routers and modems. Learn more on the official RobustOS operating system page.
Example compatible products: R1520 Global, R2111, R2120-5G, R3000-Lite, and R5020e. This list is illustrative; check the specific product page and firmware version for exact OS support.
Static Status Report Package
Approximate package size: 18 KB. Uploaded when the device reconnects to RCMS after a reboot or RCMS App restart, and when a user manually selects Update Data for the Full Status Report. It is not a routine periodic update while the device stays connected.
| Section | Fields included |
|---|---|
| System | System time, device board, device model, kernel version, RAM usage, device platform, serial number, firmware version, hardware version, uptime |
| Link 1 | Link, status, IP address/netmask, gateway, DNS, uptime |
| Active link | Active link |
| Cellular | Modem status, current SIM, Reg, registration, Cell ID, operator, network type, PLMN ID, local area code, IMSI, modem model, IMEI, firmware version, ICCID, phone number, band, CSQ, RSRP, RSRQ, CSQ value, ARFCN, TAC, ECIO, SINR, bit error rate |
| LAN | Interface, MTU, MAC address, IP address/netmask, RX bytes, RX packets, TX bytes, TX packets |
| Route 1 | Destination, netmask, gateway, interface, metric |
| Dynamic status | CPU |
| Wi-Fi status | Mode, region, enable, AP frequency, bandwidth, channel, SSID, broadcast SSID, status, MAC address, security mode, band, clients |
| Wi-Fi client status | Channel, SSID, broadcast SSID |
Dynamic Package
Approximate package size: 2 KB. Default data collection and upload intervals are both 60 minutes. The source says these are configured in the Data Report feature under Remote Action.
| Section | Fields included |
|---|---|
| SIM / cellular | TX bytes, RX bytes, daily TX bytes, daily RX bytes, delay time, CSQ value, ARFCN, bit error rate, SINR, ECIO, RSRQ, RSRP, CSQ, active link, link uptime, IP address, band, network type, Reg, registration, PLMN ID, Cell ID, local area code, TAC, operator |
| WAN | TX bytes, RX bytes, daily TX bytes, daily RX bytes, delay time |
| WLAN | TX bytes, RX bytes, daily TX bytes, daily RX bytes |
GPS Package
Approximate package size: 174 bytes. Default upload interval: 60 minutes.
| Section | Fields included |
|---|---|
| GPS | Longitude, latitude |
Keepalive Package
Approximate package size: 182 bytes. Sent at the configured Keepalive value, which defaults to 600 seconds (10 minutes).
| Section | Fields included |
|---|---|
| Ping | Ping package |
RobustOS Pro
RobustOS Pro is Robustel’s Debian-based operating system for edge gateways. Learn more on the official RobustOS Pro operating system page.
Example compatible products: EG3120e, EG5100, EG5101, EG5120, EG5200, LG5100, and LG5120. This list is illustrative; check the specific product page and firmware version for exact OS support.
Static Status Report Package
Approximate package size: 9 KB. Uploaded when the device reconnects to RCMS after a reboot or RCMS App restart, and when a user manually selects Update Data for the Full Status Report. It is not a routine periodic update while the device stays connected.
| Section | Fields included |
|---|---|
| System | System time, device board, device model, kernel version, RAM usage, device platform, serial number, firmware version, hardware version, uptime |
| Active link | Active link |
| Cellular | Modem status, current SIM, Reg, registration, Cell ID, operator, network type, PLMN ID, local area code, IMSI, modem model, IMEI, firmware version, ICCID, phone number, band, CSQ, RSRP, RSRQ, CSQ value, ARFCN, TAC, ECIO, SINR, bit error rate |
| LAN | Interface, MTU, MAC address, IP address/netmask, RX bytes, RX packets, TX bytes, TX packets |
| Route 1 | Destination, netmask, gateway, interface, metric |
| Dynamic status | CPU |
| Wi-Fi status | Mode, region, enable, AP frequency, bandwidth, channel, SSID, broadcast SSID, status, MAC address, security mode, band, clients |
| Wi-Fi client status | Channel, SSID, broadcast SSID |
Dynamic Package
Approximate package size: 2 KB. Default data collection and upload intervals are both 60 minutes. The source says these are configured in the Data Report feature under Remote Action.
| Section | Fields included |
|---|---|
| SIM / cellular | TX bytes, RX bytes, daily TX bytes, daily RX bytes, delay time, CSQ value, ARFCN, bit error rate, SINR, ECIO, RSRQ, RSRP, CSQ, active link, link uptime, IP address, band, network type, Reg, registration, PLMN ID, Cell ID, local area code, TAC, operator |
| WAN | TX bytes, RX bytes, daily TX bytes, daily RX bytes, delay time |
| WLAN | TX bytes, RX bytes, daily TX bytes, daily RX bytes |
GPS Package
Approximate package size: 174 bytes. Default upload interval: 60 minutes.
| Section | Fields included |
|---|---|
| GPS | Longitude, latitude |
Keepalive Package
Approximate package size: 224 bytes. Sent at the configured Keepalive value, which defaults to 600 seconds (10 minutes).
| Section | Fields included |
|---|---|
| Ping | Ping package |
EV8100 (RobustOS Pro)
The Robustel EV8100 is an industrial 4G/LTE VoIP gateway that connects analogue voice equipment to IP-based voice networks. It is designed for applications such as elevator emergency phones, intercoms, and alarm panels.
The EV8100 runs RobustOS Pro. The package sizes and fields below apply to the EV8100.
For product specifications and downloads, visit the official EV8100 product page.
Static Status Report Package
The Static Status Report is uploaded when the device reconnects to RCMS after a reboot or when the RCMS App is restarted. It can also be uploaded when a user selects Update Data for the Full Status Report in RCMS. It is not a routine periodic report while the device remains connected. Package size is approximately 4.18 KB.
| Section | Fields included in the package |
|---|---|
| System | Device board, device model, device platform, firmware version, hardware version, kernel version, RAM usage, serial number, system time, uptime |
| Active link | Active link |
| Cellular | Band, BER, Cell ID, current SIM, firmware version, ICCID, IMEI, IMSI, LAC, modem model, modem status, network type, operator, PCI, phone number, PLMN ID, registration (Reg), RSRP, SINR, TAC |
| LAN interface status | Interface, IP, IP address, MAC, MTU, netmask, RX bytes, RX packets, TX bytes, TX packets |
| LAN | IP address, MAC |
| Route 1 | Destination, gateway, interface, metric, netmask |
| Dynamic status | CPU |
| GPS | Description |
| Wi-Fi status array | Mode, region, enable, band, bandwidth, channel, SSID, broadcast SSID, status, MAC address, security mode |
| Wi-Fi access point (WIFI_AP) | Client name, client MAC address, client IP address |
The report is event-triggered, so it does not recur every hour in the ideal always-connected scenario. Reconnects or manual requests can generate additional reports and increase usage.
Dynamic Package
The Dynamic Package contains changing connection, cellular, and interface information. Approximate package size: 1.63 KB.
| Section | Fields included in the package |
|---|---|
| SIM / cellular | SIM, TX bytes, RX bytes, CSQ, delay time, ARFCN, bit error rate, SINR, ECIO, RSRQ, RSRP, dBm, active link, link uptime, IP address, band, network type, registration (Reg), PLMN ID, Cell ID, local area code |
| WAN | TX bytes, RX bytes, delay time |
Default intervals: Data collection every 60 minutes and data upload every 60 minutes. These settings are configured in Remote Actions > Data Management. The monthly profiles use the collection intervals shown above and a 60-minute upload interval.
GPS Package
The GPS Package contains longitude and latitude. Approximate package size: 174 bytes; default upload interval: 60 minutes.
| Section | Fields included in the package |
|---|---|
| GPS | Longitude, latitude |
The original monthly usage note explicitly lists Dynamic, Keepalive, and Battery packages as included in the estimate; it does not specify whether GPS traffic is included. Confirm the intended GPS reporting configuration and estimate scope before applying the totals to a deployment with GPS reporting enabled.
Keepalive Package
The Keepalive Package contains a ping package associated with the RCMS connection. It is sent at the configured keepalive interval. Default interval: 600 seconds (10 minutes); approximate package size: 350 bytes. Shorter keepalive intervals send more packages and increase monthly usage. The keepalive value is set in Remote Actions > Data Management.
| Section | Fields included in the package |
|---|---|
| Ping | Ping package |
Battery Package
The Battery Package reports battery and power information. Approximate package size: 630 bytes.
| Section | Fields included in the package |
|---|---|
| Battery | Serial number (SN), time, supply type, battery capacity percent, voltage, battery status, battery Room 1, battery Room 2, dip switch |
Default intervals: Data collection and upload every 60 minutes. These settings are configured in Remote Actions > Data Management. The monthly profile estimates include Battery Package traffic.
Call Package
Call status and call record packages are uploaded in connection with telephone activity. The approximate total for one call operation is 2.43 KB.
| Package section / event | Fields or trigger | Approximate size |
|---|---|---|
| Call Status | Serial number (SN), time, status, call mode, phone number | — |
| Call Record | Serial number (SN), time, begin time, end time, phone number, call mode, call status, error | — |
| Handset picked up | “Off-hook” status packet uploaded | 475 bytes |
| Call in progress | “In-Call” status packet uploaded | 490 bytes |
| Call ends | Call Record packet uploaded | 582 bytes |
| Other party hangs up while handset remains off-hook | “Off-hook” status packet uploaded | 475 bytes |
| Handset returned to idle | “Idle” status packet uploaded | 475 bytes |
| RCMS App re-enabled or device reconnects after reboot | Call Status package may be uploaded | 475 bytes |
Call traffic depends on telephone activity. The monthly profile figures do not specify a call volume assumption; estimate call usage separately based on expected activity.
How to interpret the estimates
- A shorter keepalive interval sends keepalive packages more often.
- A shorter Dynamic Package collection interval increases data collection activity. The upload interval determines when data is sent to RCMS.
- Static Status Reports are triggered by reconnection or a manual request; they are not routine hourly reports while the device remains connected.
- GPS uploads use their own interval. Confirm whether GPS reporting is enabled when estimating a deployment’s usage.
- EV8100 call traffic depends on call activity. The monthly profile does not specify a call volume assumption.
- Actual cellular usage may include traffic outside the RCMS packages described here.