Use case · Network & Provisioning
Service Suspension on Network
Subscriber's service suspended on network due to non-payment or request.
Order MgmtProvisioningCollection
Provisioning systemPrimary actor
Network & ProvisioningCategory
3Modules involved
At a glance
TriggerSuspension order (debt or request)
Primary actorProvisioning system
OutcomeService restricted on the network
Main flow
The usual path from start to finish.
- 1
- 2
Bar outgoing or all services as required - 3
- 4
- 5
Exceptions & alternate flows
Barring failsEscalate to avoid unbilled usage
Systems & modules involved
Order MgmtProvisioningCollection
Business rules
- Every step confirmed or rolled back
- Charging set up before service use
- Emergency access always kept
KPIs to watch
- Provisioning success rate
- Activation time
- Fallout rate
Standards & references
TMF640Service Activation
TMF641Service Ordering
3GPPNetwork subscriber data
This page describes generic industry practice and public standards. It is not based on, and does not describe, any particular vendor's product or operator's systems.