
📶 Telecom · Database ERD
A schema for subscriber data: customers, accounts, subscriptions (numbers), plans, SIMs and bills.
Drawing diagram…
ERD for telecom customer data: Customer has Accounts (prepaid or postpaid); Account has Subscriptions, each with an MSISDN, a Sim (ICCID) and a Plan; Plan belongs to the product catalog with price and allowances; Bill is generated per Account per cycle with BillLines.
erDiagram
CUSTOMER ||--o{ ACCOUNT : owns
ACCOUNT ||--o{ SUBSCRIPTION : has
SUBSCRIPTION ||--|| SIM : uses
PLAN ||--o{ SUBSCRIPTION : "subscribed to"
ACCOUNT ||--o{ BILL : "billed as"
BILL ||--|{ BILL_LINE : contains
CUSTOMER {
int id PK
string name
string kyc_status
}
ACCOUNT {
int id PK
int customer_id FK
string type
}
SUBSCRIPTION {
int id PK
int account_id FK
string msisdn
int plan_id FK
string status
}
SIM {
string iccid PK
int subscription_id FK
string imsi
}
PLAN {
int id PK
string name
decimal price
int data_gb
}A simplified 5G standalone network: phones and radio sites, the 5G core network functions, and the connection out to the internet.
The states a mobile SIM goes through, from stock in the warehouse to active service, suspension, porting out and deactivation.
The IT stack of a mobile operator: business support systems (CRM, billing, orders) and operations support systems (inventory, provisioning, assurance).
How a subscriber moves their number to another operator: porting code, request through the clearing house, donor approval and cutover.
What happens when a customer recharges a prepaid mobile: plan selection, payment, balance update in the charging system and confirmation.
How network usage becomes a customer bill: call detail records, mediation, rating against the plan, billing and invoicing.