Definition
Resume opens the network again on an IoT SIM that was suspended. A nonpayment suspension waits for the payment. An exhausted-data suspension waits for a renewal or a new plan. A successful payment can start resume on its own, together with plan provisioning and the payment callback.
How resume is started
- Automatic: The user pays or renews with WeChat Pay or Alipay. The channel sends a payment callback. After the check, the platform provisions the plan and resumes the SIM. Nobody has to click it.
- By hand: An enterprise administrator or an agent resumes a named SIM in the console. This fits a prepaid top-up or an offline settlement.
- In a batch: Many SIMs are filtered and resumed together, so operations is not clicking one row at a time.
Resume sits after the plan is written
Resume usually follows a plan order and plan provisioning. The user orders and pays. The platform writes the allowance onto the SIM first, then resumes, so the SIM comes back onto a plan it can actually use. If resume fails, the job has to retry and a person has to be able to take it. Suspend and resume is the paired entry.
Payment, provisioning, and the command to the operator
Resume, the payment callback, and plan provisioning are one loop. After the user pays, provisioning and resume both have to finish, or the payment does not restore service. A failure retries, can be taken by a person, and should tell the user. A batch has to deliver the command to the operator. A success can send an SMS or an in-app message. With suspension, this pair is how an IoT SIM is cut off and brought back.
What the operator must confirm first
The resume command leaves the IoT Cloud Platform and is executed by the operator. Only then does the SIM attach again. The platform has to show resume status and retry a failure. A nonpayment resume checks that the money has arrived. An exhausted-data resume checks that the new plan has been provisioned. Resume is the second half of suspend and resume, and it matches the in-service state on the card lifecycle. An enterprise can start it from user self-service or the agent self-service portal. A consumer who has paid is usually resumed automatically.
Pay, then the SIM opens
With the payment callback and plan provisioning, resume is the “payment opens the SIM” loop. After WeChat Pay or Alipay, the platform provisions the plan and resumes. A failure retries, can be handled by a person, and should notify the user. Together with suspension, this is the core of IoT SIM state control. The command still has to reach the operator. A local “resumed” flag is not enough.
The module still looks offline after resume succeeds: which layer to check
Resume splits into three layers: the platform accepts it, the operator carries it out, and the device attaches again. Missing any layer means the user has not actually got data back. Payment arriving only satisfies the precondition of the first layer. A nonpayment suspension first confirms that the payment order is booked and that the amount covers what is owed. An exhausted-data suspension first confirms that the new plan’s provisioning receipt succeeded. Only then is the resume command sent to the operator. A successful command return only means the operator accepted the request to open data. If the module has cached an old reject reason, or the base-station policy has not refreshed, the device stays offline. Do not charge again. Look at the attach result and the last reject code. SimtoLink suspend and resume should keep “command succeeded” and “an attach has been observed” as two statuses, so support can see, by SIM number, which layer the SIM stopped on.
Which suspensions may open automatically, and which need a person
Automatic resume applies only when the reason code is explicit and the condition that lifts it has already been met. Clearing a nonpayment balance, or renewing exhausted data, can send the command automatically. A violation suspension, a manual freeze, or a SIM reported lost stays pending approval even if the user pays for another plan. The plan can be booked first and not provisioned, or it can be provisioned while the SIM stays cut off. Only one of those two may be chosen, and it has to be written into the product rule. A bulk resume filters by reason code. It cannot select every SIM whose current status is suspended. If the same SIM is resumed repeatedly in a short time, the request id makes the call idempotent, so the operator side does not open several work orders that overwrite each other. If, inside the resume window, the SIM is already normal on the operator side while the platform still shows suspended, align the status instead of sending open again. Some interfaces report an error on a repeated open and mark the platform attempt as failed.
From which second the resume moment and the plan cycle are counted
The plan write succeeding and the resume succeeding can be minutes apart. If the cycle starts at successful payment, the SIM consumes days before it is opened. If it starts at the resume receipt, the gap between payment and first use is not counted in the cycle. Once the rule is chosen, the cycle start and end on the bill have to use that same moment. The page cannot show the payment time while billing uses the receipt time. A receipt that crosses midnight also moves a monthly rent that is counted by calendar day. If resume fails and enters a manual queue, the cycle should not start, or the user sees service still down while the days run. A cancelled SIM that receives a resume request should fail outright and go to refund. After an international or roaming SIM is resumed, the network it attaches to may not be the home operator. The home-side status is still the authority. Do not resume again just because a query in the visited network still shows suspended. When the visited status is delayed, use the home operator’s receipt, and say on the page whether the query is the home side or the visited side, so support does not keep clicking open on the same SIM.