BryanNetTime-based versus usage-based plans
Prerequisites and authority
Use the official organization interface. Customer procedures need account ownership; provider configuration and manual grants need authorized operator access.
Compare time and usage plans
| Rule | Time plan | Usage plan |
|---|---|---|
| Access boundary | Validity end | Quota exhaustion or validity end |
| Data allowance | Only where the product explicitly defines one | Specified quota |
| Speed | Plan's configured rate | Plan's configured rate |
| Simultaneous devices | Plan concurrency | Plan concurrency |
| Queued ordinary purchase | Duration starts at activation | Validity starts at activation |
A usage plan is not unlimited time until the quota is consumed. Its time boundary remains important even when data remains. Likewise, a time plan's speed limit is not a promise of upstream performance.
Example: an illustrative usage offer has a 10 GB allowance and seven-day validity. If the customer consumes the allowance on day two, that entitlement ends then. If data remains on day seven, validity still ends. The exact displayed GB convention and decimal support must match the release; do not substitute an undocumented byte conversion.
Current-subscription usage should combine eligible traffic across devices and routers without counting earlier subscriptions again. Display delays can occur when live sampling or reconciliation is interrupted; use Usage or device/session accounting looks wrong for unexpected totals.
Before purchase, compare price, validity, quota and concurrency together. An administrator assigning explicit dates must communicate that grant's actual expiry rather than borrowing the duration-based queue description.
Related guides
Related guides: Purchase a plan and understand activation, Credentials, devices and concurrent logins, Telegram customer onboarding and commands, Website registration account linking and recovery, Payment succeeded but internet did not activate.