Service Lifecycle Actions – Suspend / Resume
Service Lifecycle Actions – Suspend / Resume
Product: i2i Core OSS/BSS
Company: i2i Tech Services Private Limited
Purpose
Suspension and resumption are controlled lifecycle actions used to enforce policy (non-payment, misuse, temporary hold) without full termination. These actions must be consistent across customer/account/service/subscriber states.
When to Suspend
- Billing/collection policy trigger (as approved)
- Security/abuse policy trigger (as approved)
- Customer-requested temporary hold (if supported)
When NOT to Suspend
- When service must be permanently disconnected (use termination workflow)
- When entity ownership is unclear (verify customer/account first)
Operational Workflow
- Open the service → verify current status and active subscriber identity.
- Trigger Suspend → confirm reason code/notes (if required).
- Validate downstream: AAA should deny/limit session as per policy.
- For Resume: confirm approvals/collection closure → resume → validate sessions.
Validation
- Confirm the correct service and subscriber mapping before action.
- Confirm the expected downstream enforcement behavior (AAA state).
- Record action reason for audit trail.
Troubleshooting
- Service suspended but user still online → verify AAA session handling and session termination policy.
- Service resumed but cannot authenticate → verify subscriber status and mapping.
Screenshots
Screenshots not yet added.