Definition
Operator integration is the IoT Cloud Platform opening an API to an operator — China Mobile, China Unicom, or China Telecom — for card activation, suspend and resume, plan provisioning, usage lookup, and operator reconciliation.
Core capabilities
- API connection: Each operator’s interface is wrapped in one API, and the platform routes the call to the operator that owns the SIM.
- Data sync: SIM status, usage, and plan information stay in step with the operator, down to the minute.
- Bulk commands: Opening a SIM, suspend and resume, and plan changes can be sent in bulk. A batch on the order of ten thousand does not block the queue.
- Security: Certificate authentication, an IP allowlist, and encrypted transport, as the operator requires.
What the connection covers
The connection covers the life of the SIM: card activation, plan provisioning, plan change, suspend and resume, card information query, usage statistics, and operator reconciliation. Through operator mapping, a house data plan is tied to the operator tariff plan. At provisioning, the call is routed to that operator’s API.
How this relates to operator mapping
Operator integration answers how to connect. Operator mapping answers which operator tariff plan matches the house plan. Once the connection is in place, the mapping keeps plan provisioning and operator reconciliation accurate. On a unified three-network connection, the platform picks the interface from the operator on the SIM.
What implementation requires
Connecting an enterprise to an operator takes a qualification review, a signed agreement, a certificate, and an IP allowlist. Field definitions differ, so the platform adapts them and exposes one API. After go-live, operator reconciliation is checked on a schedule so billing and usage still match.
Two ways to connect
There are two modes. Direct means the enterprise calls the operator API itself. Through a platform means the call goes through an IoT cloud platform such as SimtoLink. The platform path obtains three-network coverage in one connection, without a separate project for each operator, and it cuts access cost and operations work. The platform handles interface adaptation, retries, and reconciliation. The enterprise stays on its own business.
Failures and retries
An operator API can time out, hit a rate limit, or fail briefly. The platform needs retries, a circuit break with a fallback, and alerts so the business can continue. A failed card activation, plan provisioning, or suspend and resume is logged and can be retried by hand or automatically. A regular check against operator reconciliation finds data that has drifted, so it can be corrected.
On timeout or rate limit, has this command already taken effect
Operator integration is the platform sending activation, suspend and resume, plan writes, and usage queries to the matching operator API, then writing the result back onto its own SIM file. A request that has gone out with no receipt can only be “processing.” After a timeout, retry with the same business request id. If the operator has already succeeded, the retry should return the original result, not open the account again or write the plan again. On a rate limit, put the request back on the queue. Do not immediately mark it a business failure and have the user pay again. A circuit break only stops further hits on a failing API. It cannot close a SIM that is already processing as a finished failure. SimtoLink operator integration picks the channel from the operator that owns the SIM. Addresses, signatures, and fields for China Mobile, China Unicom, and China Telecom are adapted separately. Outward, the acceptance result stays one set: success, processing, or failure with a reason.
Which expiry stops every channel: certificate, allowlist, or callback
A connection that works depends on an account that is still valid, a certificate that has not expired, an egress address that is still on the operator allowlist, and a callback path that still points at the current environment. An expired certificate often shows up as every channel failing at once, not as bad data on one SIM. After the egress address changes, update the allowlist before the new address takes effect, or retries only multiply the failures. If the callback is blocked by a gateway, the platform stays in processing and needs an active order lookup to fill in the result. Lookup and callback must enter the same status update. A test-environment address cannot remain on the channel configuration of a production SIM. Keys are stored by operator account. Even when several tenants share a platform channel, logs must not print the full key. When an API field is added, adapt first and then upgrade the call. Before an old field is retired, confirm that no in-flight request is still using it.
Usage sync and command dispatch should not share one rate limit
Usage can wait a few minutes and still be aligned. A delay in suspension or in writing a plan makes the SIM unusable, or charges twice. On the queue, commands and usage queries should be separate, and usage jobs should yield first when the rate limit is hit. Late usage must not trigger a status that contradicts a command. If a resume command has already succeeded, and an older usage query still says suspended, the SIM must not be changed back. The sync watermark is recorded by operator and by account. After a failure, pull continues from the watermark. It does not reload the full month from the start every time. A full reload both trips the rate limit and can overwrite a new status with an old file. If reconciliation finds a day of usage missing, pull that day again, mark the catch-up batch, and recalculate the bill only for the SIMs that day touches. The three operators cut the bill day differently. The day boundary of the sync job stays the same as the reconciliation day boundary. Do not use midnight in one place and 08:00 in another. On the day a channel is switched or a certificate is replaced, a command that is still processing stays on the original channel until the receipt. Do not resend it mid-way with the new certificate and open the service twice.