Definition
A data pool pools the data of many IoT SIM cards so they share it. The total in the pool is available to those cards. When one card’s own allowance is gone, it can keep using the pool. That fits projects whose usage swings and whose cards work together. Traffic billing charges the pool total, then allocates that charge to each card or project by a rule.
Billing Methods
- Even distribution: The data is evenly allocated among the cards in the pool, simple and fair, suitable for scenarios with similar usage.
- Actual usage: Each card is billed according to its actual consumption, with cards that use more shouldering more cost, more precise.
- Weighted distribution: Pre-set weight allocation, for example, one card has weight 2, others weight 1, suitable for main card + secondary card scenarios.
Applicable scenarios
A data pool fits a project where many cards swing in usage and one card’s usage is hard to forecast, such as a fleet, a cluster of shared devices, or monitoring across many sites. The pool total can be drawn on as needed, so one card does not suspend while the others sit idle. The platform needs pool creation, cards joining and leaving, a usage query inside the pool, and allocation rules for traffic billing. Unlike a single-card data plan, the pool is billed as a pool and then allocated. See billing mode.
Data pool and carriers
A data pool needs support from the carrier. Carriers differ in how they bill a pool and in which APIs they offer. Through carrier mapping, the pool plan is matched to the product on the carrier side. Usage inside the pool comes from the carrier or from the platform’s own usage collector, and it feeds traffic billing and carrier reconciliation. When the pool total is used up, cards in the pool may suspend together, so the pool has to be renewed or enlarged in time. Running the pool is a main part of operating IoT SIM cards in bulk.
Data pool and data plan
A pool plan is set up through plan packaging. Unlike a single-card data plan, the pool is billed as a pool. Cards join through plan subscription. After plan delivery, the pool holds the total allowance. A card that has used up its own share can keep drawing on the pool. When the pool total is gone, the pool has to be renewed or enlarged. Billing follows the billing mode: an even share, actual usage, or weight. A pool fits a fleet, shared devices, or many sites whose usage swings, and it sits beside the single-card plan rather than replacing it.
Data pool billing
Data-pool billing charges the enterprise for the pool’s total usage, then allocates that charge to each card by an even share, by actual usage, or by weight. When the pool total is used up, cards in the pool may suspend together. The pool itself needs carrier support. Through carrier mapping, the pool plan is matched to the product on the carrier side. Managing the pool is a main part of running IoT SIM cards in bulk, and it stays tied to traffic billing and carrier reconciliation.
From which moment joining or leaving the pool changes billing
A data pool is a billing container in which a group of cards jointly consume one total quota. The pool has an identifier, a total quota, a cycle, a member list, and an allocation method. A member joining or leaving has to carry the moment it takes effect. If a mid-month join consumes pool quota only from the join date, usage before the join is still a personal plan or test traffic. If it is traced back to the first day of this cycle, usage already billed on the personal plan has to be reversed. Without an effective moment, the same card appears once on the personal bill and once on the pool bill.
Leaving the pool cannot be only a deletion from the list either. Usage after the moment of deletion leaves the pool. Usage before the deletion stays in this cycle’s pool allocation. Whether a suspended card still occupies a member slot affects the denominator of an even split. If a suspended card still occupies a slot, the other cards are charged less. If suspension removes the card, the denominator shrinks and the share of cards still online rises. Both are reasonable, but one of them must be fixed, and it must be visible in the member-change record.
Do not change the allocation method in the middle of a cycle
An even split suits a project whose members use similar amounts and whose management cost has to stay low. Allocation by actual usage suits a fleet or a set of sites whose usage differs a lot: each card’s usage comes first, then the pool charge is multiplied by that card’s share of usage. Allocation by weight suits a case where the primary card bears more. The weight comes from a member attribute, not from a figure typed onto the bill at the last minute. One pool uses one method inside one cycle. Changing from an even split to usage-based allocation in the middle of the month makes the historical days and the remaining days impossible to line up. The change should take effect in the next cycle.
When the pool total is used up, the response applies to the member set, not only to “the card that produced traffic last.” Otherwise the card that ran traffic first exhausts the pool, and a card that comes online later has no usage and is still suspended, or the reverse. SimtoLink’s data pool manages the member effective time and the allocation method. Billing reads only members that have already taken effect, so a list change is not traced back into a period that is already closed.
The pool cycle and a personal plan cycle may not line up
A data pool may settle on the calendar month, while a member’s original personal monthly pack rolls from the activation date. If the personal cycle keeps running after the card joins the pool, usage on the same day has to be decided as entering the pool or entering the personal pack. The rule should say that, from the moment the join takes effect, the personal plan is paused, deferred, or voided. If it is paused, the remaining quota is frozen and restored for the remaining days after the card leaves the pool. If it is voided, say whether the unused fee is refunded. If neither is written, billing deducts both the pool quota and the personal quota for the same session. SimtoLink’s data pool stores, on the member’s effective record, how the personal plan is handled. At billing, only usage after that moment enters the pool.