CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
🌙☀️
Log inStart free
Home/Templates/Telecom

📶 Telecom · Database ERD

Telecom Customer Data Schema

A schema for subscriber data: customers, accounts, subscriptions (numbers), plans, SIMs and bills.

More Telecom templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • One customer can have several accounts and numbers
  • Each subscription links a number, a SIM and a plan
  • Bills are generated per account

Prompt used

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.

Mermaid code
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
  }

Inside this diagram

An entity relationship diagram with 7 tables, 18 columns and 6 relationships.

Tables and their columns

  • CUSTOMER: id (PK), name, kyc_status
  • ACCOUNT: id (PK), customer_id (FK), type
  • SUBSCRIPTION: id (PK), account_id (FK), msisdn, plan_id (FK), status
  • SIM: iccid (PK), subscription_id (FK), imsi
  • PLAN: id (PK), name, price, data_gb
  • BILL
  • BILL_LINE

Relationships

  • CUSTOMER owns ACCOUNT: each CUSTOMER has zero or more ACCOUNT, each ACCOUNT belongs to exactly one CUSTOMER
  • ACCOUNT has SUBSCRIPTION: each ACCOUNT has zero or more SUBSCRIPTION, each SUBSCRIPTION belongs to exactly one ACCOUNT
  • SUBSCRIPTION uses SIM: each SUBSCRIPTION has exactly one SIM, each SIM belongs to exactly one SUBSCRIPTION
  • PLAN subscribed to SUBSCRIPTION: each PLAN has zero or more SUBSCRIPTION, each SUBSCRIPTION belongs to exactly one PLAN
  • ACCOUNT billed as BILL: each ACCOUNT has zero or more BILL, each BILL belongs to exactly one ACCOUNT
  • BILL contains BILL_LINE: each BILL has one or more BILL_LINE, each BILL_LINE belongs to exactly one BILL

Make your own diagram like this

Describe your own system in plain English and the AI ER diagram generator draws it in seconds, in the same style as this template.

Related templates

NetworkTelecom

5G Core Network Topology

A simplified 5G standalone network: phones and radio sites, the 5G core network functions, and the connection out to the internet.

State MachineTelecom

SIM Activation Lifecycle

The states a mobile SIM goes through, from stock in the warehouse to active service, suspension, porting out and deactivation.

C4 ArchitectureProTelecom

Telecom OSS/BSS Architecture

The IT stack of a mobile operator: business support systems (CRM, billing, orders) and operations support systems (inventory, provisioning, assurance).

SequenceTelecom

Mobile Number Portability

How a subscriber moves their number to another operator: porting code, request through the clearing house, donor approval and cutover.

SequenceTelecom

Prepaid Recharge Sequence

What happens when a customer recharges a prepaid mobile: plan selection, payment, balance update in the charging system and confirmation.

Data FlowTelecom

Telecom Billing and Rating Pipeline

How network usage becomes a customer bill: call detail records, mediation, rating against the plan, billing and invoicing.