Definition
An operator is a communications company that provides cellular service. In China the three are China Mobile, China Unicom, and China Telecom. An IoT SIM is issued by an operator. The IoT Cloud Platform has to connect to that operator’s system for operator reconciliation, operator mapping, and data sync.
The three operators
- China Mobile: Wide coverage and the largest IoT SIM base. Connections such as OneLink are mature.
- China Unicom: Flexible tariffs and an advantage in international roaming. Platforms such as Jasper are widely used.
- China Telecom: CDMA and LTE, a large government and enterprise base, and a growing IoT business.
What the platform has to connect
The IoT Cloud Platform connects to the operator system to sync SIM information, provision plans, look up usage, and run operator reconciliation. Operator mapping ties a house plan to the operator tariff so plan packaging and data billing stay accurate. Several operators are managed together, and a command is routed by the operator that owns the SIM.
How the API is reached
An operator usually offers a B2B platform or an API, such as China Mobile OneLink, China Unicom Jasper, or the China Telecom IoT platform. The calls cover card information query by ICCID or MSISDN, plan subscription and provisioning, usage lookup, suspend and resume, and usage detail. The enterprise signs a commercial agreement and receives an account and a key. The API specifications differ, so the platform wraps them in one adaptation layer. Stability and delay show up directly in plan provisioning and card information query.
Operators and billing
The operator supplies SIM procurement, data plan tariffs, and usage. The platform maps its own plans to those tariffs through operator mapping. Usage feeds data billing and operator reconciliation. With more than one operator, commands are routed by the operator on the SIM so plan packaging and plan provisioning stay correct. The operator is the source of the IoT SIM network and the tariff. The core of the IoT Cloud Platform depends on that connection.
The three operators, in short
China Mobile has wide coverage and the largest IoT SIM stock. China Unicom has flexible tariffs and an international-roaming advantage. China Telecom has many government and enterprise customers. They usually offer a B2B platform or an API, such as Mobile OneLink or Unicom Jasper. The calls include card information query, plan subscription and provisioning, usage lookup, and suspend and resume. The enterprise signs a commercial agreement and receives an account and a key. How stable that connection is shows up in plan provisioning and card information query.
Which carrier owns this SIM cannot be read from the number prefix alone
An operator is the carrier that provides cellular access for this IoT SIM and bills it on its own tariff. In domestic SIM business the usual names are China Mobile, China Unicom, and China Telecom. Coverage, account systems, and APIs differ across the three. Which operator a SIM belongs to is decided by the operator account and the number-range resource fixed at stock-in. It cannot be guessed from the first three digits the user sees. After resale or a second packaging, the brand on the card face may be the platform’s or the enterprise’s name. The network side is still one operator. Commands, mapping, and bills all go back to that operator. Sending them to another fails outright or disappears. SimtoLink’s operator API gateway picks the channel from the operator field on the SIM. A SIM whose field is empty cannot be subscribed. Complete the file before selling it.
The three APIs look alike, but the fields cannot be copied across
Each operator can query a SIM, write a plan, suspend and resume, and pull usage. Product codes, status enumerations, and usage units are defined separately. The platform can present one acceptance result outward, and it should keep the original return code inward, so troubleshooting can tell “SIM does not exist” from “tariff not authorized.” A test account that works at one operator does not mean the other two can use the same certificate. If international roaming or an overseas SIM is still resold by one domestic operator, the billing party may still be that operator, while coverage has to be read from the tariff plan on its own. A domestic plan’s data tier cannot be promised abroad. Choosing an operator also depends on device bands and coverage at the site. An API cannot make up for a site with no signal. When stock from several operators exists at once, the sales page should filter plans by the SIM’s operator, rather than let the user pick a tariff that SIM cannot be written with.
If the commercial account stops, where the technical path stops first
A SIM works only if there is coverage on site and the operator account signed with the enterprise can still be called. An account in arrears, an expired certificate, or an allowlist change shows up as commands failing across a wide area, not as one SIM suspended. Stop new subscriptions first, so money is not still collected when provisioning cannot run. Whether SIMs already in service have been suspended in bulk on the operator side follows the status that was synced. Do not first mark every SIM suspended on the platform and make the books disagree with the network. Changing operator, or moving a number range from one operator to another, is not a dropdown edit. The old SIM is cancelled, the new SIM is stocked in, and the device changes SIM or is rewritten. Mapping and unfinished orders both need a migration list. The party on reconciliation and on invoices is the operator that owns the signed account. That is not the same document as the retail invoice the platform issues to the user. Combining the three bills into one “communications cost” can be an internal report. Payment and appeals still split by account. A sub-customer or a project under an account is only attribution inside the platform. It is not another operator for which a separate API should be applied.