Definition
Quota refers to the usage limit set for a data pool, individual SIM, or customer, used to control resource consumption and costs. In the International IoT Cloud Platform (ICMP), Quota supports quota alerts, Overage handling, Fair Usage Policy cost control, and is one of the core configurations for connection management and billing.
Working Principle
Quota can apply to different levels: SIM Quota—sets a monthly or lifetime traffic limit for each SIM; Pool Quota—sets a total limit for Pooled Data or Shared Bucket; Customer Quota—sets a total usage limit for all devices under a customer. The platform accumulates usage based on CDR or real-time usage. When usage approaches or reaches the Quota, it can trigger alerts, Overage billing, or Suspension. Quota can work with Usage Aggregation, supporting daily, weekly, or monthly resets to meet different billing cycle requirements.
Use Cases
Typical scenarios include: Cost Control — Enterprises set quotas for fleets or production lines to prevent abnormal usage from causing a billing surge; Data Plan Management — Data plans purchased according to Tiered Pricing or Volume Discount correspond to a fixed quota, and once exhausted, are handled according to Overage or upgrade; Fair Usage — Fair Usage Policy uses quotas to limit the usage of a single SIM or customer, preventing abuse from affecting overall service quality; Trial and POC — Small quotas are set for test SIMs, and formal limits are opened after verification.
Practice in ICMP
SimtoLink ICMP supports multi-level quota configuration: customers can set quotas for data pools, device groups, or individual SIMs in the Global Dashboard, configure alert thresholds (e.g., 80%, 100%), and excess usage policies (continue using charged as Overage or trigger Suspension). The platform aggregates usage in real time, displays quota usage via Usage Analytics, and supports Event Subscription to push quota alerts. Combined with RESTful API and SDK, customer systems can actively query quota status to achieve automated usage management.
Counting Level and Reset Cycle
A quota is a counting ceiling with a level and a cycle. It must say what kind of usage is counted, whether the count sits on a single SIM, a shared pool, or the customer’s total account, when it starts, and when it returns to zero. A warning threshold, a hard ceiling, and the action after the ceiling are three different parameters. A warning only notifies. The hard ceiling is what triggers overage pricing, throttle, or suspension. The counting measure must also use the same unit as the rate card. If the tariff accumulates billed CDRs while the quota accumulates bytes the device reports on its own, the two diverge on late records and on rounding.
Configure a quota only when it is already known whether the business is constraining abnormal consumption on one device or the total budget of a group of devices. When only the total budget is constrained, still decide whether one SIM may exhaust the total before the others have used their share. The cycle should line up with the billing cycle. Otherwise a quota that resets on the calendar month will not match a cross-border bill issued on the billing month. Whether late usage counts into the old cycle or the new one must be fixed in the rule. A change to a shared-pool quota should not reach back into usage that has already occurred. It takes effect only on counts after the change, so historical reports are not rewritten.
Treating a Warning Line as a Suspension
A common error is to read a warning at some percent as service already stopped. When the notice goes out, the device is still transmitting. If operations then tell the customer “it is already suspended,” the two sides see different states. Another error is a per-SIM quota and a pool quota that exist together with no written order of which runs first. The SIM’s own allowance remains, the pool is already exhausted, the device is stopped, and the screen still shows this SIM with “a lot remaining.”
If the reset runs at each customer’s local midnight while usage is cut into days by the platform time zone, a device that crosses time zones is counted into the wrong cycle around the reset. A quota change should also keep the old value, the new value, the effective time, and the operator. Without that record, there is no way to explain why the same SIM’s available amount this month does not match last month’s contract. A quota is a counting rule. It is not a static picture of remaining data.
When the allowance changes in the middle of a cycle, write down how usage already incurred is treated. A common practice is to keep the old allowance until the cycle ends, and start the new allowance next cycle. If it must take effect immediately, recompute the remaining amount as the new allowance minus usage already incurred this cycle. The usage already incurred is not rewritten. Zeroing the counter to “make the new allowance effective” makes this cycle’s consumption disappear, and the invoice and the quota no longer match. When the allowance is lowered, if usage already incurred exceeds the new allowance, apply the overage rule at once. Do not wait for the reset day.
When a shared allowance and a per-SIM allowance exist together, judge the SIM first and then the pool, or the reverse order if that is what was written down, but there can be only one order. The screen shows two remainders at once: how much this SIM still has, and how much the whole pool still has. Showing one “remaining” leaves the user unable to understand why the SIM still has a number while service is already limited. A new SIM starts consuming the shared allowance from the moment it joins the pool. After it leaves the pool it no longer consumes, and usage from before it left stays in the pool’s total for this cycle.
Test the reset time together with the billing time. Produce a stretch of usage just before the reset and a stretch just after, and confirm the earlier stretch enters the old cycle and the later stretch enters the new one, and that late usage from the old cycle does not deduct the new cycle’s remainder early. A customer who crosses time zones should declare the time zone the reset uses. Test SIMs use their own small allowance. When it is exhausted, the formal pool is not affected. The quota record keeps the old value, the new value, the effective time, and the operator, so it is possible to explain why the available amount changed during the same month.
Beside a quota figure, also write the counting cycle and the level. Without those two notes, a remaining amount cannot say whether it is what this SIM has left this month, or what the whole shared pool has left for the whole contract. Support should read those two items before telling a customer whether transmission can continue.